PDA

View Full Version : [Announce] Spotty v1.9.0 - now with experimental Spotify Connect support!



Pages : [1] 2 3 4

mherger
2017-09-22, 00:21
The title says it all :-). Except for how to enable the feature. Read all of this announcement to get there. Really!

23700

I'm currently playing a Daily Mix on my Transporter. Spotify Connect support - what does that mean:


Control Spotify playback on your Squeezebox using Spotify's applications (desktop, mobile)
Get access to (some of - see below) the Spotify content which is not available through their API yet, thus can't be accessed through the plugin
Transfer Spotify playback from your office Squeezebox to your phone to your car to your phone to your home Squeezebox


As the title says, this is still somewhat experimental. It's a bit of a hack, but it's the best I could get done so far (and I've failed many other approaches...). So here's the list of open issues and limitations I'm aware of already (though I bet people will skip this part and ask about them anyway...):


No Windows support (yet)
For whatever reason Spotify would not allow me to play Podcasts to Spotty
The metadata display can sometimes get slightly out of sync. Squeezebox would show the next track's metadata 5-10s before it actually starts playing (whil the previous track was still active)
Turning Spotify Connect off for a player would not always kill the daemon. Restart LMS to get rid of it, if this bothers you.
Spotify's limitations apply: if you play music to your Squeezebox using Connect, you cannot listen to Spotify on your phone or any other Spotify Connect endpoint.
Doesn't work with password protection on LMS.


Looks like a lot of limitations compared to the number of feature bullet points :-).

If you want to give this Spotty Connect a try anyway, go to the LMS web UI, Settings/Player/Spotty, and enable the feature for the device(s) you want. Please note that every activated player will launch a daemon in the background. Be careful if you run LMS on a NAS with 256MB or even less...

Many thanks go to marcelveldt who inspired me with his Spotify implementation for Kodi!

PS: NAS devices known to be compatible or not with Spotty at this point:

Synology: check out your model in the CPU architecture overview (http://www.synology-wiki.de/index.php/Welchen_Prozessortyp_besitzt_mein_System%3F). If it's in the Intel x86-*, or armv7 section, then you're fine. Make sure you're running the latest DSM and LMSRepack (http://forums.slimdevices.com/showthread.php?107180-Synology-7-9-1-packages&highlight=lmsrepack) or LMSUpdate. Otherwise I'm sorry.
ReadyNAS: The old Sparc based devices (Duo, NV), as well as their ARMv5 based successors (Duo v2, NV v2) will not work. On newer models you might need to manually install IO::Socket::SSL (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0&p=889635#post889635).
QNAP: similarly to Synology there are many different models. Unfortunately I haven't found a good overview (https://eu1.qnap.com/Storage/TechnicalDocument/20140618-QNAP_Turbo_NAS_Hardware_Manual_ENG.pdf). If you're on Intel, then you should be fine. ARM - depends on what exact model. You, too, might need to install IO::Socket::SSL (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0&p=890362&viewfull=1#post890362)

mherger
2017-09-22, 00:22
(Did I mention that this slightly premature release is not only to get things tested, but to celebrate the 5000th active Spotty user, too?)

castalla
2017-09-22, 01:22
Installed. BUT can't find any way to enable the player device.

mherger
2017-09-22, 01:31
You did read the announcement, didn't you?

castalla
2017-09-22, 01:44
You did read the announcement, didn't you?

Yes! Settings - Player - enable .... but there's no Spotty to enable

Evertjanus
2017-09-22, 01:59
Same here. With no clue how to get to Settings/Player/Spotty

Great work btw, this spotty app!

mherger
2017-09-22, 02:53
Hmmm... it's in the web UI only. Did you check that? I've installed it on three systems so far. And it has always worked.

What about your server.log? The implementation requires some command line tools (pv, wget or curl). Are they available on your systems?

castalla
2017-09-22, 03:07
Okay

log:

Plugins::Spotty::Connect::_getPVcmd (357) Didn't find the pv (pipe viewer) utility

so, we need to install this pv, I guess

Evertjanus
2017-09-22, 03:55
log states:
[17-09-22 09:52:56.2624] Plugins::Spotty::Connect::_getWgetCmd (343) Can't initialized Spotty Connect without the 'wget' utility. Please install curl using your package manager.


Being not very technical, I'm at a loss here.

mherger
2017-09-22, 04:10
> Plugins::Spotty::Connect::_getPVcmd (357) Didn't find the pv (pipe
> viewer) utility

Oh... two mistakes on my end: a.) I added a message about the lack of
those tools to the page which is not shown in case they were missing,
and b.) I thought pv was pre-installed in almost any Linux (except pCP -
for which I include a copy...). Will fix/improve this.

--

Michael

mherger
2017-09-22, 04:11
> log states:
> [17-09-22 09:52:56.2624] Plugins::Spotty::Connect::_getWgetCmd (343)
> Can't initialized Spotty Connect without the 'wget' utility. Please
> install curl using your package manager.

....and another poor copy/paste job... Oh well. That one's easy to fix
(the message only).

> Being not very technical, I'm at a loss here.

What operating system are you using?

--

Michael

Evertjanus
2017-09-22, 04:27
LMS is running on a MacMini, osx.

mherger
2017-09-22, 04:31
LMS is running on a MacMini, osx.

What version? These tools should be either pre-installed or part of Spotty. I'm doing my dev work on macOS.

Evertjanus
2017-09-22, 04:34
macOs Sierra 10.12.6 (16G29)

Logitech Media Server: 7.9.1

mherger
2017-09-22, 04:36
macOs Sierra 10.12.6 (16G29)

What if you typed "curl" in a terminal window? IIRC curl comes pre-installed with macOS. And wget should only be needed if curl was missing.

Evertjanus
2017-09-22, 04:41
I tried that, but curl isn't missing:

$ curl
curl: try 'curl --help' or 'curl --manual' for more information

mherger
2017-09-22, 04:49
I tried that, but curl isn't missing:

$ curl
curl: try 'curl --help' or 'curl --manual' for more information

Hmm... that's fine. What about "which perl"?

Evertjanus
2017-09-22, 04:55
$ perl -v

This is perl 5, version 18, subversion 2 (v5.18.2) built for darwin-thread-multi-2level
(with 2 registered patches, see perl -V for more detail)

mherger
2017-09-22, 04:57
Oops... should have been "which curl". Typed literally.

Evertjanus
2017-09-22, 05:11
Sorry, that command didn't work:
$ which curl
/usr/bin/curl
$ "which curl"
-bash: which curl: command not found

Evertjanus
2017-09-22, 05:13
I tried this:
$ curl --version
curl 7.54.0 (x86_64-apple-darwin16.0) libcurl/7.54.0 SecureTransport zlib/1.2.8
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets

mherger
2017-09-22, 05:28
Are you really, really sure, that page does not exist in Settings/Player/(your player)/Spotty Spotify?!? Please double-check... If that's really the case, then please set logging for plugin.spotty to INFO (Settings/Advanced/Logging), check the "keep settings for restart" box on the page, save settings. Then restart LMS, and upload your server.log file. Thanks!

d6jg
2017-09-22, 05:41
Tried this with an SB3 and worked first time.

The only issue which I have tripped over already is that control does not switch back to LMS

In the attached screenshot track 1 (thanks Pippin) was played from Spotify iPhone app, the rest (all local files) was added via the LMS web gui

What actually happens is that the Spotify track keep playing over and over even if you hit next

23707

EDIT
It is only the "next" button that doesn't work. If you click play on the next track control is back with LMS

EDIT 2
Initially I just tried a single track in Spotify
After choosing a playlist I can confirm that the "next" button will play the next Spotify track - although you never see the whole playlist in the web gui only the single track being played
If you add tracks from LMS to the player you have get control back from Spotify by hitting Play on an LMS track
This applies to the web gui and also control from iPeng

It is still great work Michael

Evertjanus
2017-09-22, 05:46
[17-09-22 14:43:31.1381] Plugins::Spotty::Plugin::getHelper (577) Found Spotty helper application: /Users/evertjanwijerde/Library/Caches/Squeezebox/InstalledPlugins/Plugins/Spotty/Bin/darwin-thread-multi-2level/spotty
[17-09-22 14:43:31.1489] Plugins::Spotty::Connect::_getWgetCmd (343) Can't initialized Spotty Connect without the 'wget' utility. Please install curl using your package manager.
[17-09-22 14:43:32.1313] Plugins::ShairTunes2W::Plugin::publishPlayer (369) avahi-publish-player not in path
[17-09-22 14:43:32.1320] Plugins::ShairTunes2W::Plugin::publishPlayer (372) start dns-sd "Eetkamer"
[17-09-22 14:43:32.1349] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (280) create client Slim::Player::SqueezePlay=ARRAY(0x7f8615c50808) with proc Proc::Background=HASH(0x7f8611f33eb8)
[17-09-22 14:43:32.5853] Plugins::ShairTunes2W::Plugin::publishPlayer (369) avahi-publish-player not in path
[17-09-22 14:43:32.5862] Plugins::ShairTunes2W::Plugin::publishPlayer (372) start dns-sd "Keuken"
[17-09-22 14:43:32.5909] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (280) create client Slim::Player::SqueezePlay=ARRAY(0x7f860d16d7e0) with proc Proc::Background=HASH(0x7f86158b4a58)
[17-09-22 14:43:32.8569] Plugins::ShairTunes2W::Plugin::publishPlayer (369) avahi-publish-player not in path
[17-09-22 14:43:32.8576] Plugins::ShairTunes2W::Plugin::publishPlayer (372) start dns-sd "Huiskamer"
[17-09-22 14:43:32.8656] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (280) create client Slim::Player::Squeezebox2=ARRAY(0x7f8611f8a978) with proc Proc::Background=HASH(0x7f8615c55fe0)
[17-09-22 14:43:36.8233] Plugins::Spotty::API::_call (1183) Trying to read from cache for me
[17-09-22 14:43:36.8235] Plugins::Spotty::API::_call (1192) API call: me
[17-09-22 14:43:37.0208] Plugins::Spotty::API::__ANON__ (1237) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[17-09-22 14:43:37.0213] Plugins::Spotty::API::__ANON__ (1239) Data cached (https://api.spotify.com/v1/me)

mherger
2017-09-22, 05:53
Evertjanus - could you please upload the _full_ server.log file? In 7.9.1 there's a link to get a zipped copy.

Plus please report what the binary search path in Settings/Information would report.

And post a screenshot of the various options you have in the Settings/Player dropdown...

d6jg
2017-09-22, 06:00
Tried it on a Sync group containing an o2 Joggler and 3 x Pi's by enabling Connect on the Joggler only.

Selecting the Joggler and hitting Play results in exactly what you would hope for fully synced music from all devices!

Nice one Michael

mherger
2017-09-22, 06:09
> In the attached screenshot track 1 (thanks Pippin) was played from
> Spotify iPhone app, the rest (all local files) was added via the LMS web
> gui
>
> What actually happens is that the Spotify track keep playing over and
> over even if you hit next

Ok, I see. Are you using any other service with this kind of
self-refreshing track (Pandora, Deezer SmartRadio, Slacker)? How would
they behave if you pressed the fwd button?

--

Michael

d6jg
2017-09-22, 06:24
> In the attached screenshot track 1 (thanks Pippin) was played from
> Spotify iPhone app, the rest (all local files) was added via the LMS web
> gui
>
> What actually happens is that the Spotify track keep playing over and
> over even if you hit next

Ok, I see. Are you using any other service with this kind of
self-refreshing track (Pandora, Deezer SmartRadio, Slacker)? How would
they behave if you pressed the fwd button?

--

Michael

No Michael I am not. Sorry.
I have found a few other things - do you want them posted here or would you prefer I PMd you or emailed ?

castalla
2017-09-22, 06:40
Installing pv got connect working .... a bit clunky in displaying track details, and difficult to switch away from to another connect player (using both spotify desktop and the spotify web browser control).

Evertjanus
2017-09-22, 06:55
Michael, Not being sure what you mean by binary info, I'll send you the requested screenshot and a zip file of the server.log. Would have pm'd if I knew how to handle attachments there.

d6jg
2017-09-22, 07:03
A few other observations

With DSTM OFF

Works correctly apart from when you add local tracks.
Pressing Next plays the next track in the Spotify playlist not the local tracks.
To get control back you must explicitly press Play on a local track.

If you do not add Tracks but leave Spotify playing then everything works.
Next will play the next track from the Spotify playlist.

With DSTM ON

Spotify Connect track playing.
DSTM will populate the playlist in the Web Gui.
Once this has occurred the Spotify Connect track from the playlist contiunues to play repeatedly.
Hitting Next also repeats the same track.
Hitting Play on a subsequent track reverts control to LMS as above



Spotify Connect (Generally)

After you have enabled a device the only way to remove it from Spotify Connect is to go to Spotify itself and then Account Settings and "Sign out of everywhere". Unticking it in the web gui isn't sufficient.

Sync Groups - its only necessary to enable one device in the group.

Hope this helps you Michael

mherger
2017-09-22, 07:12
> Installing pv got connect working .... a bit clunky in displaying track
> details, and difficult to switch away from to another connect player
> (using both spotify desktop and the spotify web browser control).

But it's exactly the same as for any other Spotify Connect endpoint,
isn't it?

--

Michael

mherger
2017-09-22, 07:15
> No Michael I am not. Sorry.

IMHO they behave the same: as long as one of those "stations" is
playing, FWD would bring up the next track on that station, but not skip
to a local track. I might be wrong, but that's what I've seen in my
little testing with Deezer.

> I have found a few other things - do you want them posted here or would
> you prefer I PMd you or emailed ?

Mail is probably best (michael ät slimdevices). Thanks!

--

Michael

mherger
2017-09-22, 07:23
Michael, Not being sure what you mean by binary info, I'll send you the requested screenshot and a zip file of the server.log. Would have pm'd if I knew how to handle attachments there.

Go to Settings/Information. There's a list of various paths. One of the is for the "helper applications" or the like.

I'm running out of ideas, really. For whatever reason Spotty fails to find curl - which is installed. I have no idea why :-(

castalla
2017-09-22, 07:25
> Installing pv got connect working .... a bit clunky in displaying track
> details, and difficult to switch away from to another connect player
> (using both spotify desktop and the spotify web browser control).

But it's exactly the same as for any other Spotify Connect endpoint,
isn't it?

--

Michael

Honestly, I couldn't say anymore, as I'm getting confused with all the devices in my connect list.

mherger
2017-09-22, 07:26
> With DSTM OFF
>
> Works correctly apart from when you add local tracks.
> Pressing Next plays the next track in the Spotify playlist not the local
> tracks.
> To get control back you must explicitly press Play on a local track.

As mentioned before I think that's the behaviour as seen for others like
Pandora or Deezer SmartRadio.

> With DSTM ON
>
> Spotify Connect track playing.
> DSTM will populate the playlist in the Web Gui.

This certainly shouldn't happen. And it doesn't happen for me: as long
as you only have that one Spotify track, DSTM should not kick in. Maybe
it's related to syncing? When you tested this, did you have players synced?

> After you have enabled a device the only way to remove it from Spotify
> Connect is to go to Spotify itself and then Account Settings and "Sign
> out of everywhere". Unticking it in the web gui isn't sufficient.

Well... I knew nobody would read the announcement. But this is bullet
point #6 in the "known issues" list :-P

--

Michael

d6jg
2017-09-22, 07:33
>

This certainly shouldn't happen. And it doesn't happen for me: as long
as you only have that one Spotify track, DSTM should not kick in. Maybe
it's related to syncing? When you tested this, did you have players synced?



Yes it was a group of synced players.




Well... I knew nobody would read the announcement. But this is bullet
point #6 in the "known issues" list :-P

--

Michael

RTFM ! You must be joking. Sorry :)

Jackisidore
2017-09-22, 09:40
On my Mac (10.12.6) and LMS 7.9.1 - 1505480690 with
curl --version
curl 7.54.0 (x86_64-apple-darwin16.4.0) libcurl/7.54.0 OpenSSL/1.0.2k zlib/1.2.11
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets HTTPS-proxy

server.log displays

[17-09-22 18:26:47.7648] Plugins::Spotty::Connect::_getWgetCmd (343) Can't initialized Spotty Connect without the 'wget' utility. Please install curl using your package manager.

so I installed wget with
brew install wget

after a restart of LMS it worked!

Thanks!!

zordaz
2017-09-22, 12:31
I think it is a good idea to add "pv" as a recommended package to the .deb builds of LMS 7.9.
I am not very familiar with .rpm anymore, but assume a similar solution is possible for .rpm based Linux distributions.

mherger
2017-09-22, 12:58
> server.log displays
>
> [17-09-22 18:26:47.7648] Plugins::Spotty::Connect::_getWgetCmd (343)
> Can't initialized Spotty Connect without the 'wget' utility. Please
> install curl using your package manager.

Oh my... that's rather embarrassing... I had commented out curl in order
to test wget. And forgot to re-enable curl... It seems most Linux
systems come with wget pre-installed, but macOS does not. Therefore the
reports from Mac users only.

I'll push out a fix asap. Thanks for the heads up!

--

Michael

Evertjanus
2017-09-22, 14:04
On my Mac (10.12.6) and LMS 7.9.1 - 1505480690 with
curl --version
curl 7.54.0 (x86_64-apple-darwin16.4.0) libcurl/7.54.0 OpenSSL/1.0.2k zlib/1.2.11
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets HTTPS-proxy

server.log displays

[17-09-22 18:26:47.7648] Plugins::Spotty::Connect::_getWgetCmd (343) Can't initialized Spotty Connect without the 'wget' utility. Please install curl using your package manager.

so I installed wget with
brew install wget

after a restart of LMS it worked!

Thanks!!

Thank you, this is how I managed to get it working too! (apart from having to install some xcode dev software too).

Jackisidore
2017-09-22, 14:41
> server.log displays[color=blue]

I'll push out a fix asap. Thanks for the heads up!

--

Michael

Uninstalled wget with brew uninstall wget
Spotify connects now works with 1.9.1

I noticed some odd behaviour. Even if spotify is disconnected from spotify connect LMS sometimes stops a LMS playlists and starts a single spotify track. Can't pinpoint what's going on. I'll watch my log

entries like this are flooding the log. Who or what is donnie

[17-09-22 23:28:45.8183] Plugins::Spotty::API::_call (1183) Trying to read from cache for search?limit=50&market=from_token&q=donnie&type=track
[17-09-22 23:28:45.8210] Plugins::Spotty::API::_call (1186) Returning cached data for search?limit=50&market=from_token&q=donnie&type=track
[17-09-22 23:28:45.8339] Plugins::Spotty::API::_call (1183) Trying to read from cache for search?limit=50&market=from_token&q=donnie&type=artist
[17-09-22 23:28:45.8345] Plugins::Spotty::API::_call (1186) Returning cached data for search?limit=50&market=from_token&q=donnie&type=artist
[17-09-22 23:28:45.8395] Plugins::Spotty::API::_call (1183) Trying to read from cache for artists/2ylIKKdMukkuprCgY4ZDFE?limit=50&market=from_token&offset=0

cramcram
2017-09-22, 15:00
Anybody got this running on Synology?

mherger
2017-09-22, 15:02
> Uninstalled wget with brew uninstall wget
> Spotify connects now works with 1.9.1

Thanks for the confirmation!

> I noticed some odd behaviour. Even if spotify is disconnected from
> spotify connect LMS sometimes stops a LMS playlists and starts a single
> spotify track. Can't pinpoint what's going on. I'll watch my log

Yes, I've seen that one, too. I think I know what's going on: I forget
to tell Spotify Connect to stop playback when a local track is being
played. After a while Spotify decides the next track should be played,
and tells LMS to play that track.

I'll try to fix this asap, too. :-)

--

Michael

Jaca
2017-09-22, 15:34
Hi Jaca - could you please head over to the 1.9.0 thread (http://forums.slimdevices.com/showthread.php?t=108030) and post your server.log file there? Also: what does Settings/Advanced/Spotty say? What max2play Version? Please post all answers in that other thread. Thanks!

Hi Michael, info as requested:
1. max2play - version is Version 2.44 (basic one without premium licence activation on old and cheerful Raspberry PI B)
2. Settings/Advanced/Spotty - this screen behaves rather oddly:
- it shows my account login - I've tried to remove account few times but it seems impossible.. after clicking "delete" button screen changes to 'automatic authorisation instructions' but my details are remembered at the bottom
- "Spotify Client ID" field is empty as suggested
- "Only show my library's albums for my library's artists" is unchecked..
- Spotty Helper Application - "/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty (v0.7.0)e"
- apart of that there is no other info showing status or errors or anything...
3. Logs 23712

I believe could be smth wrong with transcoding ??.. I've tried to change Spotty file type settings.. and when enabled flac there was no more "Problem: Can't open file for:" Songs was playing but silently (no audible :D) so wasn't really playing but no errors.
(btw I'm aware spotify stream isnt flac..)

Just to describe problem again ( pasted from other thread);

All worked fine until I updated spotty to v1.9.0.
I'm not able to stream any music from spotify now.. I can see my playlists etc.. (so I'm logged in) but whenever I try to play smth I get error on player display:
"Problem: Can't open file for:"

Thank you!

mherger
2017-09-22, 15:47
> Anybody got this running on Synology?

What Synology? I guess an armel based again?...

--

Michael

mherger
2017-09-22, 15:55
> 2. Settings/Advanced/Spotty - this screen behaves rather oddly:
> - it shows my account login - I've tried to remove account few times
> but it seems impossible.. after clicking "delete" button screen changes
> to 'automatic authorisation instructions' but my details are remembered
> at the bottom

That seems to be working as designed. The details are remembered by your
browser, not Spotty.

> I believe could be smth wrong with transcoding ??.. I've tried to

Please check whether transcoding to flac is enabled. If so, disable it
and try again.

--

Michael

Jaca
2017-09-22, 16:46
Please check whether transcoding to flac is enabled. If so, disable it
and try again.

Michael

Flac is disabled, I have only turned it on temporarily for diy troubleshooting , is was off as default.

Just to double check.. Is my old raspberry pi powerful enough to handle latest spotty version?

grimmace92
2017-09-22, 19:46
> Anybody got this running on Synology?

What Synology? I guess an armel based again?...

--

Michael

I have a synology DS1812+ with a Intel Atom D2700 processor. How do you install pipe viewer on it? Everything I have found is old and it appears ipkg is dead?

mherger
2017-09-22, 22:57
> Just to double check.. Is my old raspberry pi powerful enough to handle
> latest spotty version?

I'm sorry, that was premature optimization on my end :-(. Pi1 requires a
different binary than the others. I'll add it back...

--

Michael

cramcram
2017-09-23, 00:24
> Anybody got this running on Synology?

What Synology? I guess an armel based again?...

--

Michael

Nope - Intel based. LMS says pipe viewer and curl / wget is missing. Before I start fiddling around with packet managers I'd be happy to hear from somebody if it works and which packet manager is recommended.

Jackisidore
2017-09-23, 01:01
I disabled spotify connect for all my players, restarted LMS. Spotify (not Spotty) still remembers two spotify connect players and they also work.
After I switch back to the spotify app the track stops on the squeezebox. After a short pause it start playing again forever.

jr01
2017-09-23, 01:50
Hi Michael,

Very nice work! I got spotify connect fully working on my DS212/arm with some hacks.

#1 built spotty for DS212/armel with the rust-mdns patch I described here: https://github.com/plietar/rust-mdns/issues/10

#2 built custom pv, since the one in arm-linux folder gave 'illegal instruction' and pv wasn't available on the DS212


git clone https://github.com/icetee/pv
cd pv
export HOST=x86_64-unknown-linux-gnu
export TARGET=armv5te-rcross-linux-gnueabi
export CC=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-gcc
export AR=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ar
export LD=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ld
export CFLAGS="-Wall -Os -fPIC -D__arm__ -mfloat-abi=soft"
./configure --HOST=$HOST --TARGET=$TARGET
make

#3 Modified $knownIncompatible in Settings.pm


I can control the Squeezebox via the Spotify app (android&windows) and I am very happy with this :)

d6jg
2017-09-23, 01:57
I disabled spotify connect for all my players, restarted LMS. Spotify (not Spotty) still remembers two spotify connect players and they also work.
After I switch back to the spotify app the track stops on the squeezebox. After a short pause it start playing again forever.

I saw this too. I don't think stopping & starting LMS kills the daemon but a reboot of the box does.


Sent from my iPhone using Tapatalk

mherger
2017-09-23, 02:05
> I have a synology DS1812+ with a Intel Atom D2700 processor. How do you
> install pipe viewer on it?

I'll include a copy with the next update. Hopefully it'll work...

--

Michael

mherger
2017-09-23, 02:06
> Nope - Intel based. LMS says pipe viewer and curl / wget is missing.
> Before I start fiddling around with packet managers I'd be happy to hear
> from somebody if it works and which packet manager is recommended.

A fix is in the working. Running some tests right now before pushing it out.

--

Michael

Jackisidore
2017-09-23, 02:06
I saw this too. I don't think stopping & starting LMS kills the daemon but a reboot of the box does.



Yes, now I see. stopping LMS left four instances of spotty running. killing them solved the problem

mherger
2017-09-23, 02:09
> #1 built spotty for DS212/armel with the rust-mdns patch I described
> here: https://github.com/plietar/rust-mdns/issues/10

Does the copy which comes with Spotty not work?

> #2 built custom pv, since the one in arm-linux folder gave 'illegal
> instruction' and pv wasn't available on the DS212

Oh... Thanks, will give that a try! BTW: --HOST and --TARGET should be lower case.


> #3 Modified $knownIncompatible in Settings.pm

Another "Oh my...". Thanks for the heads up!

--

Michael

mherger
2017-09-23, 02:30
Spotty v1.9.2 now comes with pre-built pv binaries for most platforms. The code should use the system's copy if available, falling back to using the copy coming with Spotty. Thanks to jr01 this now should work on armel (ARMv5) based systems like many of the popular Synology NAS.

In addition to the improved Connect support I've added back the helper application required for Raspberry Pi1.

Oh, and the "Spotify Connect comes back after playing some local content" issue should hopefully be fixed, too.

Please note that Windows still is a no-go. Any other user please let me know about your findings.

Jackisidore
2017-09-23, 02:40
Spotty v1.9.2 now comes with pre-built pv binaries for most platforms. .

On MacOS spotify connect stopped working "Spotify Connect is not available: please use your system's package manager to install "pv" (Pipe Viewer), and "curl" or "wget"."

brew install pv

solved this

mherger
2017-09-23, 02:54
> mherger wrote:
>> Spotty v1.9.2 now comes with pre-built pv binaries for most platforms. .
>
> On MacOS spotify connect stopped working -"Spotify Connect is not
> available: please use your system's package manager to install "pv"
> (Pipe Viewer), and "curl" or "wget"."-

Running 1.9.2?!? Argh... do you have any message in server.log? What if
you renamed the pv-spotty file in the Bin/Darwin sub-folder of the
plugin to just pv?

v1.9.3 is on its way...

--

Michael

jr01
2017-09-23, 03:13
> #1 built spotty for DS212/armel with the rust-mdns patch I described
> here: https://github.com/plietar/rust-mdns/issues/10

Does the copy which comes with Spotty not work?


No it doesn't on the DS212 since it has a kernel < 3.9. This is the error that spotty -n a shows:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /home/mh/git/rust-cross-libs/rust-git/src/libcore/result.rs:906:4
Aborted

Jackisidore
2017-09-23, 03:13
running 1.9.3 now. didn't uninstall the brew pv version.

Only issue I see now is the spotty deamons don't quit if I disable spotify connect or stop LMS.

mherger
2017-09-23, 04:06
>>> #1 built spotty for DS212/armel with the rust-mdns patch I described
>>> here: https://github.com/plietar/rust-mdns/issues/10
>>
>> Does the copy which comes with Spotty not work?
>>
>
> No it doesn't on the DS212 since it has a kernel < 3.9. This is the
> error that spotty -n a shows:

But that's "only" a problem with discovery mode, isn't it? Any other
functionality should still work?

I'll look into adding your patch in some way. Thanks!
--

Michael

Jaca
2017-09-23, 05:33
> Just to double check.. Is my old raspberry pi powerful enough to handle
> latest spotty version?

I'm sorry, that was premature optimization on my end :-(. Pi1 requires a
different binary than the others. I'll add it back...

--

Michael

No worries Michael, I have updated to v1.9.3 and I can hear music again :D Yay!! Many thanks..

Just to let you know: "Connect" function is still not working in my case:
Automatic authorisation seems to work as info screen disperses after selecting it from client app and it recognise my account.. (btw yes you were rigth -it was browser login details before :D)
but it never connects and after few attempts it's no longer available as connect device: there is also hint: "Spotify not active on this device" (printscreens of behavior in attachment/below)

23715

peeter
2017-09-23, 06:04
Hi again!

I installed the latest version (1.9.3) on my Mac Mini with OS X 10.9, but I also removed the fix plugin that I had installed since a previous version, thinking that if that broke anything I could always install it again... But now that it has broken something (same problem as before - no sound) I wonder if you could reupload the fix plugin to your repo, as I can't find i there anymore.

edwin2006
2017-09-23, 07:13
after spotty reinstall with version 1.9.3 / lms 7.9.1 - 1505480690 @ Fri Sep 15 22:32:08 UTC 2017 something is broken.
When starting a track it wil play for 1 second normal and start to stotter. Already tried restart lms, removing all 3rd party plugins (except spotty) without luck. Please help

grimmace92
2017-09-23, 07:23
> mherger wrote:
>> Spotty v1.9.2 now comes with pre-built pv binaries for most platforms. .
>
> On MacOS spotify connect stopped working -"Spotify Connect is not
> available: please use your system's package manager to install "pv"
> (Pipe Viewer), and "curl" or "wget"."-

Running 1.9.2?!? Argh... do you have any message in server.log? What if
you renamed the pv-spotty file in the Bin/Darwin sub-folder of the
plugin to just pv?

v1.9.3 is on its way...

--

Michael

I just tested and it works but here is what I'm seeing. I played a song in the spotify app and it started correctly however when it went onto another song the Spotify app doesn't think its playing anything. It's still connected via spotify connect but the app itself doesn't pull up the song currently being played anymore nor can I bring up my available players in the Spotify app. I can tap another song and it will skip to it and start playing but the controls within the app have disappeared.

Update. I restarted LMS and things appear a little more stable. I’m using the airplay bridge though to make my players available. If I use connect and try to change the song the Spotify app boots me off of the player. I assume this has something to do with the one player at a time limitation but not 100% sure.

jasell
2017-09-23, 07:51
.... Any other user please let me know about your findings.
Just upgraded to 1.9.3
In 1.9.1 I just had to re-start my Qnap to get Spotty playing, I also lost all my apps until i restarted.
I guess I had several daemons running and that's why start/stop of LMS didn't do the trick.

Connect don't work yet, red message that PV and wget or curl is needed.
On the QNAP I can confirm that both wget and curl is available but not PV. I can't find a CPAN build for PV either, to manually install.
Is it possible for you to bundle it? (Intel based QNAP 459 U+ and 439 Pro II+)

If music is playing fine, should still change any transcoding to save CPU on my Qnaps?

mherger
2017-09-23, 08:27
> I installed the latest version (1.9.3) on my Mac Mini with OS X 10.9,
> but I also removed the fix plugin that I had installed since a previous
> version, thinking that if that broke anything I could always install it
> again... But now that it has broken something (same problem as before -
> no sound) I wonder if you could reupload the fix plugin to your repo, as
> I can't find i there anymore.

I plan to update the main macOS binary with the version you've been
testing, soon. Until then I'm putting that old file back. Please let me
know if that works again (Spotify Connect will NOT work with that
version, but I'm working on it).

--

Michael

mherger
2017-09-23, 08:30
> after spotty reinstall with version 1.9.3 / lms 7.9.1 - 1505480690 @ Fri
> Sep 15 22:32:08 UTC 2017 something is broken.
> When starting a track it wil play for 1 second normal and start to
> stotter. Already tried restart lms, removing all 3rd party plugins
> (except spotty) without luck. Please help
>
> *Server:* LMS on Pi3 7.9.1. on PcP 3.21

Did you try a system reboot? That's the configuration I'm using all day
long in the office.

--

Michael

edwin2006
2017-09-23, 08:40
> after spotty reinstall with version 1.9.3 / lms 7.9.1 - 1505480690 @ Fri[color=blue]

Did you try a system reboot? That's the configuration I'm using all day
long in the office.

--

Michael
I did a reboot after upgrading lms and reinstalling spotty. Just now i did a reboot again, no luck.
Also noticing that play / pauze in spotty is not reacting as quick as before.

cramcram
2017-09-23, 12:31
> I have a synology DS1812+ with a Intel Atom D2700 processor. How do you
> install pipe viewer on it?

I'll include a copy with the next update. Hopefully it'll work...

--

Michael

Success on my Synology DS-712+ (Intel-based). It works. I love you, Michael.

mherger
2017-09-23, 14:11
> Success on my Synology DS-712+ (Intel-based). It works. I love you,

Good to know! Thanks! (for the confirmation, this is :-))

--

Michael

mherger
2017-09-23, 14:15
> Just to let you know: "Connect" function is still not functioning in my
> case:

Is there anything in server.log?

TBH: I haven't tested with a Pi1 at all. It's the kind of system I
thought would be borderline: not much memory, some architecture
compatibility issues etc...


--

Michael

DaiWelsh
2017-09-23, 14:43
Hi Michael, great job on this tool, I just successfully installed on Win10 LMS and hooked up my squeezebox, spotify is back! My three kids will be so happy :)

joede121
2017-09-24, 06:08
Hi All

@ Michael Thanks for your great work.

I got the Spotify connect function working but i have one big problem. If I start for example my personal mixtape from the Spotify app the first song will be played on the connected squeezebox device but it will never switch to the next song automatically. The song will be played in loop and in the Spotify app the playback is shown as stopped. I tried the playback with mixtapes, albums, playlists etc. but with the same result. Does anyone experienced the same behavior?

My setup: LMS 9.1 on max2play rpi2, Spotty 1.9.3, Touch as player, android phone with Spotify app.
.
In the server.log i can see following entries regarding the spotty plugin, I'm not sure if these error message are related to my problem:

[17-09-24 14:56:42.2029] Plugins::Spotty::API::__ANON__ (1261) error: 401 Unauthorized
[17-09-24 14:57:34.4522] Plugins::Spotty::API::__ANON__ (1261) error: 401 Unauthorized

