Announce: Squeezelite - a small headless squeezeplay emulator for linux (alsa only)

[PasTim]

Any squeezelite and/or LMS logs showing errors?

I realise that you supplied one squeezelite log, but is there nothing else? Do you get the library errors on the system running LMS? Can you compare the logs from both PIs?

[anotbot]

Hi PasTim,

Thank you for your help.

Here is the log from the Pi server - I'm not sure what any of it means :-)

I was trying adding various options to the squeezelite command line.

The first bit is the default for the just boom card : -o hw:CARD=sndrpijustboomd -V Digital -Q

It was suggested that I add -s myserver.local:9000 or -s myserver.local - the first broke the player and the second made no difference. So I can't be sure if the any errors that are being reported are due to the above...

#### SQUEEZESERVER LOG ####
[17-05-17 18:41:25.7579] Slim::Networking::Slimproto::client_readable (414) Client not found for slimproto msg op: STAT from 192.168.0.12
[17-05-17 18:53:15.8443] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
[17-05-17 18:54:14.9176] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
[17-05-17 19:58:30.0733] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-17 19:58:30.1036] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-17 20:58:28.6592] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-17 20:58:28.6915] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-17 21:58:27.2543] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-17 21:58:27.2988] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-18 09:03:29.8931] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 09:03:34.9497] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 09:03:40.0044] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
2017-05-18 09:08:11 squeezeboxserver_safe stopped.
2017-05-18 12:16:27 squeezeboxserver_safe started.
[17-05-18 12:16:32.3580] main::init (387) Starting Logitech Media Server (v7.9.1, 1493198727, Sat Apr 29 04:38:50 UTC 2017) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
[17-05-18 12:16:36.8669] Plugins::NPRRadio::Metadata::init (21) Register NPR meta provider, default icon=
[17-05-18 12:27:32.7936] Slim::Networking::Slimproto::client_readable (414) Client not found for slimproto msg op: STAT from 192.168.0.12
[17-05-18 12:32:14.0424] Slim::Networking::Slimproto::client_readable (414) Client not found for slimproto msg op: STAT from 192.168.0.12
[17-05-18 12:32:24.1567] Slim::Networking:iscovery::Players::_players_error (146) Unable to get players: Timed out waiting for data
[17-05-18 12:41:24.0725] Slim::Networking::Slimproto::client_readable (414) Client not found for slimproto msg op: STAT from 192.168.0.12
[17-05-18 13:59:20.2046] Slim::Networking::Slimproto::client_readable (414) Client not found for slimproto msg op: STAT from 192.168.0.12
[17-05-18 13:59:20.7322] Slim::Web::Cometd::handler (422) errorNeedsClient: 02:46:90:3d:fd:97, status, -, 1, tags:JjaldBxKAc, subscribe:60
2017-05-18 14:08:01 squeezeboxserver_safe stopped.
2017-05-18 14:08:17 squeezeboxserver_safe started.
[17-05-18 14:08:36.1254] main::init (387) Starting Logitech Media Server (v7.9.1, 1493198727, Sat Apr 29 04:38:50 UTC 2017) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
[17-05-18 14:08:43.0297] Plugins::NPRRadio::Metadata::init (21) Register NPR meta provider, default icon=
[17-05-18 14:08:48.6544] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:d3:61:3a, status, -, 1, tags:JjaldBxKAc, subscribe:60
[17-05-18 14:08:48.6598] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:08:53.7180] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
2017-05-18 14:08:58 squeezeboxserver_safe stopped.
2017-05-18 14:08:58 squeezeboxserver_safe started.
[17-05-18 14:09:02.0954] main::init (387) Starting Logitech Media Server (v7.9.1, 1493198727, Sat Apr 29 04:38:50 UTC 2017) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
[17-05-18 14:09:04.6760] Plugins::NPRRadio::Metadata::init (21) Register NPR meta provider, default icon=
[17-05-18 14:09:08.9543] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:09:14.0931] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:09:18.6615] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:09:18.6658] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:09:39.6789] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 14:09:39.7583] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:d3:61:3a: request not dispatchable!
[17-05-18 21:19:12.0024] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed
[17-05-18 21:19:12.0389] Slim::Plugin::UPnP::Events::error (323) Subscribe/unsubscribe error: 412 Precondition Failed


#### PERL VERSION ####
v5.20.2

[PasTim]

Hi PasTim,

Thank you for your help.

Here is the log from the Pi server - I'm not sure what any of it means :-)

I was trying adding various options to the squeezelite command line.

The first bit is the default for the just boom card : -o hw:CARD=sndrpijustboomd -V Digital -Q

It was suggested that I add -s myserver.local:9000 or -s myserver.local - the first broke the player and the second made no difference. So I can't be sure if the any errors that are being reported are due to the above...

#### SQUEEZESERVER LOG ####
.....

I don't understand much of this either, but maybe other more knowledgeable people here will. It certainly looks as if your remote squeezelite player is struggling to make itself known to the LMS server.

Have you tried using -s with the local-IP-address:9000 rather than 'myserver.local'? A correct IP address or resolved host name shouldn't break the player.

[anotbot]

Yes, I've tried that and though the squeezelite player starts up, it can no longer be found by any controller... so not a solution :-(

[PasTim]

Yes, I've tried that and though the squeezelite player starts up, it can no longer be found by any controller... so not a solution :-(

Beats me - sorry. You really don't have any firewalls set up anywhere do you?

[anotbot]

Beats me - sorry. You really don't have any firewalls set up anywhere do you?

Thank you for your help PasTim.

No, no firewalls - my other squeezeplayers work fine (iPad and Mac) it's just the Pi ones that don't... thinking it might be something to do with the Max2Play software, as I know someone else is having the same problem...

What are you using on your Pi?

