[Development] The dark side of QtMultimedia

Thiago Macieira thiago.macieira at intel.com
Mon Nov 17 17:43:53 CET 2014

On Monday 17 November 2014 09:43:33 André Somers wrote:
> Thiago Macieira schreef op 17-11-2014 01:48:
> > Why do you want to render video non-fullscreen anyway on a device with
> > a small screen? Once the user clicks the play button, go to full
> > screen with rotation support.
> What a short-sighted comment. I really respect you, but this comment
> really misses the mark I think. Not every iOS device is a phone, and
> even these can get rather large these days. 

Unless it's a 23" screen or larger, it's still small. Render the video full 

> And don't you need to render controls? 

Yes, but I imagine that the video player has those controls already.

> You don't think rendering video's embedded in a larger
> application is ever needed in for example a simple video editor (for
> which a device like the iPad Air 2 is perfectly suitable in terms of
> processing power)?

No, I don't think there's any need to render in a smaller frame except for 
specialised applications like the video editor that you mentioned. Those 
specialised applications that do video as their main functionality will not 
use the generic multimedia framework from the OS anyway.

> IMHO, it is not up for framework developers to decide that user won't
> need this kind of capability. It does need to be there, so application
> developers can be creative in how they use video playback.

While it would be nice if we could render at any resolution, in any window, 
with any dynamic overlay controls, rendering it fullscreen with generic 
controls is better than nothing.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list