maks / squeezelite

Automatically exported from code.google.com/p/squeezelite
Other
0 stars 0 forks source link

Squeezelite sound output stops after a few hours on Armv5 Pogoplug with Arch #90

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Configure squeezelite to start as a service and start it with systemctl.  
This is the command from the service file:

/home/peter/squeezelite -m ab:cd:ef:12:34:59 -n dining

2.  Listen to pandora without issues for hours.  Go to bed.

3.  Wake up 8 hours later with this player "dining" still showing up in LMS, 
and with the service still showing up in "htop", but with no output at the 
speakers.

What is the expected output? What do you see instead?

The expected output is high quality sound which works for hours after starting 
the service.  
This problem is totally resolved by either rebooting, or stopping and 
restarting the systemctl service.

What version of the product are you using? On what operating system?

The version is squeezelite-armv5te, and this is running on Arch Linux on a 
Pogoplug V4 which has 3 USB ports- one is occupied by an Edimax wifi dongle, 
and one is occupied by a C-Media audio card. 

Please provide any additional information below.

I have replicated my setup on two separate devices at the exact same time, and 
they both produce the same issue.  After the initial setup of Arch, and getting 
wifi working, these are the instructions that I followed:

pacman -Sy faad2 libmad mpg123 libao alsa-utils avahi

#audio fix
echo "use_mmap=no" >> /etc/libao.conf

#Configure alsa - asound.conf file
cd /etc
wget https://dl.dropbox.com/u/42238/pogoplug/v2/asound.conf

cd /home/peter

#download the latest squeezelite version
wget http://squeezelite-downloads.googlecode.com/git/squeezelite-armv5te
mv squeezelite-armv5te squeezelite

#make executable
chmod a+x squeezelite

#download service file
cd /etc/systemd/system
wget http://dl.dropbox.com/u/42238/pogoplug/v2/squeezelite.service

#edit the service file accordingly

[Unit]
Description=Squeezelite lightweight headless squeezebox emulator
After=sound.target
Requires=avahi-daemon.service
After=network.target
After=avahi-daemon.service

[Service]
ExecStart=/home/peter/squeezelite -m ab:cd:ef:12:34:59 -n dining
Restart=always

[Install]
WantedBy=multi-user.target

#start squeezelite and avahi-daemon
systemctl start squeezelite avahi-daemon

#autostart squeezelite and avahi-daemon on reboot
systemctl enable squeezelite avahi-daemon

Original issue reported on code.google.com by monkmand...@gmail.com on 30 Jan 2015 at 1:56

GoogleCodeExporter commented 9 years ago
Can you try using a wired connection versus wireless to see if you're able to 
reproduce the same issue?

Original comment by quih...@qnology.com on 31 Jan 2015 at 12:20

GoogleCodeExporter commented 9 years ago
Hey, my hero!  I'm glad you are here.  I already tried that, great suggestion.  
It's not a wireless issue.
Qui, did you know that this setup works without the asound.conf file?  What 
made you add that, do you mind me asking?
Thanks for everything!
Peter

Original comment by monkmand...@gmail.com on 31 Jan 2015 at 12:22

GoogleCodeExporter commented 9 years ago
I added the asound.conf file for AirPlay.

Original comment by quih...@qnology.com on 11 Feb 2015 at 1:35

GoogleCodeExporter commented 9 years ago
Same for me. Pogoplug E02, ALARM, followed the Qnology.com tutorial. Had the 
same problem with Series 4 and Arch. However, have another E02 that is working 
fine with VAMP 0.4, updated to squeezelite 1.5. 

Here's what it sounds like: https://clyp.it/to1h3jww

Original comment by Barton.M...@gmail.com on 21 Mar 2015 at 3:46

GoogleCodeExporter commented 9 years ago
It's not clear if the OP's issue is with an E02 or V4 Pogoplug. I'm using an 
E02 and it's rock solid. OTOH, the V4 has serious issues with the USB 
interface. For me when connecting with a Shiit Modi, the V4 will open the 
device once and only once. When closed, it will not reopen the device. In fact 
the system essentially freezes and cannot be shutdown except by removing power.

Original comment by mervinb...@gmail.com on 24 Mar 2015 at 1:07