Messages

There is a bug with the last new builds (July 13th, 16th and 22nd): the file browser doesn't work and the 5D MKIII is frozen until I take out the battery.

I tested 3 time the same Raw footage to Prores 422HQ with
1- AE (with ACR)
2- NukeX (with J_Ops_2.0v1)
3- Resolve 9 Lite
Result of render time:
40 min AE 
18 min NukeX (works the same with DNG or CinemaDNG)
2 min Resolve 9
I know quite well ACR (so I used quite a lot corrections), a bit less Nuke (I didn't use any any chromatic aberration) and I don't know much about Resolve for the moment and I didn't use (and see) any chromatic aberration or any recovery exposure (for the high lights for example) but used Black Magic LUT with some other few color correction.

I have to go deeper to the investigation because as you see, it might depend on the raw settings.

Yes, aaphotog, you're right, that's exactly what I have done. When I created my personal menu in ML, a file named "settings" in ML folder has been created so that each time I boot my camera, I have my own settings back. But it seems that there were a conflict between the settings I created for the June 22th build and the same settings I intended to use with the July 13th build. I know it was stupid to keep it... I couldn't imagine such an issue. Hope it makes sense for you jas.brooks.

And sorry if it's not the discussion but FYI, I tested 3 time the same Raw footage to Prores 422HQ with
1- AE (with ACR)
2- NukeX (with J_Ops_2.0v1)
3- Resolve 9 Lite
Result of render time:
40 min AE 
18 min NukeX (works the same with DNG or CinemaDNG)
2 min Resolve 9
I have to go deeper to the investigation because it depends on the raw settings but it might interest some people.

@3pointedit
I found why I had non fluid footage with raw setting 1920x1080 25fps (with 64GB Lexar x1000 5D MKIII):
I kept my old ML setting while I updated the new nightly builds. I put it away and keep only the new build (july 13th) and it works well now.
I also discovered that with the new builds I can keep now the setting raw+L(jpg) on the Canon menu, the ML Raw rec 1920x1080 25fps works perfectly well without any drop. Any chance the sound could come back? Thanks again...

I've compared the Raw 1920x1080 25fps (with 64GB Lexar x1000 5D MKIII) with the H.264 (Canon native) with the same traveling camera and, as everyone knows, the Raw is better... except that it's really more fluid with the H.264. The Raw footage looks more stroboscopic when I move the camera. Does anyone feel the same and does that mean that I need to add motion blur on post (AE for example)? Does it come from the way each images are recorded on the CF card? Any suggestion to have smoother result? Thanks again ML team!

Suggestion:
What's your Canon firmware? 1.2 or 1.1.3? (If your 5D MKIII is new you should be with V1.2 and you have to downgrade to 1.1.3)

Just for your information, it's possible to convert the DNG files (from Raw2dng) to Tif with Capture One (6.4 and 7). ACR is not the only one.
It might help some of us even if the workflow is better with Rawmagic + Resolve.

I don't want to be boring but can someone tell me where I can find a Raw2dng able to convert a 10 GB raw file (I mean bigger than 4GB)?
I tried with the Mac and PC version but none of them can do it.

Ok, I've got it now. I knew that I have better result when I shoot at multiples of ISO 160 (only available if Highlight Tone Priority is disabled) as said most of the directors using the 5D MKII-MKIII but I didn't get the exact explanation. I've found this (http://blog.vincentlaforet.com):
"Technically, the camera is native on the ISO's that are multiples of 100.  For the ISO's in-between, the camera digitally pushes or pulls one of these native ISO's.  For instance, ISO 125 is really ISO 100 with a digital exposure push, and ISO 160 is really ISO 200 with a digital exposure pull.  As a result, 160 and its multiples look the "cleanest" because its really a native ISO rating with the exposure pulled down, which hides more of the digital noise".
Thank you A1lex and Aaphotog

Sorry A1ex, I'm not sure to understand about the ISO:
Does it mean that ISO 800eq is the value at which I'm recording when the Canon is at ISO 640?
And why the ISO in Raw is different to the ISO in H.264?

And in the file browser, the files have a wrong size (always smaller than it supposed to be).
By example, M17-2340.raw is 2.9 GB instead of 7.5 GB
Is there any reason?

With the new builds (from the June 11th to 17th), the way the ISO is displayed is different when Raw Rec is OFF (ISO 640 buy example) and when Raw Rec is ON (ISO 800eq with the same example).
Does it change something or is it just the way the ISO appears now?

New build June 10th(ed914b3) works fine.
1920 x1080 25fps works fine with global draw on (unlimited) except when raw zebras ON (130 frames only); For zebra, luma fast ON works great. As default ML set up is Raw zebra ON, check with Raw zebra OFF, it would go really faster.
Lexar 64GB 1000x card