Topics

Like a lot of you, I've been experimenting the past few days with the new 3k/4k modes in crop_rec and really loving the results I'm getting.

At first I was using mlv_dump in the command line to output DNG files one at a time. The files I got opened up and played back fine in Resolve without any issues.

After a bit, I decided to check out cr2hdr and really like the batch processing it does. However, my DNGs from cr2hdr end up having flickering frames where I'm guessing either the white or black level has fluctuated slightly.

I searched around the forum a bit and found a post referencing setting blacks to 2048 and whites to 16383. So I reprocessed one of my MLV files using these values in cr2hdr, but I'm still getting the flickering issues in Resolve.

Does anyone know why mlv_dump on the command line is giving me perfect results right out of the gate without any manual settings (just -o to specify output name and --dng) but cr2hdr even with settings dialed in still results in flicker frames?

I really want an easy way to batch footage, rather than do it one at a time! Thanks for any help.

Hey guys, well I screwed up big time. I was trying to go to the format card menu to quickly check how much space was left on my card (bad idea, I know) and in my haste I accidentally clicked "Yes" when it asked if I wanted to format my card. I pulled the card from the camera immediately as I know there's a pretty good chance I can get that stuff back if I don't do anything else to the card first.

So, I was shooting RAW video on a 5Dmk3. The card was formatted ExFAT. After the camera reformatted it, it switched to FAT32. I've tried Transcend's data rescue app and it didn't seem to do much, I'm also running StellarPhoenixPhotoRecovery on it right now but so far the scan hasn't turned up anything. I think maybe because these apps are looking for .CR2 or .NEF files, not .RAW .R00 etc video files.

Does anyone know the best app for OS X to scan for these? Am I totally hosed here? I'm so angry with myself for formatting that card, I never normally would make such an error but I was in the middle of a very hectic and stressful shoot where, alas, there was no DIT and I was wearing far too many hats at once.

Any help would be super super appreciated, thank you!

So I've just received my new MKIII and I figure the install will be a breeze having done this dozens on times on my MKII... guess not!

For some reason, I can't get MacBoot to recognize any of my SD cards. My understanding is that on the MKIII you run ML off the SD card and then record to the CF. I like this idea since it means I don't have to prepare multiple CF cards with ML before shooting.

Anyway, MacBoot doesn't recognize my SD cards (8GB and 16GB). I tried formatting them in the MKIII (as FAT32) and on my Mac (as ExFat). MacBoot scans them and says they aren't suitable.

My 64GB CF card meanwhile shows up just fine. What am I missing? I guess I could just install ML on the CF card, but this is bugging me.

I'm trying to figure out a good workflow where I can edit proxies of my 5Dmk2 raw footage and then relink back to the original DNGs for grading in AE at the end. I figured I'd make this thread to write about what's working right now and hopefully people can chime in with ways on improving.

First off, the only way this works is with proper file management and good renaming. I've been renaming all my shots so that the folder looks like (for example):

/5d2raw-2013-05-27-shot001/
/5d2raw-2013-05-27-shot002/
/5d2raw-2013-05-27-shot003/

Within this, the files would be numbered like:

/5d2raw-2013-05-27-shot001-image00001.dng
/5d2raw-2013-05-27-shot001-image00002.dng
/5d2raw-2013-05-27-shot001-image00003.dng

And so on. No more of this /M0000001/000001.dng stuff. Right now I'm just doing it with Name Mangler, which automatically derives the folder name from its creation date, and then derives the image file names from the parent folder. It still requires me manually dragging and dropping each folder and clicking rename, because if I do a whole shoot (say 10 clips) as a batch, the image numbers increase even when a new shot starts. It would still work that way (the first file for shot002 might be 00185.dng) but it seems kinda funky to me.

Okay, everything's been renamed and organized. Now it's time to convert to something I can actually edit in realtime. Right now I'm opening up an entire folder of DNG's in Photoshop CS6, finding my hero shot, making a quick adjustment for exposure/highlights/shadows/etc, then syncing that adjustment to all the other DNGs in the sequence and saving that out as a series of jpg files with the exact same name, just a different extension.

It's a pretty slow process to grind through many thousands of DNGs to get them into JPG form, so I hope that's something that can be accomplished faster. Even if the output wasn't top notch quality (which these are right now), that'd be okay. It's just a proxy.

Okay, onto Premiere CS6. I import my JPG image sequence; seems you have to do this one at a time, and check that it is in fact an image sequence - any better way to do this? Once that's done, drop it on a timeline and start editing. Plays back at full quality without a hitch. Edit away.

When done, I'm exporting an XML file of my Premiere sequence and then using Pro Import AE in After Effects CS6 to bring it in. That gets my sequence in with all the cuts intact.

Now the cool part - if I then reconnect the image sequence in the AE bin to my DNG files, I've now got an edited sequence of raw DNG files. I can then grade away at these, including re-opening Camera RAW and making all the adjustments I want.

When it's time to render out, I can do it from the highest quality source possible (the original DNG) to whatever format I want.

I've seen Windows workflows for rendering out proxy files in formats like mp4, but for me it makes a lot more sense to stay with image sequences for the relinking ability at the end.

What do you guys think? Obviously the holy grail here would be if we could get these files natively into Resolve - then it's basically the R3D/BMCC workflow... import the raw files, do a one light, export proxies, edit, conform and color at the end with a lot less steps!