It seems problem surface for OBS software too: https://github.com/obsproject/obs-studio/issues/10213#issuecomment-193114006... Can you try to set codec to generic av1 (or av1_vaapi) via our video codec mapping override (somewhere in manual)
I am responding here because the title is more appropriate than in the other thread.
you can simply comment out line "remap_video_decoder libaom-av1=libdav1d" in ffmpeg/decode.opts
Yes, hardware decoding with libaom works. There are no messages on the terminal. The GPU is only 8-21% busy but the CPU is only 2-6% busy. However, if scrolling there are still freezes and artifacts; the performance seems to me similar to dav1d and so I don't think it is convenient to use libaom. Note: again, until I deleted .bcast5, and started from 0, was left with working libdav1d instead of libaom. If you have other ideas/tests for me to do, please let me know.
can you try this patch for av1 hw decoding without commented out remap line? I also wonder if anything else (shotcut, openshot, kdenlive) can utilize hw av1 decoding better on your specific setup? пт, 26 апр. 2024 г., 15:52 Andrea paz <[email protected]>:
I am responding here because the title is more appropriate than in the other thread.
you can simply comment out line "remap_video_decoder libaom-av1=libdav1d" in ffmpeg/decode.opts
Yes, hardware decoding with libaom works. There are no messages on the terminal. The GPU is only 8-21% busy but the CPU is only 2-6% busy. However, if scrolling there are still freezes and artifacts; the performance seems to me similar to dav1d and so I don't think it is convenient to use libaom.
Note: again, until I deleted .bcast5, and started from 0, was left with working libdav1d instead of libaom.
If you have other ideas/tests for me to do, please let me know.
Your patch doesn't seem to work: the message still appears that 'libdav1d does not support vaap'i. You can't see any load on the GPU. It is the same starting CinGG with “CIN_HW_DEV=vaapi” than without. I have tried various appimages: - kdenlive has the option for GPU disabled (I think I need to install motif). - Openshot doesn't start because it requires glibc 2.35 while I have 2.39. - Shotcut works: GPU = 10-30%; CPU = 10-30%. However, it indicates that it is using libdav1d for the decoding and I don't understand why it works.
пт, 26 апр. 2024 г., 19:52 Andrea paz <[email protected]>:
Your patch doesn't seem to work: the message still appears that 'libdav1d does not support vaap'i. You can't see any load on the GPU. It is the same starting CinGG with “CIN_HW_DEV=vaapi” than without.
Ah, thanks. Then I guess only way to get vaapi accel for av1 is to comment line in ffmpeg/decode.opts
I have tried various appimages: - kdenlive has the option for GPU disabled (I think I need to install motif). - Openshot doesn't start because it requires glibc 2.35 while I have 2.39. - Shotcut works: GPU = 10-30%; CPU = 10-30%. However, it indicates that it is using libdav1d for the decoding and I don't understand why it works.
May be indication of decoder itself a bit broken in this case? Anyway, may be situation will be a bit better with some async patches floating at mesa and ffmpeg mail list/patch tracker .... If you think this is generic bug in AMD's vaapi driver you can try to enter it at mesa's bugtracker. May be this time our name/program will stick for at least some devs .....
participants (2)
-
Andrea paz -
Andrew Randrianasulu