[DONE] FPS override to 36fps

[kaco]

Hi!

Is there any fundamental reason why FPS override settings is disabled to the value of 36? (When you scroll on FPS override it jumps from 35 to 37)

Having 36fps would mean better workflow for documents - 150 % for slowmo, blending every third frame for real speed. Realtime playing back 35/37fps footage in 24fps sequence brings much more problems.

Thank you,

[a1ex]

... it got lost near a line break and nobody noticed (back in 2014).

[kaco]

... it got lost near a line break and nobody noticed (back in 2014).

Wow, sounds promising. I have created ticket request, unfortunately that is the only thing I know (and shooting in ml_raw)
https://bitbucket.org/hudson/magic-lantern/issues/2835/fps-override-to-36fps

[a1ex]

Done (crop_rec_4k build).

[domasa]

When I have:
FPS override: 36.0 (Optimized for Exact FPS)
Crop mode: 1920 1:1

maximum shutter is +-1/310... why?

FPS 30 - max +-1/4000
FPS 31 - max +-1/1100
FPS 32 - max +-1/960
FPS 33 - max +-1/390
FPS 34 - max +-1/410
FPS 35 - max +-1/280
FPS 36 - max +-1/310
FPS 37 - max +-1/220
FPS 38 - max +-1/210
FPS 38 - max +-1/200
FPS 39 - max +-1/180
FPS 40 - max +-1/160

magiclantern-crop_rec_4k.2018Mar10.5D3113

[kaco]

Done (crop_rec_4k build).

Hi a1ex, could we have this also in raw_video_10bit_12bit_LVState branch? I find 36fps much more useful for 10bit and I still use this over crop_rec.

Thank you!