Announce: Spotify Premium Plugin (Beta)

[JElzenaar]

Do try the server and plugin on a intel based machine to see if there is any difference. You are using an arm based NAS which is relatively low power and may be contributing to the problem. I don't think you should right off squeezeboxe's just because of performance issues which may be due to a specific nas (or in this case the spotify servers not working with the arm version of their library if this is the case). Do you have more debugs of it going wrong and are they the same?

Hi Triode,

I tested it under Windows and it works fine. Maybe my NAS is not powerful enough. I have a 411j but the strange thing is it always worked fine before upgrading

[Triode]

Hi Triode,

I tested it under Windows and it works fine. Maybe my NAS is not powerful enough. I have a 411j but the strange thing is it always worked fine before upgrading

The arm version uses a different version of libspotify as the older one had bugs. Can you reproduce the error messages on it (maybe the library or the speed of the NAS)

[grabhorn]

What does the helper app log say at the time when you say it crashes (there is a link from the settings page for the plugin). Do you use the same account and are you trying to access the account at the same time from both machines?

Thanks for responding, Triode.

I just did a quick experiment where I started the LMS, then played a playlist in Spotify to induce the crash. Here's what shows in the spotifyd.log:

[10:25:20.124] main:375 C:\DOCUME~1\ALLUSE~1\APPLIC~1\SQUEEZ~2\Cache\INSTA L~1\Plugins\Spotify\Bin\MSWIN3~1\spotifyd.exe 2.2.5 started

(So, nothing interesting that I can see. Logging is set to "Error.")

The server.log file has this, though:

[12-06-16 10:25:20.2812] Slim::Utils::PluginManager::load (348) Warning: Couldn't call Slim::Plugin::UPnP::Plugin->initPlugin: Network::IPv4Addr: invalid netmask specification:
at C:/PROGRA~1/SQUEEZ~2/server/Slim/Plugin/UPnP/Discovery.pm line 79

At this stage, the LMS is not running, but spotifyd.exe still shows in the list of running processes.

In answer to your questions, we use different accounts at home and at work (we do run them concurrently, but that shouldn't be an issue since they're distinct accounts).

Thanks again for looking into this with us.

[JElzenaar]

The arm version uses a different version of libspotify as the older one had bugs. Can you reproduce the error messages on it (maybe the library or the speed of the NAS)

Reproduce it on the windows version, and then try to run it at a same speed as my NAS? How am i able to do that? Underclock my processor to a very low speed?
And what do you mean by the library? Use the ARM version library under the windows version? Should find out how to do all that.. I work in IT so i should be able to do it but i need some more directions..

[Triode]

Reproduce it on the windows version, and then try to run it at a same speed as my NAS? How am i able to do that? Underclock my processor to a very low speed?
And what do you mean by the library? Use the ARM version library under the windows version? Should find out how to do all that.. I work in IT so i should be able to do it but i need some more directions..

To simplify - can you reproduce the error and the same error messages in the helper app log when using the windows version rather than the arm version ?

