News for hackers. Stuff that matters.
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by coldnose on Saturday February 20, 2010 @03:54PM (#1139461)
If Adobe wants access to h264 acceleration, use the QuickTime libraries.

In fact, why isn't Adobe using QTKit? Why are they rolling out their own appalling h264 implementation?

Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by wmf on Saturday February 20, 2010 @03:57PM (#1139466)
Adobe claims there's a mismatch between QTKit and Flash Player's rendering model, so using QTKit would either introduce more overhead or require a re-architecture of Flash Player.
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by coldnose on Saturday February 20, 2010 @04:34PM (#1139523)
I performed a little experiment on my MacBook (Core 2 Duo, no hardware acceleration). With flash, rendering 720p h264 routinely eats 100% of the cycles on one of my cores. That same video eats 10-20% in QuickTime.

This isn't very scientific - ignoring cache and lots of other considerations - but memcpy()ing 30fps of 720p video from one buffer to another eats 5%. Decoding h264 in QT, and copying the buffer would take 15-25% total. 25% compares favorably to 100%.

I'm aware that the problem is the way Flash writes into Safari's window. But if Adobe thinks that h264 acceleration would dramatically improve its performance, they'd still have to copy frames into Safari somehow.

(Maybe they mean they want to write directly to the GPU's buffer...)

Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by bobbyi on Saturday February 20, 2010 @04:12PM (#1139489)
Well then, I guess they need to re-architect some of Flash Player. They've had more than three years to get this figured out.
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by Anechoic on Saturday February 20, 2010 @04:02PM (#1139471)
How does Perian handle it?
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by wmf on Saturday February 20, 2010 @04:09PM (#1139482)
AFAIK Perian doesn't use hardware decoding either. Also, Perian isn't bound by the weird Flash rendering model.

http://blogs.adobe.com/penguin.swf/2010/01/solving_different...

Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by duskwuff on Saturday February 20, 2010 @04:51PM (#1139557)
Perian is just a set of decoders for QuickTime, not a full video player pipeline.
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by GeneralMaximus on Sunday February 21, 2010 @01:19AM (#1140231)
Yes. Perian mostly includes ffmpeg decoders that plug into the OS X Component Manager.
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by yuvi on Saturday February 20, 2010 @05:11PM (#1139581)
By not overriding Apple's decoder for baseline and main profile H.264
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by kelnos on Saturday February 20, 2010 @09:13PM (#1139940)
I may be misremembering, but I believe QTKit basically just lets you hand it encoded video data, and then it decodes and renders it to the screen (where you tell it to, of course).

Because of how browser plugins work, Flash needs an API that will let them decode the video, get the decoded YUV data back, and then do something with them. I don't think QTKit provides this.

This is why VDPAU on Linux is also unsuitable for in-browser video acceleration.

Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by bshep on Sunday February 21, 2010 @08:32AM (#1140545)
Thats what video compositing is for I am not a QTKit expert but just quick glance over the documentation they offer QTMovieLayer which allows you to have multiple layers of media which will be composited later ( i.e. one for video, one for the media controls, etc )
Re:About Adobe's Flash Player Not Having Access to H.264 HW ... by kelnos on Tuesday February 23, 2010 @08:14PM (#1146966)
Cool! I hadn't known about QTMovieLayer. Thanks for the correction.