Sharing FCP 6 and FCP 7 files - Possible

N

newadam

Well-known member
Does FCP 7 change the file format from FCP6? Basically We have a mixture of G5 and Mac Pro and Macbook Pro machines. We have FCS2 now. I know the G5 machines will not run the new version. But can we keep them on FCP6 (FCS2) for basic editing, and then go back and forth between the new FCP. I am sure Motion will not do this, but will FCP? Please try it someone.

Thanks,

Adam
 
Yeah it can be done with a lot of messing around with XMLs or EDLs but bottom line is you'll need to dump those PowerPC machines for Intel machines if you want to run smoothly. And everyone should be on 7 for optimal workflow. It's spend now or later.

Noah
 
But FCP 7 will open existing FCP 6 projects with no sweat, right? I'm stuck with v6 on my Powerbook for P2 ingest, but plan to edit on a Mac Pro/FCP 7.
 
FCP6 to FCP7 will work.

But I would stay with one version and not open previous projects in a later version.
 
Ok...interesting. I still have FCS2 on my G5 dual 2.7. Slow as molasses compared to the 8-core MP, but it might be better for existing projects prior to the Compressor stage I suppose...

What kinds of surprises might I encounter when opening v6 projects on v7?
 
No real surprises I've found- problem is it's a one way trip. Once you save a project in FCP 7 you won't be able to open it in FCP 6.

Noah
 
Thanks Noah. What about saving a migrated v6 project in v7 with a new name (ie: open "My project 01v6", save as "My project 02v7")? Would all of the files and other assets still be readable if "My project 01v6" was reopened later in v6? Obviously, any changes made the v7 version wouldn't be there...

It brings to mind a feature that would be nice (if possible). In DAWs like Pro Tools, Digital Performer and others, it's possible to do a "save as" in an earlier rev. So in PTv8 you can save as PT6 or earlier (v8 files will still open in v7). They manage this by showing a dialog box before you save that notes what aspects of the file will be lost in the downrev translation, which is often just fine, particularly at earlier stages of a project, before some of the fancier features of later versions are brought into play.

In FCP this would present certain problems of course, like when attempting to save a v6 version that contains mixed formats as a v5 version that doesn't allow it. In cases like that, a dialog could simply say that that can't be done, but for many situations (if not most), it might work just fine. Like a basic DVCPROHD timeline with rough edits/fades and an audio mix, for example. Having at least that kind of backward compatibility doesn't seem like too much to ask, no?
 
Last edited:
You must log in or register to reply here.
Back
Top