Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Kuky

Pages: [1] 2
The sticky to end all stickies. Read this first.

Composition FPS?

baldand seems to think the problem is with the header.  IIRC, the correct FPS tag doesn't get written to files when using FPS override.  Until that is fixed, consider the quoted Q&A as correct, even though the wording doesn't exactly describe this problem.

edit:  Added a new Q&A.  Thanks for the heads up.

Yeah, thanks for googling it for me, but as I mentioned before it has nothing to do with the metadata tag. In fact it's just a workaround and the Q&A is relevant if the DOP and the editor are the same person. If not, my experience tells me, being a post supervisor since 1997, that many of the editors will ingest the footage, growling "garbage in, garbage out". Of course there are also editors who will take the initiative and make a phone call or will try to guess the correct fps.

yet i didnt see what i always ask for in this case.
the output of "mlv_dump -v" for the whole file or the first blocks at least.

Make sure you change your composition FPS. This is covered in the thread started by audionut about questions that are redundant. Also double posting. :-)

Composition FPS? What composition FPS? What thread? Search does not reveal any relevant results.

BTW, AE composition settings (maybe this is what you're talking about) has nothing to do with the fact that mlv has incorrect fps metadata when shooting crop mode. Of course you can interpret footage any way you like.

Yeah, I wasn't sure, that's why I shot a timer  :)
But counting the frames it appears to respect FPS override


If you shoot crop mode (x5 zoom) with a 5D Mark III and use FPS override (for example 24 exact FPS) MlRawViewer will report 29,776 fps. Maybe it's a metadata mistake.

I verified shooting a timer watch in crop mode. It's actually using the override setting. Here is an actual file (2,2 Gb):

Posted also in MlRawViewer thread.


If you shoot crop mode (x5 zoom) with a 5D Mark III and use FPS override (for example 24 exact FPS) MlRawViewer will report 29,776 fps. Maybe it's a metadata mistake.

I verified shooting a timer watch in crop mode. It's actually using the override setting. Here is an actual file (2,2 Gb):

When trying to convert spanned raw files to video this error keeps poping out: "No video sequence folder found"


