[Announce] Squeezelite-X

[rgdawson]

Thanks Greg. Now I think I understand what's going on.

I'm running LMS under Docker. In the "run docker" command I have the 9090 port mapped to 51415 for the reasons mentioned above. So LMS is responding to your discovery protocol with the port it thinks it's running - 9090 - when in fact outside of Docker it's running port 51415. Once it locks to 9090 I can't find any way to change it.

Maybe you can set the port in LMS Settings to use 51451 and then it will report that in discovery

R Greg Dawson

[puzzler]

I have never seen this, but I'll take a wild guess. Since squeezelite-X is a "player" (like other physical players - touch, radio, etc) perhaps you can check the LMS player settings, maybe crossfade...LMS UI->Settings->Player (tab)->audio (pulldown)

If you had another player that doesn't do this, maybe you could compare the settings between them

In my minds eye this might make sense regarding "often not always" if some songs end abruptly, but others have a long, barely audible fade out, or even silence at the end of the recording

Jim

I very much appreciate the suggestion. It appears that crossfade is off, although the crossfade time is set to 10 seconds. Also, the cutoff is abrupt, not a fade out. Maybe I'll try turning *on* the crossfade with a short duration, to see if a crossfade of 0 or 1 seconds is an improvement over the current behavior.

I do have a vague memory of long ago, when first setting up my original squeezebox player (which has since died, thus my interest in squeezelite-x), I think I configured it to have "gapless playback" between tracks. I wonder if that could be causing the quirk I'm experiencing in squeezelite-x. However, I can't find any such setting in the UI currently. Any ideas on whether "gapless playback" is still a setting, and if so, where to find it?

[Redrum]

Any ideas on whether "gapless playback" is still a setting, and if so, where to find it?

You know, I really don't know...I thought I had remember seeing it, but that might have been in another application that I use to batch convert music to mp3 for portable use (Media Monkey) Maybe someone else knows?

I did stumble on another thought. In squeezelite-x settings (the gear in the top bar, not material settings) there is a method to choose your output device. I'm using a cheap sound bar in Windows, and there are three choices for it. Perhaps the problem lies in the playback driver/device? I tend to try to think about "what's different with the problem system" (from others), and with sl-x it's the hardware - PC, sound card, driver, device..

I also am remembering from an old thread that LMS starts to buffer the next song before the current is finished. Maybe this event is related somehow.

Sorry if it's just another stab in the dark, it's all I got!

Jim

[zordaz]

I'm encountering an issue with Squeezelite-X where, fairly often but not always, the player will cut off the last several seconds of a song and advance to the next song.

Any tips on how to fix this? Thanks.

I am also experiencing this behaviour sometimes with Squeezelite-X and my two piCoreplayer-based software players. My SB Radio's play fine. Therefore I think it is an issue within Squeezelite itself. No crossfade configured btw.

[davidfox2116]

Maybe you can set the port in LMS Settings to use 51451 and then it will report that in discovery

R Greg Dawson

Thanks! Worked like a charm. So obvious once you pointed it out to me

[Francy07]

The default WASAPI behaviour, shared mode, has not changed, so is limited to 16/44.1.

You must add -a :1 to the command line to use a WASAPI device in exclusive mode which allows squeezelite to detect and use all sample rates that the device supports.
The Allow applications to take exclusive control of this device must be enabled in control panel, then the Default Format setting in control panel does not matter.

From the wasapi devices I have access, the list of sample rates supported by these devices is limited so I'd suggest to include -R -u E on the command line as well. Squeezelite will then resample content but only if the sample rate is not one supported natively by the device. This is common if you listen to internet radio.

Shared mode (default)
C:\> squeezelite-win -o "Speakers/Headphones (Realtek High Definition Audio) [Windows WASAPI]" -d output=debug

[07:50:53.120] output_init_pa:573 init output
[07:50:53.120] output_init_pa:593 requested latency: 0
[07:50:53.244] output_init_common:350 outputbuf size: 28224000
[07:50:53.244] output_init_common:374 idle timeout: 15000
[07:50:53.589] [B]output_init_common:414 supported rates: 44100[/B]
[07:50:53.589] pa_monitor:275 start monitor thread
[07:50:53.620] output_flush:427 flush output buffer
[07:50:53.620] output_flush:427 flush output buffer
[07:50:53.620] set_volume:111 setting internal gain left: 2048 right: 2048