[PasTim]

Thank you for your help PasTim.

No, no firewalls - my other squeezeplayers work fine (iPad and Mac) it's just the Pi ones that don't... thinking it might be something to do with the Max2Play software, as I know someone else is having the same problem...

What are you using on your Pi?

I don't have one (see my signature), and know nothing about Max2Play. I just use squeezelite on my server and sometimes other desktops/laptops.

[bpa]

Yes, I've tried that and though the squeezelite player starts up, it can no longer be found by any controller... so not a solution :-(

If there are no firewalls blocking broadcast packets, player being visible to controller depends on being on the same subnet.
How are IP addressess of player, controller and LMS allocated - statiic or DHCP ?
If static what is the IP address and mask of player, of controller and of LMS ?

[trung224]

question about output stream on squeezelite

Hello,
I have a problem when using Squeezelite. I am using Logitech Media Server streaming flac (native, no transcoding) to Squeezelite. Problem is, Squeezelite renderer cannot output stream at native rate. For example, if I don't choose anything about bit depth in Configure squeelite>ALSA params, the output streamon Squeezelite is always in 32 bit.
If I choose 24bit, the output stream is 24bit regardless my input stream (16bit FLAC or 24bit FLAC) is.

So I want to ask if you could add imprementation about native output stream on squeezelite renderer.

Thanks in advance and best regards,
trung224

[paulster]

I have a problem when using Squeezelite. I am using Logitech Media Server streaming flac (native, no transcoding) to Squeezelite. Problem is, Squeezelite renderer cannot output stream at native rate. For example, if I don't choose anything about bit depth in Configure squeelite>ALSA params, the output streamon Squeezelite is always in 32 bit.
If I choose 24bit, the output stream is 24bit regardless my input stream (16bit FLAC or 24bit FLAC) is.

So I want to ask if you could add imprementation about native output stream on squeezelite renderer.

Why is this causing a problem? The values in the source data are not being changed, but you are getting an extra one or two least significant bytes which are all zero, which will just be ignored. The only possible downside I can see would be your DAC reporting 24-bit on a 16-bit file if it had a display, but the music wouldn't be any different.

[bpa]

Hello,
I have a problem when using Squeezelite. I am using Logitech Media Server streaming flac (native, no transcoding) to Squeezelite. Problem is, Squeezelite renderer cannot output stream at native rate. For example, if I don't choose anything about bit depth in Configure squeelite>ALSA params, the output streamon Squeezelite is always in 32 bit.
If I choose 24bit, the output stream is 24bit regardless my input stream (16bit FLAC or 24bit FLAC) is.

So I want to ask if you could add imprementation about native output stream on squeezelite renderer.

Are you using the "right" Alsa output device ? Depending on the device Alsa can do unwanted conversions.

[Richard Kimber]

Squeezelite always needs to be restarted frequently

I’m running LMS and Squeezelite on a Raspberry Pi 3 with a wired ethernet connection. I use it mostly for internet radio.

I’m connecting the USB output to a T+A DAC 8 DSD. This sounds fine at first. However, if I switch off the music (via the SqueezeCtrl app on my tablet) and then return to play more music after a longish, as yet undetermined, period, then I get intermittent and distorted sound. As far as I can tell it’s not a DAC issue as its diagnostic lights indicate the connection is properly maintained. It also has (once) happened after several hours of playing music - the music just stopped followed by a regular pulsing version of the sound. Killing Squeezelite and restarting it solved it.

In fact this issue can always be resolved by restarting Squeezelite (usually after having been killed first, rather than just stopped). But it’s a pain to have to keep doing that.

Previously, before I experimented with USB, I used a HiFiBerry Digi+ and connected with a phono lead. There were no problems whatever with this (except that it’s limited to 24/192). The basic hardware seems to be OK, there seems to be a software issue of some sort.

[Man in a van]

I’m running LMS and Squeezelite on a Raspberry Pi 3 with a wired ethernet connection. I use it mostly for internet radio.

I’m connecting the USB output to a T+A DAC 8 DSD. This sounds fine at first. However, if I switch off the music (via the SqueezeCtrl app on my tablet) and then return to play more music after a longish, as yet undetermined, period, then I get intermittent and distorted sound. As far as I can tell it’s not a DAC issue as its diagnostic lights indicate the connection is properly maintained. It also has (once) happened after several hours of playing music - the music just stopped followed by a regular pulsing version of the sound. Killing Squeezelite and restarting it solved it.

In fact this issue can always be resolved by restarting Squeezelite (usually after having been killed first, rather than just stopped). But it’s a pain to have to keep doing that.

Previously, before I experimented with USB, I used a HiFiBerry Digi+ and connected with a phono lead. There were no problems whatever with this (except that it’s limited to 24/192). The basic hardware seems to be OK, there seems to be a software issue of some sort.

Hi Richard, you don't say how you have implemented Squeezelite, but have you tried using one of the other output settings for the dac?

Ronnie

[Richard Kimber]

Hi Richard, you don't say how you have implemented Squeezelite, but have you tried using one of the other output settings for the dac?

Ronnie

I'm using max2play on the Pi 3, and used the max2player implementation.

I'm using the default DAC 8 DSD HDAudio, because that seemed the obvious choice. There is a 'sysdefault DAC 8 DSD HDAudio' option, but why would that be any different?

- Richard.

[marcoc1712]

I'm using max2play on the Pi 3, and used the max2player implementation.

I'm using the default DAC 8 DSD HDAudio, because that seemed the obvious choice. There is a 'sysdefault DAC 8 DSD HDAudio' option, but why would that be any different?

- Richard.

You could try to add -C 1 at the squeezelite command line (don't know where in max2play), this cause squeezelite to release he connection to the dac after 1 sec of silence and re-open it when sound starts over.