mirror of
https://github.com/kokarare1212/librespot-python.git
synced 2026-04-26 00:55:53 +03:00
[GH-ISSUE #154] [BUG] Audio key error when switching to very high quality #23
Labels
No labels
bug
dependencies
duplicate
enhancement
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot-python-kokarare1212#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mponweiser on GitHub (Sep 16, 2022).
Original GitHub issue: https://github.com/kokarare1212/librespot-python/issues/154
Describe the bug
Hi @kokarare1212, I am following the example "Get Music Stream", and depending on the AudioQuality flag, I am getting a RuntimeError:
Error message:
I am very certain I have a family account and in the desktop app on Linux can stream on HQ, so I don't see how this error can happen.
Would you be willing to look into this?
@kokarare1212 commented on GitHub (Sep 16, 2022):
Generally, such errors are caused by codecs that are not supported, account issues that prevent playback at the highest audio quality, or music that does not support the highest audio quality.
Can you tell me the Spotify URI where the problem occurs?
@mponweiser commented on GitHub (Sep 17, 2022):
Thank you, this makes it a bit easier to understand what might be the problem.
However, what are "account issues"? Is Spotify selectively disabling HQ playback on their side, even for premium users?
As to your question: the song ID is in the bug report, but others are causing the same problem:
@kokarare1212 commented on GitHub (Sep 17, 2022):
Strangely enough, it worked fine when I tried it.
I think the possible cause is that the songs do not correspond to the region of the account.
@mponweiser commented on GitHub (Sep 17, 2022):
OK, so I re-checked everything and it seems I was using an old - free - account, so the error was to be expected.
Thanks a lot you for your attention and patience, and of course, your work :-)