-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 | Streams and Podcasts take very long to play / don't play at all #805
Comments
Does this relate to #807? |
I don't think so because local mp3s play without problems. |
Understood |
@JuliH29
|
Thanks for your help @MiczFlor !
No, my wifi runs smoothly. My phoniebox has the same issue in different wifis however.
Rather unlikely, as the problem appears in different wifis
Happens all the time, unfortunately. I wonder if it is a connectivity issue which is rather rrelated to buster than to phoniebox. On the other hand, Spotify does not seem to be affected. |
I found something via
I pasted the whole output here |
I assume you checked, if another client can play that stream? Did wait for around 15 minutes after the box has booted, if it’s a network resolution issue? And (probably unrelated): Your RFID Reader is not recognized:
To fix this, see https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/CONFIGURE-stretch#identify-and-configure-your-rfid-reader and https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/CONFIGURE-stretch#register-your-usb-device-for-the-phoniebox |
I have the same problem on different wifis and also after my phoniebox is running for more than 20 minutes. The stream plays without problems in the browser of my computer (so the stream itself is OK).
Is there anything else I can try? |
Uh, I might have just found the solution: While I'm happy about having found a solution I'm quite surprised that the Cloudflare DNS didn't work. Update I did some more testing: Other DNS services (for example Google) work as well. Only cloudflare seems to create problems.
|
I did some research on that. Apparantly it's a general problem of the Spotify architecture. Link |
So this issue could be closed for now? |
I guess so, as the issue is not on Phoniebox‘ side. |
I would like to reopen this thread because I did some research on podcasts: Die Sendung mit der Maus starts playing after 15 seconds, xml-file 13 kB Ohrenbär starts playing after 2 minutes 15 seconds, xml-file 781 kB Lage der Nation starts playing after a very long time (more than 10 minutes), xml-file 3,2 MB Here you can find the output of Beside of that, is there any way to find out what is happening in the background? |
Hi @JuliH29
Lage der Nation has a weird redirect URL in their enclosure tag:
... not sure if that also confuses mopidy. Is there any giganticly long RSS that plays faster? Three thoughts:
|
Tried Maus and Ohrenbear on Classic 2.0RC8 and no issues with them. |
Hi @MiczFlor , Thanks for your help.
I couldn't find any Umlaute in the filenames.
It's rather the opposite (Die Maus ca. 30MB, Ohrenbär ca. 10MB).
I don't think so because Spotify connects quite quickly and I can easily play anything from spotify.
Obviously this is a Spotify-version-only issue... Any more ideas? |
I found this: |
A quick update on this: I get a lot of error messages like these: Have a look at all of them if you want. Does anyone have an idea how we could fix this? |
I have the same problem. I tried adding
to I'd love to listen to podcasts - is there anything else we could try, here? Thanks for all this! |
Interesting idea. Is there some place else where we could try to override the limit of 5000ms?
I'm not quite sure but to me it seems that the bug/error is actually happening during step d). Do you agree, @bkis ? |
The logs indicate that it happens during step d), yes. Because just like in your comment it tries to address the actual mp3-URLs.
but it's weird that overriding the value doesn't change anything. To be fair, I didn't sink much time in this, yet. I will investigate further as soon as I have a chance. |
Hi, have you found a solution yet? I'm experiencing probably the same problem with the current Spotify version. Raspbian GNU/Linux 10 (buster) |
Hi there, It would be really cool if we could get this feature to work! |
Just starting to setup a new phoniebox spotify edition. Same problem here sadly! |
Bug
I downloaded the sample content which includes podcasts and streams. All the local files play smoothly. However, streams take very long to start playing and podcasts do nothing at all.
Podcast even seem to block/crash phoniebox and I have to reboot (which takes much longer than usually).
I run Phoniebox 2.0 RC8 on the develope branch but had the same problem with versions. At some point I thought it was a DNS problem #663 but that didn't fix it.
Right now I configured 1.1.1.1 and 1.0.0.1 as DNS.
static domain_name_servers=1.1.1.1 1.0.0.1
in
/etc/dhcpcd.conf
Example for podcast
http://www.kakadu.de/podcast-kinderhoerspiel.3420.de.podcast.xml
Example for stream
http://br-br2-nord.cast.addradio.de/br/br2/nord/mp3/56/stream.mp3
Any idea where I could start looking for a solution?
The text was updated successfully, but these errors were encountered: