Watch out! 10.0.4 upgrade warning…

[Bill Davis]

Since very few people are reporting anything like this, I doubt it’s a general problem.

One thing I did note was that as with every X upgrade, the changes under the hood have to propagate throughout all your projects and connections. So there will be some beach balling that will occur while X does it’s housekeeping.

The WORST thing you can do is constantly get frustrated and dive out before the software can run it’s upgrades and organize everything.

Be patient. Sure, if 20 minutes goes by and you don’t see any progress – unless it’s a massive project – then you should feel free to dive out and re-start.

Then, in my experience the best path is to start with just the central system and your internal drives. Let X “find” it’s first tier assets and pipes. Then add external storage as necessary, letting X “discover” and re-link to those as needed.

In my case, since I store ALL my work on external drives, I can reboot into X with just a couple of small “main drive” timelines that are very small and easy for X to load – then I bring the big projects back via drive attachment one at a time.

This has always worked really well for me and my overall system doesn’t get bogged down with X trying to communicate with and re-link to so many projects – any one of which might have missing elements, renders needed, or other processor heavy issues that can bog the upgrade process down.

FWIW.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[David Battistella]

Thanks Bill,

I’ve actually followed that exact procedure and everything is stored externally. I’ve left the software for over an hour thinking it was exactly what you describe so well.

I’ve provided feedback to apple and will continue to troubleshoot and report back in this thread.

David

______________________________
The shortest answer is doing.
Lord Herbert
https://vimeo.com/battistella

[Steve Knattress]

On past upgrades a problem I had was that x decided that it did not like my referenced mp4 files ( from a POV.HD head cam.) QT was fine with them ( as was every other editing application I possessed including the old x and fcp7)

I started by just running clean drives to make sure that this version of x successfully ran.

I then connected drives and let fc do its thing. At this stage I got beach balls, errors and crash, which could be duplicated by apple support, after I had sent them a problematic file

Unfortunately i could do no more until the next update, when the files were recognised, other than convert the files outside of x and then import the converted pro-res files.
I did not want to do this as I did not want to duplicate all of my rushes files and bloat into prores.

Steve

[David Battistella]

here is a breakdown of all that I have tried.

I think I have this narrowed down to a corrupt project file which can not be updated to 10.0.4.

I just need to get an XML out of FCP X and import the XML into the new version. My problem now is that both of my machines have been updated to FCP X .0.4 (I know, I can commit a boneheaded move once in a while)

I have it narrowed down to one corrupt project file (unfortunately the latest version of the cut).

Tried Digital Rebellion toolkit
Tried ONYX
Tried backup versions of multiple projects.
Tried repairing permissions, etc.
Tried to install and uninstall KONA 3 drivers.

Let’s put it this way. It’s been a troubleshooting kind of day. All of my projects open in 10.0.4 except the current version of the latest thing I am working on.

If anyone wants to open this file for me in FCP X 10.0.3 and export an XML and get that to me, I would appreciate it.

David

______________________________
The shortest answer is doing.
Lord Herbert
https://vimeo.com/battistella

[Bill Davis]

David,

Thanks very much for pursuing this.

This is precisely the kind of thing that helps the entire community solve real problems.

It seems as if with the new database structure, changes in X have to be applied to the metadata of the code for all the assets that are linked to a project. When the software gets to a bit of code that is “non-standard” (i was going to use the term “corrupt” but with so many camera codecs, wrappers, and alternatives, I’m guessing that it doesn’t have to necessarily be broken, just non-sensical to what X is looking for) the program can hang up trying to figure out what to do.

I think this is an offshoot of the new era where people want to throw so many alternate formats into a timeline, something that is beneficial to all, but not so easy for the software to handle.

I expect digital editing was easier when every timeline expected the editor to be working in a single, known format.

Industry groaning pains which I suspect will sort out over time.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[David Battistella]

Thanks Bill,

I’ll keep posting as I work toward a solution.

Hopefully I can get an XML out of the sequence that was working in 10.0.3 so I can get this film finished.

David

______________________________
The shortest answer is doing.
Lord Herbert
https://vimeo.com/battistella

[Eric Santiago]

David thanks for this post and your patience 😉
Finally a FCPX problem that didnt lead to another breakdown in net society 😉
I too have updated but not found any problems.
I did however update only 2 of the 5 systems Im using FCPX on.
Wish you luck!

[David Battistella]

Eric,

Would you consider trying to open up the 10.0.3 version of the project and send me an. XML if you can open it?

It sitting up on a website where it can be downloaded.

Anyone?

I really would love to just get my last cut back up and running.

Thanks

You can get my email in my contact page.

David

______________________________
The shortest answer is doing.
Lord Herbert
https://vimeo.com/battistella

[David Battistella]

Reporting back again, it seems pretty certain that what I am dealing with here is a corrupt project file that for some reason will not allow itself to be updated to 10.0.4.

The files opened fine in FCP 10.0.3 until the update.

Every other project has come across painlessly, going right back to the very first project I ever did and wrote about here on the COW just one day after the public release.

The only thing I can think of is that this was the only project I ever used “Auto remove silence” on and it seemed to put gremlins into the system.

Now, I am just hoping I can get it opened in 10.0.3 and get an XML out of there so I do not have to rebuild a 25minute film from memory…

David

______________________________
The shortest answer is doing.
Lord Herbert
https://www.davidbattistella.com

[Steve Connor]

Have just mailed you David, I have a 10.03 partition here

Steve Connor
“FCPX Professional”
Adrenalin Television