Aubin Paul wrote: > Ok, I've got it happening consistently now. If you play one track and > let it continue to the next, it always cuts off after between 8 and 10 > seconds and skips to the next, which plays in it's entirety, the next > one cuts off and so on. > > I can't figure out why the 'exit' command is being sent to the app > arbitrarily.
I can't reproce the bug, I guess we have some strange thread timing. Let's see: AudioItem, player and mplayer all have a stop() function this function will be called from other objects (very confusing btw). But the stop() function should only return when the music really stopped. playlist.py will only play a new item, when the old is stopped. Since everything is blocking, this should work. When mplayer finished, PLAY_END will be send. This causes the 'sending stop command'. Doesn't matter that the child is already dead. Since playlist.py is the last one in the list, everyone should know that playing is already stopped. Can you add a trace (a real traceback) who is calling the childapps kill function? And can you add full debug please. Dischi -- Fast, cheap, good: pick two. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
