Hang X, dude? Apple is mostly talking about the Player app, but under-the-hood QT improvements could be meaningful to visualists and live visual apps.

Okay, having gotten my rant about Apple’s extreme level of secrecy out of the way (I’m standing by that), we can at least talk about what Apple is saying about QuickTime X, cutting through the marketing as best as possible.

We’ve known for some time that QuickTime X would be a ground-up rewrite – one badly needed. That could have some implications for compatibility, though, which is something to watch. The details are sketchy at this point, but here’s what’s possible to say:

  • X is more integrated with Core technologies. Apple promises that QuickTime X will build on Core Audio, Core Video, and Core Animation. Some of that is to say that the long-in-the-tooth player application itself will work with those technologies more than the underlying QuickTime framework.
  • There’s a new player. It’s about time: QuickTime Player gets an update. The nicest feature here is the slick trimming interface Apple has added. A lot of us use QT Player for quick edits and other tasks, so this is definitely welcome.
  • There’s no more “Pro.” Finally, you don’t have to spend thirty bucks just to make QuickTime Player a useful tool. In fact, you’ll get all of Snow Leopard for that price (if you already have Leopard).
  • Playback is more efficient. Here’s the part that could be most useful to live visual apps. Playback is now more “optimized” and makes use of the GPU for scaling, display, and hardware-accelerated H.264 decoding. Decoding, interestingly, uses the NVIDIA 9400M integrated chip. Most live visual apps already use the GPU for scaling and display, but under-the-hood performance tweaks and decoding features should be good news.
  • HTTP video streaming. You can now stream video live over HTTP, which means you can use a standard Web server like Apache instead of a specialized video server, and you don’t have to open special ports on your firewall.
  • ColorSync for maintaining color profiles on the computer and on mobile devices (well, provided those devices are also made by Apple).
  • Built-in screen recording: You can now create quick screencasts using QuickTime player – groovy. (The Mac is, unquestionably, the easiest platform out there when it comes to making screencasts. Ask any tech journalist or educator.)
  • Quick capture: Capture is improved in QT Player for quick recording – always a handy thing to have.
  • Performance improvements. QuickTime X promises to take advantage of Grand Central Dispatch, the new Apple threading technology, and 64-bit computing for better performance.


The new trim feature may actually wind up being the most useful addition in X.

Of course, what’s missing in all of this is any mention of how this works for developers, how things like color profiles might be interoperable on non-Apple platforms, or what happens to QuickTime for Windows. In typical Apple fashion, this is all about what benefits the Mac and what’s built on the Mac’s own technologies. That’s not necessarily a bad thing – in fact, Microsoft, you are still working on DirectShow, right (cough)? But the more these platforms become proprietary and specific, the more painfully obvious the need for better cross-platform frameworks becomes. Nor does everything always have to be tied up with the OS. Apple’s own emphasis – portability to mobile devices, GPU-native processing – in fact speaks directly to cross-platform, OS-agnostic issues.

Already, many interesting commercial and open source applications are starting to build on cross-platform frameworks like ffmpeg/GStreamer. To call these developer-friendly, though, would be an exaggeration. Part of the problem is that the dark cloud of patent confusion, fueled by the US’ antiquated intellectual property law, casts a shadow over more widespread use of such frameworks.

I think there’s value in creating OS-specific tools, and it certainly makes sense given Apple’s business model. But because we rely on these foundations for art, and because development often extends beyond devices with Apple logos on them, the alternatives are important. Apple had at one point aspired to build across platforms – but the legacy of QuickTime never became that, which is part of why it missed out on Web deployment to Flash and why it could miss out again on emerging trends in development.

Apple is focused – perhaps fairly so – on their ecosystem. But when you see images like the mobile export option, don’t you wonder a little bit about what would benefit your ecosystem?


Hmmm, good thing the only hardware in the world is made by Apple!

At least the good news is, my sources suggest Snow Leopard should be a really nice visualist upgrade for Mac fans – and while there’s nothing I can get on the record, Quartz Composer should continue to develop, too. Stay tuned for fall, the official release, and compatibility info.

More information:



  • Horst Paschulke

    Does "Decoding, interestingly, uses the NVIDIA 9400M integrated chip." mean, it will ONLY support hardware accelaration of H.264 playback on that particular chip?

  • @Horst: Yes, that's how I read it. It appears to be a 9400M-specific feature.

  • Quite Cool I Guess.

    The best new features for me is the 'lack of the pro' and the screen recording is going to be great for teaching, podcasts etc.

  • Pingback: PolyPink » Blog Archive » Quicktime X is what interest me most from WWDC’09()

  • great review. thanks Peter!

  • Gumby

    I notice they've gone for black as the main colour now…WMP Anyone?

  • @Gumby: Actually, I think you mean Winamp. 😉 (WMP isn't black.) Justin Frankel FTW!

  • Gumby

    @ Peter Krin: XP version of WMP is black at the top and bottom, Vista version is the one which isn't.

  • True, true (among the many shade Microsoft seems to choose for its UIs)… but Justin was black before black was cool.

  • QuickTime X is a disaster for developers.

    There is just one hardware accelerated codec.

    If you play content in a 64 bits application if you open an unsupported codec in 64 bits you go through a slow path were a server app is launched and the content is rendered in 32 bits… and performance suffer. There is no way to know if you are on the fast 64 or slow 32 bits lane. Apple engineers said that they will bring more codecs to 64 bits as they move forward but they did not comment on what will be available at snow leopard launch.

    Most of the old QuickTime API is unsupported, basically you can just open play content. By example if you want to get access to the audio of a movie to process it in your real-time video engine it's simply impossible in 64 bits.

    I did switch to ffmpeg since a long time…

  • Pingback: Quicktime X a little more info | Final Cut User()