8000 Feature Progress: Vero V widevine L1 Support for Inputstream · Issue #761 · osmc/osmc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature Progress: Vero V widevine L1 Support for Inputstream #761

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.

Sign up for GitHub

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

Jump to bottom
Open
ghost opened this issue Jan 2, 2024 · 3 comments
Open

Feature Progress: Vero V widevine L1 Support for Inputstream #761

ghost opened this issue Jan 2, 2024 · 3 comments

Comments

@ghost
Copy link
ghost commented Jan 2, 2024

Writing this to keep the public up to date on Widevine L1 support implementations on Inputstream using Vero V. L1 keys are burned onto Vero V. This feature has been hinted at but also has been downplayed for not wanting to advertise the capability before its ready. I would like to stress however that this is a feature that other plugins will have to implement like Amazon Vod so it would be nice to get progress updates to know when it will be ready for 3rd party implementation.
@ghost ghost mentioned this issue Jan 2, 2024
Closed
4 tasks
@samnazarko
Copy link
Contributor

This issue is for confirmed issues only, but I am happy to provide details.

Widevine L1 is implemented at the InputStream level.

Our current approach is:

  • Implement a custom wvDecrypter
  • Implement a custom Widevine CDM library -- we have already made suggestions to Inputstream Helper developers on how to recognise a downstream add-on and not replace it with the Chromebook ones.
  • Implement Secure Video Pathway (TVP decoder)

Therefore the Amazon Prime Video add-on should not need adjusting. Negotiation of content will give us L1 and we will handle the decode with hardware acceleration accordingly.

The last time we had this working was on v18.9 and we will look again after v21. With a new kernel and video pathway for V on the horizon, it makes sense to look after this unless we get a lot of pressure from commercial customers. We will probably roll out HDCP2.2 as standard as an early step of this in the coming weeks

@ghost
Copy link
Author
ghost commented Jan 4, 2024

Wait, You make it sound to me like L1 support is relatively short coming, does this mean we should soon get 1080p/4k on things like Amazon Prime which downgrade to 540p on L3? My impression was that software support for L1 wasn't even a guarantee.

@samnazarko
Copy link
Contributor
samnazarko commented Jan 4, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samnazarko
0