1. app calls pause(), not stop(). I don't mean it is late to call pause().
I think either pause() or stop() is ok. Pause() doesn't release hw resource, 
but it give a quick response when player is resumed

2. when player is send to background and bring foreground, its view port 
changed several times (by meego-qml-launcher). 
View port change will trigger media pipeline change because GLContext decides 
video rendering (video sink).
When media pipeline is changing its video sink on the fly (without stop/destroy 
pipeline), it will hang when seek() is called.


-----Original Message-----
From: Lynch, Rusty 
Sent: Wednesday, July 27, 2011 9:23 AM
To: Zhao, Halley
Cc: Arjan van de Ven; [email protected]; [email protected]
Subject: Re: [meego-packaging] [meego-commits] 23214: Changes to 
MeeGo:1.2:oss:Testing/qt-mobility

We stop the video when the app is placed in the background... are you 
saying we call stop too late?

On 07/26/2011 06:13 PM, Zhao, Halley wrote:
> My typo, it is 3s. I will correct it.
> More details here: https://bugs.meego.com/show_bug.cgi?id=21534#c7
>
> Meego-app-launcher enables opengl acceleration for app when app comes to 
> foreground ( by set QGLWidget to its viewport).
> Video rendering capability changes upon the above QGLWidget
> So video sink (video rendering component) in media pipeline will be changed 
> on the fly without stop/destroy media pipeline. This change happens in async 
> mode.
> Finally, Pipeline hangs when app try to call seek(0) in this transition state,
>
> This regression is caused by app call seek(0) when it come back from 
> background. this seek(0) is not correct because app just pause playback when 
> it goes to background, not stop it.
> To be a robust media engine, it shouldn't crash in such use case. So seek at 
> the beginning of playback (only when app come to foreground) is ignored.
>
>
>
> -----Original Message-----
> From: Arjan van de Ven [mailto:[email protected]]
> Sent: Tuesday, July 26, 2011 11:11 PM
> To: [email protected]
> Cc: Zhao, Halley; [email protected]
> Subject: Re: [meego-commits] 23214: Changes to 
> MeeGo:1.2:oss:Testing/qt-mobility
>
> On 7/26/2011 1:47 AM, Halley Zhao wrote:
>    
>> ++    QTimer::singleShot(3000, this, SLOT(setSeekable(true))); // wait 3ms 
>> to setSeekable
>>      
> Are you sure 3 ms is enough? Where is this 3ms coming from ?
>
> _______________________________________________
> MeeGo-packaging mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-packaging
>    

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to