I played a few albums, and it seems the problem has gone away with alsa
and pa_snapshot-20090419.
I noticed that at the same time squeezeslave used to stop (around -20s
before the end of the track, when the next song begins to be buffered)
there's a very small cut - maybe 1/4 second silence.
Thanks for the offer. The silence gap is due to the way buffering is
handled in SS and as such SS doesn't claim gapless playback. There's
also an outstanding issue with the buffer code that only triggers using
ALSA and not OSS, which I suspect is what you've been hearing. See the
TODO file in
I don't think it's a problem with squeezeslave, but I'm bias ;-) There
are other posts like 'this'
(http://forums.slimdevices.com/showthread.php?t=71949) one describing
similiar issues with the hardware players.
Are there any messages in the log file when the player stops?
What you describe
there's nothing in the log, except a few
Slim::Web::JSONRPC::requestMethod (383) request not dispatchable!
but I'm quite sure they're not time-correlated with my problem.
I just wiped out 7.4.1 and configured 7.3.4 with the patch for replay
gain; now it may take some time to see if
Nothing in /home/juke/squeezeslave.log either?
--
ralphy
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=71894
nothing in /home/juke/squeezeslave.log either, it stays empty...
--
boris
boris's Profile: http://forums.slimdevices.com/member.php?userid=34556
View this thread: http://forums.slimdevices.com/showthread.php?t=71894
hmm, I forgot I flushed the log at each squeezeslave restart. It just
stopped with 7.3.4, and the log contains:
Error in recv 1: Success
Retry in 10 seconds.
Error connecting to 192.168.19.1:3483
Retry in 10 seconds.
Error connecting to 192.168.19.1:3483
Retry in 10 seconds.
and so on.
I just
'Error in recv 1: Success' indicates that the server closed the
connection and squeezeslave is trying to reconnect. Is your server
going into a power saving mode by chance? From the squeezeslave.log you
just posted it appears that SS is working the way it should.
--
ralphy
no, the server is always up, nothing is configured to spin down/suspend.
There's a rather strict firewall on that machine, but nothing that could
drop/close/reset a connection. (and I never had any problems for the
months I used the pulseaudio setup described earlier).
I don't think it's a
As a test, can you try applying the freebsd patch from 'this'
(http://forums.slimdevices.com/showpost.php?p=476422postcount=19) post
and change the makefile.linux26-alsa to add -D__FREEBSD__ to line 37?
Code:
36:.c.o:
37:$(CC) $(CFLAGS) -D__FREEBSD__ -c
Hello ralphy,
First, thanks for your time maintaining squeezeslave !
I patched/compiled squeezeslave like you said; just when I was thinking
to reply that everything was going well (3+ hours playing without
problem), squeezeslave hanged a few times like before.
Yesterday I compiled the oss
Hi there,
I have a problem with squeezeslave: it randomly stops near the end of
tracks: at around -19 seconds left (plus/minus 1 or 2 secs), sound
stops, and the track's progress bar loops indefinitely between -19 and
[-17,-10] range. Hitting the next button will play the next track.
12 matches
Mail list logo