-
Notifications
You must be signed in to change notification settings - Fork 22
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
AVC+Prk mode and DDPlus (Atmos) for Higher Bitrate #5
Comments
Not 100% sure but I think some of the HEVC/prk profiles will error out if you try to request them on a platform that doesn't actually support 4K, so they'll need to be gated behind some kind of "use_hevc" setting |
Idea: Since we're already doing regex magic with cadmium, it might be possible to extract out all possible profile strings automatically, and create some kind of checkbox interface that lets the user fiddle with which ones to enable/disable |
Prk with avc main that works on non-4k devices can be achieved with following profiles:
The above will unlock 1080p video at higher bitrate |
Hi, I really love this extension. It works greats in Chrome for 1080p playback. I just wish it could playback the videos in full bitrate mode, AVC mode, which occasionally has 50% more bitrate compared to AVCHigh.
Here is an extension that successfully does so in Chrome (it only does AVChigh + DDPlud on edge in 1080p mode on most computers). However, If the hardware is compliant, it also outputs 4k in edge):
https://github.com/lkmvip/netflix-4K-DDplus
And the following fork outputs AVC and DDPlus in 1080p mode on Edge but doesn't use prk (the developer has not updated the extension since Netflix introduced prk):
https://github.com/Sparoney/netflix-4K-DDplus
The problem with above extensions is that they need occasional maintenance due to the playercore updates. And this extension, which patches on the fly, is more future proof besides being efficient. So once the above features arrive, this extension will be the perfect one for netflix. Thanks again for all the hard work!
The text was updated successfully, but these errors were encountered: