Messages

In all modes, when using FPS override: Is FPS override a 'true' frames per second? If I set it to "24.00fps, Exact FPS" is the camera actually recording a proper 24.00 even frames in a second? Or is it interpolated/faked? IE: If I set FPS Override to "24.00," is the camera really recording a 29.976fps and dropping frames from 29.976fps resulting in 24.00fps?

It was my understanding that MLV2.0 was the current/supported raw module?

Also when recording raw, picture styles don't affect the mlv raw data right? I can crank up sharpness without it affecting mlv raw?

Also, when using zebras, is it referencing RAW sensor data? Or is it referencing the current picture style?

And if you use canon "24p" its 23.976 and crop mode will be recorded at 29.976.

Is "29.976" mentioned above a typo? If your set to canon's 24p (23.976,) and when using crop mode, you get NTSC 30p instead?

Or it's a typo?

And if you use canon "24p" its 23.976 and crop mode will be recorded at 29.976.

I'm a little confused. If you use Canon "24p" you get NTSC 30fps?

When you say "crop mode," is that the "crop_rec" experimental build?

Thanks for the response! I like to shoot a flat 24fps because I want to follow proper film standards and because I also create my own music and can cut perfectly to 72bpm, 96bpm, 120bpm.

In some examples, I've seen 10bit get quite noisy in the shadows and thus results in lost dynamic range. Have you had good results with 10bit?

On the 5DMKIII, ssing the experimental 10/12-bit RAW video: "magiclantern-raw_video_10bit_12bit.2019Mar24.5D3123" build.

I can get 1920x1280 (3:2) 12bit continuous RAW/.MLV with sound

That said, on my 5DmkIII, it's getting the full width of the sensor (I believe? Yes?).

Is it pixel binning/skipping to get the full width? Or is it super sampling the whole sensor?

Also, with the "mlv_snd" module, do I still get sound if I'm doing a FPS override at an even 24.00fps? (FPS override says that it disables sound.)

Thanks all!