본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Youtube 60fps framedrops (Edge and IE no drops)

  • 3 답장
  • 1 이 문제를 만남
  • 71 보기
  • 최종 답변자: Da Vinci

more options

Hello,

the following issue concerns all (new) browsers Firefox, Edge Chromium, Chrome and Opium, from what I have tested. I have noticed the issue when using my 2016 notebook which has an intel n3710 cpu.

The issue: 60 fps videos on youtube have severe framedrops (15-20%) on all those browsers. The catch:(old) Edge and Internet Explorer have 0 framedrops. How can this be?

Two things:

1. By default Youtube uses the VP9 codec for video playback. The (old) Edge browser automatically disables VP9 and fallsback to AVC1 codec, when your hardware doesn't support VP9 decoding. All the newer browsers do not fallback to AVC1, which means even if your hardware doesn't support it, by default VP9 is used, which means high cpu usage, framedrops on 60fps videos, lower battery life. Why do the new browsers not fallback to AVC1 codec on youtube, if the hardware doesn't support it?

2. There are ways to force the AVC1 codec on youtube on the newer browsers via third party addons, or tweaks in the "about:config", which I already did. Stats-for-nerds on Youtube report that the AVC1 codec is being used, still, 60 fps videos have 15-20% framedrops. Hardware acceleration is active, obviously.

TLDR: Edge (old), Internet Explorer -> Youtube 60fps = 0 framedrops Firefox, Edge Chromium, Chrome -> Youtube 60fps = framedrops

Any ideas?

Hello, the following issue concerns all (new) browsers Firefox, Edge Chromium, Chrome and Opium, from what I have tested. I have noticed the issue when using my 2016 notebook which has an intel n3710 cpu. '''The issue:''' 60 fps videos on youtube have severe framedrops (15-20%) on all those browsers. The catch:(old) Edge and Internet Explorer have 0 framedrops. How can this be? Two things: 1. By default Youtube uses the VP9 codec for video playback. The (old) Edge browser automatically disables VP9 and fallsback to AVC1 codec, when your hardware doesn't support VP9 decoding. '''All''' the newer browsers do not fallback to AVC1, which means even if your hardware doesn't support it, by default VP9 is used, which means high cpu usage, framedrops on 60fps videos, lower battery life. Why do the new browsers not fallback to AVC1 codec on youtube, if the hardware doesn't support it? 2. There are ways to force the AVC1 codec on youtube on the newer browsers via third party addons, or tweaks in the "about:config", which I already did. Stats-for-nerds on Youtube report that the AVC1 codec is being used, still, 60 fps videos have 15-20% framedrops. Hardware acceleration is active, obviously. '''TLDR:''' Edge (old), Internet Explorer -> Youtube 60fps = 0 framedrops Firefox, Edge Chromium, Chrome -> Youtube 60fps = framedrops Any ideas?

글쓴이 Da Vinci 수정일시

모든 댓글 (3)

more options
more options

I am using that addon, which enables AVC1 codec. Without the addon the videos are unwatchable. With the addon, 30fps videos are fine, 60 fps vidoes have 15-20% framedrops, while (old) Edge and IE play 60 fps videos with 0 framedrops.

As a side note: Why does it require a third party addon to play youtube videos? This isn't progressive. Again, the old Edge automatically detects if the hardware supports VP9, and fallsback to AVC1 automatically, without the need for third party addons.

Firefox, Edge Chromium, Chrome should fix this.

글쓴이 Da Vinci 수정일시

more options

One more important thing: When watching any Youtube video on the old Edge or Internet Explorer (regardless if 30fps or 60fps), in Windows task manager under GPU-Engine it says "GPU0-Video Decode", and when using Firefox, Edge Chromium and Chrome it only says "GPU0 -3D"

I suspect that this is the reason why all the newer browsers have framedrops when watching 60fps videos, as it stresses the cpu more, and if the cpu is not powerful enough it will drop frames. Ideally it should all be decoded via gpu hardware, like on old Edge/IE and not using the cpu.

EDIT:Turns out that on the desktop PC with dedicated AMD gpu, it says "GPU0-Video Decode" in task manager using Firefox. That makes me believe the newer browsers do not correctly recognize the Intel mobile CPU n3710 from 2016. Maybe the gpu list for hadware decode needs to be updated?

Please report this to the mozilla team

글쓴이 Da Vinci 수정일시