Messages

@beauchampy - sorry, I messed up  I wrote it from memory. I can't remember V12 doing this either.

Set RCM input to Rec709 (or any colorspace - doesn't matter)  / gamma to Linear (i.e. don't bypass it).

This override's the Camera Raw colorspace settings. If RCM input is bypassed you can still use the Camera Raw colorspaces - but that would get confusing very fast.


DNGs are behaving differently in 12.5 with split RCM. I need to investigate further before I can give a definitive answer.

Thanks for looking into this Andy.

For anyone else looking for a 'quick fix' - Hunters LUT is very close to Alexa Rec709, so I'm using that in conjunction with a LUT made for R709 Alexa.

[Master Project settings]

@Andy600

Thanks for taking the time to reply, I feel like I understand this a bit better now.

I'm still a bit confused however, and the results I'm getting are a bit strange.

Basically I'm working on a 'behind the scenes' music video project. I have DNG files from 5d MK III (BTS camera) as well as Arri Alexa Log-C ProRes (the A camera on the shoot). If possible, I'd like to get the 5D Raw in the same space as the Alexa so we can just use the same LUTS and get the same look..

So I'm in Resolve 12.5

Go to Master Project settings and change the Color science to 'DaVinci YRGB Color Managed'

In 'Camera Raw' I have my CinemaDNG set to Color Space 'BMD' and Gamma 'BMD Film'

Color Management
- Use separate color space and gamma checked
- Input colorspace: Bypass / Greyed out
- Timeline: Arri Alexa V3 / Arri LogC
- Output: Rec709 / Rec709

But now my 5D Raw looks incredibly crushed, clipped and over saturated. I'm aiming for an Arri LogC image which I can use Alexa Luts on..

I'm just delivering for web / Youtube / Vimeo if that helps.

Nailing this workflow would be a game changer for me. If you can help me work out where I'm going wrong, I'll be really really grateful.

Thanks so much

Beauchampy

Does anyone have an up to date method of getting 5D3 DNGS to Alexa LogC colour space using Resolve 12?

Just shot nearly 2TB of MLV over 2 days in Panama. Not a single corrupt frame on 113 + a1ex's modified mlv_rec module in 23.976 and 50p with audio and GD on.

A1ex, is it possible to use this feature to record an area of the sensor that is 1440x1080?

Could be a useful way to implement 4:3 recording for anamorphic lenses.

I'd stick with the 1066x. I've bought six of the 128gb (from Amazon) over the past 12 months and they've all been good.

Hi there dfort,

Thanks for your response. I shot in RAW mode (not MLV rec). So I had to convert the RAW to DNG and then to MOV ProRes (via DaVinci). I ran it in Cinema Tools after exporting it to ProRes since I can't run DNGs in Cinema Tools.

Why don't you just adjust the 'clip attributes' of your 50p footage in Davinci to conform it to 24/25p before rendering out to ProRes?

Okay thanks! Do you have the log of two sample files, good and bad?

Use mlv_dump -v file.mlv > log.txt

Give me a couple hours and I'll do this for a bad clip on the April 01 2016 Nightly VS the same build but with the replaced mlv_rec module.

EDIT: Here's the log files. log_bad.txt is from a bad clip with pink frames, log_good.txt is from a clip recorded with the debugging disabled.
https://drive.google.com/folderview?id=0B-GY59oq1k7eN3o2OFVBajJtZ0E&usp=sharing

EDIT2: If it makes any difference here are some frame numbers that were bad: 215, 216, 382

Woohoo!

Good timing too. I'm just about to shoot a crowdfunding trailer for my feature.

Thx a1ex. 3x3 crop anamorphic looks great @ 2K.

Tell me about it, I'm jumping on a plane to Panama in 2 days to shoot a BTS for a well known international music artist.. Gonna be road testing this hard.

A1ex - I use 1.2.3 from time to time for interviews where I need a backup from the HDMI. Should I just wait a few days on a nightly for a 1.2.3 fix?

[PASS]

You uploaded two corrupted clips. I couldn't download them (I get to a page that says "Trotzdem herunterladen", and clicking it just reloads the page); can you (or someone else) convert them with mlv_dump? Do you get pink frames?

I can confirm the pink frames are still present after converting with mlv_dump on those particular clips.

Here's another mlv_rec.mo for you to try:

mlv_rec.mo

Looks like g3gg0 provided a way to disable his change about debug logging, and the second module does just that, without throwing away the change completely. So, if it works, I prefer including this one in the nightly builds.

Just ran the same test using this module.

Test 5:
FW: magiclantern-Nightly.2016Apr01.5D3113 w/ mlv_rec.mo - debug logging disabled.
BAD: 0
GOOD: 20
PASS 

40GB Test: PASS

Next I tried this build (MLV)
magiclantern-Nightly.2015Mar02.5D3113.zip (e8cc6e5)
I managed to get ONE single pink frame with 60fps 720p mode default global draw settings plus focus peaking on. Ran maybe 7-8 recordings. All stopped after around 200 frames

7-8 clips isn't a conclusive test. I find that on a bad build you can get lucky and have 10+ good clips in a 20 clip test. Please run again with more clips. 16 would be good.

[FAIL]

So, are you saying that:

* magiclantern-Nightly.2015Mar02.5D3113.zip (e8cc6e5) is buggy? (has pink frames?)
* magiclantern-Nightly.2015Feb20.5D3113.zip (36ff475) is fine? (as in, can you throw a lot of abuse at it without getting pink frames?)

