von eriktechn - 11.03.10 20:07
Ich zitiere jetzt einfach mal aus den Kommentaren und erspare mir das Ganze in eigene Worte zu packen:



If you do a little research on Apple not letting Adobe access low-level hardware acceleration, the picture is this:


1.  Adobe can access the exact same APIs as Apple uses in Safari.  These wrap hardware acceleration in the CoreVideo API.


2.  Apple doesn't allow anyone - not Safari, not Quicktime, not nobody - direct video acceleration access except through its APIs (which Safari and Quicktime use).  The main reason for this is system stability (and a decade of graphics device drivers causing Windows to fall over the vast majority of the time bears this explanation out).


3.  Flash doesn't use those APIs well the vast majority of the time "just in case" the Flash file might need to do random overlays in the middle of the video (ads etc), which are harder to do in the accelerated APIs without being able to "read back" the rendered pixels.  Really, Adobe's complaints are that the APIs Apple provides don't include the read-back feature they have built their stack around.  For what it's worth, Microsoft's APIs don't do
this either, which is why Adobe did an end-run around the DirectX stack and petitioned all the graphics device driver vendors to add this feature to their drivers ...  a feature which no one but Flash can use because it isn't a "stable" API.