spottedbear;568724 Wrote: > When chosing a record from a spotify search-artist list usinng the web > interface, I sometimes get something else played (pretty much any > record at all by ELO. Why it's always ELO is curious, but perhaps > accidental.) > > I have only ever had this happen if I leave the browser window open > over night with the (for example) "Home > Spotify > Recent Searches > > Search Artists: rush > Rush > Albums (28)" pane on the left, and the > record play list on the right. Now, come morning, I click on some > record in the search pane, and it choses a seemingly random ELO record > instead. > > The spotifyd.log shows nothing strange, it seems convinced that it was > in a "Home > Spotify > Recent Searches > Search Artists: electric light > orchestra > Electric Light Orchestra > Albums (??)" pane instead. > > > Code: -------------------- > > > [09:35:51.267978] main:455 req: status.json res: (null) par: (null) prot: HTTP/1 > .0 auth: (null) > [09:35:51.268039] process_status:1016 process status > [09:35:51.298444] main:455 req: search.json res: (null) par: o=0&i=Rs&q=artist:e > lectric%20light%20orchestra prot: HTTP/1.0 auth: (null) > [09:35:51.340817] log_message:65 log: 07:35:51.340 I [ap:1368] Connecting to AP > A1.spotify.com:4070 > > [09:35:53.316130] main:787 search: artist:electric light orchestra offset: 0 art > ist count: 200 album count: 0 track count: 0 > [09:35:53.316303] container_loaded:78 playlist container loaded > [09:35:54.317570] search_callback:511 search: ok > [09:35:54.346211] main:455 req: browse.json res: spotify:artist:7jefIIksOi1EazgR > TfW2Pk par: (null) prot: HTTP/1.0 auth: (null) > [09:35:54.494545] main:673 created artist browse > [09:35:55.948777] browse_artist_callback:107 browse artist: ok > [09:35:55.956914] metadata_updated:69 new meta > [09:35:55.967037] main:455 req: browse.json res: spotify:album:66QcFfxG6WN0bgbam > FB6FR par: (null) prot: HTTP/1.0 auth: (null) > [09:35:55.967130] main:700 created album browse > [09:35:56.639313] browse_album_callback:410 browse album: ok > [09:35:56.693984] main:455 req: stream.flc res: spotify:track:0mwmH04zqNZqyOfRTu > Byws par: player=00%3A04%3A20%3A12%3A3b%3A65&start=0&sync=2&id=85 prot: SPOTSTRE > AM/1.0 auth: (null) > [09:35:56.694135] main:542 newstream connection from 192.168.1.117 > [09:35:56.697473] main:455 req: stream.flc res: spotify:track:0mwmH04zqNZqyOfRTu > Byws par: player=00%3A04%3A20%3A16%3Aef%3Abe&start=0&sync=2&id=85 prot: SPOTSTRE > AM/1.0 auth: (null) > [09:35:56.697522] main:542 newstream connection from 192.168.1.107 > [09:35:57.140836] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d844 > 9cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.176545] write_cover:57 cover fetch: No error > [09:35:57.176823] metadata_updated:69 new meta > [09:35:57.176977] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d844 > 9cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.180767] main:1062 Now playing: Turn To Stone > [09:35:57.180832] log_message:65 log: 07:35:57.180 I [file_picker.cpp:88] File p > icker: track=0bef7f3a768d433ab4b8417577060efc, file=1ed763287cf8d76def0ab04036ad > 511a427453f4, bitrate=160000, max=320000, target=320000, num=2 > > [09:35:57.180974] write_cover:57 cover fetch: No error > [09:35:57.181224] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d8449cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.184615] write_cover:57 cover fetch: No error > [09:35:57.275280] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d8449cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.279288] write_cover:57 cover fetch: No error > [09:35:57.300612] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d8449cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.305077] write_cover:57 cover fetch: No error > [09:35:57.305346] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d8449cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.308728] write_cover:57 cover fetch: No error > [09:35:57.828787] main:455 req: cover.jpg res: 720d1e382fa3578557c55dda1e942d8449cb7206 par: (null) prot: HTTP/1.0 auth: (null) > [09:35:57.832057] write_cover:57 cover fetch: No error > [09:35:57.979697] log_message:65 log: 07:35:57.979 I [file_streamer_simple.cpp:757] Request for file 1ed763287cf8d76def0ab04036ad511a427453f4 complete (code: 0) > > [09:35:58.299194] log_message:65 log: 07:35:58.299 I [file_streamer_simple.cpp:757] Request for file 1ed763287cf8d76def0ab04036ad511a427453f4 complete (code: 0) > > [09:36:12.924530] log_message:65 log: 07:36:12.924 I [file_streamer_simple.cpp:757] Request for file 1ed763287cf8d76def0ab04036ad511a427453f4 complete (code: 0) > -------------------- > > > > This was with 1.0.2 on Linux x86, squeezeboxserver version 7.5.1. I > upgraded the spotify plugin to 1.0.3 after this log was captured, but > I have obviously not had a chance to try this one over night. > > I'm not convinced that this really has anything to do with the > spotify plugin, but I've never experienced anything like this > otherwise.
I suspect this is due to length of time the server caches the current browsing session for (1 hour). If you go back to the same web page after this time within an "xmlbrowser" session then I would expect random results. I don't think I can do anything about this from within the plugin. -- Triode ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=79706 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