Codec is 10 bit so I guess I'm losing color now converting? I've yet to find an intermediate that is better in terms of file size and quality so I live with the bugs. :(

Nope, cineform is able to work both in RAW and RGB/YUV space. CineformRAW it's ... well... RAW. They just use a proprietary compression to reduce size, but keep it raw.
The ideea behind this is great but I find the implementation not be as good as ACR. If some of this problems are solved could be the fastest way to preview/edit/colour correct keeping the media in raw format.

hi! Do you think that it is possible to convert ML dng raw to resolve format (cinema dng)?

If you transcode to cineform raw quicktime format it opens in Davinci.

Later update.

Color noise reduction is killing this workflow. Also it appears that debayer filter enhances also the color noise.

Here is a link to a dng file from canon raw movie. Also included screenshots for acr and cineform studio interfaces. Check the metalic bars, but noise is present in the entire image.

Any help appreciated

5D3 update files. Replace existing files.
includes cf_acc: module as noted on

There is also a raw_rec.o file in MODULES folder. Is this needed? New files you posted don't have this file...

What I've found so far:

- highlight restore implementation is much weaker than ACR. Cineform Studio & FirstLight does not provide controls to do it. Also if you load the cineform file in AE you cannot "dig" into the highlights.
   In ACR it's amazing how much can be restored.

- Cineform doesn't implement any color noise reduction (or did not found it ?). I've found instances where there are artifacts after debayering through cineform.

- Debayering through ACR gives better details than Cineform, but here I may be wrong. Have to check more.

- there is a small bug when using regional settings in Windows (comma instead of point). 23.976 fps files will transcode insted to a monstrous 23976 fps file. I have to revert to English(US) region or reinterpret in AE.

- did not find a way to save colour matrix in Studio as a preset.

Any feedback appreciated,

I didn't find any of the demosaic options to be as good as the ACR one.
Advanced Detail 3 seem to work best but it's not on the same level.

Also going through cineform raw I didn't find any  options to recover highlights on the same level as ACR/LR.

Any feedback appreciated.

Camera tests = more cat and dog videos online...  :-\

I am lazy. Next time I will do the flowers ???



Camera: 5D Mark III
Build: Magic Lantern May 17 (f686b8c)
Card: SanDisk Extreme Pro 90Mb/s 16Gb CF
Resolution: 1920x1080 23,976 fps
No droped frames, but there are some glitches in the recording. Actually this CF it's very reliable on recording 1920 x 1080. Never had dropped frames.
Minor CC done.
Download to see in real FullHD.

I can confirm that a 5D mk 3 with Peter Linov posted firmware (from 12May) and a Sandisk Extrem Pro 90MB/s 16 Gb CF card    *CAN*    record 1920x1080 without skipping frames.

I don't know what commit number is that firmware but it does not appear to have tearing/stuttering. But didn't do many tests.

I had the impression that both my CF card had roughly the same speed:

- Lexar Professional 600x UDMA 16 Gb
- Sandisk Extreme Pro 90MB/s 16 Gb

Here are both cards benchmarked with commit b6c2ae6:

Bottom line:

Lexar GO HOME!

Sorry, my English is not very good.
The settings in the camera 5DMIII?
Or how I process RAW, what .... I'm sorry, I do not understand.

The firmware. A zip file containing autoexec.bin and ML folder.

Thank you,

@Peter Linov

Can you pls post a link or just post the build you are using for 5dmk3?
I'm trying the ommit b6c2ae6 commit but can't open dng files.

It appears that a Sandisk Extreme Pro 90MB/s 16 gb is able to do 1920x1080 without skipping with this commit but I can't confirm because I'm unable to see the recording on the PC.

parameters are the same for both videos!
there is no difference
diaphragm 8
  shutter 500
  iso 125

shutter 500 ?

I do not have the 1000-х  flash card. But on 400-x  working well with 1920х720!
500мм f6.3,  SIGMA150-500...

If you are interested in an uncompressed download here:

How ?? On a 5Dmk3? You are not skipping any frame on long shots?

Using Commit b6c2ae6 on a 5Dmk3 I'm able to do max 1920 x 680 on a Lexar Professional 600x UDMA 16Gb card. From 1920 x 700 it begins to skip frames.

But DNG files can't be opened! Help!

macgregor wrote "since there's no metadata on the raw files, there are no color profiles asigned to the images. Camera raw I suspect is using the standard adobe color profile, which in my opinion sucks. Canon profiles are much better. Adobe over saturates blues and skintones are less nice. So I wonder if the ML guys could apply the canon profiles to the dng so we could fix this. We could even use VSCO film raw picture profiles, for some extra fun."

Colour profiles have nothing to do with raw formats. When you transcode to an RGB format you can assign a colour profile to it.

But what can you do is make camera calibration (dcp file) by shooting a colourchecker passport card (macbeth). But soon you'll find out that LR doesn't let you assign the dcp file to the dng files created by the raw module. That is happening because LR doesn't recognise the DNG as being created with a Canon 5D (or whatever). LR thinks it is clever and doesn't let you apply custom camera calibrations.

But RawTherapee will let you do that (much clever program to decode raw) and you end up with a colour managed shooting with the Canon RAW.


What worflows do you guys use with the DNG files in Windows environment?

I found out that:

A. Davinci Resolve does not support them.
B. Adobe Speedgrade does not support them.
C. Adobe Lightroom it's ok, but only for simple tasks. For example if you do a highlight recovery and sync all dng files then export to a nle will result in flicker. Probably because although all files have exactly the same settings, internally LR will try to optimise the highlight recovery on a per file basis. (?).
D. AfterEffects through the ACR import. This will have best results. Once you set the interpretation on first file, it's smart enough to keep things consistent for the sequence.  Very, very slow.
E. Cineform Studio/Pro (also the dpx2cf tool) will recognise dng files and convert the sequence to a cineform raw file. You have to fiddle with demosaic (advanced detail 3 seems to work best) and all other settings. The fastest way to preview your movies. Converting it's ultrafast and the result is realtime playable. Fastest way to edit, until now.
F. uffraw batch. Tried once, but slow.

Any other ideas? It seems that cinemadng files and dng files are not *exactly* the same thing and didn't find a way to convert from one to another.


PS. If the raw2dng could convert directly to cinemadng would be awesome.

about the fix for tearing, it worked for me, but I got a lot of stuttering this time...

5D3 600x Sandisk Card. This one was shot lo-res (720x480), so, it's way below the card's max speed. any fixes or explanations?

Uff, it's looking bad... Same as on my test (Reply #493) minus the tearing.

Check this test also and look carefully (on the HD version on vimeo website) at the cars on the 14-bit raw crop


To me it appears that the stuttering it's not tied to the movement of the camera, but somehow the frames are not aligned in time very precise. There are more or less 24 fps but not "genlocked" (don't know a better term).

Double buffering seems to have fixed 5d2:

Frame dropping starts about 18 seconds in and continues for the rest of the video (as expected)

Very hard to judge from that video. More likely not. Maybe put the camera on a tripod and do a smooth pan. Use the smallest resolution which can eliminate dropped frames (maybe 1280 x 720 ?). I'm curious also what happens.

Pages: [1] 2