Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Html5 h264 video hardware acceleration not working

  • 3 பதிலளிப்புகள்
  • 2 இந்த பிரச்னைகள் உள்ளது
  • 11 views
  • Last reply by alez

Firefox nightly 45.0a1; Windows 10; Direct2D Enabled: true; Video example: https://www.youtube.com/watch?v=5CCOkiaqL0g

Firefox doesn't use hardware acceleration for html5 h264 codec videos. Cuz of that i got 100% CPU usage and freezing video playback. Chrome or Edge has about 15% CPU usage on same videos and smooth playback. Is it possible to fix it by myself or is it software bug?

Firefox nightly 45.0a1; Windows 10; Direct2D Enabled: true; Video example: https://www.youtube.com/watch?v=5CCOkiaqL0g Firefox doesn't use hardware acceleration for html5 h264 codec videos. Cuz of that i got 100% CPU usage and freezing video playback. Chrome or Edge has about 15% CPU usage on same videos and smooth playback. Is it possible to fix it by myself or is it software bug?

All Replies (3)

Hi alez could you first check if the hardware acceleration is checked in:

about:preferences#advanced (type this in address bar) and see if "use hardware acceleration when possible" is checked. ______________________ Also, could you take a screenshot from : https://www.youtube.com/html5 ______________________ Are you using flash player or html5 to watch youtube?

logglog said

Hi alez could you first check if the hardware acceleration is checked in: about:preferences#advanced (type this in address bar) and see if "use hardware acceleration when possible" is checked. Also, could you take a screenshot from : https://www.youtube.com/html5 Are you using flash player or html5 to watch youtube?

"Use hardware acceleration when available" is checked. ______________________ "https://www.youtube.com/html5" everything is supported besides "MSE & WebM VP9 " ______________________ i'm using html5 player with h264 codec, not vp9.

Found that firefox modification https://pcxfirefox.wordpress.com/ Works like a charm! So it is a software bug in current firefox version.