Best Regards

Joe

castalla
2017-09-24, 08:31
Spotty updated to 1.9.3 - this appears in log:

[17-09-24 16:44:10.9741] Plugins::Spotty::Connect::_getCurlCmd (329) Didn't find the 'curl' utility. Please install curl using your package manager.

I thought it was either/or for wget and curl ?

Gwaelod
2017-09-24, 09:23
Hi
Brilliant work with Spotty so far...I'm really enjoying it.

However I'm struggling to get this to work.

Running 7.9.1 on a Ubuntu 14.04 headless server

Seems like it's installed fine although I had to install pipe viewer first.

Ticked the option under settings/player but can't see The player appearing in the Spotify Connect app on my Android

My Spotify account is premium, and works fine with main Spotty implementation.

The player I'm trying to send it too is a Pi Zero W running PiCoreplayer/squeezelite.

Tried a couple of server reboots but still not showing up.

slartibartfast
2017-09-24, 09:37
Just installed 1.9.3 on my Pi3 with Max2Play. Connect seems to work but with some strange issues. Sometimes the track playing time bar does not move even though a track is playing. Sometimes the play icon is displayed instead of the pause icon. I think both of these things happen after tapping the next track icon while playing an album.

Sent from my SM-G900F using Tapatalk

slartibartfast
2017-09-24, 10:02
Is anyone else finding that tracks seem to crossfade when using connect.

Sent from my SM-G900F using Tapatalk

bernt
2017-09-24, 11:50
Hi!

Got Connect running on ReadyNAS RN202. Great work as always. Thanks! :D

Logitech Media Server Version: 7.9.1 - 1505480690 @ Fri Sep 15 14:14:32 UTC 2017
Operativsystem: Debian - SV - utf8
Plattformsarkitektur: armv7l-linux
Perl-version: 5.20.2 - arm-linux-gnueabi-thread-multi-64int
Audio::Scan: 0.95
Databasversion: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Totalt antal anslutna spelare: 4

Regards
Bernt

bernt
2017-09-24, 12:47
I noticed that a few settings like Music quality is not available in Spotify then using "Spotty Connect". Guess it is a limitation in Spotify beacuse the settings is missing then connected to a CCA to.

Connected to a Spotify Connect device like Audio Pro ADDON C5 the setting is there.

strim
2017-09-24, 13:03
Hi Michael,

Thanks again for this amazing plugin.
It Just Works !


Max2Play on an Pi3
Squeezebox Touch
Spotify on the Macbook

Sander

Oh No! it only plays the first song in the playlist ??

fraho
2017-09-24, 20:36
Hi Michael, thanks for bringing back Spotify to LMS and the implementation of Spotify Connect! I'm running LMS on an armel based Synology and can see my Squeezeboxes as target devices in the Spotify app as soon as I'm activating them in LMS - Settings - Player - Spotty Spotify for Squeezebox. However, after some time, don't know exactly how long, they disappear and I have do de- and reactivate the setting for both players to have them back.

mherger
2017-09-24, 21:05
> I thought it was either/or for wget and curl ?

Yes, it is. But the message is given no matter whether the other tool is
found or not. I assume it does work anyway?

--

Michael

mherger
2017-09-24, 21:09
Connect seems to work but with some strange issues. Sometimes the track playing time bar does not move even though a track is playing. Sometimes the play icon is displayed instead of the pause icon.

Yeah, something is not quite right there... I did get some random skipping of tracks, too. And looking at the diagram of requests being used I bet there's too many "pause" events going on:

23731

That orange line is the "pause" command, while the other lines represent all kinds of other API calls, like getting playlists, searches etc... And that's for all users together, many of which probably haven't even tested Connect yet.

mherger
2017-09-24, 21:11
> Hi Michael, thanks for bringing back Spotify to LMS and the
> implementation of Spotify Connect! I'm running LMS on an armel based
> Synology and can see my Squeezeboxes as target devices in the Spotify
> app as soon as I'm activating them in LMS - Settings - Player - Spotty
> Spotify for Squeezebox. However, after some time, don't know exactly how
> long, they disappear and I have do de- and reactivate the setting for
> both players to have them back.

Did Connect ever work at all on that device?

--

Michael

slartibartfast
2017-09-25, 00:02
Yeah, something is not quite right there... I did get some random skipping of tracks, too. And looking at the diagram of requests being used I bet there's too many "pause" events going on:

23731

That orange line is the "pause" command, while the other lines represent all kinds of other API calls, like getting playlists, searches etc... And that's for all users together, many of which probably haven't even tested Connect yet.In another post I mentioned that all tracks played using connect seem to crossfade. Have you noticed this? I don't hear this when playing to a Bluetooth speaker from my phone.

Sent from my SM-G900F using Tapatalk

fraho
2017-09-25, 00:14
Did Connect ever work at all on that device?


It's not possible to control the volume or anything else with the Spotify app. Switching Spotify Connect between my two Booms results in the song then being played from the beginning on the second device and having the first Boom continuing it. But at least I can hear something (unless both Booms are configured to be in sync, then there's no sound at all)

mherger
2017-09-25, 00:35
> It's not possible to control the volume etc.

Not possible from the Spotify app, yes. That's a known issue.

> or switch Spotify Connect
> between my two Booms without the song then being played from the
> beginning on the second device and having the first Boom continuing it.

Are you running LMS 7.9.1?

--

Michael

mherger
2017-09-25, 00:36
> In another post I mentioned that all tracks played using connect seem to
> crossfade. Have you noticed this? I don't hear this when playing to a
> Bluetooth speaker from my phone.

LMS settings apply. Do you have crossfading configured in LMS?

--

Michael

fraho
2017-09-25, 00:43
Are you running LMS 7.9.1?
Michael

No, it's 7.9.0

mherger
2017-09-25, 00:57
>> Are you running LMS 7.9.1?
>
> No, it's 7.9.0
That would explain why the track is starting from the beginning. You'll
need 7.9.1 to allow seeking within a track.

--
--

Michael

slartibartfast
2017-09-25, 00:58
> In another post I mentioned that all tracks played using connect seem to
> crossfade. Have you noticed this? I don't hear this when playing to a
> Bluetooth speaker from my phone.

LMS settings apply. Do you have crossfading configured in LMS?

--

MichaelThat will be it then although I have Smart Crossfade enabled which in LMS does not crossfade between tracks on the same album when played in order. I suppose an album on Spotify is not recognised as an album by LMS since tracks seem to appear one at a time in the Web UI.

Sent from my SM-G900F using Tapatalk

slartibartfast
2017-09-25, 02:25
Yeah, something is not quite right there... I did get some random skipping of tracks, too. And looking at the diagram of requests being used I bet there's too many "pause" events going on:

23731

That orange line is the "pause" command, while the other lines represent all kinds of other API calls, like getting playlists, searches etc... And that's for all users together, many of which probably haven't even tested Connect yet.I am getting the skipping tracks today after around 8 seconds the pause/play icon changes and the track skips. The skipping only seems to happen if the pause icon is displayed in the Spotify app and the time bar is changing. If the play icon is displayed and the time bar is not changing skipping does not occur.
When the time bar is not changing in Spotify it is changing in LMS.

Sent from my SM-G900F using Tapatalk

mherger
2017-09-25, 08:34
> That will be it then although I have Smart Crossfade enabled which in
> LMS does not crossfade between tracks on the same album when played in
> order. I suppose an album on Spotify is not recognised as an album by
> LMS since tracks seem to appear one at a time in the Web UI.

When playing in Connect mode, Spotify tracks are just tracks without any
context to LMS.

--

Michael

fraho
2017-09-25, 09:05
That would explain why the track is starting from the beginning. You'll
need 7.9.1 to allow seeking within a track.
Michael

O.k., but I wasn't trying to seek within a track. It happens when switching from one player to another in the Spotify app. Or has this technically the same background?

Btw: The issue with the dis- and reappearing devices in the Spotify app seems to be gone, after several hours my Booms are still listed in the Spotify Connect section. What I'm finding a little bit "unaesthetic" is that you can see the Mac-Address in brackets behind the player name.

d6jg
2017-09-25, 09:18
1.9.4 has just appeared as available. What's changed in it Michael?

bruinboy
2017-09-25, 09:32
Michael:

mac os 10.9.5
lms 7.9.1
spotty 1.9.3

spotify connect: I see my squeezebox player on spotify connect choices. Spotify connects and appears to play (on spotify player)... but...

no sound
no metadata on web browser/squeezebox player

thanks for helping me troubleshoot

SB

mherger
2017-09-25, 10:46
> 1.9.4 has just appeared as available. What's changed in it Michael?

It hopefully fixes the frequent pausing of the playback that happened on some installations.

Michael

mherger
2017-09-25, 10:48
> mac os 10.9.5

For macOS 10.9 you'd have to additionally install SpottyMacBin.

> lms 7.9.1
> spotty 1.9.3
>
> spotify connect: I see my squeezebox player on spotify connect choices.
> Spotify connects and appears to play (on spotify player)... but...

Connect currently doesn't work on 10.9 and older.

Michael

mherger
2017-09-25, 10:50
> O.k., but I wasn't trying to seek within a track. It happens when
> switching from one player to another in the Spotify app. Or has this
> technically the same background?

Yes, technically it's just starting playback at a specific position. Seeking would be interactive, Connect transfer automatic.

Michael

edwin2006
2017-09-25, 11:42
I did a reboot after upgrading lms and reinstalling spotty. Just now i did a reboot again, no luck.
Also noticing that play / pauze in spotty is not reacting as quick as before.
Just removed spotty, rebooted pi, installed spotty (1.9.4), rebooted pi. Still no luck.
Track is stuttering and playtime is jumping back and forth.
Please help.

slartibartfast
2017-09-25, 12:01
> 1.9.4 has just appeared as available. What's changed in it Michael?

It hopefully fixes the frequent pausing of the playback that happened on some installations.

MichaelJust installed 1.9.4 and see the same behaviour as 1.9.3. The first track of a palylist plays for 8 seconds while pause icon is displayed then playback skips to the next track and play icon is displayed while the track plays and track time stays at 0 seconds.

Sent from my SM-G900F using Tapatalk

slartibartfast
2017-09-25, 12:33
Just installed 1.9.4 and see the same behaviour as 1.9.3. The first track of a palylist plays for 8 seconds while pause icon is displayed then playback skips to the next track and play icon is displayed while the track plays and track time stays at 0 seconds.

Sent from my SM-G900F using TapatalkNever mind I rebooted the server reconnected the player and now it is fine.

Sent from my SM-G900F using Tapatalk

mherger
2017-09-25, 12:55
> Just removed spotty, rebooted pi, installed spotty (1.9.4), rebooted pi.
> Still no luck.
> Track is stuttering and playtime is jumping back and forth.

What player? Wireless or wired? Anything in server.log?

--

Michael

d6jg
2017-09-25, 14:00
Michael
Should an LMS restart also kill and restart the Connect daemons? I don't think it does so a Plugin upgrade probably needs a full system reboot to become effective?

slartibartfast
2017-09-25, 14:05
Michael
Should an LMS restart also kill and restart the Connect daemons? I don't think it does so a Plugin upgrade probably needs a full system reboot to become effective?

I found I needed to reboot my Pi to kill the daemon so I think your are correct.

jasell
2017-09-25, 18:53
Is it possible to add the PV module for Qnap-intel with in Spotty-plugin?
And just to sure, is this the Pipe Viewer -PV, we need:
http://www.ivarch.com/programs/pv.shtml

bruinboy
2017-09-25, 19:43
I upgraded (accidentally... meant to upgrade to os x sierra) to high sierra. spotty seems broken.

Thanks for all you do
BB

mherger
2017-09-25, 20:53
> Should an LMS restart also kill and restart the Connect daemons? I don't
> think it does so a Plugin upgrade probably needs a full system reboot to
> become effective?

Yes, there indeed is a problem with this. I tried to add some
brute-force "killall" approach in 1.9.4 when shutting down LMS. Can you
check whether this improves the situation?

--

Michael

mherger
2017-09-25, 20:55
> Is it possible to add the PV module for Qnap-intel with in
> Spotty-plugin?

It should be there already. Not QNAP specific, but Intel 32/64 bit. What
plugin version are you running? Can you log in to the device to run some
tests manually?

--

Michael

mherger
2017-09-25, 20:55
> I upgraded (accidentally... meant to upgrade to os x sierra) to high
> sierra. spotty seems broken.

Please define "broken". Working fine here.

--

Michael

philippe_44
2017-09-26, 00:28
> Should an LMS restart also kill and restart the Connect daemons? I don't
> think it does so a Plugin upgrade probably needs a full system reboot to
> become effective?

Yes, there indeed is a problem with this. I tried to add some
brute-force "killall" approach in 1.9.4 when shutting down LMS. Can you
check whether this improves the situation?

--

Michael

Hi Michael - BTW, I had to do the same on Shairtunes2 with my mDNS processes (one per player). Any idea why sometimes the player deletion callback does not seem to be called? I've had this problem only on Linux, not on Windows (for once ...)

slartibartfast
2017-09-26, 00:35
> Should an LMS restart also kill and restart the Connect daemons? I don't
> think it does so a Plugin upgrade probably needs a full system reboot to
> become effective?

Yes, there indeed is a problem with this. I tried to add some
brute-force "killall" approach in 1.9.4 when shutting down LMS. Can you
check whether this improves the situation?

--

MichaelI restarted LMS on Max2Play and that disconnected my Touch from Spotify Connect so this change works for me.

Sent from my SM-G900F using Tapatalk

mherger
2017-09-26, 01:15
> Hi Michael - BTW, I had to do the same on Shairtunes2 with my mDNS
> processes (one per player). Any idea why sometimes the player deletion
> callback does not seem to be called? I've had this problem only on
> Linux, not on Windows (for once ...)

I think in Spotty's case it's my using pipes in the command: the pid
stored in the Proc::Background object isn't spotty's, but the shell's.
That shell is killed correctly, but spotty (and pv) stay alive. I'm not
sure whether this is expected behaviour or not... Are you using
Proc::Background, too?

--

Michael

mherger
2017-09-26, 01:16
> I restarted LMS on Max2Play and that disconnected my Touch from Spotify
> Connect so this change works for me.

That would be good news. Thanks!

--

Michael

edwin2006
2017-09-26, 01:19
> Just removed spotty, rebooted pi, installed spotty (1.9.4), rebooted pi.
> Still no luck.
> Track is stuttering and playtime is jumping back and forth.

What player? Wireless or wired? Anything in server.log?

--

Michael
Appears to be a mixed issue. First that evening my wife also had a webinair problem. Resetting the modem and the router solved this.

This morning retested and SBRadio (wifi), SB Boom (wifi), SB2 (wired), RPi3-PCP3.20beta5-Squeezelite v1.8.6-945 (wired) are working ok with spotty now.
SB Player on android and RPi3-OSMC+squeezelite (not sure how to determine version) on rpi both are stuttering.
For the RPi with OSMC i noticed the follow line in server.log almost continously;
[17-09-26 09:22:05.9450] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:fc:ad:ed: request not dispatchable!
rebooted the osmc box and now it's working ok. Still almost every second the line [17-09-26 09:52:35.6171] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:fc:ad:ed: request not dispatchable! in the server.log. What could be causing this?

Strange part is that after rebooting the OSMC RPi also the Android SB PLayer is working normal?

Regards, Edwin

steves999
2017-09-26, 08:41
Apologies - I'm sure I've missed something obvious, but I can't get Connect working. I have 1.9.4 installed and the player enabled... The player shows up on the android spotify app and implies that it's transferred playback and is playing, but there's no response at all on the player or web ui.
Spotty itself is working fine.

I installed PV using apt-get and it seems to be present.

There's nothing obvious that i can see in the log.

My system is:
Odroid U3 running Max2Play (updated) with squeezeserver 1.9.1
Player - Joggler running Squeezeplay OS
Player - RPi 3 running PCP

mherger
2017-09-26, 09:01
> There's nothing obvious that i can see in the log.

Set the logging level for plugin.spotty to INFO, try again. Then upload
your server.log file.

--

Michael

d6jg
2017-09-26, 09:06
Pi3 with piCorePlayer 3.20 - dedicated LMS (Wired)
Logitech Media Server Version: 7.9.1 - 1505480690 @ Fri Sep 15 22:32:08 UTC 2017
Hostname: piLMS
Server IP Address: 10.0.0.7
Server HTTP Port Number: 9000
Operating system: piCore - EN - utf8
Platform Architecture: armv7l-linux
Perl Version: 5.24.0 - arm-linux-gnueabihf-thread-multi-64int
Audio::Scan: 0.95
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 8
Spotty 1.9.4

Running with a group of synced players (all wired) I am getting 5 seconds or so of a track, followed by a whole track, followed by 5 seconds of that track repeated, then the next track.
I haven't noticed DSTM / LastMix kick in though.

steves999
2017-09-26, 09:30
> There's nothing obvious that i can see in the log.

Set the logging level for plugin.spotty to INFO, try again. Then upload
your server.log file.

--

Michael

Does this help?
23742

TripleT
2017-09-26, 09:52
Hi,
sorry if this has been covered before, but I couldn't find anything. I'm trying the Spotify Connect thing on a Synology DS214. In server.log, I just get continuous messages like the following:


[17-09-26 17:49:32.7319] Plugins::Spotty::SettingsAuth::startHelper (134) Starting authentication deamon: /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a

