[FFmpeg-trac] #11473(undetermined:new): Seeking video in mpv started to cause green and blocky glitches with FFmpeg 7.1 (using VAAPI)

FFmpeg trac at avcodec.org
Sun Feb 16 12:41:23 EET 2025


#11473: Seeking video in mpv started to cause green and blocky glitches with FFmpeg
7.1 (using VAAPI)
-------------------------------------+-------------------------------------
             Reporter:  jumperes     |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  7.1          |               Resolution:
             Keywords:  h264_vaapi,  |               Blocked By:
  VAAPI, va-api, mpv                 |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by jumperes):

 I was assuming anyway that SVG rendering is entirely unrelated to this
 issue - the terminal window icon might be rendered from the corresponding
 png asset under `/usr/share/icons` for all I know. I only linked the asset
 for illustrative purposes, in order to contextualize the glitches shown on
 the attached images. In any case, the icon is visible on screen so it
 already has to be decoded and rendered somewhere in memory before mpv and
 therefore ffmpeg are launched in the first place, right?

 In case the GPU Model I specified using output from `lspci` isn't enough:
 I am using an Intel HD 3000 (Sandy Bridge), so it's not quite as old as a
 an AMD 770 but I am aware that it is on the more ancient side. However, I
 believe that just that on its own shouldn't mean that regressions like
 this are unfixable? (Especially since it appears to hinge on one specific
 commit isolated to the vaapi code in FFmpeg.)
 I might be wrong here; in that case I'd very much appreciate at least some
 explanation (or pointers to appropriate reading material if it exists) as
 to why this issue is rooted in flawed hardware design limited to very old
 GPUs and why it would be infeasible to fix regressions like this.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11473#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list