-
Installed 5.1.3 – Now Project is Corrupted!
-
A lot of folks out there seem hell bent on getting the latest update to everything the second it comes out.
The biggest thing I learned for my years as an I.T. consultant, you absolutely NEVER upgrade your software unless you have to.
Like if its not broken DON’T fix it.
I’ve seen a lot of folks learn this the hard way and its not pretty.
-
[Borjis] “The biggest thing I learned for my years as an I.T. consultant, you absolutely NEVER upgrade your software unless you have to.”
Sorry, but by and large that’s a pretty antiquated attitude. We’d still be with Windows 3.1, 98 or 2K and Mac OS9. First of all, with all of the security updates and OS-related issues, much of modern software is interrelated. This is especially bad in Apple’s case because they aren’t very forthcoming with what their fixes really entail. So for instance, it is quite possible to make some other update that breaks code in a supposedly unrelated application. This has happened at least once with Windows Hot Fixes and Avid. In the case of Apple, you are safest keeping all apps, QT and OSX as near to current as possible.
Second, someone has to go first, otherwise you never know what the issues are. There are things in 5.1.3 that did fix other problems. I have encountered them. In my case I upgraded with nothing critical happening, so I take my chances.
Your attitude blames the user. That’s unfair. FCP users have a right to expect that Apple would have at least passed a beta by key 3rd party developers and that doesn’t appear to have happened. This just leaves us a bit more leery for the next time. Just remember that software is the only thing you typically purchase that is already broken when you buy it. You pay for the option of fixing it.
Sincerely,
OliverOliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Sorry, but by and large that’s a pretty antiquated attitude.”
Not really, I never recommend anyone update their software unless they check with all 3rd party software / hardware vendors before updating.
[Oliver Peters] “Your attitude blames the user. That’s unfair. FCP users have a right to expect that Apple would have at least passed a beta by key 3rd party developers and that doesn’t appear to have happened.”
Apple NEVER gives out beta software / hardware to ANYONE, especially third party vendors. Witness the third party vendors who lined up at Apple Stores the day the Mac Pros were released so they could finally get to work on one.
Apple is notorious about holding software / hardware from anyone and everyone on these forums are wise to wait on any Apple FCP update before installing. Apple might release the upcoming specs for hardware / software but that’s not the same as actually getting to use the gear.
So yes, it’s up to the User to make sure that their machine / software / 3rd party hardware is ready for the update BEFORE they allow it to proceed.
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
[walter biscardi] “So yes, it’s up to the User to make sure that their machine / software / 3rd party hardware is ready for the update BEFORE they allow it to proceed.”
And how do you propose doing that until someone goes first? Bear in mind that on some FCP systems, 3rd party vendors might be 20+ companies by the time you factor various plug-ins into the equation. Even if Apple didn’t hand out betas to 3rd party developers, if they had run a build with even one of the popular packages installed that involved custom UIs, they would have hit the problem internally themselves. Bottom line is shoddy QC.
Sincerely,
OliverOliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “And how do you propose doing that until someone goes first?”
You’re welcome to go first, I don’t do any updates until at the very least AJA says they are good to go with the update.
[Oliver Peters] “Even if Apple didn’t hand out betas to 3rd party developers, if they had run a build with even one of the popular packages installed that involved custom UIs, they would have hit the problem internally themselves. Bottom line is shoddy QC.”
Who knows what they do. It’s obvious with the entire build of Final Cut Pro 5 it’s been the buggiest version of the application ever released so it’s obvious their beta testing / quality control is not all that great right now.
Another reason to wait and it’s ultimately the User who has control over their own computer. Unless you’re having a real problem with your system, leave it alone, let someone else take the plunge and report back.
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
It is up to the user to be wary.
I install the updates on my laptop to test, not my main machine. And I am in the habit of keeping older versions of the application, in case something doesn’t work…which happens a lot.
I too do not update on my main machine until I get the ALL CLEAR signal from AJA…if I had a Decklink card, I’d wait for word from them….or MATROX.
It is a shame that Apple doesn’t let third party vendors in on this…that would solve issues. But, until they do, caution is the word…
Shane
Littlefrog Post
http://www.lfhd.net -
[Shane Ross] “I install the updates on my laptop to test”
Shane,
This is exactly what I did.
Walter,
With all due respect, considering all your issues with FinalTouch, I think we’re all in the same boat 😉
Now, I attempted to get back to FCP 5.1.2 and that’s not fixing the problem unless I do a total restore and quite frankly it’s not that important to me. My guess is this is buried in the FxPlug architecture somewhere and unless you reinstall the whole Studio you’re not going to fix the issue. AE plugs, like Synthetic Aperture retain their custom UI features, but FxPlugs do not. Moving to 5.1.3 altered something deep, which isn’t getting fixed by reinstalling an earlier version of FCP. That’s probably why the original poster couldn’t get to an uncorrupted project.
Sincerely,
OliverOliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up