On Sun 11 Jul 2021 at 14:09:45 -0000, Michael van Elst wrote: > In the best case, the CPU is still decoding the input stream and > filling the display pipeline. If the CPU is too slow, or the decoder > latency cannot be anticipated, the decoded results will come too > late and frames get dropped. Sure, but with --vo=xv it works fine at the slowest cpu speed. As far as I know, with Xvideo, the cpu must do all the decoding, and Xvideo pretty much only takes care of the scaling and displaying. And scaling, now that I think about it, is even entirely absent when the video is already at HD size. Usually that is the slowest part. So there must be some other step involved that is much more efficient with XVideo than with dri/drm/MesaLib/gpu... hmmm.... -Olaf. -- ___ "Buying carbon credits is a bit like a serial killer paying someone else to \X/ have kids to make his activity cost neutral." -The BOFH falu.nl@rhialto
Attachment:
signature.asc
Description: PGP signature