Forum Discussion
Dev 155.0.4268.0 - HEVC cannot be played via hardware
Starting with Dev build 155.0.4268.0, HEVC content fails to playback throwing an error. This is attempting to use any hardware acceleration (NVIDIA, Intel, Qualcomm, etc). On the Stable channel, it still works as intended. I submitted feedback, but this is a rather impactful issue since a lot of websites use HEVC content.
Hi lexcyn - This issue should be fixed in Beta v155.0.4283.24, which was just released. If you are still having issues once updating to the newest Beta let us know. Thanks for the feedback!
-Kelly
15 Replies
- lexcynSteel Contributor
I know the team did not have enough time to fix it this fast, so I just wanted to note the issue is still present in the latest update 155.0.4273.0 if anyone is wondering!
- lexcynSteel Contributor
Just received the 156.0.4295.0 build on Canary and HEVC is now working as expected!!
Because HEVC still works in Stable but fails in one Edge Dev build across several graphics vendors, treat this as a likely preview regression until diagnostics show otherwise. In the affected Dev build, open edge://gpu and confirm whether Video Decode is hardware accelerated. Then reproduce playback and inspect edge://media-internals to record the codec, decoder name, and any initialization error. HEVC in Edge depends on a working Windows decoder path and a valid HEVC Video Extension, so record whether the extension is installed instead of assuming the GPU alone is responsible. Compare the same clip in Stable without changing the driver first. Keep Dev updated and submit the diagnostic details through Edge Feedback, including the exact Dev version, GPU, driver, codec information, and a reproducible public test source. A temporary Stable-channel workaround is reasonable for affected media, but do not permanently disable graphics acceleration without confirming that it changes the failure.
- lexcynSteel Contributor
Yeah, I already did all of the troubleshooting hence the post.
This was more just a warning to people of the issue and hopefully it does not make its way into the stable release, because we've seen that happen before, unfortunately.