-
DaVinci Resolve FCP X roundtrip
This may be an issue with the FCP XML coming from Resolve or a problem with FCP X itself. The edited sequence was cut in FCP X, sent to Resolve for grading via FCP XML and then re-imported into FCP X via FCP XML. This was a video-only sequence linked to the graded/render files from Resolve, so I exported a mixdown of my audio from the “before Resolve” sequence as a stereo AIFF. This file was re-imported and attached to the new “from Resolve” Project/timeline as a connected clip. So far so good.
Today I needed to add titles to the front and back. From this point forward all exports of this project (Resolve video+AIFF mixdwon) resulted in the last second or so of the audio fade being clipped in the exported file. It sounded fine inside FCP X. The full video exported, but the audio outpoint was clipped. Ultimately the fix was to copy & paste the complete “from Resolve” timeline into a new project. Then connect the mixdown again and rebuild the titles. This worked and exported as expected.
Seems that SOP for now will need to be as follows. Anytime you roundtrip into FCP X from a FCP XML file (as from Resolve) you should copy & paste into a fresh project to avoid potential and seemingly invisible issues.
I have also cross-posted this in the DaVinci forum
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
19 Replies
-
Not to sound like a total dunce, but is the frame rate correct on the return?
I was seeing some errors from CatDV on return XMLs.
How much of the audio is getting clipped? Is it consistent no matter the length of the program?
-
[Jeremy Garchow] “Not to sound like a total dunce, but is the frame rate correct on the return?”
Actually that’s a very good question. This was a 23.98 project. I noticed that Resolve ID’ed the XML from FCP X as 24fps. I changed the settings in Resolve to 23.98 and rendered accordingly. Back in FCP X everything appeared correct and no shift in sync, duration, etc. No need to render media (except dissolves) and the info indicated 23.98 for the project setting. The amount clipped was about 1 sec (in 2:10 length), so really nothing that would be caused by a 23.98 versus 24 issue. Note that the audio DID NOT go through an XML roundtrip. Only Media Export-Audio-AIFF. Then import the mixdwon as new audio. Remember, the audio was fine in the project. It was only clipped in the exported file and in that file video ran longer than audio, which was the case in the timeline as well. So clipping was a premature clip of the audio only, not the entire file.
However, this does indicate that there are problems with the FCP XML out of FCP X. I have had other issues in some conversions via Project X27, but they were able to fix it through an update on their end. Right now FCP XML roundtripping is a bit unpredictable and definitely not ready for anything mission critical. My guess is that something “dark” in the project metadata from this imported FCP XML file was the cause. What I don’t understand is why it cropped up after I started adding titles. Originally after I imported the XML, I turned on stabilization for the few shots that needed it (this info is lost in the roundtrip) and added my track of mixed down audio. It was all fine. This only showed up today after I starting adding titles. Once I realized it, I tried removing titles to get back to the previous state, but nothing worked as long as I was in the sequence directly imported as the FCP XML from Resolve.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I’m just throwing hail Mary’s here, but.
If the sequence is any other length, is the audio cutoff amount consistent?
What if you made the trailing audio a compound clip with another audio clip, delete that clip and leave a gap clip, and make the audio the same length as the video (with empty space)?
Might not be worth the testing, but just trying to see what’s going on.
Was this a 1080 sequence?
-
[Jeremy Garchow] “If the sequence is any other length, is the audio cutoff amount consistent?”
There didn’t seem to be any correlation between sequence length and audio clipping; however, the clipping appeared to always be in the same place, regardless of adjustments I made. I did try making it a compound clip to no avail. Yes, it’s 1080.
Thanks for the suggestion, but I really don’t want to do any more tests. Not because it isn’t a good idea, but ultimately any solution would be a workaround for something that should work.
Right now the only viable solution is simply to copy & paste the whole sequence (all clips, effects and transitions) into a brand new project. Not ideal, but actually pretty consistent with fixes for issues of various types in FCP 1-7 in the past. I do appreciate the suggestions, though. Thanks.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] ” I do appreciate the suggestions, though. Thanks.”
Yeah, no worries. My hunch would be some sort of translation error as well. Fcpxml doesn’t seem very robust at the current time.
My other guesses in case the motivation moves you would be to delete render files, or try a different export method at first.
But, whatever, I’m sure it’ll be sorted by final cut XVII.
Jeremy
PS My Alexa shoot got changed to an Epic shoot. I was really looking forward to Alexa. It was 300fps that swung it.
-
[Jeremy Garchow] “PS My Alexa shoot got changed to an Epic shoot. I was really looking forward to Alexa. It was 300fps that swung it.”
Too bad. EPIC at that speed is a windowed portion of the sensor area. That translates into more noise and larger compression artifacts as a portion of the screen. EPIC will be better for that than RED One, but it is an issue for some.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I plead my case, but alas, I didn’t get my wish. I even tried to get both cam bodies, but the budget is full.
It’s for tv only, and ironically the slow motion is for a very quick shot.
Oh well, there will be a next time for Alexa, I’m sure.
-
Wow. Just snuck in a few camera tests. 300fps, yikes.
I don’t know if this is going to work.
Also got to look at an Alexa, unfortunately, this one only had 60p on it, the other 4 120fps cams were out.
Alexa is super sweet.
-
[Jeremy Garchow] ” 300fps, yikes.”
In what way? A friend of mine (who owns an EPIC) told me 120fps in EPIC is still 4K. Maybe they should consider that.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
But if we go 120fps, why not go Alexa, you know? It will make my life so much easier (and the shoot much easier, really).
We just shot 4K @ 96 and 120, but I haven’t had a chance to look closely. I am rendering out footage now.
4k will work @ 120.
5k does look incredible.
The 300 fps looks like scaled web movies, kinda milky in the edges, tons of inescapable noise. On top of that, you then have to fill the frame from 850 vertical to 1080 vertical. Now, it’s scaled, scaled web video.
Thanks for giving a shoulder to cry on, by the way.
Jeremy
Reply to this Discussion! Login or Sign Up