Home

Youtube and VP9 CPU decoder

%3CLINGO-SUB%20id%3D%22lingo-sub-475374%22%20slang%3D%22en-US%22%3EYoutube%20and%20VP9%20CPU%20decoder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-475374%22%20slang%3D%22en-US%22%3E%3CP%3EPlaying%20youtube%20videos%20by%20default%20will%20use%20VP9%20video%20decoder%2C%20however%20most%20computers%20do%20not%20have%20hardware%20support%20for%20VP9%2C%20so%20CPU%20decoding%20is%20used%20instead.%20This%20leads%20to%20high%20CPU%2FRAM%20usage%2C%20low%20battery%20life%2C%20and%20on%20many%20CPUs%3A%20choppy%20video%20playback.%20In%20%22old%22%20Edge%20this%20issue%20was%20resolved%20as%20VP9%20is%20disabled%20by%20default%20when%20hardware%20acceleration%20is%20not%20present%2C%20this%20is%20ideal%20behaviour%20which%20you%20can%20test%20and%20verify%20yourselves.%20A%20potential%20problem%20though%20is%20that%20access%20to%204k%20youtube%20video%20(on%20devices%20without%20hardware%20VP9%20support)%20is%20removed%20which%20massively%20contributes%20to%20the%20perception%20of%20%22Chrome%20is%20better%20than%20Edge%22%20therefore%20I%20suggest%20implimenting%20a%20flag%20to%20optionally%20disable%20VP9%20decoding%2C%20but%20leaving%20the%20default%20functionality%20in%20parity%20with%20Chrome.%20For%20context%3A%20the%20Chrome%20extension%20%22enhanced-h264ify%22%20offers%20the%20desired%20functionality%20I%20feel%20should%20be%20present%20in%20flags%3B%20The%20older%20%22h264ify%22%20extension%20is%20similar%20but%20mistakenly%20disables%20the%20opus%20audio%20codec%20and%20you%20should%20avoid%20replicating%20this%20issue.%20The%20h264%20codec%20is%20hardware%20accelerated%20on%20most%20computers.%20Ideally%20this%20flag%20should%20be%20implimented%20directly%20into%20Chromium%20as%20it%20would%20also%20benefit%20non-Edge%20users.%20Thank%20you%20very%20much%20for%20reading%20this%20feedback!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700505%22%20slang%3D%22en-US%22%3ERe%3A%20Youtube%20and%20VP9%20CPU%20decoder%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700505%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20may%20be%20able%20to%20use%20the%20%3CA%20href%3D%22edge%3A%2F%2Fflags%2F%23disable-accelerated-video-decode%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eedge%3A%2F%2Fflags%2F%23disable-accelerated-video-decode%3C%2FA%3E%20Experimental%20Flag%20in%20Microsoft%20Edge%20Insider%20Builds%20to%20disable%20the%20hardware%20acceleration.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGabriel%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Playing youtube videos by default will use VP9 video decoder, however most computers do not have hardware support for VP9, so CPU decoding is used instead. This leads to high CPU/RAM usage, low battery life, and on many CPUs: choppy video playback. In "old" Edge this issue was resolved as VP9 is disabled by default when hardware acceleration is not present, this is ideal behaviour which you can test and verify yourselves. A potential problem though is that access to 4k youtube video (on devices without hardware VP9 support) is removed which massively contributes to the perception of "Chrome is better than Edge" therefore I suggest implimenting a flag to optionally disable VP9 decoding, but leaving the default functionality in parity with Chrome. For context: the Chrome extension "enhanced-h264ify" offers the desired functionality I feel should be present in flags; The older "h264ify" extension is similar but mistakenly disables the opus audio codec and you should avoid replicating this issue. The h264 codec is hardware accelerated on most computers. Ideally this flag should be implimented directly into Chromium as it would also benefit non-Edge users. Thank you very much for reading this feedback!

1 Reply

You may be able to use the edge://flags/#disable-accelerated-video-decode Experimental Flag in Microsoft Edge Insider Builds to disable the hardware acceleration.

 

Gabriel