Announce: Spotify Premium Plugin (Beta)

[seren]

I did finally get 2.2.1 to install. Had to uncheck auto-update plugins.

But to no avail. Still same problem: Connect timed out: Transport endpoint is not connected

[seren]

Crap, removing the plugin f**ked up my squeezebox server. Won't run anymore. Now I still have to reinstall everything.. Damn, I should have known better and kept my hands off of the plugin

Update: Never mind, was a bit frustrated. A reboot of the NAS itself and then starting squeezebox again has me at least a working squeezebox config again (without spotify).

[veragooner]

Are you able to stream flac files without "bitrate limiting" set
for the player? If so the spotify plugin should be able to stream, but it depends on the quality of connection to spotify's servers. The default bitrate is higher than all but the radio3 bitrates from the iplayer plugin, so you may want to try with the 160k stream setting. Other than that, there are occasional spotify server congesion issues, but I don't see it happening that regularly.

I played an hour of FLAC files without any buffering, haven't had time to try Spotify again. It needs to be run and watched to be certain there's no buffering.

I did try 160k a while ago and still had problems but will give it a go if necessary.

Thanks for your time and help.

[NikolajC]

There are reports of some arm systems not liking the new spotify libraries - can you try a manual install of the 2.0.4 version which includes the last known working spotify library for these systems. Location should be: http://xdevtriodeplugins.xpdev-hoste...nux-v2.0.4.zip

I have tried what I thought was the correct way to do a manual install:

1. Remove newest plugin and stop server.
2. Copy 2.0.4 to \var\lib\squeezeboxserver\cache\InstalledPlugins\P lugins (that's where I found 2.2.1 plugin too - \var\lib\squeezeboxserver\Plugins is empty).
3. Setting group and user/owner to standard squeezeboxserver (like 2.2.1 had).
4. Starting the server again.

But for the life of me I cannot get the helper app to start with anything but 2.2.1

What am I missing?

It doesn't seem to actually install using the above method. For instance there are no .conf files in Spotify\Bin\arm-linux for starters.

[robob]

When I recently tried to upgrade to LMS 7.0, I had problems with Triode’s Spotify – it disappeared from the user menus, rendering it inaccessible. However, it was offered as an upgrade via the web interface to 2.2.1. Accepting the upgrade made it accessible again, but it didn’t work. It appeared that the helper app wasn’t running. A full removal and reinstall of LMS / Spotify still gave the same result (helper app not running). In desperation, I did a full system restore on the Mac (using Time Machine) to be sure I had got rid of LMS and to revert to the previous Spotify version. Sadly this produced exactly the same symptoms as the LMS upgrade (had to upgrade to Spotify 2.2.1 before I could use Spotify, then the helper app again refused to run). So much for system restore!

The helper app log produces pairs of error reports as shown below. I’ve tried fiddling with permissions and haven’t noticed any improvement.

I’d be really grateful for any ideas of how to get Spotify running again. It would probably be handy to know where the “Trace file” mentioned in the log should appear.

Hardware is Mac Mini (G4 PPC, Not Intel) OS 10.5.8. It had previously been running Triode’s Spotify OK since May.

Thanks for reading this,
Rob

[19:57:35.327381] main:361 /Users/Rob/Library/Caches/Squeezebox/InstalledPlugins/Plugins/Spotify/Bin/darwin-thread-multi-2level/spotifyd 2.2.1 started
[19:57:35.329007] main:419 Unable to create session: Unable to open trace file

[19:58:00.967500] main:361 /Users/Rob/Library/Caches/Squeezebox/InstalledPlugins/Plugins/Spotify/Bin/darwin-thread-multi-2level/spotifydppc 2.2.1 started
[19:58:00.969318] main:419 Unable to create session: Unable to open trace file

[nieldm]

I have the identical problem, all of a sudden the helper app won't run with the same error message:

Unable to create session: Unable to open trace file

[Triode]

I have the identical problem, all of a sudden the helper app won't run with the same error message:

Unable to create session: Unable to open trace file

What machine type is this - which OS?

[nieldm]

In my case this is a Mac Powerbook G4, OSX 10.5. Just upgraded to 7.7.1 with the same error.

[Triode]

[19:57:35.327381] main:361 /Users/Rob/Library/Caches/Squeezebox/InstalledPlugins/Plugins/Spotify/Bin/darwin-thread-multi-2level/spotifyd 2.2.1 started
[19:57:35.329007] main:419 Unable to create session: Unable to open trace file

[19:58:00.967500] main:361 /Users/Rob/Library/Caches/Squeezebox/InstalledPlugins/Plugins/Spotify/Bin/darwin-thread-multi-2level/spotifydppc 2.2.1 started
[19:58:00.969318] main:419 Unable to create session: Unable to open trace file

This looks to be only impacting ppc based Macs. Could one of the people with the problem try the following:

1) Open a shell and change directory to the location of spotifyd and spotifyd.conf.
2) prove spotfyd stops with this above error message by running it: ./spotifyd
3) edit the spotifyd.conf file to change the loglevel to TRACE
4) try running spotifyd again - do you see any different error messages?

(the trace feature should be switched off by default - I am not sure what is happening here yet, but the above should create a tracefile)

[Triode]

I have tried what I thought was the correct way to do a manual install:

1. Remove newest plugin and stop server.
2. Copy 2.0.4 to \var\lib\squeezeboxserver\cache\InstalledPlugins\P lugins (that's where I found 2.2.1 plugin too - \var\lib\squeezeboxserver\Plugins is empty).
3. Setting group and user/owner to standard squeezeboxserver (like 2.2.1 had).
4. Starting the server again.

But for the life of me I cannot get the helper app to start with anything but 2.2.1

What am I missing?

It doesn't seem to actually install using the above method. For instance there are no .conf files in Spotify\Bin\arm-linux for starters.

IF you manually install the plugin you will need to unzip the contents of the zip folder into the plugin location and make sure the plugin folder is at the top level of the Plugins's folder:

you should see a file:
../Plugins/Spotify/install.xml

Where .. depends on which plugin path you used.