FCPX to Resolve with RAW footage

[Oliver Peters]

FWIW – I ran a quick test with the “Afterglow” CinemaDNG clips that BMD has had on the web. I wasn’t able to reproduce the raw issue. Changing the names on the ProRes Proxy files in FCP X did not affect whether or not I could access raw controls

I hit a different issue, though. I used the roundtrip back into FCP X and there, some of the files showed black in the project timeline. If you match-framed the timeline clip, then a normal and visible clip showed up in the browser, but it didn’t update to show video in the timeline. There it was still black.

These black clips didn’t correspond to those that were renamed. As I’ve found out before, the FCPX/Resolve roundtrip (when actually going back) is pretty messed up.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[David Mathis]

I hope this is fixed in the new version due out soon, whatever that means. Should the new version hold up to its promise I might start doing an entire project in Resolve. Of course I still like the Motion workflow for custom lower thirds, titles, and transitions. Doubt we will see anything like that from Fusion, would be a nice feature to have. Resolve tempts me, teases me and sometimes likes to torture me. 😉

[Michael Gissing]

I had advised Scott on the Resolve forum to make sure the ProRes proxies were no where near the Resolve machine and to import with the option to relink to camera originals so I am sure there was no issue there.

I have no idea why the RAW settings were then greyed but if X somehow set a different metadata flag during the renaming, then perhaps Resolve didn’t automatically recognise them as DNG files. It might have been fixable by seeing if on the RAW panel in Resolve, the correct camera was selected. It might have defaulted to Alexa or RED and needed manually changing. The other thing is on the Media page, checking that the clips were forced to data not auto where it may have incorrectly interpreted as Rec 709.

So Scott, if the grader can check those settings you might find the culprit. My best guess is the flagging on the files was not defaulting to data and auto was making it video levels which may have locked out the RAW settings option.

[Scott Witthaus]

[Michael Gissing] “The other thing is on the Media page, checking that the clips were forced to data not auto where it may have incorrectly interpreted as Rec 709.”

That is a good clue. Again, it was during a 48 Hour Project so we were all sleepless and rushing. Thanks Michael (I sent the colorist a link to your advice on the Resolve page, so I assume all the steps were followed.).

sw

[Oliver Peters]

I’ve run into roundtrip issues when moving between different machines. These didn’t occur when both apps were being used on the same machine. However, this mainly affects the return trip using FCPXML from Resolve into FCPX. Nevertheless, it could be a factor here.

Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Scott Witthaus]

And Resolve was on a different machine.

Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter