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
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
Describe the bug
Episode 5 of De Mol won't play.
Possibly link to the VMP requirement #69 if I look at the logs.
On 30/3 there was a similar issue with De Slimste Mens #131. Keiem sent an e-mail to GoPlay to ask why we couldn't watch 'De Slimste Mens' on a PC with an ARM processor. They answered that this wasn't the intention and they would check what was wrong. Possibly the same is going on here?
It is odd that in the title it says: REPLAY.
The previous episodes of De Mol are playing fine as do other programmes (e.g. Nonkels).
Expected behavior
A clear and concise description of what you expected to happen.
Issue is "resolved". As of this afternoon, the episode with "REPLAY" in the title got replaced and this one plays.
This issue was definitely related to the DRM and VMP requirement for live streams.
Ususally the live stream gets replaced with the "normal" version roundabout 22:00 (once De Mol Café is finished). This time it took quite a lot longer...
Describe the bug
Episode 5 of De Mol won't play.
Possibly link to the VMP requirement #69 if I look at the logs.
On 30/3 there was a similar issue with De Slimste Mens #131. Keiem sent an e-mail to GoPlay to ask why we couldn't watch 'De Slimste Mens' on a PC with an ARM processor. They answered that this wasn't the intention and they would check what was wrong. Possibly the same is going on here?
It is odd that in the title it says: REPLAY.
The previous episodes of De Mol are playing fine as do other programmes (e.g. Nonkels).
Expected behavior
A clear and concise description of what you expected to happen.
Logs
https://paste.kodi.tv/uxulelogin.kodi
System
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: