This a branch from the Garbled Audio thread in General as a spearate problem seem to have been discovered.
Twice yesterday and once today while testing AlienBBC with SoftSqueeze on a Linux box and Slimserver 6.1.2 on Windows, the R4 stream restarted by itself. "Hangtight" had a similar experience but not definite. I had ethereal running for last 2 events. The problem is a result of Slimserver sending a TCP packet with FIN set from port 9000. This results in a RST on the Mplayer connection to the BBC and then Mplayer restarts with a new connections. The time between first packet on port 9000 and first Fin packet was 12197 and 12183 seconds. A difference of only 14 seconds in 12,000 on two separate days with a different number of lost packets - that is too small a difference to be a coincidence. Any timers of about 200-203 mins/ 12000-12100 secs in slimserver ? I think the tets problem is reproducible but it take 3.5 hrs to run - any suggestion (e.g. a debug flag to set) for next run ? DEBUGPIPE on second run did not show "Stalled" just "kill movedata thread" so socketwrapper is not the culprit. -- bpa _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
