Rolling back to 10.0.3 ??

Hi. I wonder whether there is a way to roll back to 10.0.3 from 10.0.6. Like an idiot I upgraded - not mid project - but 2 projects landed immediately afterwards. I've put up with the random crashes, the importing bug that logs me out and closes all open programs loosing all data without warning and the fact that automatic (audio based) synchronisation no longer works for multicam and all the other weird rendering issues - these have been annoying and added time I could do without but I'm now faced with outputting 36 Mpeg2's from the timeline via Compressor - using multiple compressor jobs with in and out points set, as I have done successfully since 10.0.1 - except that compressor will cope with 1 or maybe 2 before it locks the machine up solid - no response, frozen mouse, hold in power button for 4 seconds. When I reboot the reload FCPX and compressor, even though I saved the (incredibly time consumer to set up) list of jobs in compressor, the job submit fails as it need to be "sent" from FCPx again. Its going to take me a day or so to do these one at a time... I don't even want to think about my next job. Clients not happy with the delay either. I really don't want to have to re-format my system drive and re-image from backup - there's loads of other stuff I would have to re-update as I use the machine for music as well.

Any suggestions gratefully received - rolling back to 10.0.3 would be ideal if it's possible - worked fine for me.

System is Mac Pro 8 Core 2.26, 16Gb Ram, running 10.6.8 with ATI5770. I've read about the Firewire issue but all video is running off internal Raid 0 Pair.

Thanks in advance.

If you have already updated the event's and projects to 10.0.6 there is no way to go back with those projects/events. It sounds like you need to trash the prefs for FCP X 10.0.6 and if you have plugins uninstall them. 10.0.6 should be working very well on your system. Multi cam audio sync should work, works for me, and you shouldn't have weird rendering issues. I'm using an 8 core 2.26 mac pro.

Most (all?) FCPX version upgrades also include database changes to events and projects that occur the first time you run the new version. If you have a backup of FCPX 10.0.3 that includes your events and projects as they existed at that time you could, I suppose, restore from that backup and continue. But... you'd lose all edits and imports done since then. You'd also lose the ability to use any motion based plugins/effects/titles that changed since 10.0.3.

Ah yes, of course, thanks for pointing out what should have been obvious - even if I could go back to 10.0.3 my project would be useless. I supposed I could try outputting a Master file and using my old Mac Pro with 10.0.3 to handle the exports by creating a new project with just the Master file in..

Otherwise I'm screwed...

Thanks for your speedy response guys - it's late, I'm tired and frustrated and I was looking for some clarity..

I must admit, having used FCPX since 10.0.1 I've always sung it's praises - but I'm started to get a little tired of my Macs acting like PCs. When I moved over to Macs for all my music production in 2006 it was amazing - I went from 3 crashes a day to 1 crash about every 6 months. When I started using them for video with 7 it was the same. Now I'm back to 3 crashes a day - if only, make that 5 or more... but on a Mac. I don't care what I work on, Mac, PC, Apple, Adobe. it's only a tool after all. But I hate having to learn new software - it's such a waste of time. Almost as much of a waste of time as my current situation with 10.0.6. (sigh)

Thanks for your help.

I realize this is no help, but it sounds like you've either got a bad FCP X install, or some system issues causing problems. Since .03 was working, maybe a bad install? You can remove it and do a clean install if you want...

support.apple.com/kb/HT5149

This seems to fix a lot of weirdness after an update. Worked for me.

Maybe do the same with compressor? It's a pain, but not too difficult or time consuming. Re-downloading the app takes the most time. For the system, if you haven;t already, run disk utility and repair prefs, then verify the internal drive. If it's finds problems when verifying, you can do this:

Hold CMD-R when booting your mac, you'll enter recovery mode and you can repair your disk with disk utility.

Or... for extra nerdly fun... Reboot while holding CMD-S. After the unix boot text finishes scrolling you'll get a blinking cursor. type in "fsck -fy" exactly, with a space before the dash, (but do not include quotation marks!) then hit RETURN. Let it run, it will either say it's OK, or find problems and fix them. When it's done, it'll tell you and the blinking cursor will reappear. Type in "reboot" (again, no quotes) and hit enter. Your mac will restart. Fun!


Oh... back up everything first! Do it at your own risk etc. If your machine blows up don't blame me!

Every time I update FCP X or Motion 5 I copy the previous versions into a folder for safe keeping. Then update.

The update puts a copy of the last version's databases into an "Old Versions" folder so you can retrieve them later. In face one of my Events has Jan, April, May, & Oct dated previous versions in it.

Then you can go back if the new version screws you too badly.

That's good to know BenB, I had heard before that you would have to back up your events/and projects.

But now I see the folder for older versions in events and project, that's a relief. I didn't update to 10.0.6 until a couple of week ago on one of my computers, due to fear of messing up one of the features I was working on at the moment.