Exclusive mode
C:\> squeezelite-win -R -u E -a :1 -o "Speakers/Headphones (Realtek High Definition Audio) [Windows WASAPI]" -d output=debug

[07:49:57.677] output_init_pa:573 init output
[07:49:57.677] output_init_pa:593 requested latency: 0
[07:49:57.802] output_init_common:350 outputbuf size: 28224000
[07:49:57.818] output_init_common:374 idle timeout: 15000
[07:49:57.818] test_open:197 [B]opening WASAPI device in exclusive mode[/B]
[07:49:58.130] [B]output_init_common:414 supported rates: 192000 96000 48000 44100[/B]
[07:49:58.130] pa_monitor:275 start monitor thread
[07:49:58.176] output_flush:427 flush output buffer
[07:49:58.176] output_flush:427 flush output buffer
[07:49:58.176] set_volume:111 setting internal gain left: 2048 right: 2048

Hello,
I installed Squeezelite X on Windows 10 Pro (from exe file “SqueezeliteX-2.11.7.0-setup_win64” which installs Squeezelite version 1.9.9-1401). I have an Audioquest Dragonfly Black dac that plays up to 96 Khz. I tried, to have the Wasapi exclusive mode, to give the following command, but I only sound with 96 Khz files and with 44.1 Khz I have no sound:


C:\Users\vince>C:\Programmi\Squeezelite-X\squeezelite-x64.exe -R -u E -a :1 -o "Altoparlanti (AudioQuest DragonFly) [Windows WASAPI]" -d output=debug
[18:14:19.879] output_init_pa:574 init output
[18:14:19.879] output_init_pa:594 requested latency: 0
[18:14:20.067] output_init_common:360 outputbuf size: 28224000
[18:14:20.067] output_init_common:384 idle timeout: 0
[18:14:20.067] test_open:197 opening WASAPI device in exclusive mode
[18:14:20.082] test_open:217 sample rate 1536000 not supported
[18:14:20.082] test_open:217 sample rate 1411200 not supported
[18:14:20.082] test_open:217 sample rate 768000 not supported
[18:14:20.082] test_open:217 sample rate 705600 not supported
[18:14:20.082] test_open:217 sample rate 384000 not supported
[18:14:20.098] test_open:217 sample rate 352800 not supported
[18:14:20.098] test_open:217 sample rate 192000 not supported
[18:14:20.098] test_open:217 sample rate 176400 not supported
[18:14:20.193] test_open:217 sample rate 32000 not supported
[18:14:20.193] test_open:217 sample rate 24000 not supported
[18:14:20.193] test_open:217 sample rate 22500 not supported
[18:14:20.193] test_open:217 sample rate 16000 not supported
[18:14:20.208] test_open:217 sample rate 12000 not supported
[18:14:20.208] test_open:217 sample rate 11025 not supported
[18:14:20.208] test_open:217 sample rate 8000 not supported
[18:14:20.208] output_init_common:426 supported rates: 96000 88200 48000 44100
[18:14:20.208] _pa_open:384 opening WASAPI device in exclusive mode
[18:14:20.218] _pa_open:410 opened device 13 - Altoparlanti (AudioQuest DragonFly) [Windows WASAPI] at 44100 latency 19 ms
[18:14:20.286] set_volume:111 setting internal gain left: 1230 right: 1230
[18:14:20.286] set_volume:111 setting internal gain left: 1230 right: 1230
[18:14:20.443] _output_frames:65 start buffer frames: 524287
[18:14:20.443] _output_frames:153 track start sample rate: 44100 replay_gain: 0
[18:14:20.444] pa_callback:526 pad with silence





I ask for resolution of the problem, possibly by Ralphy.
Best Regards.


Vincenzo, Italy

[nibblerrick]

I'm encountering an issue with Squeezelite-X where, fairly often but not always, the player will cut off the last several seconds of a song and advance to the next song.

Any tips on how to fix this? Thanks.

So I am not the only one...

On my SB Radio this doesn't happen and on the picoreplayers it doesn't happen, too.
What I tried so far:
- Running LMS 8.2 and 8.3
- tried on Win10 and Win11
- tried with default audio device and setting a specific device
- only happens with local files, radiostreams play fine and spotty-tracks play fine, too.
- I tried different settings with and without crossfade, direct streaming, proxy streaming
- the logwindow hat nothing conspicious in it

