Announce: Spotify Premium Plugin (Beta)

[OppfinnarJocke]

So it played ok for a long time, playlists and fwd and bwd etc, but suddenly it played just the first track and then stopped. Maybe, *maybe* had something to do with the fact that I minimized the cmd win. Seems far-fetched, still, that's what happened... And now it doesn't play the next track, I have to do that manually

The cmd win shows the following;

[20:14:46.281] end_of_track:234 end of track
[20:15:21.390] main:376 new connection
[20:15:21.390] main:401 req: cover.jpg res: cd0e1aa4539ebaefe674746eaa78a9646132
7843 par: (null) prot: HTTP/1.1
[20:15:21.390] write_cover:33 cover fetch: No error
[20:15:39.718] main:376 new connection
[20:15:39.718] main:401 req: stream.flc res: spotify:track:6AKzUB8aY7xRasHhCYHqS
Y par: player=00:04:20:16:d6:58&start=0 prot: SPOTSTREAM/1.0
[20:15:39.718] main:670 Now playing: Get It On
[20:15:39.718] log_message:63 log: 18:15:39.718 I [file_picker.cpp:88] File pick
er: track=d89e1108cea24915a09e611713385d20, file=c176efd2ce559acd2d9c20724267cfd
12ae1a0fe, bitrate=320000, max=320000, target=320000, num=3

[20:15:43.734] streambuf_canwrite:85 resetting stream
[20:15:43.734] streambuf_write:44 can't write: Unknown error 10054
[20:15:43.734] music_delivery:216 closing stream - flac returns error
[20:15:43.734] music_delivery:157 streamfd is 0 - discarding frames
[20:15:43.750] main:376 new connection
[20:15:43.750] main:401 req: stream.flc res: spotify:track:6AKzUB8aY7xRasHhCYHqS
Y par: player=00:04:20:16:d6:58&start=0 prot: SPOTSTREAM/1.0
[20:15:43.750] main:670 Now playing: Get It On
[20:15:43.750] log_message:63 log: 18:15:43.750 I [file_picker.cpp:88] File pick
er: track=d89e1108cea24915a09e611713385d20, file=c176efd2ce559acd2d9c20724267cfd
12ae1a0fe, bitrate=320000, max=320000, target=320000, num=3

[20:15:49.109] main:376 new connection
[20:15:49.109] main:401 req: stream.flc res: spotify:track:6AKzUB8aY7xRasHhCYHqS
Y par: player=00:04:20:16:d6:58&start=0 prot: SPOTSTREAM/1.0
[20:15:49.109] main:453 existing streaming connection exists - killing
[20:15:49.109] main:670 Now playing: Get It On
[20:15:49.109] log_message:63 log: 18:15:49.109 I [file_picker.cpp:88] File pick
er: track=d89e1108cea24915a09e611713385d20, file=c176efd2ce559acd2d9c20724267cfd
12ae1a0fe, bitrate=320000, max=320000, target=320000, num=3

EDIT: Yes! Definitely works much *much* better running this way (with spotfyd.exe in its own cmd win). Been running now for some hours with only minor glitch.

[sondek]

I can only play my playlists and nothinh else? When i try to search for artist, album and play it or play what´s new i get at timeout

[sondek]

from which directory do i run
spotifyd.exe?

[OppfinnarJocke]

Here's a new one. Suddenly spotifyd.exe just quits:

[22:55:57.796] log_message:63 log: 20:55:57.796 I [file_streamer_simple.cpp:757]
Request for file ef5216eb5aba818d4d04c4ba07d2cca1773e1d51 complete (code: 0)

[22:56:20.062] end_of_track:234 end of track
[22:57:09.656] main:376 new connection
[22:57:09.656] main:401 req: (null) res: (null) par: (null) prot: (null)

C:\Users\All Users\Application Data\Squeezebox\Cache\InstalledPlugins\Plugins\Sp
otify\Bin\MSWin32-x86-multi-thread>^A

Staring it again (from the cmd win) it works.

[OppfinnarJocke]

from which directory do i run
spotifyd.exe?

Open win explorer and search on your system disk (C: probably) for "spotifyd.exe". When you've found it, right click and open cmd win there. Then type "spotifyd.exe" followed by return.

If you don't have "Open Command prompt here" (or similar) in your right click menu, look here: http://www.microsoft.com/windowsxp/d...powertoys.mspx

[joca]

And stranger thing... trying to play All Songs of an album from which the first song has already played, then doesn't even play the first song, just shows the artwork and counts the seconds. My Duet controller shows the artwork and says "Connecting".

I have had this problem to one time yesterday and one time today. I restarted my internet router (combined adsl modem, firewall and WiFi) and then everything plays normal again. Have tried from a Boom, Radio and SBC3 both playlist and search artists and songs and it all works.

[terjehaa]

I was assuming that when you select 320k they are all 320k, but if you set the helper app logging to DEBUG and look at the log you can see that this is not always true. This information is not made available anywhere other than the log.

Any idea why not all streams are 320kbps?

[sondek]

I get these errors in my log.

Connect timed out: Bad file descriptor
[10-06-19 23:56:36.5578] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/toplist.js...lbums&r=Sweden
Connect timed out: Bad file descriptor
[10-06-20 00:05:41.2196] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/playlists.json
Connect timed out: Bad file descriptor
[10-06-20 00:13:28.7515] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/search.json?q=tag:new
Connect timed out: Bad file descriptor

[Triode]

I get these errors in my log.

Connect timed out: Bad file descriptor
[10-06-19 23:56:36.5578] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/toplist.js...lbums&r=Sweden
Connect timed out: Bad file descriptor
[10-06-20 00:05:41.2196] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/playlists.json
Connect timed out: Bad file descriptor
[10-06-20 00:13:28.7515] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.0.197:9001/search.json?q=tag:new
Connect timed out: Bad file descriptor

Those mean that the spotifyd process has not responded within the timeout. Assume it has recoved after this it is nothing to worry about. It can be due to Spotify being busy (seems to have been today?)

[OppfinnarJocke]

Those mean that the spotifyd process has not responded within the timeout. Assume it has recoved after this it is nothing to worry about. It can be due to Spotify being busy (seems to have been today?)

Are you saying that most (all?) of our problems are related to spotify being busy? I can buy that... will try again tomorrow morning...