[Development] The dark side of QtMultimedia

Simon Hausmann simon.hausmann at theqtcompany.com
Tue Nov 11 10:50:25 CET 2014

On Tuesday 11. November 2014 10.41.49 Knoll Lars wrote:
> On 11/11/14 09:47, "Simon Hausmann" <simon.hausmann at theqtcompany.com>
> wrote:
> >On Monday 10. November 2014 09.43.25 Holger Hans Peter Freyther wrote:
> >[...]
> >
> >> Now really getting to my two cents. Instead of wrapping API
> >> Qt should make sure the framework can be integrated. E.g. in
> >> terms of GStreamer provide plugins that allows to easily embed
> >> video into Qt applications but ask users to use the "native"
> >> API to manage the pipeline/playback.
> >
> >
> >I share that philosophy and support any efforts towards making
> >integrations 
> >like that easier. In the case of multimedia that can be tricky though,
> >but 
> >that's not necessarily Qt's fault. It did take a while until gstreamer
> >had 
> >basic OpenGL texture streaming support, while frameworks on other
> >platforms 
> >have had it longer. Nevertheless once you can get hold of that, I think
> >the Qt 
> >Quick Scene Graph API is rather well suited for the graphics integration.
> Well, if you’re doing a complex multimedia app, this might be the right
> approach. But for the 90% use case (show a video, play a sound, capture
> something from the camera), we can’t tell people to write 10 different
> implementations for the 10 platforms/OSes we support.

Yeah, I think that justifies the existence of qtmultimedia very well.


More information about the Development mailing list