It happens quite often, but not always and it even doesn't happen at the same time on the same track sometimes.
I saw this behaviour for about three month now, so some updates where in between.

I have absolutely no idea what causes this. So I can't help much and probably the things I tried doesn't help much, either.

But if someone finds a solution please let us know. I'll still try different settings from time to time to see if I get a working solution.

[bwaldron]

So I am not the only one...

I have absolutely no idea what causes this. So I can't help much and probably the things I tried doesn't help much, either.

But if someone finds a solution please let us know. I'll still try different settings from time to time to see if I get a working solution.

I have experienced this in the past with squeezelite on my Windows PC. Using the option -b 16384 resolved it for me.

[nibblerrick]

Hi!

Thanks, I'll try that out ASAP. Curious if it makes a difference. Thanks very much!

[nibblerrick]

I have experienced this in the past with squeezelite on my Windows PC. Using the option -b 16384 resolved it for me.

Just wanted to drop a big THANK YOU!
That fixes it for me, too, very nice!

[Peter Galbavy]

Oddly this has just hit me today. Only difference to "normal" is I am playing MP3s on my PC and not the normal FLACs. Checking a bit more.

[Peter Galbavy]

This is consistent. The track playing is 3:08 but, as can be seen from the timestamps, only plays for 2:10. The playback of the new track starts 10 seconds after the playlist open. Just testing FLAC again, but I have been listening to those all morning so confident it's not those.

Waited for a FLAC playback, all OK and playlist open happens 10 seconds before actualy end of track - log below MP3 one.


I expect this is more Squeezelite related; so just to get more details:

Squeezelite v1.9.9-1403, Copyright 2012-2015 Adrian Smith, 2015-2021 Ralph Irving.

MP3 track 3:08 long in reality:

INFO   13:01:57.013  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Downloaded/Artists/amazonmp3/Sting%20&%20Shaggy/44%20876/08%20-%20Dreaming%20In%20The%20U.S.A..mp3
INFO   13:01:57.058  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Downloaded/Artists/amazonmp3/Sting%20&%20Shaggy/44%20876/08%20-%20Dreaming%20In%20The%20U.S.A..mp3
INFO   13:02:06.928  RCV (CLI): 00:25:ab:a8:4f:68 playlist newsong Dreaming In The U.S.A. 7
INFO   13:02:06.929  SND (CLI): 00:25:ab:a8:4f:68 [title ?, artist ?, album ?]
INFO   13:02:06.961  RCV (CLI): 00:25:ab:a8:4f:68 title Dreaming In The U.S.A.
INFO   13:02:07.023  RCV (CLI): 00:25:ab:a8:4f:68 artist Sting & Shaggy
INFO   13:02:07.028  RCV (CLI): 00:25:ab:a8:4f:68 album 44/876
INFO   13:04:08.690  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Downloaded/Artists/amazonmp3/Sting%20&%20Shaggy/44%20876/09%20-%20Crooked%20Tree.mp3
INFO   13:04:08.736  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Downloaded/Artists/amazonmp3/Sting%20&%20Shaggy/44%20876/09%20-%20Crooked%20Tree.mp3
INFO   13:04:18.909  RCV (CLI): 00:25:ab:a8:4f:68 playlist newsong Crooked Tree 8
INFO   13:04:18.909  SND (CLI): 00:25:ab:a8:4f:68 [title ?, artist ?, album ?]
INFO   13:04:18.949  RCV (CLI): 00:25:ab:a8:4f:68 title Crooked Tree
INFO   13:04:18.973  RCV (CLI): 00:25:ab:a8:4f:68 artist Sting & Shaggy
INFO   13:04:18.976  RCV (CLI): 00:25:ab:a8:4f:68 album 44/876

FLAC Track - 4:26 long

