-
Notifications
You must be signed in to change notification settings - Fork 242
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
[Bug] Latest ISA build from Github Actions carshes ISA #1690
Comments
are you able to try cherry-pick the commit from PR #1683 and rebuild it? |
do a checkout at 1683 and then build? |
maybe more easy for you manually edit the files |
It worked. |
thanks for the feedback |
@CastagnaIT |
clear key license request fwik is mandatory use POST request, |
What if the server already knows the current keyID which would be requested? |
what you are saying sound a bit weird to me looks like a out-of-spec thing, exists some test stream that can prove this? |
I am currently using this because ISA can't extract the Default KID from the media segments. Edit: My use case is described in Dash-Industry-Forum/DASH-IF-IOP#159 (comment)
|
yes what you are describing is the DRM key rotation behaviour, is not supported in ISA but your request is a workaround an attempt to mitigate this unsupported feature |
currently ISA can successfully extract default KID from initial segments but not from media |
initial segment is similar but different thing, |
See my above comment. I quoted something from the DASH IF. |
Describe the problem
I downloaded the latest builds from Github actions to test the new
inputstream.adaptive.common_headers
property.It was successfully installed. But when I tried to play any content with ISA (no matter the property used), it crashes Kodi.
Possible fix
No response
Steps to reproduce
Debug log
Stream manifest file(s)
No response
Additional info
No response
Operating system(s)
Linux
Operating system version(s)
Arch Linux
InputStream Adaptive version(s)
22.1.5
Kodi version(s)
Kodi (22.0-ALPHA1 (21.90.700) Git:20240924-20ad993b8e1-dirty)
The text was updated successfully, but these errors were encountered: