Re: Quicktime API
Artem Baguinski <[email protected]>
| Newsgroups | gmane.comp.multimedia.media-api |
|---|---|
| Message-ID | <[email protected]> |
before you start diggin: http://developer.apple.com/documentation/Cocoa/QuickTime-date.html i just ran into it several times while reading on Cocoa. a quote: QuickTime is Apple's multiplatform multimedia technology for handling video, sound, animation, graphics, text, interactivity, and music. As a cross-platform technology, QuickTime can deliver content on Mac OS X, as well as all major versions of Microsoft Windows. another one: How do users obtain the System Software? Apple distributes the QuickTime system software on the Internet, free of charge, in separate versions for the MacOS and Windows. Apple and other manufacturers also ship QuickTime in new computers as built-in software. Finally, software developers can license QuickTime from Apple and include it with their products. [...] What is the QuickTime API like? Applications access QuickTime's features through a set of about 1200 system-level functions and associated data structures. However, you don't need to understand the whole QuickTime API; this book provides you with a road map to the specific calls you need for each programming task. Besides implementing most standard multimedia effects, the QuickTime API also lets you create custom software components to perform new actions. On Mon, Jan 05, 2004 at 02:24:57PM +0100, Steve Lhomme wrote: > Actually I'd be glad to add Matroska support to the Quicktime player, if > that's possible. Lots of Mac users are too computer-dumb to get and use > VLC or MPlayer OSX. So if we can add support for the default player (as > we can for WMP on Windows), it could be a nice boost on Mac OS. > > Christian HJ Wiesner wrote: > > > > >On a sidenote, > > > >has anybody ever had the time to look at the Quicktime API ? Especially > >the matroska team had been attacked a lot why we were reinventing the > >wheel, while MOV was such a great container doing everything you ever > >wanted to do, and they even have a nice common codec API so that codec > >developers could make their own codecs for MOV file creation ? > > > >I can try to dig out some links, i remember rjamorim posting them once > >on hydrogenaudio.org, but only if there is real interest. > > > >Christian > > > _______________________________________________ > Media-api mailing list > [email protected] > http://lists.matroska.org/cgi-bin/mailman/listinfo/media-api -- gr{oe|ee}t{en|ings} artm