Testing the 7toX Final Cut Pro 7 to Final Cut Pro X conversion
We finally get a tool to do what we thought would be possible from FCPX v1.0.0
By Scott Simmons | February 12, 2012
When Apple released the latest Final Cut Pro X update there was a very important 3rd party utility released right alongside the 10.0.3 update that finally allowed the importing of legacy FCP7 projects into FCPX. It wasn't entirely surprising that it was Intelligent Assistance releasing 7toX for Final Cut Pro. I say that because they had already created Xto7 (to move projects from FCPX to FCP7) and are arguably the best company for creating high-quality XML workflow tools for the FCP universe. There's been tons of blog posts about 7toX for Final Cut Pro since its introduction but most of them are nothing more than a here it is here's the link kind of thing, including one of my own. Many have taken a simple sequence to try this conversion but my thought was to throw everything at 7toX for Final Cut Pro and see how well it did ... or didn't work.
Of course the most surprising thing is still that Apple didn't build this capability directly into FCPX from the beginning but it's better to get it late from a 3rd party rather than never get it at all.
We all know that Apple has said that it wouldn't really be possible for FCPX to import FCP7 projects due to the difference in the timeline, differences in media management and overall different philosophy in how the two applications work. This point was reiterated further upon the 10.0.3 release when Apple stated that "it was never going to be possible for us (Apple) to do perfect fidelity" in an FCP7 to FCPX conversion. That's probably true of anyone since the two applications differ so greatly. With that Apple passed this task to Intelligent Assistance. Better to let them feel the wrath of the angry user when the conversion doesn't go as planned I suppose.
Putting it to the test on a big project
I was very curious as to how well the conversion would work. One thing that's mentioned on the 7toX website is that the conversion isn't just for sequences. It works via XML out of FCP7 and XML into FCPX. One thing about XML from FCP7 is that it's dependent on what you have selected when you export. A single sequence selected will export just that. Nothing selected will export the entire project.
I was curious as to how well it would work converting an entire project. The project I chose to throw at it was a music video that was cut from a live performance, a bit of music video specific performance and a ton of broll. It was a large job considering there was well over 10 hours of media. The performance itself was captured with 7 cameras and that includes rehearsals as well as the live performance. There were the odd GoPro placed around the stage. Add to that a few takes of the artist performing parts of the song to a track in a more abstract setting (I don't have permission to show any of the footage or images) and that's over 25 angles.
To complicate things even more, during the live performance that was captured the band wasn't exactly playing the same version of the song from the master audio that we had to cut to. That means the sync didn't hold. All things considered when I got done with my cut I had one messy timeline.
While it looks like quite the mess this timeline is actually quite organized!
Normally I wouldn't let a timeline that sloppy see the light of day but in this case it was a necessity. Some angles were able to be grouped into an FCP7 multiclip. Several multiclips had to be made; some for the live performance, some for the rehearsal. The abstract performance was stacked above everything else. I made a sync map of all the angles I could before I began to see what I had. I actually made a number of sync maps for different things, labeled them with a color and sent them to PluralEyes for syncing. After I got a performance cut I liked I then layered in broll as the edit went along. When I was done was the timeline above is what I gave it to the director to view and make any tweaks that he thought was necessary.
The export from Final Cut Pro 7
As for how the media in the FCP7 project was structured:
I didn't want to take up the screen real estate to twirl down all the footage bins.
This was to be quite the test for 7toX. To get my XML I deselected everything in FCP7 and exported the XML.
While the edits were only around 4 minutes there was over 10 hours of media.
I then ran that XML through 7toX for Final Cut Pro. It took 7toX 15 minutes to process the 17MB XML.
As 7toX was progressing it will often show what exactly it is translating. This is a nice touch when you've got a big job like this one.
I often wondered if it had crashed but I didn't force quit, I let it soldier on. Finally, a 2.6 MB FCPX XML came out the other side.
Once 7toX is done it asks what to do.
The import into Final Cut Pro X
I took that new .fcpxml and imported it into FCPX. That import process took about 13 minutes and I really did wonder of FCPX had crashed as the beach ball started spinning after a few minutes.
This is usually a bad sign.
I think normally I would have force quit … in fact I did but when I went back into FCPX it has processed through and imported some of the events. The second time I kept an eye on the media drive (as well as the cpu) and occasionally saw it flashing so I knew FCPX was doing something. Even with the Force Quit window saying FCPX was not responding after 13 minutes it had finished. Then I had a new Event in FCPX with a lot of events and a lot of media.
That's pretty similar to the FCP7 project above.
As I looked around in FCPX I found all my master clips, quite a few Compound Clips that represented my sequences from FCP7 (in an event called FCP7 Sequences) as well as new to 10.0.3 Multicamera Clips. I then opened up my final timeline by editing the Compound Clip into a timeline and choosing Break Apart Clip Items.
That's a pretty nice conversion of a complex timeline for something that we were told probably wasn't possible.
I have to admit I was stunned that it came across so well. Almost everything is there in this rather insane timeline. Multicamera clips, the master audio, both enabled and disabled clips. It wasn't 100% as there were some clips that were out of sync but for the most part it worked. And that was a lot of DSLR media and we all know DSLR media isn't the best when it comes to timecode. Was the "fidelity" 100%? Nope but it's a conversion that Intelligent Assistance should be proud of because this wasn't an easy project to convert.
The biggest overall problem that I saw in this conversion came from the scratch audio on all the cameras. This wasn't a problem of 7toX but rather in the way FCPX works. It wouldn't be a problem in some edits but in this type of project it would cause some extra work. All the clips imported into the FCPX timeline with camera audio intact while that camera audio had been removed from the FCP7 sequence. This is one of those fundamental differences between the applications and points to FCPX's weakness in handling audio overall. When I would play the cuts in FCPX I would hear my master audio and depending on the cameras chosen their scratch audio would come blaring out, sometimes more clips than one.
There's no easy way to disable all the audio at once and when I would select the Multicamera clips in the timeline to disable the audio in the Inspector it said this:
It didn't work to uncheck the audio for the Multicamera clips in the Inspector but the Volume did.
What I was able to do is select more than one clip at a time in the FCPX timeline and just turn the Volume down all the way. It worked but it was tedious and it makes me think FCPX is having to process some unnecessary audio. If they can figure out a way to deal with this audio conversion from 7 to X then a translation of this type edit might be near flawless.
Up Next: Some thoughts on the conversion as well as some other timeline comparisons.
Get articles like this in your inbox: Sign Up
editblog - Tue, May 21 2013 - 7:54 am
@videoaaron @tstrachanedit Great keyset … I need to update the Keyboard Manifesto for @AdobePremiere Don't really think it'll work for FCPX
editblog - Tue, May 21 2013 - 6:46 am
@amyfame Reading into the comments on an article like that is always fun too. overall not a happy article for our generation to read