пн, 1 дек. 2025 г., 18:11 Andrea paz <[email protected]>:
> Did you export variables before giving these commands? Because I keep > getting errors using your commands (with my media). > No, no env. variables here. However, when I said that I don't understand decoding, I wasn't referring > to ffmpeg and vulkan, but to CinGG in general. I always get strange and > variable results that I can't figure out. > Well, hw decoding depend on driver (mesa components + kernel) and hardware itself. Newer AMD cards have different decoding/encoding block, and may support those drm modifiers for various interoperability reasons. X11 + use direct performance depend on compositor (viewport?) size, so on bigger screen you get bigger compositor window, more pixels to push (if no additional transforms applied, no camera/track movements , no fade, just single freshly loaded video track) -> less fps you see. Sometimes some AMD GPUs were just stuck at low gpu clocks, with obvious performance drop. I think it was mostly about older rx480 .... Software decoding may depend on how fast your drive, how well media file was cached (I run short tests from tmpfs), was cpufreq governor active .... Usual advice is to check temperatures/voltages with "sensors" under load (if they show believable values), ran memtest, look if other programs exhibit some strange behavior .... > _______________________________________________ ffmpeg-user mailing list -- [email protected] To unsubscribe send an email to [email protected]
