Messages

Ok, thanks a lot 1% for the explaining!

Ok, if FPS override is on 1fps, than the LV will refresh once every second, so the longest exposure is 1 second - am I right so far? The smallest fps I can get is 0.15 (but only in 'High Jello'-mode, what is that and what effect does it have?). With 0.15 fps a maximum exposure time of 6 seconds should be possible.
So a exposure time longer than 6 seconds (for example 20 seconds) is generally not possible with silent pictures?!
Why? Is a fps of 0.15 the lowest fps you can get by the hardware or because the developer thought a lower fps would be impractical or could damage the sensor?

Sorry, my English is not the best and I am not sure if I understood you right. Do you have an solution for a 'silent long exposure'? What does the mode change cause?
@ a developer: Is this limitation (no long LV exposure) a hardware limitation or is it gernerally possible to extend the limits in a future release?

Thank you for that hint, but it is still pity that you can not expose longer than 1 sec...

Oh yes, I forget to mention that, any other hints for "silent" day to night timelapses?

For '4k' (3840 x 2160) you would exactly need 4 crops.
Is there already a automated version for this (and if yes, where can I find it in ML)?

Dear Alex,
thanks for clarifying that, I thought, because the expo simulation changes after changing in the Canon menu and ML is also showing 3"2 in the overlay, that this would maybe have an effect...
I thought maybe ML would mathematically add a following frame to the first frame (1/30+1/30) which would realise a theoretical 1/15th exposure and so on.
Is this the way its done if I enable FPS override? Does FPS override give the LiveView really a longer exposure time on the sensor and thus more light and allowing to use a lower Iso (or is it just mathematically "faking" a longer exposure)?
Is this (FPS override) the best option for long exposure night timelapses with silent image?
Thanks so much for your effort!

BTW. I am really using it since 2 years, but until now just the basic functions like focus points or zebra.

First of all, because this is my first posted topic, a 'Hello' to the community, I use ML since almost 2 years now. After my 600D / T3i crashed I upgraded to the 5D Mark III and I am now using ML (nightly built 20. Oct) since one week on it.

I am shooting a lot of timelapses and so I am very happy about the "silent picture" mode. Today I realised, that (the same in every mode) I can't expose longer than 1/24 second, which is far shorter than the Canon standard with 30 seconds. So I need to go back from LiveView to the canon menu to change the exposure from e.g. 2" to 3,2" and then go back to LiveView.
Is there another option, is it a bug or am I doing something wrong?

The second thing I realised is that the aperture is not simulated in the LiveView. I know that I can set the aperture in the Expo-Tab, but is there any option, that the aperture is automatically set (like shutter priority) in LiveView?

Thanks for your answers and thanks to the developers for this great pice of software

Is there any possibility for example changing crop position (I know this would be no solution for moving objects) in LiveView ? Like the old "High Res"-silent pictures?

I tested the AETTR features today and just can say wow ! But still I have one question:
AETTR changes the ISO and the Shuttertime, but it does NOT change the aperture - Am I right so far ?
I tried it to combine it with the TV Mode to get also a aperture ramping, but this gave me a flickering (One time the completly opened aperture like bevor in Manual Mode, then the correct aperture from the TV Mode and so on...) with an intervall of about 1 second  . I made the timelapse in silent mode (Raw DNG, NO dual iso) on a 5D3.
So which is the best method to controll all 3 - the aperture, the shuttertime and the ISO - only with AETTR in M Mode (or are their better solutions to do this)?
Thanks for your answers

I need to prepare a special FIR. Short answer: call("DisableBootDisk")

but you really have to double-check that you are not in LiveView (and people managed to go there during first install despite all my double-checks).

I have read various posts in this forum and I want to summarise the current point of developing. Am I right that...
- there is a way to disable the bootflag, but this way needs a lot of safety checks (like M-Mode & no LiveView) and if you fail the checks your camera is broken (forever)
- the developer team (especially Alex) are looking for a .fir file which does this checks automatically and minimize the danger of getting a broken camera

I know that you develop ML in your spare time and you deserve our greatest respect, but can you already say how long it will take for a first version of this "disable-fir" or any other methode to disable it? 1 week, 1 month, or longer than a year?

I buyed a 5D 3 and the answers will strongly influence my decision whether I should install the "rawmode" or not.

Thanks for answering my questions!