6.03 not compatible with 6.02??

I didn't think these two were incompatible but our east coast editor sent us a a project that is incompatible with ours? Is this a 6.03 update a problem or just a corrupt file giving us the too new format error?

6.03 and 6.0.2 is not compatible.

Chi-Ho Lee
Film & Television Editor
Apple Certified Final Cut Pro Instructor

The 6.0.3 is free to update and I'm running it with no problems across PPC and Intel (both Xeon & Core2Duo)



For instant answers to more than one hundred common FCP questions, check out the LAFCPUG FAQ Wiki here : [www.lafcpug.org]

Newer versions...even .03 updates, are never backwards compatible. Sad, but true.

Well, I take that back. FCP 5.1.4 was backwards compatible with 5.1.2...but that was the only one that was.

Time to use XML...


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

> FCP 5.1.4 was backwards compatible with 5.1.2

Really? As in FCP 5.1.2 could open an FCP 5.1.4 project? I don't remember that. Then again, I waited so long to upgrade to FCP5 that I skimmed right over those earlier versions.


www.derekmok.com

Yeah...it was a shock when I realized that. 5.1.4 openable by 5.1.2. I thought it would be a new trend.

But..alas..


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

Not to be an anal retentive stickler about this. This was NOT always the case. None of the dot upgrades within 3 required a project upgrade. And I'm pretty sure none of the 4.0.x upgrades required a project upgrade either. Only from 4.0 to 4.5.

And 5.0.1 to 5.0.4 - did those require an project upgrade? I'm thinking no...not 100%.

It's really only been the recent. 5.1.x and now 6.0.x that requires a project upgrade and that is a bad trend.

Chi-Ho Lee
Film & Television Editor
Apple Certified Final Cut Pro Instructor

yeah i remember the lower dots being backwards compatible. like 4.5 and 4 obviously weren't but 6.0 and 6.0.1 were etc. I thought the 6.0.2 not working with 6.0.1 was somewhat of a big deal...

anyway, no big deal, we got her XML exports this morning, just held us up a bit...

Well, I cannot attest to 4.0 upgrades. I started with FCP 3...and all the dot upgrades and didn't need to share, so I don't know about those. Then I skipped the horror that was FCP 4.0 and went right to FCP 4.5. When I was using FCP 5, then 5.0.1, 5.0.2 and 5.0.4...EVERY TIME I opened a project it asked to upgrade it to the latest version. And when that was done, you couldn't go back. That was why I had FCP 4.5, 5.0.1, 5.0.2 and 5.0.4 all on my same system...so I could open one version and not have to worry about getting it back to the client or other editor.

The only time I wasn't asked to update the project file was when the other editor was on 5.1.2 and I was on 5.1.4. I was surprise, but worked on it, then sent it back, and he opened it fine.


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

With there not being a major upgrade at NAB, perhaps the Pro Apps team is doing some serious code rewriting to address some of these old issues. Or imagine how much time they would have if they didn't need to support a new HD codec every 6 months.

Chi-Ho Lee
Film & Television Editor
Apple Certified Final Cut Pro Instructor

yeah, used to be the dot updates were mainly compatible.
now they're mainly un-compatible.

moral is: never say never.

a lot of modern updates are adding support for new formats, i wonder if that's the deal-breaker with compatibility?


nick