QT 7.4: Bad for Apple apps too, it seems....
by Dave LaRonde
on
Jan 23, 2008 at 10:28:58 pm
This post falls under the "misery loves company" category, I guess.
Apparently, things are not all sweetness and light in Final Cut Pro Land for those who changed over to QT 7.4. I regard the following thread as a cautionary tale....
QT 7.4 is an utter disaster for AE users, and now it seems to screw up FCP users' work. What the heck good is the stinkin' thing? Better-looking movies on your iPod or something?
Hmmmmm..... a key component in professional multimedia applications that screws up the applications. I guess we found out how Apple REALLY feels about its commitment to professional applications... it's lip serivce, if you ask me.
Re: QT 7.4: Bad for Apple apps too, it seems.... by Martti Ekstrand on Jan 24, 2008 at 8:37:15 am
I've been waiting for DRM to muck up media creation apps for a couple of years now. Maybe Apple will have to split the QuickTime framework into 'consume' and 'create' versions if they are going to keep 'major' media distributors and us creating users happy simultaneously. (The 'create' version lacking the ability to access DRM protected media in any way.) Though I'd prefer if the movie/television industry will realize that DRM will never do what they hope it will do. At least the music conglomerates have started to understand this.
Re: QT 7.4: Bad for Apple apps too, it seems.... by Tim Vaughan on Jan 24, 2008 at 1:33:07 pm
I wonder if that explains why I keep crashing AE when trying to render a movie. My only solution is to render out an image sequence, re-import it, and render it out as a quicktime movie. Then bring it back in to FCP, add the audio layer, and export it again for the 3rd and final time. Need I mention I am bringing in rendered and completed FCP movies into AE, adding text and very minimal FX. Speaking of which, registered versions of Shine and Starglow are rendering out with the red X. I have to restart the app (sometimes the computer) and re-render it again before it catches. WTF? This is happening on both a PPC G5 Quad and an Intel XServe. Nothing like spending an extra 8-12 hours each week on stuff that SHOULD be working.
Motion is looking better and better each day. Only wish it could actually do the same FX as AE.....
Re: QT 7.4: Bad for Apple apps too, it seems.... by Gavin Dunt on Jan 24, 2008 at 2:45:59 pm
This is an unbelievable f**k up from Apple.
The worst upgrade since the invention of the pin hole camera.
Even my HDV 1080p clips won't play back, (yet my 720s do). If they can screw up a basic codec, what else will we find?
Re: QT 7.4: Bad for Apple apps too, it seems.... by david bogie on Jan 24, 2008 at 3:10:09 pm
The QT7.4 threads on apple.com have a common, erm, thread: "We are professionals and we must have backups, clones, and, for video, it is only reasonable that we operate quarantined Macs."
To which I say, "Bullpucky!" I say, "Class action suit!" (Oh, wait, that's what we used to scream at the rat bastards at Media 100 after every update.)
As the foundation of media handling on the Macintosh, Quicktime must be the almighty benign enabler; absolutely non-destructive. Quicktime must never be toxic.
Apple either completely failed due diligence or Apple deliberately released this stupid software knowing it would break After Effects.
bogiesan
This is my standard sigfile so do not take it personally: "For crying out loud, read the freakin' manual."
Re: QT 7.4: Bad for Apple apps too, it seems.... by Tim Vaughan on Jan 24, 2008 at 3:23:09 pm
Not to mention I just found out (after rendering out a DVD or two, encoding and uploading to the web, that QT has unsynced the audio as well. (An aiff file that was exported from FCP, precisely,) and imported directly in to AE to work with the image sequence for final export. This is turning to be a COMPLETE waste of a day, and I'm only 4 hours in..... Nothing like a deadline that keeps being pushed back and making us look bad....Thanks Apple. Really did a great job on this one.
Re: QT 7.4: Bad for Apple apps too, it seems.... by Dave LaRonde on Jan 24, 2008 at 4:20:46 pm
[david bogie]"I say, "Class action suit!" (Oh, wait, that's what we used to scream at the rat bastards at Media 100 after every update.)"
Yup, that's one way to handle it.
But since you broached the topic of M100, there's another way: don't buy another FCP system when it's time for the Big Upgrade at the shop. That's what you did in Boise, and that's what I did in Cedar Rapids.
