[mythtv] AVSync2 Refinements

Mark Kendall mark.kendall at gmail.com
Sat Dec 14 15:00:24 UTC 2019

On Fri, 13 Dec 2019 at 18:21, Tim Pletcher <pletchtd at gmail.com> wrote:
>> I was able to do a little more testing today and figured out how to nicely parse the log playback,timestamp data into a comma-delimited file to enable me to look more closely at some real data.
>> First, I found that a 0.4 gain and 0.9 filter as I initially proposed does work well.
> Apologies Mark.
> I just noticed you already committed the 0.04.  I don't mean to appear so indecisive on this :)   I think it is probably splitting hairs at this point as the control seems to work pretty good with either settings.


No problem. I'm minded to go back to 0.4 as it generally seems a
little slow to respond at the moment.

With respect to deinterlacers, hopefully the extra jitter you've
demonstrated is just a result of system load (in this case GPU rather
than CPU).

The VAAPI/VPP deinterlacers use FFmpeg/libavfilter code to run. These
will only return deinterlaced frames when they have seen at least 2
frames as they need multiple frames to work with. Hence there should,
in theory, be a 1 frame delay inherent in the filter. The same applies
to the OpenGL/shader kernel deinterlacer. It is that delay that I want
to feed back to the player.

The EDID data that is present in most modern displays is a set of
static figures that indicate to the connected device how long it takes
to process video frames prior to display. It just needs to be checked
once at the start of playback.


More information about the mythtv-dev mailing list