Linked by Thom Holwerda on Thu 2nd Dec 2010 23:20 UTC
Multimedia, AV The sweet smell of competition is lingering in the air. That sweet smell which indicates that somewhere in the vicinity a company is working on actually improving a product so we can all benefit. This time around, it's Adobe, delivering the first Flash 10.2 beta. Prime feature? Complete hardware acceleration of the entire video pipeline - fully cross platform, cross-form factor. Cross-platform! There's a catch, though.
Thread beginning with comment 452168
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[9]: Thank Apple
by kaiwai on Sat 4th Dec 2010 15:06 UTC in reply to "RE[8]: Thank Apple"
Member since:

I believe most devs are using the old carbon framework because the new one doesn't have many features beyond playing a video and outputting sound (is there even a public api for the new framework?).

There is a huge difference between the QuickTime X player and the QuickTime framework - please spend some time learning the difference *please*.

Here is some documentation:

According to that documentation it doesn't seem 'limiting'. Considering it was only made available in 10.5 maybe it was a matter of waiting till it made sense to move - if you're going to move to a new framework you might as well do it at the same time as you move to 64bit thus hitting two birds with one stone.

The QuickTime X player is limiting on Snow Leopard but that has more to do with Apple choosing only to do a very simple player instead of something covered all the bases. What will Lion do? it depends on whether Apple see's merit in extensively adding more features to QuickTime or whether at best the player remains very basic.

Reply Parent Score: 2

RE[10]: Thank Apple
by _txf_ on Sat 4th Dec 2010 18:27 in reply to "RE[9]: Thank Apple"
_txf_ Member since:

I never said Quicktime X player; It is just a player that uses QTKit. I'm talking about Quicktime X as opposed to Quicktime 7. QTKit is built on top of these and provides a simpler api to both.

If you choose to use QTX you forfeit things like saving and editing and if QTX fails it falls back to QT7. Incidentally this appears to be the reason that no media editing app uses QTX.

You told me to read the documentation and so I did; Did you? It appears that you are mistaken on what QTX is...

Reply Parent Score: 3

RE[11]: Thank Apple
by kaiwai on Sun 5th Dec 2010 02:24 in reply to "RE[10]: Thank Apple"
kaiwai Member since:

Apologises for my previous post - I should have read the documentation rather than relying on second hand information I heard through the grape vine. Maybe this explains why there has been such a long time between Apple's professional tools being released - that there is a whole lot of features that need to be added to QtKit before they can migrate across.

I've read the documentation and would it be correct to assume that QtKit is abstracted above QuickTime C based API? I've had a look at the framework reference itself and it makes sense if you're interested in abstracting as high as you can and not want to deal with the details but the current Kit as it stands doesn't seem to allow the kind of low level I think you mentioned in a previous post.

From the vantage point of a lay man it seems like a bit of a clusterfuck - if you want a feature complete low level API you have to use the QuickTime framework in C which only supports 32bit or you have to give up that those low level features if you want 64bit support. I can only hope that maybe Lion will bring about a completing of QTKit so that developers are able to move their code fully to the new API and thus make their products 64bit rather than being stuck in a state of limbo of having to use an IPC between 32bit QuickTime and their 64bit project like what Adobe Media Encoder CS5 does.

Reply Parent Score: 2