Slashdot Mirror
QuickTime 7 Released, HD Movie Trailers Available
mmarlett writes "The long-anticipated release of Tiger has brought with it QuickTime 7, which was available on Thursday separately from Tiger, but not yet available for anything other than Mac OS X. That's to be expected, but as I was checking out the recent trailers for Batman Begins and Serenity, I realized that they (along with many other things) were also available as giant H.264 HD Quicktime files that require QuickTime 7. Makes me wish I had that 30" display."
Recommended Hardware Configurations for H.264 High Definition (HD) Playback
To play high definition video, a large amount of data must be processed by your computer. A powerful system will deliver the best playback experience.
For 1280x720 (720p) video at 24-30 frames per second:
* 1.8 GHz PowerMac G5 or faster Macintosh computer
* At least 256 MB of RAM
* 64 MB or greater video card
For 1920x1080 (1080p) video at 24-30 frames per second:
* Dual 2.0 GHz PowerMac G5 or faster Macintosh computer
* At least 512 MB of RAM
* 128 MB or greater video card
For much more excellent detail on Quicktime 7, go read the relevant section of John Siracusa's in-depth Tiger review for Ars Technica. From his description there, Quicktime 7 seems to be a radical & long overdue redesign of Quicktime that wouldn't be possible without some of the architectural changes that OSX 10.4 has delivered, particularly Quartz 2D Extreme and CoreImage. To quote from Siracusa's Quicktime analysis:
The changes to Quicktime 7 seem to be drastic enough that I'm a little surprised that they were able to get QT7 to work at all on previous versions of OSX, not to mention Windows. Presumably, the new APIs had to be at least partially encapsulated and backported to Panther and will have to be crossported to Windows. That, in turn, has me wondering if it will be possible to use Quicktime to write software on Panther or Windows that takes advantage of these new tools -- probably not, but it's tantalizing.
Anyway, Siracusa's reviews of Panther and previous versions have been consistently excellent, going way more in depth than any other reviews of the system have done. These articles should be considered required reading for anyone that wants to really understand OSX.
DO NOT LEAVE IT IS NOT REAL
I would like to thank the people at Apple who did not do the idiotic thing and run this at 1960x1080 (1040i) interlaced, which looks damn awful on most computer screens.
If the original source is film (which it almost always is), then it is a relatively trivial operation to turn 1080i into 1080p which looks fantastic on most computer screens. I do it every day watching brodacast HDTV from NBC and CBS which are always 1080i.
When information is power, privacy is freedom.
But they play on my laptop pretty well. There is no reason Apple couldn't start releasing trailers in 480p (720x480) that would play on most recent Macs without a problem.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
For the rest of the conversation I will assume that Apple changed the qt format, as I never had any problems playing quicktimes before.
QuickTime is a container format, that can, er contain many different codecs. In this case, the codec in question is H.264, which is currently only available in QuickTime 7. Same format, new codec.
Lastly I would like to ask the Mac experts about H.264. It seems that this codec is nothing new, and ffmpeg has supported it for a couple of years now.
ffmpeg might have had H.264 decoding support for a while, but definitely not " a few years", and encoding is till pretty fresh. As in : BIG FAT WARNING: x264 is still in early development stage. (Also, many of the other existing H.264 implementations don't follow the spec, and do stupid things like use AVI containers.)
Why could this not be placed into an older qt version? Or is it just that it was not?
A little of both, with a dose of marketing. QuickTime was showing it's age -- QuickTime 6's MPEG-4 implementation was a joke, mostly because of assumptions made with QuickTime 1 that no longer hold true.
The marketing comes in when you consider that the installed base of QuickTime users is more likely to upgrade if you go on about HD and pristine quality and fast downloads than APIs and architectures. It's a lot easier to get people to upgrade when you have a carrot to dangle in front of them.
Why H.264 is such big news?
The news is that it is now supported natively by a popular content creation platform, with an installed content delivery platform that is (IIRC), second only to Flash. This means that you can create H.264 content and have the reasonable expectation that people will be able to view it.
Don't become a regular here -- you will become retarded.
QuickTime 7 is required for H.264 playback in order to support B-frames. QuickTime's original architecture back in 1991 required that frames only reference previous frames, not future frames - a feature that is a basic requirement of H.264. Apple has been working on a major rewrite for years to get this working.
The good news is that out of order playback means better MPEG-1, MPEG-2, and MPEG-4 Part 2 implementations are also now technically possible within QuickTime.
My video compression blog
The number of people viewing avi's and wmv's are much larger than the number of people who are ready to view qt's.
... Quicktime7 is the same old qt format, but the program now has a better MPEG-4 stream handling plus an AVC handler?
.mov container as before. What has changed is QuickTime-the-software, which has been significantly upgraded. In other words, the file format was capable of things the software was not.
.mov, and it might support H.264, but it might not support H.264 inside .mov (this example might not be true, but such things do happen). The standard specifies only two container formats: .mp4 (based on QT), and .mpg (MPEG-2/DVD style muxed streams), so it's entirely possible that there's some limitation or difference in mplayer, et al.'s .MOV support that makes it not work. Likewise, Apple may use some part or "profile" of AVC that isn't supported by mplayer yet.
True, of course. I guess I blocked WMV from my mind because it isn't suitable for my own stuff. As for Real vs. QuickTime, I recall seeing numbers that put them very, very, close -- and as a creator, I would choose QT over Real any day -- I don't think I'm alone in that. In any event, the point was that QT7/H.264 is news because it's gone mainstream.
Also I am beginning to doubt my own understanding of MPEG-4.
It doesn't help that MPEG-4 is utterly bewildering.
So is quicktime7 a new format or not?
My understanding is that it is the same
But then in that case if they had released these trailers before qt7, the only people who would not be able to play them are the people with Quicktime players, while people with mplayer will have had no problems.
Not quite. It's more confusing than that. Players don't always support every format in every container that they support. mplayer might support
So, my conclusion there is "Maybe. MPEG-4 is confusing. My head hurts."
I've read elsewhere of people using H.264 video + MP3 audio inside AVI containers, which is so incredibly non-standard that it makes me dizzy.
Don't become a regular here -- you will become retarded.
I don't know about the rest of you but on my G4 733 with 1 GB of RAM and a Radeon 9000 Pro it is a joke.
.... with a few stops at 0.
I turned off all programs except Quicktime even turned off dashboard widgets (Running Tiger) and I sized the QT window to 1/2 native resolution and the informaiton window told me it was running between 3 and 9 FPS
DAMN that is insane.
haven't installed OS X 10.4 (Tiger) yet, and the new Quicktime update is causing some hiccups on systems running 10.3.9. here's a re-installer for Quicktime 6.5.2 for those of you need it.5 2reinstallerformac.html
http://www.apple.com/support/downloads/quicktime6
-- Boycott Shell
Actually if you read all the posts made above, you would notice that the downloaded file in the new format is playing just fine using mplayer, and it is the streaming that is causing the problem, as apparantly libquicktime/mplayer does not handle it.
Notice no Windows DLLs were used in the running of the file. libquicktime was handling the qt wrapper, while ffmpeg was playing the movie without any trouble.
As for the Windows, I would imagine that anyone with Quicktime Alternative dshow plugin can play these files as well.
badness 10000
This strikes me as an extremely obnoxious thing for Apple to have done. It seems to me that anything that shows up in "Software Update" should be just that: an update that will fix bugs and add new functionality, rather than replace your paid version of the software with the crippled free version of the next major release.