(The windows version uses different internals from the arm linux version, but I'll avoid discussing that to avoid confusion)

[JElzenaar]

To simplify - can you reproduce the error and the same error messages in the helper app log when using the windows version rather than the arm version ?

(The windows version uses different internals from the arm linux version, but I'll avoid discussing that to avoid confusion)

Ok i'll try. And i should playback through my Duet receiver right to try to get the same errors? Or can i just try it with my own studio monitors? As yesterday i installed everything from Windows and playback through my boxes in my room without using the Squeezebox Duet and that played fine so i'll never get those errors probably. So i need to setup the network again of the receiver using different IP's? The one of my computer actually instead of the duet?

[JElzenaar]

Probably i did understand it wrong I'll post you the helper app log from the Windows version. Installing now

[JElzenaar]

To simplify - can you reproduce the error and the same error messages in the helper app log when using the windows version rather than the arm version ?

(The windows version uses different internals from the arm linux version, but I'll avoid discussing that to avoid confusion)

This is what i get by using the Windows version and playing it through my own speakers in my room. So i'm not using my Duet now. Everything works fine. What i notice is that loading top 10 tracks takes a bit longer then most then and on my Duet that takes ages when working with my NAS and eventually it time outs. First it always worked fine. So weird.

[21:34:03.762] metadata_updated:85 new meta
[21:34:03.831] metadata_updated:85 new meta
[21:34:03.885] main:539 req: cover.jpg res: spotify:image:cc6052b5629ff7660dc720af4ccad1249af5 29eb par: (null) prot: HTTP/1.0 auth: (null)
[21:34:03.887] main:539 req: cover.jpg res: spotify:image:f0dd4a841252c146768d8a6637a45a270ab9 13af par: (null) prot: HTTP/1.0 auth: (null)
[21:34:03.887] main:539 req: cover.jpg res: spotify:image:89f42235175f352f6b2880d23adaac8b12ae f980 par: (null) prot: HTTP/1.0 auth: (null)
[21:34:03.905] metadata_updated:85 new meta
[21:34:03.915] write_cover:33 cover fetch: No error
[21:34:03.924] write_cover:33 cover fetch: No error
[21:34:03.925] write_cover:33 cover fetch: No error
[21:34:04.110] metadata_updated:85 new meta
[21:34:04.179] metadata_updated:85 new meta
[21:34:04.251] metadata_updated:85 new meta
[21:34:04.325] metadata_updated:85 new meta
[21:34:04.343] metadata_updated:85 new meta
[21:34:04.439] metadata_updated:85 new meta
[21:34:04.457] metadata_updated:85 new meta
[21:34:04.610] metadata_updated:85 new meta
[21:34:04.671] metadata_updated:85 new meta
[21:34:04.795] metadata_updated:85 new meta
[21:34:04.835] metadata_updated:85 new meta
[21:34:04.906] metadata_updated:85 new meta
[21:34:05.043] metadata_updated:85 new meta
[21:34:05.073] metadata_updated:85 new meta
[21:34:05.175] metadata_updated:85 new meta
[21:34:05.225] metadata_updated:85 new meta
[21:34:05.322] metadata_updated:85 new meta
[21:34:05.337] metadata_updated:85 new meta
[21:34:05.416] metadata_updated:85 new meta
[21:34:05.444] metadata_updated:85 new meta
[21:34:05.549] metadata_updated:85 new meta
[21:34:05.564] metadata_updated:85 new meta
[21:34:05.628] main:539 req: tracks.json res: spotify:artist:1Cs0zKBU1kc0i8ypK3B9ai par: (null) prot: HTTP/1.0 auth: (null)
[21:34:05.628] main:1225 created artist tracks browse
[21:34:05.628] browse_artist_tracks_callback:249 browse artist tracks: ok
[21:34:07.545] metadata_updated:85 new meta
[21:34:07.564] main:539 req: browse.json res: spotify:track:1x6ACsKV4UdWS2FMuPFUiT par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.564] main:996 queuing track browse
[21:34:07.564] process_track:1204 process track
[21:34:07.564] process_track:1230 browse track: ok
[21:34:07.565] main:539 req: browse.json res: spotify:track:39w8X3cyEiM4uxObz55Qm5 par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.565] main:996 queuing track browse
[21:34:07.565] process_track:1204 process track
[21:34:07.565] process_track:1230 browse track: ok
[21:34:07.566] main:539 req: stream.flc res: spotify:track:1x6ACsKV4UdWS2FMuPFUiT par: player=90%3Ae6%3Aba%3A41%3A0c%3Ae4&start=0&sync=1& id=1 prot: SPOTSTREAM/1.0 auth: (null)
[21:34:07.566] main:727 newstream connection from 192.168.178.103
[21:34:07.568] main:1575 Now playing: Titanium - feat. Sia
[21:34:07.875] main:539 req: browse.json res: spotify:track:4GgOvZJ1vL1f6QTaPJdxXP par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.875] main:996 queuing track browse
[21:34:07.875] process_track:1204 process track
[21:34:07.875] process_track:1230 browse track: ok
[21:34:07.876] main:539 req: browse.json res: spotify:track:7xV6oF0LMnrXKEs6JrWQXf par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.876] main:996 queuing track browse
[21:34:07.876] process_track:1204 process track
[21:34:07.877] process_track:1230 browse track: ok
[21:34:07.878] main:539 req: browse.json res: spotify:track:1dG3YWhLiTyFfTJyT2DanJ par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.878] main:996 queuing track browse
[21:34:07.878] process_track:1204 process track
[21:34:07.878] process_track:1230 browse track: ok
[21:34:07.879] main:539 req: browse.json res: spotify:track:3OhFnVdXqYSM2GunYD3Oa9 par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.879] main:996 queuing track browse
[21:34:07.879] process_track:1204 process track
[21:34:07.880] process_track:1230 browse track: ok
[21:34:07.881] main:539 req: browse.json res: spotify:track:5iQYqhtjNeEw4Y8Ln5Nvsi par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.881] main:996 queuing track browse
[21:34:07.881] process_track:1204 process track
[21:34:07.881] process_track:1230 browse track: ok
[21:34:07.882] main:539 req: browse.json res: spotify:track:47Z5890IcjSed81ldeLgqc par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.882] main:996 queuing track browse
[21:34:07.882] process_track:1204 process track
[21:34:07.882] process_track:1230 browse track: ok
[21:34:07.883] main:539 req: browse.json res: spotify:track:6tsMC7YCLcQxr16O77fkoX par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.883] main:996 queuing track browse
[21:34:07.883] process_track:1204 process track
[21:34:07.884] process_track:1230 browse track: ok
[21:34:07.885] main:539 req: browse.json res: spotify:track:1Etdq9veihusHBIemDgxO2 par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.885] main:996 queuing track browse
[21:34:07.885] process_track:1204 process track
[21:34:07.885] process_track:1230 browse track: ok
[21:34:07.889] log_message:80 log: 19:34:07.889 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)
[21:34:07.891] main:539 req: cover.jpg res: spotify:image:f0dd4a841252c146768d8a6637a45a270ab9 13af par: (null) prot: HTTP/1.0 auth: (null)
[21:34:07.891] write_cover:33 cover fetch: No error
[21:34:07.905] metadata_updated:85 new meta
[21:34:07.929] metadata_updated:85 new meta
[21:34:08.034] log_message:80 log: 19:34:08.034 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)
[21:34:08.066] metadata_updated:85 new meta
[21:34:08.082] metadata_updated:85 new meta
[21:34:08.188] metadata_updated:85 new meta
[21:34:08.219] metadata_updated:85 new meta
[21:34:08.312] metadata_updated:85 new meta
[21:34:08.348] metadata_updated:85 new meta
[21:34:08.457] metadata_updated:85 new meta
[21:34:08.499] metadata_updated:85 new meta
[21:34:08.547] metadata_updated:85 new meta
[21:34:13.705] log_message:80 log: 19:34:13.705 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)
[21:34:17.139] main:539 req: status.json res: (null) par: (null) prot: HTTP/1.0 auth: (null)
[21:34:17.139] process_status:1286 process status
[21:34:22.222] log_message:80 log: 19:34:22.222 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)
[21:34:30.088] log_message:80 log: 19:34:30.088 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)
[21:34:37.956] log_message:80 log: 19:34:37.956 I [c:/spotify/libspotify/client/core/optional/file_streamer_simple.cpp:789] Request for file 2bf23132902753a9cbe4ea2b0b939aa425314a67 complete (code: 0)

