You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is related to #337, which essentially delivered a workaround.
It looks like some Google servers may be closing down the connection after 90 seconds. I.e. if the track has not been fully downloaded within 90 seconds, libcurl will find the connection closed. #377 introduced an EOS event when this occurs, which will make the player jump to the next song, as a workaround to the stalling situation in #337.
It looks like a more appropriate solution would be to make the http_source component buffer the whole track before the 90 second period is over.
juanrubio
changed the title
Google Music: track downloading is interrupted seemingly randmoly
Google Music: track downloading is interrupted seemingly randomly
Jul 3, 2017
This issue is related to #337, which essentially delivered a workaround.
It looks like some Google servers may be closing down the connection after 90 seconds. I.e. if the track has not been fully downloaded within 90 seconds, libcurl will find the connection closed. #377 introduced an EOS event when this occurs, which will make the player jump to the next song, as a workaround to the stalling situation in #337.
It looks like a more appropriate solution would be to make the http_source component buffer the whole track before the 90 second period is over.
This Google Play Music peculiarity has been recently documented in simon-weber/gmusicapi#548 and home-assistant-libs/pychromecast#175
The text was updated successfully, but these errors were encountered: