Skip to content
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

h264 Hardware decoding? #207

Closed
satmandu opened this issue Nov 24, 2018 · 2 comments
Closed

h264 Hardware decoding? #207

satmandu opened this issue Nov 24, 2018 · 2 comments

Comments

@satmandu
Copy link

I'm using this through caphm's netflix plugin version from here: asciidisco/plugin.video.netflix#519

I'm able to play video but decoding appears to be software using inputstream.adaptive when other local h264 videos play using ff-h264-vaapi.

Is there a way to change this?

Debug log:
http://paste.ubuntu.com/p/ZxQbWqcY7V/

@satmandu
Copy link
Author

Ah, so I think I found the answer for this from here:
truedread/netflix-1080p#15 (comment)

Netflix uses Widevine DRM on Chrome, and with the license policy they have set (SW_SECURE_DECODE), the Widevine library decodes the frames rather than the CPU/GPU decoding the frames. As such, the frames are decoded without any sort of hardware acceleration, meaning on lower end computers, there will be frame drops. This is actually the reason Netflix only lets ChromeOS play 1080p with Chrome, because ChromeOS has hardware Widevine DRM, meaning Widevine can actually decode the frames through hardware acceleration, and as such there would be no frame drops.

So we would need the ChromeOS Widevine to work to get hardware decoding it seems. :/

@bam80
Copy link

bam80 commented Jul 27, 2019

It's interesting how it's done in ChromeOS. Can we borrow some blobs maybe for make it possible on normal linux?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants