Apple, please create an XML utility to provide access to old Final Cut Pro 7 Classic projects

FCP7 is dead with the new MacOS ships so a simple utility to extract an XML from a FCP7 projects seems an easy route to go

Apple should create and provide a free XML extraction tool that can look into a Final Cut Pro 7 project file and export an FCP7 XML of the selected sequences

The internet has been abuzz with what is finally officially official: Final Cut Pro 7 (and your old Final Cut Studio apps) will not run on your Mac after you update to the upcoming MacOS High Sierra. This should be a surprise to exactly no one as an application last updated around 2009 and subsequently replaced by another product of the same name could never be expected to run forever.

One question is what do Final Cut Pro 7 users do now?

The easy answer is to move to another NLE. Final Cut Pro X is the Apple path forward though it’s an entirely different NLE that, while very powerful, requires re-learing a lot of old habits. And some of those things are for the better. Adobe Premiere Pro CC is the lateral move that provides an interface similar to FCP7 while adding tons of modern features and cross-platform compatibility. Avid Media Composer is the Hollywood industry standard that can edit anything you throw at it and provided a free version you can try and see if it’s for you.

Those are the big three NLEs but there’s still a lot more choices that include DaVinci Resolve which features an ever growing set of advanced editing tools or MAGIX Vegas Pro if you want to move to PC and really think different.

Another easy answer is to freeze a Mac workstation that is currently launching and running Final Cut Pro 7 and never update that OS beyond what is working now. That could be a bit of a financial investment depending on your situation as you’d most likely want a new Mac that is upgradable into the future. An eBay or local classified search could find such a freezable workstation as well.

Those are the easy answers to the obvious question. But another, equally important one is this:

What should Apple do now that Final Cut Pro 7 won’t move forward?

The easy answer to this question is Apple shouldn’t do anything more than inform users that FCP7 won’t launch on the upcoming OS. And they have done just that with a letter to some registered FCP7 owners.

But, believe it or not, there is still a lot of editing that is happening on FCP7.

I honestly think there’s more that we realize and while it might be hard for many of us to believe there’s a number of reasons for this. A working FCP7 workflow and infrastructure that gets the job done means there’s little financial incentive to update hardware and retrain editors. Years and years of legacy projects that still have to updated means it will take time and money to move to another platform (that’s the case with some of the FCP7 that I still encounter). And a fear to move to another tools means you’ve got an editor who just doesn’t want to leave the familiar.

Apple should create and provide a free XML extraction tool that can look into a Final Cut Pro 7 project file and export an FCP7 XML of the selected sequences. Even if it only exported one sequence at a time the post-production community would take it.

If there is some internal reason Apple couldn’t create such a tool then they should bless a third party developer to create such an app and give them the access to reach into an FCP7 project file. Intelligent Assistance is the obvious choice here as they know more about FCP XMLs than anyone in the business.

A FCP7 project XML extraction utility is the answer for those of us that might need access to an FCP7 edit in a High Sierra future. I have to admit though my gut tells me that a lot of people who think they might need this tool will end up not ever needing it (myself included) but there are those who will. Charging a modest price for such a utility isn’t out of the question as most editors needing to get back to an FCP7 edit in the future will probably be billing for that need.

So we, the former and current Final Cut Pro 7 post-production community at large, ask you Apple, to please create, provide or allow to be created some kind of XML extraction utility for Final Cut Pro 7 project files. You post-production customers will appreciate it.

Was This Post Helpful:

0 votes, 0 avg. rating

Share Our Article

Scott Simmons was born in rural West Tennessee and didn't really realize that movies and tv had to be made by actual people until he went to college. After getting degrees in both Television Production…

Leave a Reply

25 Comments on "Apple, please create an XML utility to provide access to old Final Cut Pro 7 Classic projects"

newest oldest most voted
Notify of
Andy Field
Andy Field

Actually Automatic Duck has some great free translators from most of the big NLE’s But Hey, Adobe – why don’t you do this – Most FCP7 editors and aficionados made the switch to Premiere, not FCP7……Adobe could create that automatically import and FCP7 project application and grab some new faithful fans.

Stuart Blake
Stuart Blake

Oh puh-leeeeeeze!
Spend a whopping TEN BUCKS for XtoCC and just STOP WHINING already! For anyone with half a brain and actually MAKING MONEY editing this is a complete NON-issue. Sorry if I can’t muster ay compassion for doofus luddites that still can’t (literally!) get with the program. Why the **** could someone like that even be interested in updating their OS to begin with?? Makes absolutely ZERO sense, it’s just another bs excuse to lament like a 12 year old.

Guess I’m not PRO enough. *facepalm*

I truly agree. FCP7 is the past. But editors and producers who use it in a daily basis are not the past. Apple stabbed us and does nothing for remedy. There should be some kind of continuation from FCP7 to FCPX since the very first second. But they never implemented such transition. They just treated professionals as idiots: “We know better than you what you really need”, was their motto since FCPX launch. But it is hardly the case in any business specially in B2B industries. The matter is not if X is better or worse than 7. The matter… Read more »
Larry S
Juggling a fine balance between OS and app compatibility has always been a challenge and Apple moving from FCP Studio 7 to the ‘iMovie Pro’ model didn’t help matters. I stayed with Snow Leopard until it became much too old to support and wound up upgrading to Mavericks which still supported the original QuickTime OS integration. As most of my work can be handled in Adobe CC, I bought a used 15″ MacBook Pro (2.7GHz i7, 16GB, 2xUSB3, Thunderbolt, Firewire 800, SD Card reader) and put a 1TB Samsung EVO SSD in it which I partitioned to 250GB Mavericks boot… Read more »