-
Resolve 18 to X workflow?
I know this might be slightly backwards but here goes. I started a project in Resolve 18 because of the large amount of Braw footage- didn’t want to transcode all that stuff-. So now that Braw toolbox has arrived, I’d like to bump the project over to FCP for a happier editing experience. I know most workflows tend to head towards resolve for editing and grading but in this case I want to do the opposite. Can anyone offer insights into what might make this smoother or at least work- I made one attempt so far and that failed.
The Resolve edits so far are rough assembles no fancy transitions effects, etc, the director and I want to pick up where we left off with Resolve and make our lives “easier”
-
9 Replies
-
I haven’t used the new plug-in, but….
I would import and organize the media in to fcpx. Then export fcpxmls of any sequences from Resolve and import those in to fcpx.
I would not try and get the Resolve organization in to fcpx, I would keep that a separate process. Fcpx has much better organization tools anyway and it will be good to start the process anew using those tools
Jeremy
-
First, be sure you haven’t applied any effects or anything, just straight, raw edits.
What have you tried so far that’s not working?
From what I see, there may be a problem that BRAW Toolbox wants to import clips from scratch. The FCPCML process may not be able to include that. I’m checking with someone I know who’s very familiar with all of this, but I’m not sure BRAW Toolbox supports import via FCPXML.
That said, Synk-n-Lynk is supposed to support the BRAW Toolkit.
-
Here’s what I get when I try to import xml from resolve. I don’t care if I get the resolve organization, I just wan the time lines to come into FCP.
-
And you media is imported already using the toolkit?
-
The problem is that the FCPXML that’s coming from DaVinci Resolve has .braw files inside it, which Final Cut Pro can obviously not import.
What you could try doing is opening up the FCPXML in a text editor, and replacing all the .braw with .mov. This SHOULD now import into FCPX, although obviously all the media will be offline. You can then TRY and use the “Add BRAW Toolbox to Proxy Clips within an EVENT” tool within BRAW Toolbox. To be honest, I have no idea if it’ll work or not.
Feel free to email me the FCPXML and I can have a play/think too:
https://brawtoolbox.io/support/
-
The problem is that the FCPXML that’s coming from DaVinci Resolve has .braw files inside it, which Final Cut Pro can obviously not import.
But doesn’t the tool box expose the files to FCPX? Maybe I don’t understand how this works, but if the files can be read within FCPX, why can’t the timeline be imported? And fi the files are already imported, fcpx should automatically relink to the imported files. At least that’s how it woks with every other type of media. Does the braw toolkit not import the clips as braw?
-
Because Final Cut Pro’s decode API is private – we had to just make do with the two public API’s we had access to – Workflow Extensions and FxPlug4.
We use the Workflow Extension API as our “user interface”, where users can select the footage they want to import, and preset any RAW controls.
We use the FxPlug4 API as our “renderer”. Essentially, BRAW Toolbox is just a Filter in Apple Motion, and an Effect in Final Cut Pro, but instead of “processing” the source clip, we replace the clip contents with the processed BRAW clip.
We use Blackmagic’s official BRAW SDK – so you get all the same colour science and processing speed as DaVinci Resolve.
-
Very clever.
I watched a video and see how it works now, and I see why you can’t simply “relink” to the BRAW clips.
Cheers,
Jeremy
-
I Have used BBEdit to edit Panasonic metadata in the past to resurrect some problematic clips. I’ll take a swing at the method you offer in your conjecture and see what happens. Its a bit more in the weeds than I really want to be , but if it saves a little time by helping port those time lines over to FCP it might be worth the effort.
Reply to this Discussion! Login or Sign Up