Slashdot Mirror
Apple QuickTime DRM Disables Video Editing Apps
An anonymous reader writes "According to numerous posts on Apple's discussion forums (several threads of which have been deleted by Apple), as well as a number of popular video editing blogs, Apple's recent QT 7.4 update does more than just enable iTunes video rentals — it also disables Adobe's professional After Effects video editing software. Attempting to render video files after the update results in a DRM permissions error. Unfortunately, it is not possible to roll back to a previous version of QT without doing a full OSX reinstall. Previous QT updates have also been known to have severe issues with pro video editing apps."
Don't use Quicktime.
We suffer more in our imagination than in reality. - Seneca
Never upgrade a production box without first upgrading on a test system. And NEVER NEVER upgrade mid project. If you're an individual and not a post production facility, test the upgrade on a separate partition or physical volume.
Or wait until everyone else gets the kinks worked out.
This is all common sense, and it's really not that hard. But you'd be surprised at the number of otherwise intelligent people that do stupid shit like upgrading a key component in the middle of a project. And if you absolutely must, do it on a cloned volume with backed up data.
It's not offtopic, dumbass. It's orthogonal.
Quicktime is in fact Mac OS's Audio and Video subsystem: http://en.wikipedia.org/wiki/Quicktime#QuickTime_framework
It's much more likely that updates to the underlying API are what's breaking After Effects etc, than updates to the media player bit.
Apple is notorious for stuff like this. They have all sorts of shared components (like QuickTime, FxPlug, etc) that they update independently from each other. I develop for Final Cut Pro and Motion, and the last time I installed a beta for them, they installed a component which broke QuickTime. Now I can't launch the QuickTime player, iTunes, iMovie, or any other app that relies on certain QuickTime codecs, without them crashing immediately. Recent updates to QuickTime haven't fixed the problem either. And of course you can't uninstall anything without reinstalling the OS. Look around - there are plenty of people asking for the "Quicktime deinstaller" which does exist but has its own problems.
Between stuff like this and having to essentially port my code every time they release a new version of OS X, and the constant switching between processor architectures, APIs, UI design requirements, etc. all I can say is it REALLY sucks being a Mac developer.
Full discussion on http://discussions.apple.com/thread.jspa?threadID=1342677&start=30&tstart=0, which makes the summary quite lame. The fact that subtitles also broke with QT 7.4 does say something though..
Actually. Yes you can. It's not as simple as a quick "Roll Back this install" but by no means is it as impossible to revert as some programs in XP.
Step 1: Download 7.3.1 for what ever version of OSX you're using. http://www.apple.com/support/downloads/
Step 2: Copy the installer package to the desktop.
Step 3: Right click and "Show Package Contents", open "Contents"
Step 4: Open "QuickTime_Leopard.dist" in a text editor (Not sure what it is called in other versions.
Step 5: Scroll down to "newerQuickTimePresent()" (All Apple pre and postflight scripts are just that, scripts. You can write them in bash, perl, ruby, python, php, etc.)
Step 6: Change "return false" to "return true". Or Comment it out, etc
Step 7: Install.
Quicktime is Apple's underlying media subsystem. It's not bolted on. The Quicktime Player is bolted on to wrap the functions and play videos. The Quicktime Pro program that they sell enables editing. There is no lock-in, because anyone can provide a media layer, and anyone can access Quicktime. Even Realbasic Apps can bundle Quicktime and do whatever they want. You could write your own media player with it's own DRM and send content to Quicktime (although hackers would grab the unencrypted layer inside of Quicktime).
There should be a way to roll-back the Quicktime update, because the Package should limit changes to the Quicktime Framework and Quicktime Player apps, but I don't know that there isn't Quicktime code everywhere. It should still exist, but it's not a media player, and it's not vendor lockin.
MS gets nailed for Vendor lock-in for bundling not core programs and not letting them be removed. On a Mac, if I don't want Safari, Quicktime Player, iTunes, etc., I just drag the Application to the trash and I never see it again. I still have the underlying OS Components of WebKit (I think that it's an OS Level Framework now) and Quicktime, but I don't have the applications. Microsoft REFUSED to allow the deletion of IE/WMP, and when forced by the courts to provide a version without them, removed the underlying OS components to break Windows.
That's why MS's bundling behavior was problematic, and Apples not so much. Apple lets you remove applications you want without hosing the OS. MS refused to let you remove the application without removing the OS Components, and you NEED media capability even if you don't want WMP, and you NEED the HTML component, because many applications use it once you make it a standard OS Component.
Just to clarify: It's not the quicktime player that is the issue, it's the quicktime subsystem that is integral to AfterEffects and other pro video applications. Substituting VLC will not solve this. The issue really is much more serious. Bad fuck up on Apple's part. However, I don't think this is really going to bother most video professionals, because they will have waited to upgrade (to see what potential problems might crop up), or they're testing on non-production boxes.
It's not offtopic, dumbass. It's orthogonal.
You're missing the point. There's this thing called the Quicktime Player. That's not at issue here.
What is at issue is this other thing called Quicktime. It's a technology that provides video services for OS X and applications. Applications such as AfterEffects, Final Cut Pro, etc. and iTunes. A change in this subsystem to support a new feature in iTunes has fucked up support for AfterEffects. Apple fucked up, no doubt about it. But the sky isn't falling and this is not even comparable to MS embedding a browser in their OS to kill Netscape. Not even close.
It's not offtopic, dumbass. It's orthogonal.
Okay, 60 seconds reading the referenced link in the articles would show that it is NOT a permissions problem that can be fixed with CHMOD. The files in question will open fine with the iTunes player but not with QT.
I see the Apple happy moderators choose the more convenient and not the real "insightful" route of modding you up in defense of Apple instead of actually reading about the problem. Moderator thinking, "Oh this person must be right, there is no way Apple could have messed this up."
http://discussions.apple.com/thread.jspa?threadID=1342677&start=30&tstart=0
I learned this lesson well in 2005 when I gleefully preordered and upgraded to Tiger only to find out that After Effects 5's non-standard use of Quicktime APIs resulted in highly unstable audio with the new version of QT that came with the OS. Just scrubbing video back and forth inside the app would produce Quicktime errors, and the only way to get a complete render was to render without audio and add the soundtrack in afterward.
I don't trust Adobe or Apple to be in sync on this stuff.
Your mind is clear / The things that you fear / Will fade with how much you / Believe what you hear
Looks like most of the issues are fixed by this released today. http://www.adobe.com/support/documentation/en/aftereffects/Adobe_After_Effects_CS3_8_0_2_Read_Me.pdf
Some people have very short memories.
Recursive: Adj. See Recursive.