Re: Re: Problems with the player stopping

At 07:20 PM 1/6/2002, Sean Adams wrote:

>If the server doesn't respond, it does keep trying, but not after the
>buffer has run empty. If you wanted to resume playing automatically, it
>would be easy to detect this on the server side. However I'd much rather
>fix the original problem, than to implement a workaround which results in
>the audio dropping out for a few seconds.

I've done some more playing around with this and I have found another 
scenario where there are issues with the player stopping.

It seems to also have trouble with the title-scrolling when there is a long 
track.  Again, this might be mitigated by a faster machine.

I've used tcpdump to capture the packets, and ethereal to look at them.  It 
appears that the server will run along happily sending the mp3 data, and 
interleaving that with screen (scroll) updates about 10/second.

Then it will stop with the screen updates for about 3 seconds, while it 
still sends the mp3 data.  After that time, it sends one more screen 
update, then about 6 more mp3 datapackets.  Then it stops, and the only 
thing for about 5 seconds is packets from the player.

Then the server wakes up, and sends about 20 scroll updates, before it 
sends the same mp3data packet to the player approximately 17 times.

At this point, the server falls back into the previous pattern of sending 
mp3data in response to the player and sending scroll updates 10/second.

This happened several times before the player finally stopped (presumably 
its buffer ran out).  The time between the last mp3data packet before the 
final pause and the first mp3data packet after the final pause was a little 
over 7 seconds, while all the other pauses had been about 5 seconds long.

Hopefully, this data will help you track down why the player goes out to 
lunch, and help you fix your otherwise wonderful product.

Jordan

P.S.  I can give you a URL the packet capture (in "tcpdump -w outfile.cap" 
form) if it would help you.

P.P.S.  I just tried some more stuff.  If I have the display set to 
filename (which is this: 
"(Spirit_Caravan)_-_Elusive_Truth-02-Black_Flower.mp3") it pukes 
immediately after it tries to scroll the title the first time.  If I have 
the display set to tag-based, it does not (due to the non-scrolling, 
presumably).


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Tiny Wireless Camera under $80!
Order Now! FREE VCR Commander!
Click Here - Only 1 Day Left!
http://us.click.yahoo.com/WoOlbB/7.PDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/