[grabhorn]

What does the helper app log say at the time when you say it crashes (there is a link from the settings page for the plugin). Do you use the same account and are you trying to access the account at the same time from both machines?

Hi, Triode. Apparently the moderator didn't post my previous reply to you, so I'll try again...

The spotifyd.log has very little in it. Mostly these:

[09:45:38.626] main:375 C:\DOCUME~1\ALLUSE~1\APPLIC~1\SQUEEZ~2\Cache\INSTA L~1\Plugins\Spotify\Bin\MSWIN3~1\spotifyd.exe 2.2.5 started

But today there is also one of these:

[09:45:54.657] _sockprintf:391 unable to write to socket: 900 errno: 10054 Unknown error

In the server.log, that corresponds to these entries:

[12-06-18 09:45:25.0798] main::init (354) Starting Logitech Media Server (v7.7.2, r33893, Wed Mar 14 05:47:42 PDT 2012) perl 5.014001
[12-06-18 09:45:36.3764] Slim::Utils::PluginManager::load (348) Warning: Couldn't call Slim::Plugin::UPnP::Plugin->initPlugin: Network::IPv4Addr: invalid netmask specification:
at C:/PROGRA~1/SQUEEZ~2/server/Slim/Plugin/UPnP/Discovery.pm line 79

Also, the entry just prior to these in server.log was this:

[12-06-17 07:28:52.0143] Slim::Utils::PluginManager::shutdownPlugins (373) Warning: error running Slim::Plugin::UPnP::Plugin->shutdownPlugin: Can't locate object method "shutdown" via package "Slim::Plugin::UPnP::MediaServer" at C:/PROGRA~1/SQUEEZ~2/server/Slim/Plugin/UPnP/Plugin.pm line 58.

Thank you again. Please let me know if there's more I can dig up to help you.

[virgiliomi]

Triode,

Thanks for the great plugin! It runs great on my ReadyNAS Ultra2 Plus (dual core atom) and my SB players!

Is it possible to save a Spotify Radio station or playlist as a favorite? Is there a URL that can be used since there aren't any hearts? Any plans to add this feature? Would love to be able to wake up to a Spotify Radio station in the morning, regardless of what was playing the night before!

Thanks again for all your hard work!