[Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)

[gorman]

The very same track (Amarok 1h:00m:02s) plays flawlessly to DAC32 with this "complicated" conversion line:

[flac] -dcs $START$ $END$ -- $FILE$ | [sox] -q -t wav - -t flac -C 8 -b 16 - gain -8.5 bass +4.0 34 0.70q bass +4.5 100 0.70q equalizer 220 0.90q -2.2 equalizer 1050 1.00q -0.6 equalizer 1500 3.00q +0.7 equalizer 2200 1.20q +4.5 equalizer 2600 2.50q -2.5 equalizer 5800 3.50q -7.7 equalizer 7900 6.00q -3.0 treble -3.0 9000 0.70q

I say this because I honestly don't think it's DAC32 at fault here.

[mherger]

> The very same track (Amarok 1h:00m:02s) plays flawlessly to DAC32 with
> this "complicated" conversion line:

Please comment on the linked github issue. It's more likely a Windows
transcoding thing than Spotty.

[mherger]

> I use Max2play on a Raspberry Pi.

Did you try /etc/hosts editing trick outlined in that Github issue?

[bpa]

I am using the test socketwrapper.exe file, placed under C:\Program Files (x86)\Squeezebox\server\Bin\MSWin32-x86-multi-thread

I am just joining this thread as a result of a github comment on 1.12beta so I'll need to catch up.

In the meantime, if you enable player.source to DEBUG and run LMS from a command window - socketwrapper will produce logs.

[bpa]

.
.[22-03-06 17:59:54.5136] Slim::Player::Source::_readNextChunk (378) end of file or error on socket, song pos: 42161853
.
.
.

Buffer is filled, then it stops and plays back until the buffer is emptied.

Is 42161853 the full length of the song that should be sent to player or have converted bytes been lost ?

Confirm by running the conversion command but saving output in a fdile.

"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe" -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\ba008d57" --single-track "spotify://track:7zq1yjQyLZbJGdltQk1dka" --bitrate 320 --disable-discovery --disable-audio-cache --pass-through

[gorman]

Is 42161853 the full length of the song that should be sent to player or have converted bytes been lost ?

Confirm by running the conversion command but saving output in a fdile.

"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe" -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\ba008d57" --single-track "spotify://track:7zq1yjQyLZbJGdltQk1dka" --bitrate 320 --disable-discovery --disable-audio-cache --pass-through

I've replied to you via private message here. I don't want to clutter this discussion with endless backs and forths that mainly would stem from my technical ineptitude. I will definitely report back here if and when this gets solved, to leave a trace for future searches, etc.

[mherger]

> I use Max2play on a Raspberry Pi.

I've released v4.8.1 which has a new option to "use Spotify Fallback AP"
(Settings/Advanced/Spotty -> bottom). Could you please try this with the
other workarounds disabled? Would that help the playback issue?

[mJak]

After a week of frustrations, it looks like spotty is up and running again
I am using the fallback option.

[mJak]

After a week of frustrations, it looks like spotty is up and running again
I am using the fallback option.

Had to restart playing the album after 4 songs…..

[mherger]

> After a week of frustrations, it looks like spotty is up and running
> again

Did it resolve automatically, or did you do anything?