-
Is FCPX the Othello of NLEs?
-
[Oliver Peters] “I think Apple simply learned from RED. Buy FCP X and you’ve signed on to be a permanent beta tester ;-)”
It’s the way of the Professional electronics world. Firmware updates are not only bug fixes but feature releases that were rolled out as features ready to go.
-
[Oliver Peters] “I don’t believe they will. Look at the other current Apple software under Lion, such as Pages/Numbers/Keynote/TextEdit. There is no Save/Save As. There’s an initial Save A Version and Duplicate. I believe the FCP X design is very consistent with that.
“Exactly, apart from they stupidly haven’t actually implemented “versions” yet
“My Name is Steve and I’m an FCPX user”
-
[Steve Connor] “You mean you expected a piece of version 1.0 software to be more stable than a version 6.0 one?”
Version 6 of Avid Media Composer and Symphony is also a from-the-ground-up 64-bit rewrite. It’s just that they duplicated the design and interaction models of the existing software. It’s definitely new code.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Version 6 of Avid Media Composer and Symphony is also a from-the-ground-up 64-bit rewrite. It’s just that they duplicated the design and interaction models of the existing software. It’s definitely new code.
“Good point, if it’s correct.
“My Name is Steve and I’m an FCPX user”
-
[Steve Connor] “Good point, if it’s correct.”
Huh? I’m running it now. There are a number of differences caused by the change to 64-bit, such as filter compatibility and some of the things tied to QuickTime, which is still a 32-bit engine. So yes, it’s correct. Why not poke around on the Avid forums if you don’t believe that.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] ”
I don’t believe they will. Look at the other current Apple software under Lion, such as Pages/Numbers/Keynote/TextEdit. There is no Save/Save As. There’s an initial Save A Version and Duplicate. I believe the FCP X design is very consistent with that”But how can that possibly work?
Any serious project has, literally, countless steps. Are fcpX editors supposed to keep a note pad or calculator running while editing, or just play the lottery that when they accidentally cut that 12 hours of work and realize there’s no way to redo the mistake?
It’s like developing the new generation of fighter jet and replacing the radar and GPS with a big magnetic compass – easy to use but a bit too risky for critical missions.
-
[Steve Connor] “f you don’t want major bugs and you want stability, NEVER use a version 1.0 product of ANY software, FCPX is a complete code rewrite, what did everyone expect? It will be at least a year if not more before it reaches even a basic level of maturity.
I’m using it, knowing full well there will be issues, as it happens I think it’s surprisingly stable and usable for a first release.”
I expected bugs, just not quite as many show-stopping ones.
FCP is ” surprisingly stable and usable” until it isn’t.
I place a title, blade a compound, or add one too many markers and the UI becomes sluggish and the project unstable.
I was an iPad’s breadth away from upgrading to a new iMac until I read about people on the latest and greatest hardware having similar problems.
I don’t even mind paying to participate in a public beta program but a little more guidance from Apple would be nice.
Compare this with the release of Lightroom, when Adobe ran a free public beta, and I could listen to podcasts featuring Thomas Knoll explaining the intricacies of the exposure algorithm.
-
[Oliver Peters] “Huh? I’m running it now. There are a number of differences caused by the change to 64-bit, such as filter compatibility and some of the things tied to QuickTime, which is still a 32-bit engine. So yes, it’s correct. Why not poke around on the Avid forums if you don’t believe that.
“No, I meant that If it WAS a complete rewrite, which it appears to be. However as I understand it they have been rewriting elements of it for the last couple of versions but only compiling as 32 bit which has given them some extra time to test the code, which is why it’s relatively stable.
“My Name is Steve and I’m an FCPX user”
-
[Jim Giberti] “Any serious project has, literally, countless steps”
The design isn’t that you stop after 500 undos. It’s SUPPOSED to be the LAST 500 undos. If it works correctly, then the oldest is flushed out. Same as the 99 undos of FCP 7. As far as steps and versions, you need to duplicate your project for alternate or in-progress versions.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Steve Connor] “as I understand it they have been rewriting elements of it for the last couple of versions but only compiling as 32 bit which has given them some extra time to test the code”
I believe that’s correct. That’s still less time than Apple has been working on FCP X.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up