If the cam is in LV when ML menus are entered, CPU usage is considerably higher than if not. This cost appears to be due to normal Canon processes, not ML.
If we could find a way to reduce LV cost it would save some battery. I know we can change Canon menu when we enter ML menu, in order to stop keypresses getting passed through. I don't recall what we do in LV.
This only feels useful if we can reduce LV cost without fully dropping out of LV. Most people wouldn't want the mirror flip every time, and anyone that does want that tradeoff can manually trigger it anyway.
Observed on 5D2 and 70D.
If the cam is in LV when ML menus are entered, CPU usage is considerably higher than if not. This cost appears to be due to normal Canon processes, not ML.
If we could find a way to reduce LV cost it would save some battery. I know we can change Canon menu when we enter ML menu, in order to stop keypresses getting passed through. I don't recall what we do in LV.
This only feels useful if we can reduce LV cost without fully dropping out of LV. Most people wouldn't want the mirror flip every time, and anyone that does want that tradeoff can manually trigger it anyway.
Observed on 5D2 and 70D.