ok, when stop track, it show
***[h264_v4l2m2m @ 0xffffb1b85400] V4L2 Codec end
CPU 50% up/down playing YT-480p not my expected 30%.
Pi4/sway/wayland/foot-htop/firefox-117b9, nothing more.
ok, wait 117 release days later.
Does this mean you managed to enable vpu hw acceleration on Firefox-116.0.3 with all h264 video?
So far I can not play .mkv files. I have not done extensive testing or do I plan to have firefox running with ffmpeg-rpi all of the time since ffmpeg (v6) has to be uninstalled. Too many other programs I use depend on ffmpeg (v6). Some of the other distro’s still use ffmpeg (4.4) so not of an issue for them.
Luckily you have created “ffmpeg-rpi and mpv-1:0.36.0=3” which stream online videos which in a way mitigate the Firefox vpu hw acceleration requirement.
Ubuntu Jammy uses ffmpeg-4.4 2, how to enable Firefox-116.0.3 to activate v4l2? Would like to test it out.
fmpeg-4.4 2 would have to be replaced with ffmpeg-rpi.
Is ffmpeg-rpi compatible with Ubuntu, in terms of dependencies? If yes, what comands to install on Jammy? As ffmpeg-rpi is different from the usual “deb” packages.
I suppose one ffmpeg-rpi replaces ffmpeg-4.4.2 other apps might not work like mpv, or other apps that has dependencies on ffmpeg-4.4.2.
Uggh. Probably more trouble than it is worth for just testing. I did not think about jammy being ubuntu. Converted deb’s do work sometimes on manjaro-arm.
btw, only a line add to build ‘–enable-default-toolkit=cairo-gtk3-wayland-only’ for my used.
117 released.
add,
found chromium had ‘use_v4l2_codec=true’ flag, too.
so why not add to PKGBUILD?
1 Like
I have been testing firefox today with v4l2m2m, youtube and enhancedh264ify and so far I am pleased. It brings my cpu % way down compared to playing vp9 and my scaling of my cpu does not peg out very much.
1 Like
We do not build chromium.
and, we do not build firefox-117, either?
No we do not
jc-kynesim’s ffmpeg had some commit.
Looks like the addition of some x11 10bit pix fmt’s. Here is the new rpi-ffmpeg6 package with the latest.
md5sum:
6c23d4fbbf18d5eeae03168592697228 rpi-ffmpeg-6.0.r110072.g61733f14a6-1-aarch64.pkg.tar.zst
https://drive.google.com/file/d/1C0NH8oM0Lmb6J6F9aH16R_FgL5hi0L4m/view?usp=sharing
1 Like
Hi @Darksky,
Thanks for the latest update of rpi-ffmpeg-6.0.
It works on GT King Pro. I do notice this
[vaapi] libva: /usr/lib/dri/v4l2_request_drv_video.so init failed
[vaapi] libva: /usr/lib/dri/v4l2_request_drv_video.so init failed
jfl@jfl-gtkpro mpv --gpu-context=wayland --hwdec=auto https://www.youtube.com/watch?v=aqz-KE-bpKQ
(+) Video --vid=1 (*) (h264 1920x1080 60.000fps)
(+) Audio --aid=1 (*) (aac 6ch 48000Hz)
File tags:
Uploader: Blender
Channel_URL: https://www.youtube.com/channel/UCSMOQeBJ2RAnuFungnQOxLg
[vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback.
[vaapi] libva: /usr/lib/dri/v4l2_request_drv_video.so init failed
[vaapi] libva: /usr/lib/dri/v4l2_request_drv_video.so init failed
Using hardware decoding (v4l2m2m).
AO: [pulse] 48000Hz 5.1 6ch float
VO: [gpu] 1920x1080 drm_prime[nv12]
AV: 00:00:09 / 00:10:34 (2%) A-V: 0.000 Dropped: 2 Cache: 6.8s/5MB
Exiting... (Quit)
I noticed that the " /usr/lib/dri/v4l2_request_drv_video.so" is dated 23 Mar 2021 whereas all the other drivers in /usr/lib/dri/ are dated 12 Sep 2023.
Could this be the issue of very old driver “/usr/lib/dri/v4l2_request_drv_video.so” causing it not be able to initialized? Could this be also the cause of Firefox 116 lack of vpu hw acceleration?
Is there a newer version of v4l2_request_drv_video.so available for download?
I have seen those warings in the past with the rpi but the rpi4 does not use vaapi; it is just checking. Looks like to me it may be the same for your device since you wind up with HW decoding.
I am thinking from what I read is 116 was modified for the rpi4 64bit and have not seen any other device mentioned.
Yes, mpv with rpi-ffmpeg-6.0 vpu hw acceleration is available.
I thought the libva-v4l2_request being much older (23 March 2021) than the rest of the other drivers (12 Sep 2023) might be the issue.