If I log in via SSH and try to manually run this command, then this happens:


RUST_BACKTRACE=1 /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
Aborted


I added the RUST_BACKTRACE=1 in the hope that it would give more information, unfortunately that wasn't the case... any ideas or things that I could try?

philippe_44
2017-09-26, 12:03
> Hi Michael - BTW, I had to do the same on Shairtunes2 with my mDNS
> processes (one per player). Any idea why sometimes the player deletion
> callback does not seem to be called? I've had this problem only on
> Linux, not on Windows (for once ...)

I think in Spotty's case it's my using pipes in the command: the pid
stored in the Proc::Background object isn't spotty's, but the shell's.
That shell is killed correctly, but spotty (and pv) stay alive. I'm not
sure whether this is expected behaviour or not... Are you using
Proc::Background, too?

--

Michael

Yes I do use Proc::Background but it's a direct launch of the app, not in a shell so I assume I get the right PID. I handle creation / destruction by subscription to



Slim::Control::Request::subscribe( \&playerSubscriptionChange,
[ ['client'], [ 'new', 'reconnect', 'disconnect' ] ] );


It seems that the ->die() call does not always kill the process, but only in Linux

mherger
2017-09-26, 12:16
Yes I do use Proc::Background but it's a direct launch of the app, not in a shell so I assume I get the right PID.

From reading the documentation it seems that if you launch the application with all its parameters as a string, then the shell is being used. If you pass the executable's name and parameters as distinct elements of a list, then it shouldn't. Are you passing a string to ->new(), or a list?

mherger
2017-09-26, 12:18
[17-09-26 17:49:32.7319] Plugins::Spotty::SettingsAuth::startHelper (134) Starting authentication deamon: /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a


Make sure the __AUTHENTICATE__ folder does exist. If you call that command outside LMS, then likely this is not the case.

Would authentication using username/password work (from Settings/Advanced/Spotty)?

mherger
2017-09-26, 12:20
> Does this help?

It shows that the daemon indeed seems to be starting correctly. But it
doesn't look as if you had tried to play something. Did you?

--

Michael

philippe_44
2017-09-26, 12:20
From reading the documentation it seems that if you launch the application with all its parameters as a string, then the shell is being used. If you pass the executable's name and parameters as distinct elements of a list, then it shouldn't. Are you passing a string to ->new(), or a list?

I did not know that but I pass all parameters one by one (so in a list), not as a single string


Envoy de mon iPad en utilisant Tapatalk

mherger
2017-09-26, 12:20
> Running with a group of synced players (all wired) I am getting 5
> seconds or so of a track, followed by a whole track, followed by 5
> seconds of that track repeated, then the next track.

Yeah, I need to test the sync case. I wouldn't be surprised if that came
with a few more surprises...


--

Michael

jr01
2017-09-26, 12:37
Hi,
sorry if this has been covered before, but I couldn't find anything. I'm trying the Spotify Connect thing on a Synology DS214. In server.log, I just get continuous messages like the following:


[17-09-26 17:49:32.7319] Plugins::Spotty::SettingsAuth::startHelper (134) Starting authentication deamon: /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a

If I log in via SSH and try to manually run this command, then this happens:


RUST_BACKTRACE=1 /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
Aborted


I added the RUST_BACKTRACE=1 in the hope that it would give more information, unfortunately that wasn't the case... any ideas or things that I could try?

What kernel version are is running on the DS214? If it is < 3.9 discovery won't work until Michael picks up my patch

jr01
2017-09-26, 12:39
Hi,
sorry if this has been covered before, but I couldn't find anything. I'm trying the Spotify Connect thing on a Synology DS214. In server.log, I just get continuous messages like the following:


[17-09-26 17:49:32.7319] Plugins::Spotty::SettingsAuth::startHelper (134) Starting authentication deamon: /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a

If I log in via SSH and try to manually run this command, then this happens:


RUST_BACKTRACE=1 /volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/volume1/@appstore/LmsRepack/Cache/spotty/__AUTHENTICATE__" -n "Spotify Anmeldung (NAS)" -a
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
Aborted


I added the RUST_BACKTRACE=1 in the hope that it would give more information, unfortunately that wasn't the case... any ideas or things that I could try?

What kernel version does the DS214 have? If it is < 3.9 then discovery doesn't work, until Michael picks up my patch to rust-mdns

steves999
2017-09-26, 12:57
> Does this help?

It shows that the daemon indeed seems to be starting correctly. But it
doesn't look as if you had tried to play something. Did you?

--

Michael

Thanks for taking a look... Yes, I was playing something on the Spotify android app, it showed my player available as a device to connect to, selected it (selected player turned green and said "Listening on Lounge (mac address) in app) and playback stopped on the phone...however, nothing on the player at all.....

(btw... Connect works between other devices such as laptops running the Spotify software)

jasell
2017-09-26, 15:07
> Is it possible to add the PV module for Qnap-intel with in
> Spotty-plugin?

It should be there already. Not QNAP specific, but Intel 32/64 bit. What
plugin version are you running? Can you log in to the device to run some
tests manually?

--

Michael

Im using spotty 1.9.4 and LMS 7.9.1
I do get the warning in player settings for spotty.

I can log to the qnap using a terminal window, but what should I test manually?

mherger
2017-09-26, 21:49
> I€™m using spotty 1.9.4 and LMS 7.9.1
> I do get the warning in player settings for spotty.
>
> I can log to the qnap using a terminal window, but what should I test
> manually?

Go to Settings/Information to find out where LMS is looking for the
files (there's a section about the helper binaries). Log in to your NAS,
change to Spotty's Bin/i386-linux folder (or similar), and try to run
the various binaries you find in there. And please report what

ls -l *
file *

give.

--

Michael

TripleT
2017-09-27, 03:01
What kernel version does the DS214 have? If it is < 3.9 then discovery doesn't work, until Michael picks up my patch to rust-mdns

Thanks, ok, saw your bug report against rust-mdns. The DS214 runs on 3.2.40, so that's precisely the problem.
Will use username+password for now, which runs fine, but I'd love to be able to try the Connect functionality at some point :)

fraho
2017-09-27, 05:29
Hi Michael,

I just wanted to let you know that my two Booms had disappeared again as Spotify Connect devices until I restarted LMS. Maybe that's also an effect with LMS 7.9.0 (?)

castalla
2017-09-27, 05:31
I'm still finding the connect feature very difficult to use. Tracks play okay on Touch - BUT attempting to switch to another connect device (eg. Echo Dot) is very hit'n'miss with the chosen device failing to indicate on the Spotify list, and where the Touch is still shown as the chosen player.

Real connect devices switch immediately and without issue.

jasell
2017-09-27, 14:08
> I’m using spotty 1.9.4 and LMS 7.9.1
> I do get the warning in player settings for spotty.
>
> I can log to the qnap using a terminal window, but what should I test
> manually?

Go to Settings/Information to find out where LMS is looking for the
files (there's a section about the helper binaries). Log in to your NAS,
change to Spotty's Bin/i386-linux folder (or similar), and try to run
the various binaries you find in there. And please report what

ls -l *
file *

I login using PuTTY
Navigate to /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux

ls -l *
-rwxr-xr-x 1 ssods ssods 131404 Sep 23 07:49 pv-i386*
-rwxr-xr-x 1 ssods ssods 147400 Sep 23 08:02 pv-x86_64*
-rwxr-xr-x 1 ssods ssods 2999596 Sep 21 22:04 spotty*
-rwxr-xr-x 1 ssods ssods 2979848 Sep 21 21:33 spotty-x86_64*

file *
-sh: file: command not found

By running the binaries, do you mean just enter their name?
for any of the files I get:
pv-i386
-sh: pv-i386: command not found

This is very strange to (windows user) that these binaries can be run even though I'm in the same directory..

By adding this location to my path I can now execute all 4 binaries
echo 'export PATH=$PATH:/opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux' >> /etc/profile

But still same error in LMS settings/player/Spotty:
Spotify Connect is not available: please use your system's package manager to install "pv" (Pipe Viewer), and "curl" or "wget".

jr01
2017-09-27, 16:04
>>> #1 built spotty for DS212/armel with the rust-mdns patch I described
>>> here: https://github.com/plietar/rust-mdns/issues/10
>>
>> Does the copy which comes with Spotty not work?
>>
>
> No it doesn't on the DS212 since it has a kernel < 3.9. This is the
> error that spotty -n a shows:

But that's "only" a problem with discovery mode, isn't it? Any other
functionality should still work?

I'll look into adding your patch in some way. Thanks!
--

Michael

Yes it only panics with discovery / spotify connect mode.

Here is a PR I just created to fix the issue in rust-mdns: https://github.com/plietar/rust-mdns/pull/11

Perhaps you can change the rust-mdns reference in https://github.com/michaelherger/librespot/blob/spotty/Cargo.toml to

[target.'cfg(not(target_os = "windows"))'.dependencies]
mdns = { git = "https://github.com/jr01/rust-mdns" }
branch = spotty

and we can test the binaries here?

I think my PR could also take us one step closer to getting rust-mdns working on Windows (by adding windows to [cfg(...)]), but I haven't rust cross compiled for Windows yet...and that will take me some time to investigate...

mherger
2017-09-27, 22:25
I think my PR could also take us one step closer to getting rust-mdns working on Windows (by adding windows to [cfg(...)]), but I haven't rust cross compiled for Windows yet...and that will take me some time to investigate...

FWIW: my experience trying to cross-compile has been very poor. Not only for Windows, but eg. building on macOS for Linux. I think there's one dependency which has not been correctly configured, creating binaries for the wrong platform. As librespot is moving away from libvorbis to lewton (I think) this issue might be resolved somehow. But then there are other issues with the latest librespot version...

mherger
2017-09-27, 22:27
> By running the binaries, do you mean just enter their name?

Yes. Or put ./ in front of them to tell the system to pick the files in
the current folder.

> for any of the files I get:
> pv-i386
> -sh: pv-i386: command not found

I guess your system is x86_64 based? What do you get for the other pv
binary?

--

Michael

mherger
2017-09-27, 22:32
> Will use username+password for now, which runs fine, but I'd love to be
> able to try the Connect functionality at some point :)

Connect should work even without discovery. The clients would get the
information about available players from Spotify's servers. I eg. see
devices at home when in the office or on the road.

--

Michael

mherger
2017-09-27, 22:34
> I just wanted to let you know that my two Booms had disappeared again as
> Spotify Connect devices until I restarted LMS. Maybe that's also an
> effect with LMS 7.9.0 (?)

It's likely the daemon crashing. What platform are you on? Did you check
server.log for traces of spotty?

--

Michael

buzzsb
2017-09-27, 23:41
[17-09-28 08:36:29.0365] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Web::HTTP::processHTTP: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe3b7478)

slartibartfast
2017-09-28, 00:48
If I transfer playback from one Squeezebox device to another then the original device still plays. I assume this is because the daemon is still running.

Sent from my SM-G900F using Tapatalk

mherger
2017-09-28, 01:30
> If I transfer playback from one Squeezebox device to another then the
> original device still plays. I assume this is because the daemon is
> still running.

It's actually a deliberate choice I made, because I thought it would be
nicer not to stop the music abruptly.

--

Michael

mherger
2017-09-28, 01:30
> [17-09-28 08:36:29.0365] Slim::Networking::IO::Select::__ANON__ (147)
> Error: Select task failed calling Slim::Web::HTTP::processHTTP:
> Undefined subroutine &Slim::Utils::Network::serverURL called at
> /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm
> line 337.
> ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe3b7478)

Oh... that function is 7.9.0 only. I'll have to fix that. Thanks for the
heads up!

--

Michael

slartibartfast
2017-09-28, 02:13
> If I transfer playback from one Squeezebox device to another then the
> original device still plays. I assume this is because the daemon is
> still running.

It's actually a deliberate choice I made, because I thought it would be
nicer not to stop the music abruptly.

--

MichaelI have not tried this but will it stop playing after the current track?

Sent from my SM-G900F using Tapatalk

mherger
2017-09-28, 02:50
>>> If I transfer playback from one Squeezebox device to another then the
>>> original device still plays. I assume this is because the daemon is
>>> still running.
>>
>> It's actually a deliberate choice I made, because I thought it would be
>> nicer not to stop the music abruptly.
> I have not tried this but will it stop playing after the current track?

Yes, it's supposed to play the current track to the end, then stop
playback.

--

Michael

slartibartfast
2017-09-28, 03:20
>>> If I transfer playback from one Squeezebox device to another then the
>>> original device still plays. I assume this is because the daemon is
>>> still running.
>>
>> It's actually a deliberate choice I made, because I thought it would be
>> nicer not to stop the music abruptly.
> I have not tried this but will it stop playing after the current track?

Yes, it's supposed to play the current track to the end, then stop
playback.

--

MichaelNow I have tried this and it does not stop after the current track. It is now on the third track of an album when I transferred to another device during track one.

Sent from my SM-G900F using Tapatalk

slartibartfast
2017-09-28, 03:23
Now I have tried this and it does not stop after the current track. It is now on the third track of an album when I transferred to another device during track one.

Sent from my SM-G900F using TapatalkAnd if I stop playback on the new device from the Spotify app playback continues on the first device.

Sent from my SM-G900F using Tapatalk

mherger
2017-09-28, 04:45
> And if I stop playback on the new device from the Spotify app playback
> continues on the first device.

DSTM kicking in?

--

Michael

slartibartfast
2017-09-28, 05:18
> And if I stop playback on the new device from the Spotify app playback
> continues on the first device.

DSTM kicking in?

--

MichaelIt is playing the same album in the same order so if it is DSTM it would be a big coincidence. This would be a case when you would not want DSTM to kick in anyway since you have chosen to transfer playback away from the device. In this case DSTM was disabled for that device.

Sent from my SM-G900F using Tapatalk

castalla
2017-09-28, 07:15
Michael!

I tried the Connect feature again. After the usual inability to switch connect endpoints via the spotify web app, I then rebooted the server ... and discovered I couldn't login in via Putty (connection refused).

However, I was able to use the LMS web-gui.

I then did another cold-boot after disabling the connect option via the LMS settings.

Here's the log entries for this process:

};
[17-09-28 16:02:50.4896] Plugins::Spotty::Connect::_getCurlCmd (361) Didn't find the 'curl' utility. Please install curl using your package manager.
[17-09-28 16:03:09.1729] Slim::Formats::XML::gotErrorViaHTTP (338) Error: getting http://opml.radiotime.com/Index.aspx?partnerId=16
Connect timed out: Inappropriate ioctl for device
[17-09-28 16:03:09.1741] Slim::Plugin::InternetRadio::Plugin::_gotRadioErro r (67) Unable to retrieve radio directory from SN: Connect timed out: Inappropriate ioctl for device
[17-09-28 16:03:36.1325] Slim::Utils::Firmware::downloadAsyncError (581) Warning: Firmware: Failed to download http://update.slimdevices.com/update/firmware/7.9.1/fab4.version (Connect timed out: No such file or directory), will try again in 10 minutes.
[17-09-28 16:03:36.1406] Slim::Utils::Firmware::downloadAsyncError (581) Warning: Firmware: Failed to download http://update.slimdevices.com/update/firmware/7.9.1/baby.version (Connect timed out: ), will try again in 20 minutes.

I had installed curl way back when the first spotty connect plugin was available.

Using:

Operating system: Debian - EN - utf8
Platform Architecture: i686-linux
Perl Version: 5.18.2 - i686-linux-gnu-thread-multi-64int

takerna
2017-09-28, 09:44
Working OK in my ReadyNas Ultra 4 (OS 4) after installing just pv.

Thanks (again) for your work, mherger!

TripleT
2017-09-28, 14:12
> Will use username+password for now, which runs fine, but I'd love to be
> able to try the Connect functionality at some point :)

Connect should work even without discovery. The clients would get the
information about available players from Spotify's servers. I eg. see
devices at home when in the office or on the road.

Interesting... this doesn't work for me. When I use username+password, I cannot see Spotty on my Macbook nor on my Android phone (but those two see each other).

maddymarc
2017-09-28, 16:07
I am now playing a Spotty daily mix through my synchronized SB3, SB2, and piCorePlayer. LMS is running on another pCp with squeezelite disabled.
This. Is. Awesome.
Thank you so much, Michael, for continuing to support those of us who refuse to stop using LMS!
All the thumbs up!

Forgive me if this has been covered, but does the queue for a daily mix show up for others in LMS GUI? I only have the current song and the first listed.

frisser
2017-09-29, 00:17
Spotify Connect works perfect on my Squeezebox Touch with LMS running on a CuBox-i4Pro (Armbian). Thanks Michael, and I can only agree with maddymarc - your continuing support is amazing and highly appreciated! :)

Giza2020
2017-09-29, 06:29
Michael awesome work!

I have noticed something odd.

track plays from app for 10 or 20 seconds - shows track time.
skips to next track
Next track plays - no time info.
plays fully.
Repeats with next track skipping and next one not and so on.
1 skip . 1play. 1 skip. 1 play

on pi LMS server ( maybe 2 nighties behind)
happens on max2play
happens on boom

Android Spotify app

slartibartfast
2017-09-29, 06:47
Michael awesome work!

I have noticed something odd.

track plays from app for 10 or 20 seconds - shows track time.
skips to next track
Next track plays - no time info.
plays fully.
Repeats with next track skipping and next one not and so on.
1 skip . 1play. 1 skip. 1 play

