Since I started running 6.5b1 a week ago, and with every nightly since then, I've been having the following problem:
When I cue up an album, the songs will be added to the playlist, but some of them will be skipped on playback. This happens sporadically and on different songs, but usually hits 2-3 times on a typical 12-song album. I've made myself crazy trying to figure out what's going wrong, to no avail, so I'll provide a bunch of detail and all the things I've tried, to see if anyone has ideas. Setup: - slimserver 6.5b1, #9491 - Ubuntu 6.06, latest apt-get upgrade - installed via the Debian package - song files are AAC, ripped by iTunes - decoding via faad or mplayer (no difference) - playback to FLAC or WAV (no difference) - client is Squeezebox 3 or SoftSqueeze (no difference) - worked fine with otherwise identical setup on 6.2.1 My best hunch is that it's something in the interaction with the decoder process (not the decoding itself). As I said, with either faad or mplayer I see the same main problem (songs are occasionally skipped). However, the failure mode is slightly different. With faad, when a song is skipped, there will be two faad processes created. The first one seems to continue decoding the skipped song to completion, running as fast as it can. The second one runs fast until the buffer fills, then is throttled until the song ends. (Note: the same thing happens if I manually skip songs with the remote: faad processes will start piling up, until they all churn through their respective songs.) However, with mplayer, when there is a skip, the first mplayer process exits immediately, leaving a message on stderr about being interrupted by signal 13 (SIGPIPE). Then a second mplayer process starts right after, and runs fine. These clues are what lead me to believe it's something in controlling the decoder process. Throughout this, slimserver seems happy (or at least doesn't produce any error messages). I've tried all the various debug switches, but it mostly looks like a bunch of innocuous protocol chatter. The only suspicious thing I see when a track is skipped is 2006-09-08 10:26:13.1710 Got <file1> 2006-09-08 10:26:13.1758 extracted: <file1> followed immediately by 2006-09-08 10:26:13.5603 Got <file2> 2006-09-08 10:26:13.5649 extracted: <file2> Hence the skipped track. :-( I'm getting bored with random playback and radio, so any help will be greatly appreciated! Thanks, --Andy -- av249 ------------------------------------------------------------------------ av249's Profile: http://forums.slimdevices.com/member.php?userid=7381 View this thread: http://forums.slimdevices.com/showthread.php?t=27190 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
