Quote:
Originally Posted by k2director
Its real issue is performance -- it slows down to a crawl as projects expand beyond a couple of minutes, and that's on top-of-the-line gear.
Yeah, I noticed this. Motion does this too and it makes sense now that they share the same render engine. FCPX shouldn't really need to render so much though as it's not an effects package. I can see a convergence of the two apps down the line and if that happened, it would explain a lot.
Quote:
Originally Posted by charlituna
is the issue really that some people just don't like change
Nope. If you replaced a filmmaker's Arri Alexa with a Canon 5D, you could ask if their reason for moaning is just because they don't like change and they will reply 'nope'. An experienced filmmaker can probably get good shots on both but they require different workflows and different experience and that time investment is only justified if the change allows them to do a better job. Final Cut Pro X hasn't really demonstrated that it allows experienced editors to do a better job but it did make some things worse, so for the time being, I'd say people are entirely justified to migrate to a platform that works better for them.
There's a period of time that a piece of software goes through before it is production ready. That very rarely comes with a version 1 product, which is how the FCPX designers refer to it. They should have been aware that the film industry wouldn't adopt a product that isn't production tested because the costs of failure are high.
There's a simple test to do, we just take away Apple's professional milling tools for their hardware design and replace them with a more modern machine designed for low-volume use. Then we'll see who complains when they can only make 5 iPhones a day. Do as you would have others do unto you.
Quote:
Originally Posted by zoffdino
requirements for HFS volume (why??? Lightroom can work with any disk format)
This is probably related to metadata in some way. Attributes stored by Aperture are probably accessible from other parts of the OS.
Quote:
Originally Posted by Dick Applebaum
I listened to Raudonis advocate an open mind for FCPX, on several occasions...
He did not appear as one who could be (or needed to be) bought.
Yeah, he apparently switched from Avid originally years ago simply because their products didn't cut it:
http://www.avid2fcp.com/switcher-stories/mark-raudonis
I guess you just have to switch the companies round now and it's the same story:
"Looking back now to my switch, Im reminded of Robert Frosts poem, The Road Not Taken.
I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I
I took the one less traveled by,
And that has made all the difference."
The biggest investment would have been hardware originally, which at least isn't the case this time round.
Quote:
Originally Posted by TenoBell
What makes you think Apple's innovation stems around its pro apps?
I'd say most of Apple's recognised software started life at the top and worked down, not the other way:
Logic -> Garageband
FCP -> iMovie
Shake -> Motion
It's better to have more capability than you need. If you have less, you have no choice but to go somewhere else. Consumers also tend not to push boundaries. Look at the Think Different ad. Are any of those people average Joes sitting in their underwear until early afternoon? No, they are people who had a passion for what they do and they push the limits to do something exceptional. That's what professionals do. That's why Shake had a scanline/tile renderer because older hardware couldn't cope, same deal with Renderman. They adapt software to do the best job.
Quote:
Originally Posted by Suddenly Newton
You guys are trying to spin this as "pro community abandons FCP sinking ship". But FCP was never the reigning big dog to begin with.
That is a very important point but there is still a high-end community on FCP that this story demonstrates that will drift back to Avid.
Quote:
Originally Posted by FrreRange
"Reality TV heavyweight" - ROFLOL - producer of totally mindless crap!!! And this is a bad trend? Hardly.
It's not the content that's important really but the workflow. If you work on a Hollywood film, they will generally have massive budgets and the best people working on it and they work to a screenplay. If you think that Reality TV is bad, just think that's the stuff that made it through the edit. They could easily have 10 hours per day x 5 days per week x 3 cameras = 150 hours of footage to work through for a half hour show.
Quote:
Originally Posted by AdamC
The problem with a lot of professionals is if it is not complicated it is not 'pro'.
I disagree. Professionals like control and with control comes complexity. You could walk into a aircraft cabin, look at all the switches and dials and proclaim that the complexity is superficial and can be replaced with a single joystick for up/down/left/right but when you hit a problem, you have no means to fix it yourself i.e you are not in control. Professional software almost has to be an API to be production ready and Apple didn't even provide that initially in the form of the XML toolkit.
Simplicity and control aren't mutually exclusive of course as Mac OS X itself very readily demonstrates.
Quote:
Originally Posted by Jensonb
Avid was number 1 anyway, so Apple clearly just figured "what the hell"
That does seem plausible and Apple had to overhaul FCP. It did a good job but it was an ugly piece of software.
Quote:
Originally Posted by Aiwaz418
Agreed, but I would also like to add that I have cut two features and a pilot this last year with FCP7 on my MacBook Air, eschewing not only FCPX, but the Mac Pro, and it was a wonderful experience, but one that would have been impossible with the latest software revision due to the professional workflow involved.
The phrase 'professional workflow' doesn't highlight the problems specifically but I expect would include:
Changing the asset management from using any amount of scratch folders for media and rendering to an Events system that has great difficulty relinking media.
Changing the native editing engine to one that transparently transcodes everything to ProRes regardless of the change made to the media.
Limited import/export options for frame sizes and rates and requiring Compressor for flexible export.
Limited import/export for external processing like audio reworking and effects, partly fixed in recent versions.
I expect that Apple is right now hearing what all the problems are and they have worked to fix some of them. They have said openly they are trying to cater to the industry so only a few scenarios can happen:
- they ignore the requests and they are dropped
- they fix the problems and they manage to maintain some foothold in the industry with a tarnished reputation
I don't see there being a mass migration to an alternative package because they all suck in one way or another and they are all expensive so I expect the latter will be the outcome. If the Python API comes to fruition, that will open up some interesting possibilities.