Your ins and outs should still be correct for the overall clips. In your roundtripped FCPX timeline, simply select the clip that is appearing as a still image and matchframe it.
INDUSTRIALREVOLUTION FXFACTORY CRACK CODE PATCH
When you have a locked FCPX cut, duplicate your project (you should already be doing this anyway), then in the one set to go to Resolve, select all your video clips, detach audio, and then delete all the audio out of your timeline (you can also just disable all the audio from your clips in the patch panel from the inspector). Detach audio from your FCPX sequence – Resolve still doesn’t do the audio thing so well.You’ve made our lives easier.Ī couple quick workarounds that may help you if you run into problems: On behalf of editors/colorists everywhere – thank you.
This is a pretty huge accomplishment by the Resolve team. I’ve been a colorist doing this stuff since FCP7 was in its heyday, and I’ve never been able to get a timeline in and out of an application with such a small amount of conforming. The point is that my ins and outs for everything came in correctly, and I didn’t was able to get all of my footage from FCPX to Resolve with all kinds of effects and craziness largely without a problem. Even the Speed changes that I was having difficulty with previously imported without issue (although I did need to fix a few things on roundtrip). Sync N Link clips came through fine once I added the media into the media pool directly. Synchronized and multicam clips came in without issue. The basic takeaway was that things were getting really close, and I was pretty blown away with how much work they’d been able to do with speed changes… and my only real major complaints were with synchronized clips.Īnyway, I just ran those exact same XML’s through the same roundtrip in Resolve 11.1 and everything worked pretty much perfectly (except for the usual suspects that have never worked like color and Ken Burns). With the Resolve 11 Beta, I wrote a revised list of what was/wasn’t working on FCPX-Resolve roundtrip here: It’s kind of awesome what they’ve been able to do. We’re almost there with FCPX-Resolve now, so hats off to the BMD team.
INDUSTRIALREVOLUTION FXFACTORY CRACK CODE UPDATE
So, looks like the BMD guys with the latest Resolve update have filled in some MAJOR holes in the FCPX-Resolve workflow and it is now approaching “I’m not really too worried about it” roundtrip status which, I think, as a colorist, I don’t think I’ve ever said out loud about any 3rd party color roundtrip workflow.
0 kommentar(er)
