-
FCP X – Resolve – RED stupidity
-
To clarify, when I try to import the FCPXML into 10.2.1 I get “out of frame boundary” errors for all clips. Well DUH! That’s what this whole process is about. Of course, the durations won’t match.
When I try to relink specific clips, then I get the audio channel message – original file had audio, new file has no audio.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
If you import that same XML to Resolve what happens?
-
[Jeremy Garchow] “Can’t you update the linked 10.1.4 library to 10.2.1?”
No, that machine is on Mavericks. You can’t update to 10.2.1 without going to Yosemite and that’s not an option right now. However, what difference would that make? I don’t have a problem with 10.1.4. I only brought it into 10.2.1 on a different system to see if 10.2.1 still had the scaling issues. Just to troubleshoot. It does.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I don’t know, Oliver.
My experience with export and import between databases has been limited to Excel and FileMaker Pro, but my experience with FMPro is that if you specify a sort order and then export the data, the receiving database has to know how to keep the fields straight, or re-exporting back in the opposite direction can easily get hosed.
It seems to me that ‘s a pretty close description to what you’re experiencing.
So is it Apples mess up or BlackMagics? – or neither? But just two different systems with different file handling needs?
Beyond my pay grade.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
[Jeremy Garchow] “If you import that same XML to Resolve what happens?”
I tried two imports into software on my system at home – again no RED files, only the rendered ProRes clips.
Converted FCP 7 XML (using Xto7) to import into PProCC 2014. No luck on importing the XML – “general error”.
Resolve 11 – no issues whatsoever. Imports and relinks just fine.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Bill Davis] “It seems to me that ‘s a pretty close description to what you’re experiencing.”
I get that and I agree that it may be what is happening. However, if that’s so, then it’s stupid to even have a roundtrip that is anything other than 1 direction. The return trip will always have different parameters.
[Bill Davis] “So is it Apples mess up or BlackMagics? – or neither? But just two different systems with different file handling needs?”
I don’t know. I blame both. The Resolve FCPXML clearly retains some of the FCP X info that was sent to it, because it brings back the same transitions. In other words, the transitions I used in the offline edit (light noise) show up as standard dissolves in Resolve. Yet, when the new FCPXML is opened in FCP X again, it shows the light noise transitions again. Obviously this info is being passed and not stripped out. So it seems like not all of the info that should be stripped out or updated is being done.
But I also blame Apple for using an exchange format that is so clearly non-standard and so poorly understood by nearly every third-party vendor. They understand it enough to read it, but clearly not enough to write it correctly or use it for exchange.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
For grins, I just tried importing the converted XML into FCP 7. Although there are a few quirks in the sequence, it does import and I can relink to the media files. Requires the “continue anyway” override command, as expected. Sort of reinforces my original comment about needing better relinking control.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
One more data point. I imported the FCPXML into Resolve. It links correctly to the rendered files. From this timeline I exported a new FCPXML (no new renders). This new FCPXML imported fine into FCP X without issues and correctly linked to the media files. Plus it retained the original light noise transitions.
It also didn’t have the scaling issues. This would imply that a second pass through Resolve would potentially fix the problem by “washing” the FCPXML.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “One more data point. I imported the FCPXML into Resolve. It links correctly to the rendered files. From this timeline I exported a new FCPXML (no new renders). This new FCPXML imported fine into FCP X without issues and correctly linked to the media files. Plus it retained the original light noise transitions.
“That’s what I was going for.
If the other (translated) XML is also causing issues in Pr CC, it seems like that original FCPXML may be a little “iffy”.
-
[Jeremy Garchow] “If the other (translated) XML is also causing issues in Pr CC, it seems like that original FCPXML may be a little “iffy”.”
Well, the “roundtripped” FCPXML written by Resolve the first time. The second-generation Resolve FCPXML would now be linked to these ProRes media files, so any attributes related to the media files would be pulled from these clips. In the case of the FCPXML that Resolve first exported, its media attributes would be based on the 4K RED source files (with embedded audio channels).
IOW, it appears that when Resolve uses the usual FCPXML roundtrip set-up to export media with a list, it doesn’t generate an FCPXML with the attributes that match the files that it is creating. This would tend to mean that BMD is at fault for not writing a proper FCPXML. It’s simply passing through the same FCPXML that it received without properly updating it.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up