If - and only if - the answer to both questions is a solid "yes", can you check this mlv_rec.mo on any of the two builds? (ML core is identical in both).

It should display "Last update: df0bbfe" when you press Q in the module dialog, and it's the only intermediate version between the two builds.

If - and only if - the modified mlv_rec.mo works fine, and you can say it with a solid "yes", can you try it (modified mlv_rec.mo) on a recent 1.1.3 nightly?

Hey Alex,

Just spent a good few hours testing. The results are in!

Test:
Record 16 clips, camera settings as follows... 50p, 1920 16:9, MLV Snd enabled and ON, GD ON, Focus Peaking ON, Histogram ON.
Rack focus during recordings to liven up the focus peaking.
Review clips in MLRawViewer at 23.976 stretched to 16:9.
Clips that have 1 or more bad frames marked as BAD.

BENCH TEST
FW: magiclantern-Nightly.2016Apr01.5D3113
BAD: 9
GOOD: 7
FAIL

Test 1:
FW: magiclantern-Nightly.2015Mar02.5D3113.zip
BAD: 7
GOOD: 9
FAIL

Test 2:
FW: magiclantern-Nightly.2015Feb20.5D3113.zip
BAD: 0
GOOD: 16
PASS

(At this point I'm now 100% convinced about my theory)

Test 3:
FW:  magiclantern-Nightly.2015Feb20.5D3113.zip w/ the intermediate mlv_rec.mo linked in previous post matching df0bbfe
BAD: 0
GOOD: 16
PASS

Test 4:
FW: magiclantern-Nightly.2016Apr01.5D3113 w/ the intermediate mlv_rec.mo linked in previous post matching df0bbfe
BAD: 0
GOOD: 16
PASS

YOU'RE THE MAN A1EX!!! IT WORKS!!! 

This intermediate mlv_rec module produces no bad frames on the latest April 1st nightly, also records past the 40gb mark.. My camera is currently rolling next to me and has hit the 11 min mark at 24p.. Well past 40gb.

Question is, what does this all mean? What's the difference in the 'intermediate' mlv_rec module VS the mlv_rec in the 2015march02 nightly?

And also where does this leave 1.2.3?

Thanks so much for your time and efforts.

In conclusion, I've come to the realization that some of the issue with pink frames may not come from the MLV files themselves, but from the converters doing the conversion.  I can tell you that I've tested the same footage, and I've got different results from different software. 

Interesting, I had thought of this too. However, I get pink frames when I play back the MLV in camera! I also get them in MLRawViewer as well as RawMagic (yes, I know it's not welcome around here). Had a look at raw2cdng, but it seems to be PC only? Want to try and convert one of my corrupt clips? There's two right here:

https://drive.google.com/folderview?id=0B-GY59oq1k7eTHNzdms2bHRnWVE&usp=sharing

EDIT: Also please do the record 10 clips at 50p test and let us know your results.

I can throw a ton of abuse at the 7th Aug 2014 build and not one bad frame. I'm almost convinced it has something to do with the 40gb limit. I'm a dumbass when it comes to programming, but can anyone build the latest build again but with whatever change happened to lift the 40gb limit reversed?

I'd be really interested to know if anyone else can re-produce the pink corrupt frame glitches
I'm getting. Just load up my ML settings, record 10 50p RAW clips in a row and see if any of them have corrupt frames.

EDIT: a1ex, one thing I've noticed is that builds that don't have the 40gb limit on raw recording are the ones that seem to glitch for me. Could that change be part of the issue?

Can you upload your config files?

Sure, here's a Google drive folder with my config plus two corrupt clips.
https://drive.google.com/open?id=0B-GY59oq1k7eTHNzdms2bHRnWVE

I just ran the test again, and had 3 corrupted clips from 7 attempts. The two clips above are from this second test run, dumped my config settings right after.

THANKS! That's awesome news!

Unfortunately I'm still getting corrupt frames on this build using 1.2.3 +MLV on 5d3. There's already a thread on this, so if you want to help solve this, we're on it here:
http://www.magiclantern.fm/forum/index.php?topic=5473.msg165242#msg165242

So I assume it's the flashing you're referring to?

Indeed.

Did we ever get to the bottom of these pink frames? Quite keen to use the latest nightly with the new crop mode, but not if we're still getting corrupt frames..

EDIT: Just been testing the April 2nd 2016 nightly. Recorded 9 clips at 50p and two of them had corrupt frames. This is recording MLV on 1.2.3 with GD and Audio on.

I've gone back to a build from August 7th 2014th which doesn't have a problem with the above settings.

Devs - how can we be of help to isolate the issue?

Thanks man! So you recorded in 1728x442 - 2.35:1 - 60fps for 47 seconds right? That sounds awesome! What card? Have you "Frame skipping" on or off? And this isn't a april joke?!

No April fools, no! Frame skipping was off, global draw off. Card is a Komputerbay 128gb 1066x

Anyone that knows a little bit more about shooting raw with the 7D? Would be really glad to hear your thoughts!

I've got a 7d sat here infront of me. Tried your test and got 47 seconds. Anything else you want me to try?

Guessing this is some kind of april fools?

hmm 1920x1080p 50fps without any stretching ?

I still have to stretch, just set Resolve to stretch corners to frame size.

Awesome work !!!
Could you please share your method of shooting at 50p ?

What do you need to know? I just set it to 50p in the canon menu, leave it on 16:9 and shoot for about 9 seconds..

Gimbal is almost always 16-34 f4 L with IS.
Other lenses were just the 24-105 f4 L and the 70-200 2.8 IS II