-
Notifications
You must be signed in to change notification settings - Fork 20
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
Some streams fail with "415 Unsupported Media Type" #307
Comments
I saw this also with an episode of Karrewiet. This also occured on the vrt.nu website. I reported this to vrt and they had fixed this. This might have nothing to do with the add-on... |
Indeed, it doesn't play on VRT NU website either: This problem only occurs with the HLS-stream, the MPEG-DASH stream is working, when you enable inputstream adaptive, the stream plays fine. |
@mediaminister Should we provide a more sensible error to the user? E.g. try again with or without inputstream.adaptive, try running it from VRT NU website and report to VRT. Thanks everyone. |
Okay, I'll "fix" this providing a message to the user. |
I added a At some point we will cover most of the common/recurring issues with proper messages so that our users know exactly what to expect (and confidence in our solution stays high despite glitches elsewhere). |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Using Widevine DRM is always a free user choice, for livestreaming and for VOD. The cause of your problem was definitely the DRM option, I overlooked that. I improved the stream error message accordingly in: #332 |
Already four episodes of Appel d'urgence are affected and VRT didn't fix this yet... |
Okay, VRT NU fixed this yesterday. |
I reported another issue related to HLS stream playback (episode S04E05 of 24 hours in police custody) and VRT confirmed they still have intermittent issues related to this that they are trying to get fixed, so it still may happen from time to time... |
VRT NU uses Unified Origin and HTTP Error 415 is documented, only VRT NU can fix it: https://docs.unified-streaming.com/documentation/vod/index.html |
So we discovered that the VRT Radio2 live stream also suffers from this issue: I opened a dedicated ticket for this at #735 |
This happened again last night on the latest De Afspraak episode (2020-04-09). I reported it to VRT NU.
|
This time only the MPEG DASH stream failed, HLS was fine. This means Inputstream Adaptive detects the HTTP 415 error, but as far as I know there is no interface to catch the error in Python and show an error message to the user... |
We cannot easily handle this better. We handed this over to IA and any conceivable way to check playback is worse than the problem IMO. |
If |
Can we make a new ticket for this? This might also be the right way to handle Widevine issues. There is a missing link there too that we can have add-ons support through inputstreamhelper. Update: I opened #727 for this. Now we need to report this upstream. |
Describe the bug
There is an outstanding issue at VRT NU where some episodes do not work when using HLS streams (i.e. when not using Widevine). The problem has been reported a few times to VRT and they have confirmed this general issue. In most cases they will fix the faulty stream by hand when reported, but the root cause is yet unknown and unfixed.
This relates to #308, #311 and #538
To reproduce
Steps to reproduce the behavior:
Fix
Work around
Enable Widevine in the settings so the VRT NU add-on selects te MPEG-DASH stream that is unaffected by this issue.
Additional context
Log (if available)
This is an example log from an earlier identical issue.
The text was updated successfully, but these errors were encountered: