Slashdot Mirror
QuickTime 6 Public Beta Available
krugdm writes "Apple has announced that a public beta of QuickTime 6 is now available. MPEG-4 support is there, as well as support for other technologies, such as JPEG2000, and Flash 5. The beta expires in October. An interesting in the FAQ's says that, '... because QuickTime 6 will include royalty-bearing technologies, a new QuickTime Pro key will be required to unlock pro functionality in the final release.'" It is available for Mac OS, Mac OS X, and Windows, and supports AAC audio too. I also wonder why MPEG-4 is ".mp4". ".mp3" isn't for MPEG-3, after all. Flummery!
One of the coolest things they demoed for Quicktime 6 was no-wait streaming, where there's no pause while the frames get buffered. You can even scrub back and forth over the timeline, streaming. Combined with an Xserve dishing out >500 simultaneous DVD-quality quicktime streams, Quicktime is looking pretty sweet. Now why don't more sites start using it?
You drank my drink, you drunk!
It's out for MacOS, MacOS X (BSD), and Windows. Remind me again why we can't have a native Linux version of it?
Same reason you can't have Photoshop for Linux, or Microsoft Office for Linux: because the vendor wouldn't make any money off of a version of their software for Linux.
The Windows port of QuickTime is important primarily because of licensing: Apple licenses the technology to companies like Adobe so they can use it in apps like Premiere, which are more popular on Windows than they are on the Mac.
But Apple knows that Linux users, as a rule, don't buy software. No third party would license QuickTime for Linux, because they couldn't make any money on their product. So there's zero motivation for Apple to port QuickTime to Linux.
In other words, this has the ability to kill all the crap about "you need FOO player to see this video".
[Extremely relevant multimedia reply - Requires Slashdot Pro to read. Please submit your Visa number....]
"Blessed is the man who walks not in the counsel of the ungodly"
Yea, but I'm a vi kind of guy...
Hey Pudge, did you mean flummery?
flummery (flm-r) n. pl. flummeries
I'm pretty sure you did...
And how, exactly, are they making money off the "free" versions they are giving out for all of the other platforms?
Hmm. Another sighting of the infamous non-reading anonymous coward.
Apple gives away the QuickTime Player software for free. This is a neat way to increase awareness of QuickTime technology among Windows and Mac users.
Apple makes money by licensing QuickTime technology to software companies that want to incorporate it into their own products. You find QuickTime technology in apps like After Effects and Premiere from Adobe, Cinestream from Media 100, and (duh) Final Cut Pro. You can also find QuickTime technology embedded in things like digital cameras.
Apple has already done extensive work to port the QuickTime libraries to Windows and to Mac OS X from Mac OS Classic, because third party licensees asked for support for those platforms. It seems that nobody is clamoring for QuickTime for Linux except desktop users who aren't going to be buying anything any time soon.
If you really want QuickTime Player for Linux, offer to buy it from Apple. If you are willing to pay the right price, and lots and lots of other people are also willing to pay, then Apple has a case for doing the port.
Hey! It appears to work fine with CodeWeaver's CrossOver Plugin for Linux.
I just installed and ran it.
I'm not a prophet or a stone-age man,
I'm just a mortal with potential of a super man.
"Instant-on" is not quite the same thing as setting your buffer size to zero. Typically, setting the buffer size to zero in a player means that there is no buffering for the entire duration of the program. This means that if you want to watch without interruptions, the available bandwidth between the server and you must exceed the bit rate of the stream at all times; since the encoding is at a variable bit rate, you will often see peaks in the bit rate which need really high bandwidth to sustain the stream.
However with "instant-on", the playback begins immediately, but the buffer continues to build. This means that you need a fairly high bandwidth initially in order to start the playback and build up the buffer, but--after that initial period--the buffer prevents interruptions which would otherwise have been caused by the peak rate of the stream going beyond the available bandwidth. So "instant-on" is not the same as setting your buffer to a fixed size of zero. Now this isn't really revolutionary; to researchers in the field the question is why everyone hasn't been doing this all along.
As an aside, the "skip protection" feature of Quicktime streaming is simply over-buffering; i.e. using the available bandwidth to build up the client buffer as much as possible instead of maintaining a fixed size buffer.
QuickTime doesn't really have any major advantages over other technologies as far as I can tell, other than it being made by Apple and therefore given lots of marketing. Why should I choose QuickTime over Real, or Windows Media, or hell even standard MPEG?
Quicktime streaming has an advantage to broadcasters: the server is open-source and free as in beer. You can download the latest snapshot via CVS, and contributions to the source from the public are welcome. The streaming protocols are all standards based (RTP/RTSP). Of course, you could always encode the data with a proprietary codec, but if you used an open codec, then the streams could be played back by any standards compliant player, not just Quicktime Player.
Finally, although ideas like "skip-protection" and "instant-on" are fairly obvious to anyone who spends some time thinking about these issues, the fact remains that only Apple seems to be taking the initiative to incorporate these into its servers and clients. What new features (from a streaming perspective) have Real and Microsoft offered in the new releases of their products? While Apple does have a big marketing push, that does not take away from the fact that there is solid work going on behind the scenes.
Contrary to popular perception, the primary problem with DivX support on macs is not lack of the proper codecs. There are actually three different DivX codecs for mac (the 3ivx, DivX, and ffmpeg projects - however windows media audio, which some files use, is only indirectly supported via DivX doctor). The real problem is quicktime's inability to read AVI files with variable bitrate audio encoded into them (vbr support was not part of the original official spec, and microsoft has since declared the format "obsolete" in favor of windows media). This has been a problem with quicktime for years, and they STILL haven't fixed it in QT6 preview, despite rumors to the contrary. The only solution is to extract the audio and video tracks and stick them together in quicktime format, using one of a variety of tools (see the sites above). DivX.com claims to have come up with an elegant hack around the issue, but they have yet to release it. Video LAN client claims to be able to play back DivX avis without doctoring, but doesn't work well at all yet.
The good news is you can play back just about any DivX file out there. The bad news is you're going to have to do a little more work than just downloading Quicktime and expecting it to play - You have to go get and install the DivX codecs yourself, and turn all your DivX AVIs into MOVs with the proper tools. I can only assume the Quicktime crew could have fixed this vbr AVI problem if they wanted to a long time ago, and possibly did - but for undisclosed reasons, they choose not to or aren't allowed to release or work on it.
---If you can't trust a nerd, who can you trust?