Hi Tom, (this got stuck in my outbox, somehow)
> I think it's generally understood that there are two optimal paths for > displaying video: 1) Textured video: Reading video as a YUV texture > using OES_EGL_image_external or similar and 2) Using video overlay > hardware. Textured video is the most generic and flexible, however it > requires the GPU to be powered up for every frame. Option 2 is less > flexible, typically only allowing scaling and 90-degree rotations but > uses significantly less power (ideal for watching movies full-screen). > Will both of these video presentation techniques be part of the Qt 5 > architecture? If so, how will it work? What about support for VDPAU, > VAAPI and similar such proprietary video presentation technologies? Generally yes, through QtMultimediaKit. On Linux we use gstreamer (with whatever elements are available for hardware acceleration), with a sink for integrating into scenegraph etc (although currently the overlay path is not really done yet, just texture streaming - it used to work for 4.7 based :). Integration with the presentation queue part is interesting, though. We haven't really looked into those specific two technologies yet although I think there's some VAAPI work contributed for MeeGo. This could be an interesting discussion at the contributors' summit, of course. Cheers, MichaelG _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