INFO   13:06:09.027  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Compilations/Heaven%20And%20Hell/01%20-%20Meatloaf%20-%20Dead%20Ringer%20For%20Love.flac
INFO   13:06:09.027  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Compilations/Heaven%20And%20Hell/01%20-%20Meatloaf%20-%20Dead%20Ringer%20For%20Love.flac
INFO   13:06:09.180  RCV (CLI): 00:25:ab:a8:4f:68 playlist newsong Dead Ringer For Love 0
INFO   13:06:09.181  SND (CLI): 00:25:ab:a8:4f:68 [title ?, artist ?, album ?]
INFO   13:06:09.230  RCV (CLI): 00:25:ab:a8:4f:68 title Dead Ringer For Love
INFO   13:06:09.260  RCV (CLI): 00:25:ab:a8:4f:68 artist Meatloaf
INFO   13:06:09.263  RCV (CLI): 00:25:ab:a8:4f:68 album Heaven And Hell
INFO   13:10:26.009  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Compilations/Heaven%20And%20Hell/02%20-%20Tyler,%20Bonnie%20-%20Holding%20Out%20For%20A%20Hero.flac
INFO   13:10:26.060  RCV (CLI): 00:25:ab:a8:4f:68 playlist open file:///media/hdd1/Music/Compilations/Heaven%20And%20Hell/02%20-%20Tyler,%20Bonnie%20-%20Holding%20Out%20For%20A%20Hero.flac
INFO   13:10:35.912  RCV (CLI): 00:25:ab:a8:4f:68 playlist newsong Holding Out For A Hero 1
INFO   13:10:35.912  SND (CLI): 00:25:ab:a8:4f:68 [title ?, artist ?, album ?]
INFO   13:10:35.948  RCV (CLI): 00:25:ab:a8:4f:68 title Holding Out For A Hero
INFO   13:10:35.975  RCV (CLI): 00:25:ab:a8:4f:68 artist Bonnie Tyler
INFO   13:10:35.978  RCV (CLI): 00:25:ab:a8:4f:68 album Heaven And Hell

[zordaz]

I have experienced this in the past with squeezelite on my Windows PC. Using the option -b 16384 resolved it for me.

I will test this setting as well. Just curious: which parameter is adjusted this way? Because the official syntax is:

-b <stream>:<output> Specify internal stream and output buffer sizes in kilobytes. Default is 2048:3446.

Your suggestion only changes one I guess? Which one?

[bwaldron]

I will test this setting as well. Just curious: which parameter is adjusted this way? Because the official syntax is:

-b <stream>:<output> Specify internal stream and output buffer sizes in kilobytes. Default is 2048:3446.

Your suggestion only changes one I guess? Which one?

I believe it changes the stream buffer. I can't recall/find exactly where I found the suggestion to try this parameter, but I'm sure it was somewhere on this forum (quite some time ago).

[ralphy]

Hello,
I installed Squeezelite X on Windows 10 Pro (from exe file “SqueezeliteX-2.11.7.0-setup_win64” which installs Squeezelite version 1.9.9-1401). I have an Audioquest Dragonfly Black dac that plays up to 96 Khz. I tried, to have the Wasapi exclusive mode, to give the following command, but I only sound with 96 Khz files and with 44.1 Khz I have no sound:


C:\Users\vince>C:\Programmi\Squeezelite-X\squeezelite-x64.exe -R -u E -a :1 -o "Altoparlanti (AudioQuest DragonFly) [Windows WASAPI]" -d output=debug

[18:14:20.208] output_init_common:426 supported rates: 96000 88200 48000 44100
[18:14:20.208] _pa_open:384 opening WASAPI device in exclusive mode
[18:14:20.218] _pa_open:410 opened device 13 - Altoparlanti (AudioQuest DragonFly) [Windows WASAPI] at 44100 latency 19 ms
[18:14:20.286] set_volume:111 setting internal gain left: 1230 right: 1230
[18:14:20.286] set_volume:111 setting internal gain left: 1230 right: 1230
[18:14:20.443] _output_frames:65 start buffer frames: 524287
[18:14:20.443] _output_frames:153 track start sample rate: 44100 replay_gain: 0
[18:14:20.444] pa_callback:526 pad with silence

I ask for resolution of the problem, possibly by Ralphy.
Best Regards.

Vincenzo, Italy

Is that the last line issued from the debug log? That log message is not likely the cause of your problem.

What happens after the pad with silence message is what matters.

There have been several fixes to WASAPI support in the portaudio library that is used in squeezelite for windows.

I've uploaded a rebuild of squeezelite-1.9.9-1403-ffmpeg-win64-2.zip which has the latest portaudio library, that includes the WASAPI changes, for you to try.