Monday
Jan212008
Thanks again Apple
Monday, January 21, 2008 at 3:53PM Apparently the new DRM-checking routine will stop your After Effects render after ten minutes because it thinks you're trying to hack your own file. And since Adobe finds out about Quicktime updates the same day you and I do, here we are.
Ahem.
Someday: The ProLost Quicktime rant from hell. But not today. Because today it goes without saying.
Reader Comments (7)
This is proof that QuickTime needs to be forked. One version needs to deal with DRM and playback features that everyday people need. The other version should support Pro Application features. Splitting Quicktime this way would allow professionals to do they're jobs without fear that some new feature will break their workflows.
That would be sweet John!
Right now, as my other comp is rendering an After EFfects Scene I realize that it's good not to update software as I'm working on a movie. As I always do.
I wonder if this is just rendering out Quicktime movies (or from comps featuring Quicktime movies)... Or just on Mac?
I upgraded to QT7.4 the same time everyone else did (i.e. through Quicktime's automatic updates) on Windows and I've just rendered out a couple of movies from AE, one TIFF image sequence and one MPEG2-DVD, neither of which used any Quicktime. Both took over 10 minutes to render, but both worked just fine.
Bah. You should be rendering to image sequences anyway. :P
Don't update to 7.4? But 7.3 has major security issues?
Nice decision: have crap or unsecure crap?
Who is this Mr. Quicktime anyway?
And who is this Mr. DR. M?
I don't trust Doctors.
Cheers
:-)
Let's put it that way: having Final Cut Pro consume proper, vanilla image sequences would have been a true boost for the platform. Quicktime was good back in the day, but it just totally sucks when you need reliability and consistent output. Instead of image sequences, they introduce another Clipped HD Compression From Hell (aka ProRes). I actually miss a proper conform app for the Mac.