Repository navigation
Conversation
Livestreams like RTS 1/2 now report DASH-DVR; exact "DASH" match skipped them, leaving the item unresolved.
Contributor
Author
|
It is not limited to live streams, so I made a separate PR for it. I respect your decision not to support live streams. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Integration Layer now reports Widevine livestreams (e.g. RTS 1, RTS 2) with protocol
DASH-DVR.play_drmmatched"DASH"exactly, so no stream was found and the item stayed unresolved ("skipping unplayable item").Match any
DASH*protocol instead, mirroring the existingHLS/HLS-DVRhandling.Tested on Kodi 21 / Raspberry Pi.