on pi LMS server ( maybe 2 nighties behind)
happens on max2play
happens on boom

Android Spotify appTry restarting LMS.

Sent from my SM-G900F using Tapatalk

Max2Play
2017-09-29, 07:27
Again, great work and congrats on a really intuitive and pratical wrinkle to an already great solution!

Obviously, we immediately tested it with a fresh Max2Play image and it works great.

We also added a little paragraph to our tutorial (https://www.max2play.com/en/how-tos/howto-spotify/) to make sure all new users don't overlook this great feature.

Jaca
2017-09-29, 09:04
Hi Michael,

I have finally managed to get Connect on Spotty "working".
I'm able to see new devices in Spotify client and switch playback to them.. however it take about 15-20 sec of Connecting/Buffering and playback stops after songs finishes (It always tries to play next song but after second or two it stops)

btw I got it working and both RaspPi 1 (modelB) and Raspi 3 (modelB) which I just received.
What I found very weird is that at one point I had LMS running and both Pi's, with half of my players connected to each. One of them (No1) had local music (NAS) playback when I was testing Connect on Other LMS (No2).. Suddenly Spotify started playing on LMS No1 but I haven't ask it to do so.. lol I'm curious whats going on behind the scene with your Connect implementation.. its very interesting :D

Anyway is this 15-20sec delay a normal behavior? Other connect devices switch immediately as far as I'm aware.
btw Raspi 1 runs on Max2Play and Raspi 3 got Raspbian Stretch installed.
Thanks

castalla
2017-09-29, 09:53
I've given up using the connect feature ... for some unknown reason, on my LMS, attempting a reboot always ends up with 'unable to access via Putty'. The last time, the server failed to reboot - had to do a reinstall from scratch.

Giza2020
2017-09-29, 10:47
Try restarting LMS.

Sent from my SM-G900F using Tapatalk

Will test further

buzzsb
2017-09-29, 11:47
I am running the latest Synology LMS package: 7.7.6-113. I will wait for your next release.

> [17-09-28 08:36:29.0365] Slim::Networking::IO::Select::__ANON__ (147)
> Error: Select task failed calling Slim::Web::HTTP::processHTTP:
> Undefined subroutine &Slim::Utils::Network::serverURL called at
> /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm
> line 337.
> ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe3b7478)

Oh... that function is 7.9.0 only. I'll have to fix that. Thanks for the
heads up!

--

Michael

verypsb
2017-09-30, 04:27
No Windows support (yet)


That looks promising! I thought librespot didn't support Spotify Connect on Windows...

Best regards,
Dennis.

Giza2020
2017-09-30, 08:51
Will test further

installed latest nightly and we seem to have lift off. no.skipping and appears to be flawless playback via Spotify connect.

As always thank you Michael and the donation button will be activated once more :-)

Giza2020
2017-10-01, 01:48
installed latest nightly and we seem to have lift off. no.skipping and appears to be flawless playback via Spotify connect.

As always thank you Michael and the donation button will be activated once more :-)

spoke too soon.

happening again.... need to investigate further

jasell
2017-10-01, 01:48
> By running the binaries, do you mean just enter their name?

Yes. Or put ./ in front of them to tell the system to pick the files in
the current folder.

> for any of the files I get:
> pv-i386
> -sh: pv-i386: command not found

I guess your system is x86_64 based? What do you get for the other pv
binary?

--

Michael
Correct, my Qnap has an intel x86_64

When I try to run the four binaries by just their name (pv-i386, pv-x86_64, spotty and spotty-x86_64) I get the same result for all:

-sh: spotty-x86_64: command not found

If I do as you suggest and add ./ they execute, for instance:
./spotty-x86_64

spotty v0.7.0
error: Required option 'name' missing.
Usage: ./spotty-x86_64 [options]

Options:
-c, --cache CACHE Path to a directory where files will be cached.
--enable-audio-cache
Enable caching of the audio data.
--disable-audio-cache
(Only here fore compatibility with librespot - audio
cache is disabled by default).
-n, --name NAME Device name
-b, --bitrate BITRATE
Bitrate (96, 160 or 320). Defaults to 160
--onstart PROGRAM
Run PROGRAM when playback is about to begin.
--onstop PROGRAM
Run PROGRAM when playback has ended.
--onchange PROGRAM
Run PROGRAM when playback changes (new track, seeking
etc.).
--single-track ID
Play a single track ID and exit.
--start-position STARTPOSITION
Position (in ms) where playback should be started.
Only valid with the --single-track option.
-u, --username USERNAME
Username to sign in with
-p, --password PASSWORD
Password
-a, --authenticate Authenticate given username and password. Make sure
you define a cache folder to store credentials.
--disable-discovery
Disable discovery mode
-t, --get-token Get oauth token to be used with the web API etc.
-i, --client-id CLIENT_ID
A Spotify client_id to be used to get the oauth token.
Required with the --get-token request.
--scope SCOPE The scopes you want to have access to with the oauth
token.
-x, --check Run quick internal check


./pv-x86_64


0.00 B 0:01:13 [0.00 B/s] [<=>


Just for reference...
wget


wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.


curl


curl: try 'curl --help' or 'curl --manual' for more information


It seems somehow that the Spotty plugins do not recognize the binaries...

I upgraded to the latest nightly of LMS 7.9.1 and clear my log-file.
On restart this is what i get in the log-file:


[17-10-01 11:17:46 ] ssctrl Stopping SqueezeboxServer 7.9.1-1505480690.
[17-10-01 11:17:47 ] ssctrl SqueezeboxServer stopped.
[17-10-01 11:18:07 ] ssctrl Starting SqueezeboxServer 7.9.1-1505480690.
[17-10-01 11:18:07 ] ssctrl Command line = /opt/ssods4/var/home/SqueezeboxServer/slimserver.pl --daemon --pidfile /opt/ssods4/var/home/SqueezeboxServer/Cache/squeezecenter.pid --cachedir /opt/ssods4/var/home/SqueezeboxServer/Cache --logdir /opt/ssods4/var/home/SqueezeboxServer/Logs --prefsdir /opt/ssods4/var/home/SqueezeboxServer/Prefs --noupnp --nodebuglog --noinfo --priority 0 --user ssods --group ssods --httpport 9001
[17-10-01 11:18:11.3787] main::init (387) Starting Logitech Media Server (v7.9.1, 1505480690, Fri Sep 15 20:21:59 UTC 2017) perl 5.010000 - i686-linux-thread-multi
[17-10-01 11:18:11.3782] main::init (387) Starting Logitech Media Server (v7.9.1, 1505480690, Fri Sep 15 20:21:59 UTC 2017) perl 5.010000 - i686-linux-thread-multi
[17-10-01 11:18:11 ] ssctrl SqueezeboxServer started.
[17-10-01 11:18:11 ] ssctrl Setting nice level to +0
[17-10-01 11:18:14.6860] Slim::Web::HTTP::addPageFunction (2568) Error: Slim::Web::HTTP::addPageFunction() is deprecated - please use Slim::Web::Pages->addPageFunction() instead
[17-10-01 11:18:14.6872] Slim::Web::HTTP::addPageFunction (2568) Backtrace:

frame 0: Slim::Utils::Log::logBacktrace (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Web/HTTP.pm line 2568)
frame 1: Slim::Web::HTTP::addPageFunction (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins/MyRadio/Plugin.pm line 47)
frame 2: Plugins::MyRadio::Plugin::webPages (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/Base.pm line 69)
frame 3: Slim::Plugin::Base::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/OPMLBased.pm line 54)
frame 4: Slim::Plugin::OPMLBased::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins/MyRadio/Plugin.pm line 20)
frame 5: Plugins::MyRadio::Plugin::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Utils/PluginManager.pm line 391)
frame 6: (eval) (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Utils/PluginManager.pm line 391)
frame 7: Slim::Utils::PluginManager::load (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 597)
frame 8: main::init (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 675)
frame 9: main::main (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 1213)

[17-10-01 11:18:16.9562] Plugins::Spotty::Connect::_getCurlCmd (361) Didn't find the 'curl' utility. Please install curl using your package manager.
[17-10-01 11:18:16.9603] Plugins::Spotty::Connect::_getPVcmd (390) Didn't find the pv (pipe viewer) utility. Please install pv using your package manager

Tony T
2017-10-01, 07:08
I noticed today that LMS still has the "Official" Spotify plugin active (though no longer working)
I've disabled it, but is there any issue if it is active?

jr01
2017-10-01, 13:58
I think my PR could also take us one step closer to getting rust-mdns working on Windows (by adding windows to [cfg(...)]), but I haven't rust cross compiled for Windows yet...and that will take me some time to investigate...

Well, today I did get one step closer....and now I have discovery + connect working on Windows with librespot and spotty :D

I only tested spotty from the command line and haven't had the time to setup LMS on Windows (yet).

My code can be found here: https://github.com/jr01/rust-mdns/tree/spotty and a PR to rust-mdns here: https://github.com/plietar/rust-mdns/pull/11

TheLastMan
2017-10-02, 07:16
I am running the latest Synology LMS package: 7.7.6-113. I will wait for your next release.
You really need to run the latest LMS instance which is 7.9.1
Details for how to get the latest version - prepared by Pinkdot - onto your Synology are on the thread linked below:
http://forums.slimdevices.com/showthread.php?107180-Synology-7-9-1-packages

schmurtz
2017-10-02, 08:03
Thanks ! Thanks ! Thanks !
It was difficult to find where to activate the option on each squeezebox but now it's OK.
I run with an ubuntu server (that I have updated because the repo was not supported anymore to add wget,pv and curl... :/)
Looking forward the volume tuning ;)
Really useful thanks again !

Jaca
2017-10-02, 11:05
Has anyone had luck with Spotty on Raspberry Pi3 running OSMC?

I get this in log:
"Slim::Utils::Misc::msg (1250) Warning: [16:36:20.6830] DBIx::Class::ResultSet::update_or_create(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /usr/share/perl5/Slim/Schema.pm line 1877"
"Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons..."
..
..
..
"Plugins::Spotty::SettingsAuth::shutdownHelper (162) Quitting authentication daemon"

I had to install perl to be able to run LMS OSMC, added SSL ,curl, pv.. wget was already there..
I can see Spotty authorisation page and players activation checkbox but it is not functioning.. (both player and authorization not visible on Spotify client)

I'm able to stream from Spotify in normal fashion (its bit slow though) but Connect isn't working at all

Any ideas? I've managed to run it on Raspbian but stuck on OSMC..

Thanks

tomsat50
2017-10-03, 04:39
PiCorePlayer v3.22 with LMS version 7.9.1, built 1505480690 @ Fri Sep 15 22:32:08 UTC 2017
Spotty v.1.9.4
Raspberry Pi 3 with HiFiBerry attached
2 x Squeezebox Radio, 1 x Squeezebox Touch
All connected to LAN (no wifi)

Michael, I hope that you can give me some advice to fix a problem when using Spotty to playback my playlists:
I have the following problem for about a week now: near the end of every track the music is 'paused' for about 1 to 2 seconds, and continues afterwards. The next track starts normally after it.
However, at the end of that track the pause is present, also near the end of the track. It shows up almost 9 of 10 times (so not always).
This only happens when listening to my Squeezebox devices. The playback using the PiCorePlayer works fine without any audio drops.
I remember that this problem did not exist some weeks ago: all worked great on all devices.
I assume that one of the updates has introduced this problem.
Can you give me some advice what to check or to modify in the configuration?
Is it possible to add some extra buffering, and where in the chain?
I hope that it can be fixed soon,

Kind regards, Tom

remoss
2017-10-04, 10:18
Michael awesome work!

I have noticed something odd.

track plays from app for 10 or 20 seconds - shows track time.
skips to next track
Next track plays - no time info.
plays fully.
Repeats with next track skipping and next one not and so on.
1 skip . 1play. 1 skip. 1 play

on pi LMS server ( maybe 2 nighties behind)
happens on max2play
happens on boom

Android Spotify app

Here the exact same thing.
PiCorePlayer v3.22 with LMS version 7.9.1, built 1505480690
Spotty v.1.9.4

Nomen Nescio
2017-10-08, 02:05
I have an empty menu in Spotty (web, iPeng, Squeeze Ctrl.
In server log: Spotty::API::getToken (137) Failed to get Spotify access token

after a reboot contents are back.

No message about a missing MS VC 2015 runtime.

slartibartfast
2017-10-08, 02:12
Here the exact same thing.
PiCorePlayer v3.22 with LMS version 7.9.1, built 1505480690
Spotty v.1.9.4Have you tried restarting LMS? If that doesn't work reboot the Pi.

Sent from my SM-G900F using Tapatalk

jasell
2017-10-08, 02:54
Hi,
What could be wrong in my setup using Qnap and Spotty
Described in this Post

I can run PV, CUrl and wget manually but it seems like Spotty cannot.
Is it acces rights or some path that is missing?

Please help, I would love to use Connect.

PS. Spotty works good playing spotify from the LMS Spotty app.

Giza2020
2017-10-08, 11:59
Have you tried restarting LMS? If that doesn't work reboot the Pi.

Sent from my SM-G900F using Tapatalk
tried both and same issue..sometimes it skips every song after 20 secs or less.
I'll keep persevering

slartibartfast
2017-10-08, 12:05
tried both and same issue..sometimes it skips every song after 20 secs or less.
I'll keep perseveringI had the same issue with version 1.9.3. After updating to 1.9.4 I had to restart to make it work. Later I tried using my Radio with it and the same issue ocurred requiring another restart. Maybe Michael has some ideas when he returns.

Sent from my SM-G900F using Tapatalk

tomsat50
2017-10-09, 06:18
I have 2 LMS systems running: one on a max2play (RPI 2), and one on a piCorePlayer (also RPI 2).
Both configurations have been installed from 'scratch', with the most recent versions of the software, including LMS and Spotty.

I have skipping problems with Spotty on the piCorePlayer when I playback with my Squeezebox Radios / Touch :mad:

No skipping occurs when I use the piCorePlayer.

In addition, no skipping occurs at all when I use the LMS of the max2play system in all combinations of Squeezeboxes and the dedicated players, including synchronization of all players......

Can anyone give me some advice which settings are relevant to check in order to trap this issue??

d6jg
2017-10-09, 11:34
Are you sure it isnt a networking issue? Tried swapping the Ethernet cables over between the 2 Pis?


Sent from my iPhone using Tapatalk

Giza2020
2017-10-10, 01:31
my skipping issue happens regardless if hardware. Pi or Boom. Synchronised or not. Pi player is max2play set up and LMS server is max2play too.
not network AFAIK as it seems like a skipping issue you get when multiple devices going for one account and not due to buffering etc at all.

tomsat50
2017-10-10, 03:50
Are you sure it isnt a networking issue? Tried swapping the Ethernet cables over between the 2 Pis?


Sent from my iPhone using Tapatalk

I have tried everything possible to exclude any issue with my network (a.o. interchanged the LMS device from it's position).
For now I have deactivated LMS on the piCorePlayer, and use it only as a music player.
So LMS is only active on my max2play device, on which all my Squeezebox devices (including the piCorePlayer) are connected to (synchronized or not).
No skipping problems any more.... :D:D

I still wonder why LMS / Spotty on the piCorePlayer does not perform like it should do... I have installed it onto a Raspberry 2 and a 3, but that makes no difference.

d6jg
2017-10-10, 03:53
I have tried everything possible to exclude any issue with my network (a.o. interchanged the LMS device from it's position).
For now I have deactivated LMS on the piCorePlayer, and use it only as a music player.
So LMS is only active on my max2play device, on which all my Squeezebox devices (including the piCorePlayer) are connected to (synchronized or not).
No skipping problems any more.... :D:D

I still wonder why LMS / Spotty on the piCorePlayer does not perform like it should do... I have installed it onto a Raspberry 2 and a 3, but that makes no difference.

My Pi3 is on piCorePlayer 3.2 and doesn't display any of these issues. I have seen reports of issues with 3.22

caplam
2017-10-10, 05:45
Hi,

I tried to make spotify connect work but with no success. It's ok for accessing spotify from lms interface or a squeezebox.
My lms (7.9.1) runs on a debian jessie virtual machine. Wget, curl and pv are installed.
I restarted lms or rebooted the vm but no success.
I also use philippe's plugins (airplaybridge, upnpbridge, shairtunes2W).
With shairtunes i can play from my iphone's spotify ap to a sonos play1 or squuzeboxboom or squeezebox3.
I didn't find any other log than server.log which contains only these lines concerning spotty:

Loading plugin: Spotty
[17-10-10 11:54:38.3763] Slim::Utils::PluginManager::load (343) Adding Bin directory: [/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin]
[17-10-10 11:54:38.3766] Slim::Utils::PluginManager::load (374) Adding HTML directory: [/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/HTML]

I don't see any spotty process running
At lms startup i see spotty_x64 running but only for a short time.

Edit: i forgot to add debug logging for spotty. Here is the server log:



[17-10-10 14:56:11.7643] main::init (387) Starting Logitech Media Server (v7.9.1, 1505480690, Fri Sep 15 14:05:22 UTC 2017) perl 5.020002 - x86_64-linux-gnu-thread-multi
[17-10-10 14:56:11.7747] Slim::Utils::PluginDownloader::init (42) downloading to /var/lib/squeezeboxserver/cache/DownloadedPlugins
[17-10-10 14:56:11.7749] Slim::Utils::PluginDownloader::init (43) extracting to /var/lib/squeezeboxserver/cache/InstalledPlugins
[17-10-10 14:56:11.7751] Slim::Utils::PluginManager::_loadPluginCache (610) Loading plugin cache file.
[17-10-10 14:56:11.7804] Slim::Utils::PluginManager::_loadPluginCache (619) Cache Info: {
bin => "/usr/sbin",
count => 61,
mtimesum => "91301379070",
osArch => "x86_64-linux",
osType => "Linux",
revision => "1505480690",
server => "7.9.1",
version => 4,
}
[17-10-10 14:56:12.6883] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
[17-10-10 14:56:12.6963] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
[17-10-10 14:56:12.7024] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/curl
[17-10-10 14:56:12.7026] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/curl
[17-10-10 14:56:12.7029] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/pv
[17-10-10 14:56:12.7098] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/pv
[17-10-10 14:56:15.2264] Slim::Web::JSONRPC::requestMethod (443) 00:04:20:1e:6a:90: request not dispatchable!
[17-10-10 14:56:16.3139] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:16.3147] Plugins::Spotty::Connect::startHelper (313) Starting Spotty Connect deamon: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c "/var/lib/squeezeboxserver/cache/spotty/e917fff9" -n "sq3-salon (00:04:20:12:28:b2)" --disable-discovery --onstart "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:12:28:b2\",[\"spottyconnect\",\"start\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" --onstop "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:12:28:b2\",[\"spottyconnect\",\"stop\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" --onchange "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:12:28:b2\",[\"spottyconnect\",\"change\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" | /usr/bin/pv -L20k -B10k -q > /dev/null
[17-10-10 14:56:16.3835] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:16.3842] Plugins::Spotty::Connect::startHelper (313) Starting Spotty Connect deamon: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c "/var/lib/squeezeboxserver/cache/spotty/28eafd1f" -n "sqboom-cuisine (00:04:20:1e:6a:90)" --disable-discovery --onstart "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:1e:6a:90\",[\"spottyconnect\",\"start\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" --onstop "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:1e:6a:90\",[\"spottyconnect\",\"stop\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" --onchange "/usr/bin/curl -s -X POST -d {\"id\":0,\"params\":[\"00:04:20:1e:6a:90\",[\"spottyconnect\",\"change\"]],\"method\":\"slim.request\"} http://192.168.0.103:9000/jsonrpc.js" | /usr/bin/pv -L20k -B10k -q > /dev/null
[17-10-10 14:56:27.0520] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:27.0708] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:27.8013] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:27.8325] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...
[17-10-10 14:56:27.8615] Plugins::Spotty::Connect::initHelpers (270) Initializing Spotty Connect helper daemons...



I deleted irrelevant lines (shairtunes2W, raopbridge,...)

tomsat50
2017-10-10, 08:05
My Pi3 is on piCorePlayer 3.2 and doesn't display any of these issues. I have seen reports of issues with 3.22

Indeed, I am running version 3.22... I hope that this nasty 'bug' will be fixed soon...

d6jg
2017-10-10, 09:14
Indeed, I am running version 3.22... I hope that this nasty 'bug' will be fixed soon...

Why don't you try 3.2 ? The download is still available.

tomsat50
2017-10-11, 01:53
Why don't you try 3.2 ? The download is still available.

OK, I will try this afternoon....

jimbo2ko
2017-10-11, 07:27
Long time SBT owner and Spotify user.Havent been able to get Spotty to work two days in a row. Win 7 ultimate 64 bit, All devices in house are hardwired (because of slow internet speed). Latest iteration is Spotty .exe is not working SBT says unable to connect to computer, computer says Spotty .exe is not working. Uninstalled Spotty and reinstalled. SBT says network health is fine. SBT working as Lastradio is fine. Thanks in advance for any help rendered,and please, not too technical on replies. Jim
And a recuring window on the computer telling me that spotty.exe is not working, keeps comming back along with a command prompt screen
Tried to get an answer on the SBT forum and no replies in two weeks. using v 1.94

d6jg
2017-10-11, 08:05
Long time SBT owner and Spotify user.Havent been able to get Spotty to work two days in a row. Win 7 ultimate 64 bit, All devices in house are hardwired (because of slow internet speed). Latest iteration is Spotty .exe is not working SBT says unable to connect to computer, computer says Spotty .exe is not working. Uninstalled Spotty and reinstalled. SBT says network health is fine. SBT working as Lastradio is fine. Thanks in advance for any help rendered,and please, not too technical on replies. Jim
And a recuring window on the computer telling me that spotty.exe is not working, keeps comming back along with a command prompt screen
Tried to get an answer on the SBT forum and no replies in two weeks. using v 1.94

Check that your Windows firewall is not blocking Spotty.exe

jimbo2ko
2017-10-11, 11:24
Well Spotty is not on the list of allowed programs though logitech media server is there and it shows up on LMS settings. I had spotty working though every time I tried to use it I had to jump through hoops to get it to work, but I was always able to get it to work, till now.

jimbo2ko
2017-10-11, 14:39
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 10060, message: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." } }', src\libcore\result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[17-10-11 10:12:18.9862] Plugins::Spotty::API::getToken (137) Failed to get Spotify access token
[17-10-11 10:12:18.9869] Slim::Utils::Strings::string (488) Error: missing string PLUGIN_SPOTTY_ERROR_1
[17-10-11 10:12:18.9874] Slim::Utils::Strings::string (488) Backtrace:

frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~2\SQUEEZ~1\server\SQUEEZ~3.EXE>Slim/Utils/Strings.pm line 488)
frame 1: Slim::Utils::Strings::string (C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 1176)

Nomen Nescio
2017-10-11, 22:42
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 10060, message: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." } }', src\libcore\result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[17-10-11 10:12:18.9862] Plugins::Spotty::API::getToken (137) Failed to get Spotify access token
[17-10-11 10:12:18.9869] Slim::Utils::Strings::string (488) Error: missing string PLUGIN_SPOTTY_ERROR_1
[17-10-11 10:12:18.9874] Slim::Utils::Strings::string (488) Backtrace:

frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~2\SQUEEZ~1\server\SQUEEZ~3.EXE>Slim/Utils/Strings.pm line 488)
frame 1: Slim::Utils::Strings::string (C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 1176)

Seems familiar. Jumped from WHS 2011 to piCoreplayer on a spare Raspberry Pi. Spotty works but LMS on WHS 2011 responds quicker though.

jimbo2ko
2017-10-12, 08:10
If I cant get this solved soon, I am going to Tidal

vilus
2017-10-12, 11:39
hello, thanks for the work.
what squeezeserver version is needed to have spotty work ? (I get: Spotty requires the Perl module IO::Socket::SSL. You can NOT use Spotty without this module. Please use your operating system's package manager to install it.)
I tried to find some tutos to upgrade to 7.9.1, but not sure it'll work for TS-121 (any step-by-step tuto you would recommend ?)
thanks for your help

here is what I have:
System
Hard-/Firmware : QNAP TurboStation TS-121 / 4.3.3 build 20170901
Load / Uptime : 3.13 3.53 3.49 / 0d 05.05:38 (30% idle)
Unknown HZ value! (66) Assume 100.
Memory -- Swap : 933/1011 MB (shr: 0, buf: 5, cache: 600, rss: 329) -- 8/518 MB
SqueezeboxServer
Version : 7.7.2-33893
Process status : PID 4695, state D (disk sleep)
Memory usage : 115 MB total, 92 MB (80%) RSS
Unknown HZ value! (66) Assume 100.
Unknown HZ value! (66) Assume 100.
Uptime : 47:26, 06:56 (14.6%) CPU time
Database size : 47M and 11M persistent and 14G artwork
SSOTS/SBS flags: autostart noupnp port9001 en_GB.UTF-8
SC custom files: ssods.conf
Unknown HZ value! (66) Assume 100.

alfista
2017-10-12, 18:32
hello, thanks for the work.
what squeezeserver version is needed to have spotty work ? (I get: Spotty requires the Perl module IO::Socket::SSL. You can NOT use Spotty without this module. Please use your operating system's package manager to install it.)
I tried to find some tutos to upgrade to 7.9.1, but not sure it'll work for TS-121 (any step-by-step tuto you would recommend ?)
thanks for your help



You'll find some answers and pointers in the first post of this thread (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0).
In short, the LMS version has some limitations but it shouldn't prevent spotty from running, no rush in installing 7.9.1. The CPU of that NAS could be a problem, but start by installing the required Perl module and take it from there.

vilus
2017-10-13, 00:48
You'll find some answers and pointers in the first post of this thread (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0).
In short, the LMS version has some limitations but it shouldn't prevent spotty from running, no rush in installing 7.9.1. The CPU of that NAS could be a problem, but start by installing the required Perl module and take it from there.

I know what I'll do this week-end :)
thanks

Mnyb
2017-10-13, 02:24
Well Spotty is not on the list of allowed programs though logitech media server is there and it shows up on LMS settings. I had spotty working though every time I tried to use it I had to jump through hoops to get it to work, but I was always able to get it to work, till now.

Did you then allow spotty.exe trough the firewall to solve this problem ?

Gwaelod
2017-10-13, 08:18
anyone?


Hi
Brilliant work with Spotty so far...I'm really enjoying it.

However I'm struggling to get this to work.

Running 7.9.1 on a Ubuntu 14.04 headless server

Seems like it's installed fine although I had to install pipe viewer first.

Ticked the option under settings/player but can't see The player appearing in the Spotify Connect app on my Android

My Spotify account is premium, and works fine with main Spotty implementation.

The player I'm trying to send it too is a Pi Zero W running PiCoreplayer/squeezelite.

Tried a couple of server reboots but still not showing up.

backball
2017-10-13, 16:48
Well I'm lost.

Used the official Spotify plug-in for years on my VB2.2 (LMS 7.8) system. When they pulled the plug on this earlier in the year I went to Spotty as I've read only good things about it and given we listen to Spotify really a lot I needed a migration path.

I kept having these buffering problems. First track plays without a problem then from the second track onwards it plays for say 5-7 sec and then buffers for 3-4 before doing it all over again.

Was told Spotty needed VB2.3+ so I decided to upgrade to VB2.4 (Dell OptiPlex 790 with i5 processor, 4GB RAM). Going to the latest Spotty plug-in 1.9.4 with a brand new VB the exact same thing happens again; i.e. above buffering. I can stream from the VB box perfect Internet radio at any quality but just can't get Spotty to do the same. Could Spotty require much more bandwidth than the previous plug-ins? I'm on an ADSL connection giving me about 5MB/s but as said Internet radio, even KODI works ok.

Any ideas? Thanks

castalla
2017-10-13, 17:11
Well I'm lost.

Used the official Spotify plug-in for years on my VB2.2 (LMS 7.8) system. When they pulled the plug on this earlier in the year I went to Spotty as I've read only good things about it and given we listen to Spotify really a lot I needed a migration path.

I kept having these buffering problems. First track plays without a problem then from the second track onwards it plays for say 5-7 sec and then buffers for 3-4 before doing it all over again.

Was told Spotty needed VB2.3+ so I decided to upgrade to VB2.4 (Dell OptiPlex 790 with i5 processor, 4GB RAM). Going to the latest Spotty plug-in 1.9.4 with a brand new VB the exact same thing happens again; i.e. above buffering. I can stream from the VB box perfect Internet radio at any quality but just can't get Spotty to do the same. Could Spotty require much more bandwidth than the previous plug-ins? I'm on an ADSL connection giving me about 5MB/s but as said Internet radio, even KODI works ok.

Any ideas? Thanks

Have you uninstalled the older spotify plugins?

backball
2017-10-13, 18:50
Have you uninstalled the older spotify plugins?

With uninstalled do you mean to untick the 'enabled' box or actually removing it from the file system?

castalla
2017-10-13, 19:01
With uninstalled do you mean to untick the 'enabled' box or actually removing it from the file system?

Untick then restart LMS

jimbo2ko
2017-10-14, 17:22
Did you then allow spotty.exe trough the firewall to solve this problem ?

Spotty exe does not come up on the list of programs allowed through, nor can I find it on my computer except in LMS settings. It does show up in Apps on my SBT but says that it is unable to commmunicate with my computer

mherger
2017-10-14, 23:35
Hi,
What could be wrong in my setup using Qnap and Spotty
Described in this Post

I can run PV, CUrl and wget manually but it seems like Spotty cannot.
Is it acces rights or some path that is missing?


Can you tell me what the binary search path in Settings/Information looks like?

slartibartfast
2017-10-15, 05:01
It is playing the same album in the same order so if it is DSTM it would be a big coincidence. This would be a case when you would not want DSTM to kick in anyway since you have chosen to transfer playback away from the device. In this case DSTM was disabled for that device.

Sent from my SM-G900F using TapatalkI have tried this again by starting playback of an album on a Radio then transferring to my phone. In this case the track that was playing on the Radio when the transfer was initiated repeated rather than stopping playback.

Sent from my SM-G900F using Tapatalk

jasell
2017-10-15, 16:48
Can you tell me what the binary search path in Settings/Information looks like?
These?

Cache Folder
/opt/ssods4/var/home/SqueezeboxServer/Cache

Preferences Folder
/opt/ssods4/var/home/SqueezeboxServer/Prefs

Plugin Folders
/opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins, /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins

Helper Applications Folder
/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin/i386-linux, /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin,
/opt/ssods4/bin,
/usr/bin,
/usr/local/bin,
/usr/libexec,
/usr/sbin,
/opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux, /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin

mavit
2017-10-16, 03:25
Pive Viewer

Typo. Should be "Pipe Viewer". HTH.

mavit
2017-10-16, 04:48
Heres a few things I discovered whist trying to get Spotify Connect working. Hopefully these will be helpful to someone.


The settings page says, you'll need to authorize Logitech Media Server using one of Spotify's applications. This can be their desktop client, or one of their mobile apps. As far as I can tell, the web app (https://open.spotify.com/browse/featured) doesnt count, here.

The plugin listens on UDP port 5353 (mDNS) and some random high-numbered TCP port. Youll need to allow connections through any firewalls from where-ever youre running an official Spotify client (mentioned above).

You have to have Spotify Premium for any of this to work. Perhaps thats obvious to people, but I didnt see it mentioned.

derekkao
2017-10-16, 07:48
Hi,

I have enabled Spotty v1.9.4 on LMS 7.7.3 running on DSM5 of Synology, and ticked the 'Enable Spotify Connect endpoint for this player' via LMS Web UI. I then found the following error in server log:

[17-10-15 22:29:14.1174] 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 /volume1/@appstore/SqueezeCenter/Slim/Networking/IO/Select.pm line 150.
[17-10-15 22:29:46.8727] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-15 22:29:52.0168] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:29:54.5491] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:29:54.6026] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:30:59.2676] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-16 08:20:50.1583] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-16 08:21:24.8391] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.

Any advice?

Derek

d6jg
2017-10-16, 12:41
Hi,

I have enabled Spotty v1.9.4 on LMS 7.7.3 running on DSM5 of Synology, and ticked the 'Enable Spotify Connect endpoint for this player' via LMS Web UI. I then found the following error in server log:

[17-10-15 22:29:14.1174] 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 /volume1/@appstore/SqueezeCenter/Slim/Networking/IO/Select.pm line 150.
[17-10-15 22:29:46.8727] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-15 22:29:52.0168] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:29:54.5491] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:29:54.6026] Plugins::Spotty::API::__ANON__ (1287) error: Connect timed out:
[17-10-15 22:30:59.2676] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-16 08:20:50.1583] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.
[17-10-16 08:21:24.8391] Slim::Control::Request::notify (2085) Error: Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL called at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm line 337.

Any advice?

Derek

I dont think it will work with a Synology that old and 7.7.x




Sent from my iPhone using Tapatalk

mherger
2017-10-16, 23:04
>> [17-10-15 22:29:46.8727] Slim::Control::Request::notify (2085) Error:
>> Failed notify: Undefined subroutine &Slim::Utils::Network::serverURL
>> called at
>> /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Connect.pm
>> line 337.
>
> Upgrade LMS. I don’t think it will work with 7.7.x

Hmm... I thought I had fixed this... will double-check asap.

--

Michael

mherger
2017-10-16, 23:05
> That looks promising! I thought librespot didn't support Spotify Connect
> on Windows...

I think audio support doesn't work on Windows. But as I'm piping the
audio data to LMS that's not a problem.

--

Michael

mherger
2017-10-16, 23:09
> Helper Applications Folder
> /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin/i386-linux,
> /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin,
>
> /opt/ssods4/bin,
> /usr/bin,
> /usr/local/bin,
> /usr/libexec,
> /usr/sbin,
> /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux,
> /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin

Hmm... that seems to be fine. IIRC your problem is with pv only? Could
you please enable INFO logging for plugin.spotty, then try to fire up
Connect? What would server.log say?

--

Michael

mherger
2017-10-16, 23:10
>> Pive Viewer
>
> Typo. Should be "Pipe Viewer". HTH.

Thanks :-)

--

Michael

mherger
2017-10-16, 23:13
> Here’s a few things I discovered whist trying to get Spotify Connect
> working. Hopefully these will be helpful to someone.

Thanks. I'll see how I can incorporate them with the plugin.

> - The plugin listens on UDP port 5353 (mDNS) and some random
> high-numbered TCP port. You’ll need to allow connections through any
> firewalls from where-ever you’re running an official Spotify client
> (mentioned above).

I don't like to point people to firewall issues. The past has shown that
most users don't know what that's all about and start to do dangerous
things like port forwarding stuff to the internet... If somebody
happened to have those ports blocked, oh well, he'll have to enter
username/password _once_ (and it wouldn't be stored).

> - You have to have Spotify Premium for any of this to work. Perhaps
> that’s obvious to people, but I didn’t see it mentioned.

Excellent point. Thanks again!

--

Michael

mherger
2017-10-16, 23:17
I noticed today that LMS still has the "Official" Spotify plugin active (though no longer working)
I've disabled it, but is there any issue if it is active?

As I've started work on Spotty as a protocol handler, it tries to be smart about this situation, hijacking Spotify handling if needed. That said I'd certainly suggest anyone disables any other Spotify plugin, as some of the features would potentially be conflicting (not only redundant).

mherger
2017-10-16, 23:20
Just a heads up: obviously I've been out of the loop for a while. I've tried to catch up with all the postings but surely missed one or two. If I didn't answer or you're still looking for an answer, please post a friendly reminder :-)

slartibartfast
2017-10-17, 00:11
Just a heads up: obviously I've been out of the loop for a while. I've tried to catch up with all the postings but surely missed one or two. If I didn't answer or you're still looking for an answer, please post a friendly reminder :-)Hi Michael
I still see an issue when using Connect and transferring playback from one device to another. I tried two scenarios.

1. Transferring between two Squeezebox devices resulted in the playback continuing on the original as well as the new device.

2. Transferring from a Squeezebox to my phone resulted in the the Squeezebox repeating the track playing at the time of transfer.

DSTM is disabled on all devices.

Sent from my SM-G900F using Tapatalk

mherger
2017-10-17, 07:44
Hi Michael
I still see an issue when using Connect and transferring playback from one device to another. I tried two scenarios.

1. Transferring between two Squeezebox devices resulted in the playback continuing on the original as well as the new device.

2. Transferring from a Squeezebox to my phone resulted in the the Squeezebox repeating the track playing at the time of transfer.

DSTM is disabled on all devices.

Sent from my SM-G900F using Tapatalk

1. is kind of by design: I thought leaving the current track end playback would be nicer than stopping on the source device when moving. I might change this, as it seems to be confusing.

2. did you have repeat enabled before starting the Connect session?

mherger
2017-10-17, 07:45
v1.9.5 is on its way to you. It should fix the compatibility with older LMS versions.

slartibartfast
2017-10-17, 07:54
1. is kind of by design: I thought leaving the current track end playback would be nicer than stopping on the source device when moving. I might change this, as it seems to be confusing.

2. did you have repeat enabled before starting the Connect session?

1. When I say continues playing I mean beyond one track. It will play the whole playlist.

2. No I didn't have repeat enabled.

I was surprised the behaviour was different when transferring to my phone rather than another squeezebox. Transferring to a squeezebox the original player plays the whole playlist, transferring to my phone the track repeats indefinitely.

Sent from my SM-G900F using Tapatalk

mherger
2017-10-17, 08:24
> 1. When I say continues playing I mean beyond one track. It will play
> the whole playlist.

Now that's rather surprising (unless the two players are synchronized):
as LMS never gets to see the playlist in Connect mode, Spotify would
have to control two devices in parallel. Which they explicitly do not
allow/support.

> 2. No I didn't have repeat enabled.

Again: from LMS POV there's only one track. Unless repeat is on, this
would mean that Spotify would tell the player to repeat playback.

Could you please enable INFO logging for plugin.spotty, reproduce both
cases and post your log (with pointers to the timestamps when you
triggered the two actions)?

--

Michael

slartibartfast
2017-10-17, 09:31
> 1. When I say continues playing I mean beyond one track. It will play
> the whole playlist.

Now that's rather surprising (unless the two players are synchronized):
as LMS never gets to see the playlist in Connect mode, Spotify would
have to control two devices in parallel. Which they explicitly do not
allow/support.

> 2. No I didn't have repeat enabled.

Again: from LMS POV there's only one track. Unless repeat is on, this
would mean that Spotify would tell the player to repeat playback.

Could you please enable INFO logging for plugin.spotty, reproduce both
cases and post your log (with pointers to the timestamps when you
triggered the two actions)?

--

Michael

Here is the server log. I noticed that it sometimes repeats and other times continues with the playlist. In this case I transferred from Radio to Touch at around 17.04. both players continued the playlist with 10 seconds between the devices.

mherger
2017-10-17, 21:19
> Here is the server log. I noticed that it sometimes repeats and other
> times continues with the playlist. In this case I transferred from
> Radio to Touch at around 17.04. both players continued the playlist with
> 10 seconds between the devices.

Hmm... I need to improve the logging to figure this one out. I'll see
what I can do.

--

Michael

Giza2020
2017-10-18, 01:55
Hi Michael. a few of us had issues with track skipping. my particular issue is on the latest LMS nightly. players are squeezelite using Max2play and also happening on Boom.

the effect is similar (not exactly but best example) of the skipping that occurs when playing Spotify on too many devices... 5 - 15 secs playing and then skip and same with next track etc.

Also after the initial track skip the track duration in my android Spotify app stops working and stays on 0 even though the track is playing for those few seconds.

slartibartfast
2017-10-18, 03:00
Hi Michael. a few of us had issues with track skipping. my particular issue is on the latest LMS nightly. players are squeezelite using Max2play and also happening on Boom.

the effect is similar (not exactly but best example) of the skipping that occurs when playing Spotify on too many devices... 5 - 15 secs playing and then skip and same with next track etc.

Also after the initial track skip the track duration in my android Spotify app stops working and stays on 0 even though the track is playing for those few seconds.I still get this occasionally as well. I thought restarting LMS fixed it but it seems to come back. It can occur after a complete reboot of my Pi as well.

Sent from my SM-G900F using Tapatalk

Nonreality
2017-10-18, 09:47
Well I'm lost.

Used the official Spotify plug-in for years on my VB2.2 (LMS 7.8) system. When they pulled the plug on this earlier in the year I went to Spotty as I've read only good things about it and given we listen to Spotify really a lot I needed a migration path.

I kept having these buffering problems. First track plays without a problem then from the second track onwards it plays for say 5-7 sec and then buffers for 3-4 before doing it all over again.

Was told Spotty needed VB2.3+ so I decided to upgrade to VB2.4 (Dell OptiPlex 790 with i5 processor, 4GB RAM). Going to the latest Spotty plug-in 1.9.4 with a brand new VB the exact same thing happens again; i.e. above buffering. I can stream from the VB box perfect Internet radio at any quality but just can't get Spotty to do the same. Could Spotty require much more bandwidth than the previous plug-ins? I'm on an ADSL connection giving me about 5MB/s but as said Internet radio, even KODI works ok.

Any ideas? ThanksI was barely able to use Spotty for the last 2 weeks. It kept timing out when trying to access anything beyond the first main menu. I ended up upgrading from 9.0 to Monday's 9.1 nightly. I also upgraded my netgear routers firmware. It's running great again now but by doing both at about the same time I really can't tell you which worked. [emoji853] I thought that maybe some ideas might help you and if you haven't done your router for a while it's not a bad idea to check it. Good luck.

Sent from my SM-G955U using Tapatalk

Gwaelod
2017-10-19, 13:11
Just a heads up: obviously I've been out of the loop for a while. I've tried to catch up with all the postings but surely missed one or two. If I didn't answer or you're still looking for an answer, please post a friendly reminder :-)

I can't get Spotty Connect feature to work, although Spotty otherwise works perfectly

Running 7.9.1 on a Ubuntu 14.04 headless server

Seems like it's installed fine although I had to install pipe viewer first.

Ticked the option under settings/player but can't see The player appearing in the Spotify Connect app on my Android

My Spotify account is premium, and works fine with main Spotty implementation.

The player I'm trying to send it too is a Pi Zero W running PiCoreplayer/squeezelite.

Tried server reboots but still not showing up

"Logitech Media Server Version: 7.9.1 - 1495659078 @ Sat May 27 04:38:46 UTC 2017
Hostname: #######
Server IP Address: #######
Server HTTP Port Number: 9001
Operating system: Debian - EN - utf8
Platform Architecture: x86_64-linux
Perl Version: 5.18.2 - x86_64-linux-gnu-thread-multi
Audio::Scan: 0.95
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 1"

mherger
2017-10-19, 21:19
I can't get Spotty Connect feature to work, although Spotty otherwise works perfectly

Running 7.9.1 on a Ubuntu 14.04 headless server

Seems like it's installed fine although I had to install pipe viewer first.


Did you check server.log for any hints?

mherger
2017-10-20, 00:28
> Hi Michael. a few of us had issues with track skipping. my particular
> issue is on the latest LMS nightly. players are squeezelite using
> Max2play and also happening on Boom.
>
> the effect is similar (not exactly but best example) of the skipping
> that occurs when playing Spotify on too many devices... 5 - 15 secs
> playing and then skip and same with next track etc.

Is this in Connect mode or with Spotty in general?

> Also after the initial track skip the track duration in my android
> Spotify app stops working and stays on 0 even though the track is
> playing for those few seconds.

Sounds like Connect. Yes, the experience still is a bit erratic. I have
to do some more testing/fixing.

--

Michael

Gwaelod
2017-10-20, 00:28
Did you check server.log for any hints?

No sign of a Spotty plugin starting in the log


2017-10-20 08:26:17 squeezeboxserver_safe started.
[17-10-20 08:26:17.3177] Plugins::ShairTunes2W::Plugin::revoke_publishPlaye r (352) Stop old publish players services:2445
[17-10-20 08:26:17.3263] Plugins::ShairTunes2W::Plugin::shutdownPlugin (264) Killing all processes shairport_helper-x64-linux
[17-10-20 08:26:20.4472] main::init (387) Starting Logitech Media Server (v7.9.1, 1495659078, Sat May 27 04:38:46 UTC 2017) perl 5.018002 - x86_64-linux-gnu-thread-multi
[17-10-20 08:26:37.8434] Plugins::ShairTunes2W::Plugin::publishPlayer (376) start avahi-publish-service "Conservatory"
[17-10-20 08:26:37.8904] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (292) create client Slim::Player::SqueezePlay=ARRAY(0xae9e448) with proc Proc::Background=HASH(0xaf4c030)
[17-10-20 08:26:40.0533] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:5c:67:0d: request not dispatchable!
[17-10-20 08:26:40.0569] Slim::Web::JSONRPC::requestMethod (443) 00:13:d3:22:87:31: request not dispatchable!
[17-10-20 08:26:40.0688] Slim::Web::JSONRPC::requestMethod (443) cc:cc:09:f8:fc:dc: request not dispatchable!
[17-10-20 08:26:40.0723] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:22:89:b3: request not dispatchable!
[17-10-20 08:26:40.0759] Slim::Web::JSONRPC::requestMethod (443) b8:26:eb:c1:71:f0: request not dispatchable!
[17-10-20 08:26:40.0794] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:77:dc:e6: request not dispatchable!
[17-10-20 08:27:10.1007] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:5c:67:0d: request not dispatchable!
[17-10-20 08:27:10.1060] Slim::Web::JSONRPC::requestMethod (443) 00:13:d3:22:87:31: request not dispatchable!
[17-10-20 08:27:10.1201] Slim::Web::JSONRPC::requestMethod (443) cc:cc:09:f8:fc:dc: request not dispatchable!
[17-10-20 08:27:10.1254] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:22:89:b3: request not dispatchable!
[17-10-20 08:27:10.1305] Slim::Web::JSONRPC::requestMethod (443) b8:26:eb:c1:71:f0: request not dispatchable!
[17-10-20 08:27:10.1357] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:77:dc:e6: request not dispatchable!

Walkerraiden
2017-10-20, 03:57
Hi,

ich have a Problem:

[17-10-20 12:52:06.6776] Plugins::Spotty::API::getToken (120) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 117.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: MercuryError', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[17-10-20 12:52:06.6780] Plugins::Spotty::API::getToken (137) Failed to get Spotify access token

2386523866

My System: Synology RS815+ x86-64 Avoton
Logitech Media Server Version: 7.9.1 - 1504317335 @ Mon Sep 4 22:13:00 UTC 2017
Hostname: xxx
IP-Adresse des Servers: 192.168.xx
Server-HTTP-Portnummer: xxxx
Betriebssystem: Synology DiskStation - DE - utf8
Plattformarchitektur: x86_64-linux
Perl-Version: 5.24.0 - x86_64-linux
Audio::Scan: 0.95
Datenbankversion: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Anzahl erkannter Player: 2

cant find any solution here in Forum

thx for help

mherger
2017-10-20, 04:53
[17-10-20 12:52:06.6776] Plugins::Spotty::API::getToken (120) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 117.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: MercuryError', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[17-10-20 12:52:06.6780] Plugins::Spotty::API::getToken (137) Failed to get Spotify access token

Did you go through the authorization step? Did you have to enter username/password or did you use a Spotify application?

You could go to Settings/Advanced/Logging (Einstellungen/Erweitert/Protokoll) and set the logging level for plugin.spotty to INFO. Then try to use it again, upload your full server.log (there's a link to download the zipped file at the top of that page).

Giza2020
2017-10-20, 05:37
Updated to latest spotty but not the latest nightly... connect ( spotty works perfect!) Seems to be behaving as expected ;-)
I'll let you know if it goes back to the skipping behaviour I've been seeing

clog
2017-10-20, 10:54
Clog wrote:
>> For installation of the connect feature I followed the steps in the opening post [Announce] Spotty v1.9.0 - now with
>> experimental Spotify Connect support!".
>> Whatever I did, In the Spotify connect app on my Ipad the picoreplayer remained invisible. When I stumbled upon the
>> same server message about the missing curl utility. I thought that must be it, but alas.

>> Other things to checkout ???

>> I use PiCoreplayer 3.22 on Raspberry pi 3 running Logitech Media Server Version: 7.9.1 - 1504317335 and squeezelite
>> Firmware: v1.8.7-999. Spotty version 1.9.5

Mherger wrote:
> Enable INFO logging for Spotty, then disable/re-enable Connect for your
> player - and post results in the Spotty thread.


I think this is the INFO line you meant:

[17-10-20 19:28:40.8079] Plugins::Spotty::Connect::startHelper (313) Starting Spotty Connect deamon: /usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/usr/local/slimserver/Cache/spotty/4e5687e8" -n "piCorePlayer (xxx)" --disable-discovery --onstart "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","start"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" --onstop "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","stop"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" --onchange "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","change"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" | /usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/pv-hf -L20k -B10k -q > /dev/null

Gwaelod
2017-10-20, 11:12
Did you check server.log for any hints?

Changed spotty plugin logging to info - 4th line stopHelper (406) ?

"2017-10-20 19:07:25 squeezeboxserver_safe started.
[17-10-20 19:07:26.3940] Plugins::ShairTunes2W::Plugin::revoke_publishPlaye r (352) Stop old publish players services:3093
[17-10-20 19:07:26.3985] Plugins::ShairTunes2W::Plugin::shutdownPlugin (264) Killing all processes shairport_helper-x64-linux
[17-10-20 19:07:26.4764] Plugins::Spotty::Connect::stopHelper (406) Quitting Spotty Connect daemon for b8:27:eb:8c:72:45
[17-10-20 19:07:28.9854] main::init (387) Starting Logitech Media Server (v7.9.1, 1495659078, Sat May 27 04:38:46 UTC 2017) perl 5.018002 - x86_64-linux-gnu-thread-multi
[17-10-20 19:07:41.5679] Plugins::ShairTunes2W::Plugin::publishPlayer (376) start avahi-publish-service "Conservatory"
[17-10-20 19:07:41.6169] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (292) create client Slim::Player::SqueezePlay=ARRAY(0xa5a83e8) with proc Proc::Background=HASH(0xa8c83c0)
[17-10-20 19:07:56.6543] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:5c:67:0d: request not dispatchable!
[17-10-20 19:07:56.6595] Slim::Web::JSONRPC::requestMethod (443) 00:13:d3:22:87:31: request not dispatchable!
[17-10-20 19:07:56.6779] Slim::Web::JSONRPC::requestMethod (443) cc:cc:09:f8:fc:dc: request not dispatchable!
[17-10-20 19:07:56.6831] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:22:89:b3: request not dispatchable!
[17-10-20 19:07:56.6884] Slim::Web::JSONRPC::requestMethod (443) b8:26:eb:c1:71:f0: request not dispatchable!
[17-10-20 19:07:56.6936] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:77:dc:e6: request not dispatchable!
[17-10-20 19:08:26.7153] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:5c:67:0d: request not dispatchable!
[17-10-20 19:08:26.7204] Slim::Web::JSONRPC::requestMethod (443) 00:13:d3:22:87:31: request not dispatchable!
[17-10-20 19:08:26.7373] Slim::Web::JSONRPC::requestMethod (443) cc:cc:09:f8:fc:dc: request not dispatchable!"

mherger
2017-10-20, 11:42
I think this is the INFO line you meant:

[17-10-20 19:28:40.8079] Plugins::Spotty::Connect::startHelper (313) Starting Spotty Connect deamon: /usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c "/usr/local/slimserver/Cache/spotty/4e5687e8" -n "piCorePlayer (xxx)" --disable-discovery --onstart "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","start"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" --onstop "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","stop"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" --onchange "/usr/bin/wget -q -O- --post-data {"id":0,"params":["xxx",["spottyconnect","change"]],"method":"slim.request"} http://192.168.178.16:9000/jsonrpc.js" | /usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/pv-hf -L20k -B10k -q > /dev/null

I didn't expect anything. But this certainly shows that all the helpers are found as expected (no curl needed, as wget is being used on pCP, as mentioned before). And after this there's no error message? And you still don't see it in Spotify's applications? If you're using your phone, make sure it's on the same account, same network.

Walkerraiden
2017-10-20, 15:40
I have found my problem:
"Spotify Client ID" can not contain a value :rolleyes:

thx for helping

mherger
2017-10-20, 15:46
> I have found my problem:
> "Spotify Client ID" can not contain a value :rolleyes:

Sure it can. But it must be a valid client ID. The description clearly
says not to touch this value unless you know what you're doing ;-).

--

Michael

kezz
2017-10-20, 18:42
Hey, thanks for all the effort getting things going with Connect! It's the one feature that I've wanted the most out of the Squeezebox platform over the last few years (closest we can get to Chromecast emulation)

I've just upgraded on my mac though, and before enabling the connect script for any of my players I seem to get this list of errors



[17-10-20 18:13:51.4410] Slim::Web::Cometd::handler (422) errorNeedsClient: 00:04:20:27:2b:2b, status, -, 10, menu:menu, useContextMenu:1, subscribe:600
[17-10-20 21:10:03.0376] main::init (387) Starting Logitech Media Server (v7.9.1, 1508251793, Tue Oct 17 08:43:59 PDT 2017) perl 5.018002 - darwin-thread-multi-2level
[17-10-20 21:10:04.9394] main::init (387) Starting Logitech Media Server (v7.9.1, 1508251793, Tue Oct 17 08:43:59 PDT 2017) perl 5.018002 - darwin-thread-multi-2level
[17-10-20 21:10:06.3349] Plugins::Spotty::Connect::canSpotifyConnect (67) Cannot support Spotty Connect, need at least helper version 0.7.0


I still see the helper plug-in for OSX that you suggested I install to get extra log data, yet from your repo I'm not seeing any updates for it yet...
(also preemptively I did install pv and wget from brew but that shouldn't effect anything)
Right now this error is preventing me from playing back any tracks for more than a few seconds (before skipping / doing the same thing on the next track and etc until the end of the album)

Any help would be appreciated~

Much obliged

mherger
2017-10-21, 03:39
> I still see the helper plug-in for OSX that you suggested I install to
> get extra log data, yet from your repo I'm not seeing any updates for it
> yet...

Oh... did you even try without the additional plugin?

--

Michael

Gwaelod
2017-10-21, 04:10
Did you check server.log for any hints?



Spotty Plugin logging INFO I get this but it doesn't mean much to me

"2017-10-21 12:05:34 squeezeboxserver_safe stopped.
2017-10-21 12:05:34 squeezeboxserver_safe started.
[17-10-21 12:05:37.6678] Plugins::ShairTunes2W::Plugin::revoke_publishPlaye r (352) Stop old publish players services:7448
[17-10-21 12:05:37.6705] Plugins::ShairTunes2W::Plugin::revoke_publishPlaye r (352) Stop old publish players services:7463
[17-10-21 12:05:37.6734] Plugins::ShairTunes2W::Plugin::shutdownPlugin (264) Killing all processes shairport_helper-x64-linux
[17-10-21 12:05:37.7593] main::init (387) Starting Logitech Media Server (v7.9.1, 1495659078, Sat May 27 04:38:46 UTC 2017) perl 5.018002 - x86_64-linux-gnu-thread-multi
[17-10-21 12:05:37.8389] Plugins::Spotty::Connect::stopHelper (406) Quitting Spotty Connect daemon for b8:27:eb:8c:72:45
[17-10-21 12:05:42.6328] Plugins::CastBridge::Plugin::initPlugin (42) $VAR1 = {
'isDebian' => 1,
'binArch' => 'i386-linux',
'osName' => 'Debian',
'uid' => 'squeezeboxserver',
'osArch' => 'x86_64-linux',
'os' => 'Linux'
};
[17-10-21 12:05:50.6358] Plugins::ShairTunes2W::Plugin::initPlugin (199) Initialising 0.80.1 on x86_64-linux-gnu-thread-multi
[17-10-21 12:05:50.6403] Plugins::ShairTunes2W::Plugin::initPlugin (227) selected helper: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/ShairTunes2W/Bin/shairport_helper-x64-linux
[17-10-21 12:05:50.8619] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
[17-10-21 12:05:50.9070] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
[17-10-21 12:05:50.9194] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/curl
[17-10-21 12:05:50.9198] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/curl
[17-10-21 12:05:50.9210] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/pv
[17-10-21 12:05:50.9626] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/pv
[17-10-21 12:05:51.6786] Slim::Web::JSONRPC::requestMethod (443) cc:cc:09:f8:fc:dc: request not dispatchable!
[17-10-21 12:05:52.5335] Plugins::Spotty::Connect::startHelper (313) Starting Spotty Connect deamon: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c "/var/lib/squeezeboxserver/cache/spotty/d8a55be0" -n "Conservatory (b8:27:eb:8c:72:45)" --disable-discovery --onstart "/usr/bin/curl -s -X POST -d {"id":0,"params":["b8:27:eb:8c:72:45",["spottyconnect","start"]],"method":"slim.request"} http://192.168.1.67:9001/jsonrpc.js" --onstop "/usr/bin/curl -s -X POST -d {"id":0,"params":["b8:27:eb:8c:72:45",["spottyconnect","stop"]],"method":"slim.request"} http://192.168.1.67:9001/jsonrpc.js" --onchange "/usr/bin/curl -s -X POST -d {"id":0,"params":["b8:27:eb:8c:72:45",["spottyconnect","change"]],"method":"slim.request"} http://192.168.1.67:9001/jsonrpc.js" | /usr/bin/pv -L20k -B10k -q > /dev/null
[17-10-21 12:05:52.5838] Plugins::ShairTunes2W::Plugin::publishPlayer (376) start avahi-publish-service "Conservatory"
[17-10-21 12:05:52.6383] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (292) create client Slim::Player::SqueezePlay=ARRAY(0xa328120) with proc Proc::Background=HASH(0xd5f8668)
[17-10-21 12:05:58.1522] Plugins::ShairTunes2W::Plugin::publishPlayer (376) start avahi-publish-service "Lounge HiFi"
[17-10-21 12:05:58.2057] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (292) create client Slim::Player::SqueezePlay=ARRAY(0xed35438) with proc Proc::Background=HASH(0xe9ba978)
[17-10-21 12:06:20.5562] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:77:dc:e6: request not dispatchable!
[17-10-21 12:06:20.5617] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:5c:67:0d: request not dispatchable!
[17-10-21 12:06:50.6092] Slim::Web::JSONRPC::requestMethod (443) b8:27:eb:77:dc:e6: request not dispatchable!"

jasell
2017-10-21, 05:54
> Helper Applications Folder
> /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin/i386-linux,
> /share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Bin,
>
> /opt/ssods4/bin,
> /usr/bin,
> /usr/local/bin,
> /usr/libexec,
> /usr/sbin,
> /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux,
> /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin

Hmm... that seems to be fine. IIRC your problem is with pv only? Could
you please enable INFO logging for plugin.spotty, then try to fire up
Connect? What would server.log say?
--

Michael

Here is the logfile when doing a restart of the server (debug for Spotty).
i'm not sure how to test Connect since there is this warning that PV and/or CURL is needed...


0027: [17-10-21 14:47:55.9274] Slim::Web::JSONRPC::requestMethod (443) 00:04:20:1e:99:33: request not dispatchable!
0026: [17-10-21 14:47:54.9889] Plugins::Spotty::Connect::_getPVcmd (393) Didn't find the pv (pipe viewer) utility. Please install pv using your package manager
0025: [17-10-21 14:47:54.9860] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/wget
0024: [17-10-21 14:47:54.9850] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/wget
0023: [17-10-21 14:47:54.9831] Plugins::Spotty::Connect::_getCurlCmd (364) Didn't find the 'curl' utility. Please install curl using your package manager.
0022: [17-10-21 14:47:54.9662] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty
0021: [17-10-21 14:47:54.9476] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty
0020:
0019: frame 9: main::main (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 1213)
0018: frame 8: main::init (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 675)
0017: frame 7: Slim::Utils::PluginManager::load (/opt/ssods4/var/home/SqueezeboxServer/slimserver.pl line 597)
0016: frame 6: (eval) (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Utils/PluginManager.pm line 391)
0015: frame 5: Plugins::MyRadio::Plugin::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Utils/PluginManager.pm line 391)
0014: frame 4: Slim::Plugin::OPMLBased::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins/MyRadio/Plugin.pm line 20)
0013: frame 3: Slim::Plugin::Base::initPlugin (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/OPMLBased.pm line 54)
0012: frame 2: Plugins::MyRadio::Plugin::webPages (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/Base.pm line 69)
0011: frame 1: Slim::Web::HTTP::addPageFunction (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins/MyRadio/Plugin.pm line 47)
0010: frame 0: Slim::Utils::Log::logBacktrace (/share/MD0_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Web/HTTP.pm line 2568)
0009:
0008: [17-10-21 14:47:52.9212] Slim::Web::HTTP::addPageFunction (2568) Backtrace:
0007: [17-10-21 14:47:52.9199] Slim::Web::HTTP::addPageFunction (2568) Error: Slim::Web::HTTP::addPageFunction() is deprecated - please use Slim::Web::Pages->addPageFunction() instead
0006: [17-10-21 14:47:49 ] ssctrl Setting nice level to +0
0005: [17-10-21 14:47:49 ] ssctrl SqueezeboxServer started.
0004: [17-10-21 14:47:49.7434] main::init (387) Starting Logitech Media Server (v7.9.1, 1505480690, Fri Sep 15 20:21:59 UTC 2017) perl 5.010000 - i686-linux-thread-multi
0003: [17-10-21 14:47:49.7440] main::init (387) Starting Logitech Media Server (v7.9.1, 1505480690, Fri Sep 15 20:21:59 UTC 2017) perl 5.010000 - i686-linux-thread-multi
0002: [17-10-21 14:47:46 ] ssctrl Command line = /opt/ssods4/var/home/SqueezeboxServer/slimserver.pl --daemon --pidfile /opt/ssods4/var/home/SqueezeboxServer/Cache/squeezecenter.pid --cachedir /opt/ssods4/var/home/SqueezeboxServer/Cache --logdir /opt/ssods4/var/home/SqueezeboxServer/Logs --prefsdir /opt/ssods4/var/home/SqueezeboxServer/Prefs --noupnp --nodebuglog --noinfo --priority 0 --user ssods --group ssods --httpport 9001
0001: [17-10-21 14:47:45 ] ssctrl Starting SqueezeboxServer 7.9.1-1505480690.


Seem like LMS or Spotty is missing some path information since I can run PV and Curl manually from a terminal.

jasell
2017-10-21, 07:07
After upgrading to 1.9.5 I could play from within Spotty for a while.
Then after 2 songs playback stopped.
Then I'm not able to get it to play again. I have restarted LMS, restarted the my NAS 2 times but it doesn't help.

WHen I try to enter Spotty from the WEB GUI nothing happens.
In the server logg I get this:



0069: ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe599730)
0068: [17-10-21 15:49:11.1206] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling unk: Undefined subroutine &Data::Dump::dump called at /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 125.
0067: [17-10-21 15:49:11.1182] Plugins::Spotty::API::getToken (116) Got response: {"accessToken":"BQBQDuKCdDZk78lShNbazHs4lSqdX2luLEfb-ZLLiro_PS9dMgCC0EpO6DRHRE3Fdr3NBhgLrt9ZKw09X9LKPTa NAjMHISZmE2gtxnHnOlYQgABMpMrXjwBGhbi5bBuS-zxpBjEZUqYozDtlh_4fV9PgvLegRLOZARox2DuNvwuKzV3JdNh zbBghbumARL6Wa_GNyRf18CWRlKxSmuDK585zvQyU5zh0UPgnn 1UTaxGpXUt5kMly61PO9ZdUfkwy9E9Pxku16IFBvoiGhQlkpZc ydYa70pV_X27VILekW7bgBXzc4T9BDLGB7YUmmgc","expiresIn":3600,"tokenType":"Bearer","scope":["playlist-read-private","playlist-read-collaborative","user-follow-read","playlist-modify-private","user-read-private","user-follow-modify","user-modify-playback-state","user-library-read","user-library-modify","playlist-modify-public","user-read-playback-state","user-read-recently-played","user-top-read"]}
0066: ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xdcef520)
0065: [17-10-21 15:48:56.8723] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling unk: Undefined subroutine &Data::Dump::dump called at /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 125.
0064: [17-10-21 15:48:56.8699] Plugins::Spotty::API::getToken (116) Got response: {"accessToken":"BQAdgUSpAr32_1EAgKOYdGYIOpvD-yrjEkk-olpX2uThswjSq_SKm1RyfVF_N4J-mQwK26J-qhsUScR1G82UUjydUl5EaY91L1y89-0K4qSkealjf-bruthroJ7mTm-RwZiMf8WQtE2tL2BN9WhqHSpkxUFUn8Vej5Oca64j2nCnL0_U7 bqQjIhL8HCqLcw43qtAZBy6OoLrOz6_q86ZX6SJ8kfVZd6Yk_s sh_ExH13H5lte2uLZ-O4LUUMc8WK3iwBgvfLayuuGVLGNZUZnKzB7Y4rL-94GjJnhDILJBJ_UC-E_g38HX8Y8_ryyxts","expiresIn":3600,"tokenType":"Bearer","scope":["playlist-read-private","playlist-read-collaborative","user-follow-read","playlist-modify-private","user-read-private","user-follow-modify","user-modify-playback-state","user-library-read","user-library-modify","playlist-modify-public","user-read-playback-state","user-read-recently-played","user-top-read"]}
0063: ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xdc1d980)
0062: [17-10-21 15:48:47.5878] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling unk: Undefined subroutine &Data::Dump::dump called at /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 125.
0061: [17-10-21 15:48:47.5853] Plugins::Spotty::API::getToken (116) Got response: {"accessToken":"BQDCp4N4XLYIjprDFiukqAnTxjIM_qIt8onoAaZC1dyaC6U7yI aE-ChGEWmOEzRf_mNobK-VHyXUSq7r5Hr6-UlfHeLfTlllqCWxqRoOoTXLRSuvwbKq7c76g8fMN-FzMP7XmFn9vmaQQxhzVZIRIwYaPNbbm9OiBmS55hpK0ZkPszAx VyfnVtXo5kFIdJvQShrSAT10K2faA8c-xattsctBA6exfRRb5-JGIVQO4Q0B1FMco6m-8eLsw4ycMiw9t4AuqGMFTMaryVIHqzrUpm7zvnGh69gFtZcfh2 9u-oYwwuyWtM5MJNcBopF4gHE","expiresIn":3600,"tokenType":"Bearer","scope":["playlist-read-private","playlist-read-collaborative","user-follow-read","playlist-modify-private","user-read-private","user-follow-modify","user-modify-playback-state","user-library-read","user-library-modify","playlist-modify-public","user-read-playback-state","user-read-recently-played","user-top-read"]}
0060: [17-10-21 15:48:11.4562] Plugins::Spotty::Connect::_getPVcmd (393) Didn't find the pv (pipe viewer) utility. Please install pv using your package manager
0059: [17-10-21 15:48:11.4531] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /usr/bin/wget
0058: [17-10-21 15:48:11.4522] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /usr/bin/wget
0057: [17-10-21 15:48:11.4501] Plugins::Spotty::Connect::_getCurlCmd (364) Didn't find the 'curl' utility. Please install curl using your package manager.
0056: [17-10-21 15:48:11.4331] Plugins::Spotty::Plugin::findBin (609) Found helper applicaton: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty
0055: [17-10-21 15:48:11.0997] Plugins::Spotty::Plugin::findBin (605) Trying helper applicaton: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty


Can I downgrade to 1.9.4? Or is there something else that is broken?
I already had issues with Connect but could previously play Spotify from the Spotty-app.

kezz
2017-10-21, 09:46
Okay, so with the plugin unchecked now it kinda pretends to play but I get total silence...


[17-10-21 12:38:05.1252] main::init (387) Starting Logitech Media Server (v7.9.1, 1508251793, Tue Oct 17 08:43:59 PDT 2017) perl 5.018002 - darwin-thread-multi-2level
[17-10-21 12:38:06.6634] main::init (387) Starting Logitech Media Server (v7.9.1, 1508251793, Tue Oct 17 08:43:59 PDT 2017) perl 5.018002 - darwin-thread-multi-2level
[17-10-21 12:38:12.0572] Slim::Web::JSONRPC::requestMethod (443) 00:04:20:1f:40:88: request not dispatchable!

BoxFreak
2017-10-22, 11:18
I'm running LMS on Vortexbox. Spotty - this great plugin for my Squeezebox - has worked fine until lately. Now I cannot authorize my "main" spotify account with it for some reason. Earlier it worked just fine, and there's no problem authorizing my family's other accounts. I've tried to authorize manually (username and password), and via two android devices, and via Windows Laptop, but no luck. I've also uninstalled and reinstalled spotty and rebooted my server several times. What to do next?