-
Issue with Resolve not reading multi-cam clips
Hey everyone,
I’m at the beginning stage of finishing my film, and our colorist in NY is having issues reading our XMLs. I used the Xto7 program and converted all the Final Cut X xmls to FC7 versions. But upon import into Resolve, tons of shots are missing and are instead showing up as black gaps. After spending hours researching this, I think I’ve narrowed it down to a multi-cam issue. We even tried a test where, I created a new project with only two shots on it. One was a single camera shot, the other a multi-camera shot. And in Resolve, only the single camera shot showed up.
Does anyone have any experience with this and could provide me some advice? There’s no easy way to ‘flatten’ the multi-cam clips. And about 90% of the shots in our sequences are multi-cam. So I’m hoping there may be something else I can do to correct this. I’ve tried a few different Metadata View options. But no dice.
—
Dennis Widmyer
http://www.parallacticpictures.com -
13 Replies
-
Resolve can import FCPX XML directly and will handle all of the multicam clips perfectly. Skip Xto7 entirely.
-
Hi Jacob,
It hasn’t though. It crashes Resolve repeatedly upon import. (this was Resolve version 9).
So we then converted it using xto7, and that at least allowed to be imported. But then we were seeing entire gaps where the bulk of our shots were supposed to be. The same exact thing is happening when you load the converted XML into Final Cut 7. After a series of tests, we deduced that it was the multi-cam clips that weren’t showing up. But what’s odd is, it’s not even showing an error message or a missing proxy. Rather, it’s just showing a complete gap in the shots where those clips should be. So something is definitely getting lost in the translation.
I just emailed the good folks at xto7 to see if they can help. But I’m thinking that this is probably something on the Final Cut X level that’s getting lost when I export the XML.
—
Dennis Widmyer
http://www.parallacticpictures.com -
hmm that is strange. multicam definitely won’t crash resolve. i’ve done a number of multicam music video type projects that were graded in resolve via the XML round trip. and i dont thnk Xto7 is mean to work with multicam, will probably be a dead end.
is there anything else in your timeline that’s funky that maybe you could take out? maybe try stripping anything weird or unnecesary. breaking compound clips. whatever else you can think of. then exporting XML to Resolve again.
-
What version of X and resolve are you using?
I’ve noted some very odd behaviour if you have the following situation, which is what I suspect your doing?
If you have a number of shots, each with multiple angles and you select all the clips and the make one big multiclip and then send that to resolve it can go very weird.
To get round this you need to select each shot individually and make individually multicams – it’s a pain but its the only way. Haven’t tried it with .9 and resolve ten yet but I will.
Michael Sanders
London Based DP/Editor -
I’ve flagged this with both Apple and Blackmagic – it’s one of the reasons I’m annoyed there’s no batch multicam facility.
Michael Sanders
London Based DP/Editor -
Just tried this with FCP X 10.0.9 and Resolve 10.1 Lite. If you export a multi cam sequence from the timeline it sends weird time codes and black holes.. So you end up with a mess in the resolve timeline.
As I say I’ve flagged this with Apple and BM but worth doing again.
Michael Sanders
London Based DP/Editor -
Hi Michael,
Turns out it was a combination issue of Resolve and the program Xto7. The version of Resolve was 9, which, for some reason, wouldn’t bring in the xml.fcpx files without crashing upon import. So we then purchased X to 7 to convert the xmls. This allowed us to get them into both Resolve 9 and FInal Cut 7. But in each program, we were seeing giant gaps where about 75% of our shots should be. After trouble-shooting this all morning, we figured out that it was the multicam clips that weren’t surviving the translation. I ended up finally having to email the creator of the X to 7, a very awesome dude who looked at our XMLs and determined that it was a problem with the way the app was calculating our multicam shots. o he quickly addressed and fixed the problem and then converted all our XMLs for us. After which time, they loaded into Resolve Lite (on my end) with all the clips in tact. We’re now waiting to hear back from the Colorist in NY to see if he was able to get them to load in Resolve 9 too. Fingers crossed!
—
Dennis Widmyer
http://www.parallacticpictures.com -
[Dennis Widmyer] “I ended up finally having to email the creator of the X to 7, a very awesome dude who looked at our XMLs and determined that”
Greg and Philip are great. Best customer service around. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
-
In my experience, the black hole gaps always happened where there were speed changes in X to 7.
Reply to this Discussion! Login or Sign Up