Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Cari Bantuan

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.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

h264 Hardware decoding not working

  • 2 balas
  • 0 memiliki masalah ini
  • 1 kunjungan
  • Balasan terakhir oleh maky00

maky00
maky00
more options

My potato pc(amd A8-7600, 8G ram, rx560 2G) is not capable of YouTube vp9 hardware acceleration, but I played 1080p 60fps videos without difficulty using add-ons that force h264 decoding, but the videos started stuttering a while ago. At first, I thought it was add-ons problem, but other than YouTube, too

I used the translation app because I was not good at English

My potato pc(amd A8-7600, 8G ram, rx560 2G) is not capable of YouTube vp9 hardware acceleration, but I played 1080p 60fps videos without difficulty using add-ons that force h264 decoding, but the videos started stuttering a while ago. At first, I thought it was add-ons problem, but other than YouTube, too I used the translation app because I was not good at English
Lampiran tangkapan layar

Diperbarui oleh maky00 pada

Solusi terpilih

Problem solved after 119.0 update

Thank you.

Baca jawaban ini dalam konteks 👍 0

Semua Balasan (2)

zeroknight
zeroknight
more options

See if about:support reports any differently with the latest Nightly.

maky00
maky00 Pemilik pertanyaan
more options

Solusi Terpilih

Problem solved after 119.0 update

Thank you.