hsmeets wrote: > Hi Triode, > > this is the log during slow response of the plugin, rate limit, I > wonder, is that something from the spotify servers? You probably know > best :-). > > How I trigger this error: I restarted LMS (and the helper) app and did > about 5 to 6 searches on broad terms like 'Beethoven', 'Marimba', I > paged through the results, played some tracks and started a new search, > and about the 5 or 6the time it became slow and produced the log as > below. > > What happens on screen is that the result list is shown in the left > window: titles/text that is, but the loading of coverart stalls/slows > down. > > [21:00:44.304456] main:537 rate limit > [21:00:44.517867] log_message:80 log: 19:00:44.517 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:00:50.304591] main:586 req: cover.jpg res: > spotify:image:3d6b1f81485072843bc576fba5bf369867aa6c07 par: (null) prot: > HTTP/1.0 auth: (null) > [21:00:50.305978] write_cover:96 cover fetch: No error > [21:00:50.307060] main:534 new connection > [21:00:50.307094] main:537 rate limit > [21:00:53.463158] log_message:80 log: 19:00:53.463 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:00:56.307222] main:586 req: cover.jpg res: > spotify:image:3d6b1f81485072843bc576fba5bf369867aa6c07 par: (null) prot: > HTTP/1.0 auth: (null) > [21:00:56.308478] write_cover:96 cover fetch: No error > [21:01:02.093826] log_message:80 log: 19:01:02.093 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:01:05.942828] main:534 new connection > [21:01:05.942887] main:537 rate limit > [21:01:10.664703] log_message:80 log: 19:01:10.664 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:01:11.943027] main:586 req: search.json res: (null) par: > o=50&alq=50&q=Boyce prot: HTTP/1.0 auth: (null) > [21:01:11.943098] main:1112 search: Boyce offset: 50 artist count: 0 > album count: 50 track count: 0 > [21:01:12.032417] search_callback:650 search: ok > [21:01:12.285208] main:534 new connection > [21:01:12.285265] main:537 rate limit > [21:01:18.285620] main:586 req: cover.jpg res: > spotify:image:e7c57153460e56ce8c8810d84e4c1d7f31aa2754 par: (null) prot: > HTTP/1.0 auth: (null) > [21:01:18.285771] main:534 new connection > [21:01:18.285795] main:537 rate limit > [21:01:19.065586] log_message:80 log: 19:01:19.065 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:01:24.286136] main:586 req: cover.jpg res: > spotify:image:5e31771574b33425d0891fa25cc2cc86c1b98d1d par: (null) prot: > HTTP/1.0 auth: (null) > [21:01:24.286281] write_cover:96 cover fetch: No error > [21:01:24.286433] main:534 new connection > [21:01:24.286457] main:537 rate limit > [21:01:28.051263] log_message:80 log: 19:01:28.051 I > [file_streamer_simple.cpp:789] Request for file > 98d42ffc4b349037b690ced60ece661f6ea804b2 complete (code: 0) > [21:01:30.286807] main:586 req: cover.jpg res: > spotify:image:7f5d191ac28cea3f0befb9d274431a14be0d9136 par: (null) prot: > HTTP/1.0 auth: (null) > [21:01:30.286924] write_cover:96 cover fetch: No error > [21:01:30.287065] main:534 new connection > [21:01:30.287089] main:537 rate limit > [21:01:36.287384] main:586 req: cover.jpg res: > spotify:image:2484adc07d9e1bba957302b15c1175791bfc7e5a par: (null) prot: > HTTP/1.0 auth: (null) > [21:01:36.287501] write_cover:96 cover fetch: No error > [21:01:36.287645] main:534 new connection > [21:01:36.287669] main:537 rate limit
You are hitting the rate limiting which is built into the plugin to avoid too many requests to spotify. Can you check whether every time it slow down you see the "rate limit" entry in the log? If so how much browsing are you doing to get to this point - you are the first person who has complained of getting to it. [I had a request from spotify to add some rate limiting - perhaps it is too agressive...] The current rate limiting should require high numbers of requests over 5 minutes before it kicks in - it will reset if you don't make many requests for 5 mins. ------------------------------------------------------------------------ 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 plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
