I don’t see any difference. Works and plays the same.
1 Like
hmm, so I suppose you are affected too…
If you restore a snapshot from a few hours ago, before ffmpeg update, and enable that option media.ffmpeg.vaapi.enabled",true, you will see your CPU usage drop to less than 20% while playing that same video. At least this is what I think it will happen…
Well it doesn’t matter to me if it’s using 20% or less as long as it plays the video properly? 
It matters specially when you are using a laptop.
But, also if you want to save energy, keep your coolers with lower noise..
This happens because you are wasting CPU cycles in something that your GPU could do much more efficiently than your CPU.
I suppose you are right. I’m just speaking generally for me with a desktop i don’t have any issues as long as videos play properly and no stuttering or sound issues.
1 Like
Yes, for me too, but there are users here that really need to offload the CPU, older computers and such..
I’ve been searching and so far, I’m the only one reporting this issue..
Not sure if this is a new issue, or if it is only affecting me, but I’ll keep an eye on it.
Really thanks for your help ricklinux, I’m now more confident that this problem is only affecting Firefox, and it is probably due to ffmpeg update.
2 Likes
I just got another ffmpeg update?
Edit: So now i have both of these.
[2023-03-09T13:28:13-0300] [ALPM] upgraded ffmpeg (2:5.1.2-2 -> 2:6.0-3)
[2023-03-09T13:28:13-0300] [ALPM] upgraded ffmpegthumbnailer (2.2.2-4 -> 2.2.2-5)
1 Like
Those versions you showed are the versions I’m currently testing right now, and I can’t get VA-API to work with Firefox…
Checking Firefox debug, found a few things that weren’t happening previous the update…
I’ve been comparing debugs pre and pos update.
The logs below only appeared after the update. By the way, all logs posted here in this thread, are only showing after the update from today.
They don’t appear before the update based on the debug comparisons.
[AVHWDeviceContext @ 0x7f25952b3140] VAAPI driver: Mesa Gallium driver 22.3.6 for AMD Radeon RX 6750 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.2.2-arch1-1).
[AVHWDeviceContext @ 0x7f25952b3140] Driver not found in known nonstandard list, using standard behaviour.
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: VA-API FFmpeg init successful
[RDD 4785: MediaPDecoder #1]: V/PlatformDecoderModule ProcessDecode: mDuration=33000µs ; mTime=0µs ; mTimecode=0µs
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Choosing FFmpeg pixel format for VA-API video decoding.
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Requesting pixel format VAAPI_VLD
[vp9 @ 0x7f258efee400] Format vaapi chosen by get_format().
[vp9 @ 0x7f258efee400] Format vaapi requires hwaccel initialisation.
[vp9 @ 0x7f258efee400] A hardware frames or device context is required for hardware accelerated decoding.
[vp9 @ 0x7f258efee400] Failed setup for format vaapi: hwaccel initialisation returned error.
[vp9 @ 0x7f258efee400] Format vaapi not usable, retrying get_format() without it.
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Choosing FFmpeg pixel format for VA-API video decoding.
[vp9 @ 0x7f258efee400] Failed to initialize decoder for 640x360 @ 0
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: avcodec_send_packet error: Operation not permitted
[RDD 4785: MediaPDecoder #2]: D/PlatformDecoderModule FFVPX: ProcessFlush()
[Child 4695: MediaSupervisor #3]: D/PlatformDecoderModule Sandbox RDD decoder supports requested type video/vp9
[Child 4695: MediaSupervisor #3]: D/PlatformDecoderModule Sandbox RDD decoder supports requested type video/vp9
[RDD 4785: MediaSupervisor #1]: D/PlatformDecoderModule FFmpeg decoder supports requested type 'video/vp9'
[RDD 4785: MediaSupervisor #1]: D/PlatformDecoderModule FFmpeg decoder supports requested type 'video/vp9'
[RDD 4785: MediaSupervisor #1]: D/PlatformDecoderModule FFVPX: FFmpegVideoDecoder::FFmpegVideoDecoder MIME video/vp9 Codec ID 167
[RDD 4785: MediaSupervisor #1]: D/PlatformDecoderModule FFVPX: VAAPI is disabled by parent decoder module.
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Initialising FFmpeg decoder
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: codec vp9 : Google VP9
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Set get_buffer2 for customized buffer allocation
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: FFmpeg decoder init successful.
[RDD 4785: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: End of stream.
that beautiful + relax tune .
1 Like
@anon49550872
I didn’t have libva-utils or vdpauinfo installed before. Not sure if what you see you can tell any difference?
It is still much higher than it should be if you were using vaapi..
I’m doing some tests and now instead of upgrading everything, I just upgraded a few packages to confirm if the problem persists.
Packages updated:
ffmpeg ffmpegthumbnailer chromaprint mpv
Oh, the problem didn’t happen.. so ffmpeg and ffmpegthumbnailer are not to blame!!
4k60 !!
Now, tried to upgrade firefox to version 110.0.1-2 and the problem happened… 100% CPU usage during the same test.
Downgraded firefox and it is okay again…
Edit:
Included firefox in pacman.conf as a IgnorePKG and updated everything else.
$ cat /etc/pacman.conf | grep firefox
IgnorePkg = firefox
HW acceleration is working again in Youtube, but I’m back to the beginning, Rumble videos don’t play anymore… 
I don’t waste my time on rumble. 
1 Like
I have been trying to Ungoogle my entire life.. If its Big Tech, if its Big Pharma, I’m out, no thanks.
3 Likes
Updated the following packages:
alsa-plugins gst-libav gst-plugin-gtk gst-plugins-bad gst-plugins-bad-libs gst-plugins-base gst-plugins-base-libs gst-plugins-good gst-plugins-ugly gstreamer hwdata imagemagick imath libde265 openal openexr qt5-wayland tinycompress wayland-protocols
HW acceleration vaapi working, and Rumble videos working.
When I update these packages, the problem starts:
extra/chromaprint 1.5.1-6 1.5.1-7 0,00 MiB
extra/ffmpeg 2:5.1.2-2 2:6.0-3 0,51 MiB
extra/ffmpegthumbnailer 2.2.2-4 2.2.2-5 -0,01 MiB
extra/firefox 110.0.1-1 110.0.1-2 0,17 MiB
community/mpv 1:0.35.1-2 1:0.35.1-3 0,00 MiB
Based on these findings, I would say that this problem is unrelated to any DE…
1 Like
Firefox has now been updated to 110.0.1-3 and the changelog says “restore vaapi”. Hopefully this fixes it…
3 Likes
Oh yeah, everything is working smoothly again. 
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.