This may raise your CPU usage since Netflix was never intended to be played back in 1080p on Chrome.What was once a two line modification has turned into a giant project to cover all the bases in 1080p playback. After all those operations are performed, playback is resumed like normal.Īll the Chrome extension has to do is redirect all requests to Netflix's playercore to the modified one it has in the root directory. If you use an Edge playbackContextId and drmContextId, you'll be unable to obtain a Widevine license for Chrome. This is for license acquisition: those values are for the MSL server to maintain a persistent session between manifest acquisition and license acquisition. If not, call getManifest() from get_manifest.js and replace the playbackContextId and drmContextId from the Edge manifest with values from the Chrome manifest. What this new snippet of code does is test if the current page is a /watch/ URL, and if so check the Chrome manifest to see if a 1080p profile is already included. But since it's so heavily obfuscated, it was easier to rewrite one myself. Of course there already an MSL client in JavaScript: the playercore. So, the next problem is how do you get an Edge manifest within Chrome? That's what I attempted to do with get_manifest.js, which is a Netflix MSL client written entirely in JavaScript (essentially my pymsl library ported to JS). A few videos, like Disney movies, have manifests completely restricted to Edge to the point where you can't obtain them without an Edge ESN. This works perfectly, but only for the majority of Netflix content. The next easiest thing to do is just delete the conditional to append 1080p and just make the 1080p profile apart of the regular profiles ( this.oo = -> this.oo = ). I could never get it to work when I tried, Netflix always threw license errors. ChromeOS apparently has a different DRM implementation than chrome, even though both use Widevine.
The playback profile array is set up like so: this.oo =, x.V.vA is the SD profile and x.V.wA is the 720p profile.Īfter reading this you think the easy solution would be to just change the User-agent to make it contain the string "CrOS" right? Not that simple.
If the search returns true, it appends the 1080p profile to the profile playback array (what this line a & this.oo.push(x.V.TH) is doing). What it is doing is testing your User-agent for the "CrOS" string anywhere in it.