Re: mplayerplug-in leaving zombies

Hi Kevin,

On Wed, Oct 03, 2007 at 06:14:28AM -0600, Kevin DeKorte wrote:
> Forest Bond wrote:
> > On Mon, Oct 01, 2007 at 09:38:38AM -0600, Kevin DeKorte wrote:
> >> Forest Bond wrote:
> >>> As you may remember, my application uses the mplayer plug-in to display
> >>> television channels.  I am conducting some testing where my code
> >>> continuously changes the television channel on a delay loop.  The channel is
> >>> changed by calling Stop(), SetURL(), and then Play().
> >> might want to try calling "quit()" instead of stop. As that should kill
> >> mplayer where Stop might try to pause the media. Also instead of
> >> "SetURL" you might try "Open" or "filename = "tv://x" where x is your
> >> channel.
> > 
> > Why are there so many different ways to do these things?
> 
> Compatibility with different plugins. And also how some of this stuff works.

Ok, that makes some sense, although I suspect things could be simplified at
least a little bit, maybe.

> > On the other hand, I'm not entirely clear as to why the player process is being
> > killed at all.  Why not keep the slave mplayer process alive for the entire
> > duration of the plugin instance's life?  That would certainly simplify some of
> > the thread/process management issues, and would also result in shorter delay
> > between play, stop, etc.
> 
> The main reason is this. When a media file is over in mplayer "-idle"
> mode. Mplayer doesn't say that the file is over. It just quits sending
> output. I've asked them to add this feature or even to add a property
> that can be queried to see if the file is complete. But so far no good.

There is such a property:

--------------------------------------------------------------------------------
get_property filename
ANS_filename=test.mpg
--------------------------------------------------------------------------------

But after the file has finished playing:

--------------------------------------------------------------------------------
get_property filename

--------------------------------------------------------------------------------

> > Also, I've found that things go bad when I do this:
> > 
> > mplayer.filename = 'foo';
> > mplayer.Play();
> > mplayer.filename = 'bar';
> > 
> > This seems to be necessary, instead:
> > 
> > mplayer.filename = 'foo';
> > mplayer.Play();
> > mplayer.Stop();
> > # delay here ...
> > mplayer.filename = 'bar';
> > mplayer.Play();
> > 
> 
> Have you tried "quit()" instead of "Stop()"? They actually do different
> things.

Yes, I believe I tried it.  Both require a delay that is much too long for my
application.  Using the loadfile command to mplayer reduces that delay
significantly (a power of ten or more, rough estimate).

What do quit and Stop do differently?

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Mplayerplug-in-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHA5XURO4fQQdv5AwRAmpHAJ9Abzoc5eep7+e7lqJjBH+DoPUYNwCgwTdK
LON69N9+KAx665zVXatIYXk=
=qEFj
-----END PGP SIGNATURE-----