[email protected];617545 Wrote: > Hi, > > Well, maybe I was a bit too quick there. Today I've experienced 2 > issues with v1.3.2 which I believe is due to poor network performance. > I didn't see this with 1.3.1d. > > 1. Time out while waiting for data (at times): > > 22:37:18.984788] main:470 req: status.json res: (null) par: (null) > prot: HTTP/1.0 auth: (null) > [22:37:18.984930] process_status:1042 process status > [22:37:25.743311] main:470 req: browse.json res: > spotify:artist:1YzCsTRb22dQkh9lghPIrp par: (null) prot: HTTP/1.0 auth: > (null) > [22:37:25.743893] log_message:65 log: 21:37:25.743 I [ap:1388] > Connecting to AP ap.spotify.com:4070 > > [22:37:26.316878] log_message:65 log: 21:37:26.316 I [ap:938] Connected > to AP: 78.31.12.25:4070 > > [22:37:27.771261] metadata_updated:69 new meta > [22:37:31.332709] main:742 created artist browse > [22:37:31.333493] container_loaded:82 playlist container loaded > [22:37:56.591604] log_message:65 log: 21:37:56.591 E [ap:3624] > ChannelError(0, 1, playlist) > > [22:37:56.592060] log_message:65 log: 21:37:56.592 E [ap:3624] > ChannelError(1, 1, playlist) > > [22:38:02.613193] main:1239 timeout browse_artist > [22:38:02.613408] sockprintf:291 unabled to write to socket: 12 errno: > 32 Broken pipe > [22:38:02.613503] sockprintf:291 unabled to write to socket: 12 errno: > 32 Broken pipe > [22:38:02.613573] browse_artist_callback:64 browse artist: timeout > [22:38:02.613640] sockprintf:291 unabled to write to socket: 12 errno: > 32 Broken pipe > [22:38:30.249519] metadata_updated:69 new meta > [22:38:51.857040] main:470 req: status.json res: (null) par: (null) > prot: HTTP/1.0 auth: (null) > [22:38:51.857185] process_status:1042 process status > > 2: Album cover art loading slowly - Majority of album covers not > loading. > > [22:47:40.014112] main:470 req: prefetch res: > spotify:track:44zqBRucPIZDEaeG82SAzh par: (null) prot: HTTP/1.0 auth: > (null) > [22:47:40.014401] main:686 prefetching track: No error > [22:47:40.828877] metadata_updated:69 new meta > [22:47:51.339297] end_of_track:523 end of track > [22:47:57.267397] main:470 req: browse.json res: > spotify:album:2CLi6jGPWxW8sx1JKsVm6g par: (null) prot: HTTP/1.0 auth: > (null) > [22:47:57.269009] main:770 created album browse > [22:47:58.103631] browse_album_callback:384 browse album: ok > [22:47:58.124777] metadata_updated:69 new meta > [22:48:09.498513] main:470 req: stream.pcm res: > spotify:track:44zqBRucPIZDEaeG82SAzh par: > player=00%3A04%3A20%3A17%3Ac3%3Ac0&start=0&sync=1&id=53 prot: > SPOTSTREAM/1.0 auth: (null) > [22:48:09.498768] main:585 newstream connection from 192.168.0.100 > [22:48:09.498869] main:1168 Now playing: Worrisome Heart > [22:48:13.706112] log_message:65 log: 21:48:13.706 I > [file_streamer_simple.cpp:786] Request for file > 0c8ffb80ddd3dc7c3ef4a887c005ca2af894a937 complete (code: 0) > > Just say it and I'll provide any information that can contribute. > > Thanks!
That looks like it was attached to a spotify server which was not responding - did it get better after this? The best we can do at present is connect to another server when this occurs, but this will only occur after repeated timeouts. -- 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
