It appears that HW decoding for x264 is coming in firefox 116 August 1st. There is no info I can find so far about configuring it. ./configure --help does not show much light. Another question is does there have to be a special ffmpeg rebuild.
I would like to build the dev branch to play with. If anyone comes across any info please let me know.
I doubt it will work, It might have to be compiled against ffmpeg with vpu support or ffmpeg with v4l2-m2m enabled, which I doubt ffmpeg6 have v4l2-m2m enabled by default.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not
clearly detectable. Falling back to using the only one that was found. (t=4.51349) [GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not
clearly detectable. Falling back to using the only one that was found. (t=4.51349) |[1][GFX1-]: vaapitest: ERROR (t=4.63051) [GFX1-]: vaapitest: ERROR
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not
clearly detectable. Falling back to using the only one that was found. (t=4.51349) |[1][GFX1-]: vaapitest: ERROR (t=4.63051) |[2][GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection. (t=4.63058) [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection.
You are most likely correct. But mpv-0.36.0-1 with ffmpeg6 vpu hw acceleration was triggered when playing âx262.mkvâ video. So far only with âx264.mkvâ but not âh264.mp4â videos.
mpv --gpu-context=wayland --hwdec=v4l2m2m-copy â/run/media/jfl/Elements/Movies/English Movies/300.Rise.Of.An.Empire.2014.1080p.BluRay.x264-BLOW[rarbg]/blow-300.rise.of.an.empire.2014.1080p.bluray.x264.mkvâ
(+) Video --vid=1 () (h264 1920x800 23.976fps)
(+) Audio --aid=1 --alang=eng () (dts 6ch 48000Hz)
Subs --sid=1 --slang=eng âEnglish SDHâ (subrip)
Subs --sid=2 --slang=eng âEnglishâ (subrip)
[vo/gpu/wayland] GNOMEâs wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback.
AO: [pulse] 48000Hz 5.1(side) 6ch float
Using hardware decoding (v4l2m2m-copy).
VO: [gpu] 1920x800 nv12
Invalid video timestamp: 0.000000 â 0.000000
AV: 00:01:40 / 01:42:36 (2%) A-V: 0.000 Dropped: 1 Cache: 125s/150MB
Exiting⌠(Quit)
David Turner said,
âI propose to add support to Firefox for using V4L2-M2M video decode accelerators using the FFmpeg platform, in a manner similar to the existing VA-API supportâ
I wonât know until I can get firefox 116 compiled with this ffmpeg since the one in the repo does not have v4l2m2m enabled. Hopefully I can do it here as I have some restraints locally and if no new depends are required in the new ffmpeg/firefox.
Not sure what all is needed; the stock ffmpeg does not have v4l2m2m enabled and Firefox has ffmpeg as a depend. There is no guide I can find for 116 to say what extra is needed to compile for the pi4.
I am into 2 hours compiling Firefox 116 so far with arch-arm PKGBJILD to see what happens using my ffmpeg build.
ADDED:
Well my newly compiled firefox did not seem to work very well. In fact mp4 vids had trouble playing when it would play.
thought, v4l2 codes merge into vaapi module, so can not found âmedia.ffmpeg.v4l2(m2m).enabledâ.
so, just flag âtrueâ to âmedia.ffmpeg.vaapi.enabledâ.
am i right?