Mailing List Archive

Hi John

I'll have a look but I doubt that particular commit is the problem -
more likely the ffmpeg resync?

Anybody seeing issues in master?

Regards
Mark

On Sat, 16 Nov 2019 at 13:52, John Pilkington <johnpilk222@gmail.com> wrote:
>
> Yesterday and today I have become aware of lipsync drift during
> continuous playback. Restarting and stepping forward to the same point
> restores good playback.
>
> This is using 'Normal' decoding, shown on the later page as ffmpeg &
> opengl or 'Standard', HQ Deinterlacers with no options ticked.
>
> Current build b8e27f103, first suspected in ca1453f5, for el7
>
> Seen both with and without AVSync2
>
> DVB-T recordings. They have been processed using Project-X, which may
> insert extra audio frames to maintain sync, but I've been using that for
> years. I suppose the most obvious suspect is ca1453f, but I'm not sure
> that it's active with my settings.
>
> John P
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Mark,

I have not seen sync issues in master. This on my living room system,
Intel plus NVIDIA /VDPAU.

Groetjes,
Klaas.

On Sun, 17 Nov 2019 at 12:04, Mark Kendall <mark.kendall@gmail.com> wrote:
>
> Hi John
>
> I'll have a look but I doubt that particular commit is the problem -
> more likely the ffmpeg resync?
>
> Anybody seeing issues in master?
>
> Regards
> Mark
>
> On Sat, 16 Nov 2019 at 13:52, John Pilkington <johnpilk222@gmail.com> wrote:
> >
> > Yesterday and today I have become aware of lipsync drift during
> > continuous playback. Restarting and stepping forward to the same point
> > restores good playback.
> >
> > This is using 'Normal' decoding, shown on the later page as ffmpeg &
> > opengl or 'Standard', HQ Deinterlacers with no options ticked.
> >
> > Current build b8e27f103, first suspected in ca1453f5, for el7
> >
> > Seen both with and without AVSync2
> >
> > DVB-T recordings. They have been processed using Project-X, which may
> > insert extra audio frames to maintain sync, but I've been using that for
> > years. I suppose the most obvious suspect is ca1453f, but I'm not sure
> > that it's active with my settings.
> >
> > John P
> >
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev@mythtv.org
> > http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> > http://wiki.mythtv.org/Mailing_List_etiquette
> > MythTV Forums: https://forum.mythtv.org
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 17/11/2019 21:25, Klaas de Waal wrote:
> Hi Mark,
>
> I have not seen sync issues in master. This on my living room system,
> Intel plus NVIDIA /VDPAU.
>
> Groetjes,
> Klaas.
>

Same here. I've just managed to get database access back on my kubuntu
laptop, now running yesterday's ppa build of master (somehow the bind
address=0.0.0.0 had been commented out in /etc/mysql/conf.d/mythtv.cnf)
and sync seems fine; DVB-T SD, ffmpeg decoding.

But I'm still seeing the drift in 2019-render b8e27f103 also using
ffmpeg. It gets noticeable after perhaps 10 minutes and obtrusive after 30.

John


_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, 17 Nov 2019 at 22:58, John Pilkington <johnpilk222@gmail.com> wrote:
>
> On 17/11/2019 21:25, Klaas de Waal wrote:
> > Hi Mark,
> >
> > I have not seen sync issues in master. This on my living room system,
> > Intel plus NVIDIA /VDPAU.
> >
> > Groetjes,
> > Klaas.
> >
>
> Same here. I've just managed to get database access back on my kubuntu
> laptop, now running yesterday's ppa build of master (somehow the bind
> address=0.0.0.0 had been commented out in /etc/mysql/conf.d/mythtv.cnf)
> and sync seems fine; DVB-T SD, ffmpeg decoding.
>
> But I'm still seeing the drift in 2019-render b8e27f103 also using
> ffmpeg. It gets noticeable after perhaps 10 minutes and obtrusive after 30.

John

I've looked through the commits and I can't see anything that would
obviously cause an issue. I've done some limited testing and don't see
any issues (will try again more completely later).

Can you help narrow it down at all?

Any broad idea when it started? Any particular config that causes the
issue? Hardware decoder/software decoder? Audio setup?

Essentially - any pointers:)

Thanks and regards
Mark
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 17/11/2019 22:57, John Pilkington wrote:
> On 17/11/2019 21:25, Klaas de Waal wrote:
>>   Hi Mark,
>>
>> I have not seen sync issues in master. This on my living room system,
>> Intel plus NVIDIA /VDPAU.
>>
>> Groetjes,
>> Klaas.
>>
>
> Same here.  I've just managed to get database access back on my kubuntu
> laptop, now running yesterday's ppa build of master (somehow the bind
> address=0.0.0.0 had been commented out in /etc/mysql/conf.d/mythtv.cnf)
> and sync seems fine;  DVB-T SD, ffmpeg decoding.
>
> But I'm still seeing the drift in 2019-render b8e27f103 also using
> ffmpeg. It gets noticeable after perhaps 10 minutes and obtrusive after 30.
>
>

I'm still getting loss of a/v sync in my el7 box, more noticeable in
some recordings than others, but the fedora 30 system built at the same
commit has not yet done the same, using either NVdec or ffmpeg decoding.

The OSD of playback data doesn't show any drift in the a/v sync value,
even when an offset of over 1 s has developed.

Hmm.

John


_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Mon, 18 Nov 2019 at 11:47, John Pilkington <johnpilk222@gmail.com> wrote:
> I'm still getting loss of a/v sync in my el7 box, more noticeable in
> some recordings than others, but the fedora 30 system built at the same
> commit has not yet done the same, using either NVdec or ffmpeg decoding.

I'm assuming el7 is enterprise linux 7?

What decoder/playback settings is that box using?

Thanks, Mark
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 18/11/2019 11:58, Mark Kendall wrote:
> On Mon, 18 Nov 2019 at 11:47, John Pilkington <johnpilk222@gmail.com> wrote:
>> I'm still getting loss of a/v sync in my el7 box, more noticeable in
>> some recordings than others, but the fedora 30 system built at the same
>> commit has not yet done the same, using either NVdec or ffmpeg decoding.
>
> I'm assuming el7 is enterprise linux 7?
>
> What decoder/playback settings is that box using?
>
> Thanks, Mark

Hi Mark: I'm using el7 as a coverall for several near-clones of RedHat
Enterprise Linux. The box itself is on Scientific Linux 7.7 but also
uses the EPEL and rpmfusion repos, while the build is done under F30
using Gary B's rpm script, using CentOS instead of SL, and with libvpx
disabled because it clashes with the version needed by the KDE-plasma
desktop.

Kernel is Linux 4.4.200-1.el7.elrepo.x86_64, to get better tuner support.

Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
OpenGL/ES version 1.4 Mesa 18.3.4

Usually it's stable, but gurus wring their hands...

Currently the frontend setup uses:

Advanced Playback Settings: realtime priority ticked, Audio read ahead
100 ms, Enable AVSync2 at default 10 ms

Current Video Playback Profile: Normal, Decoder Standard, Max CPUs 2,
Blocking filter enabled, renderer opengl, Deinterlacers both HQ with
boxes unticked, no custom filters.

Last night I recorded a lecture by Tim Berners-Lee on the future of the
Web. It seems to have been badly affected. Ironic grin.

Thanks,

John



_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 18/11/2019 11:58, Mark Kendall wrote:
> On Mon, 18 Nov 2019 at 11:47, John Pilkington <johnpilk222@gmail.com> wrote:
>> I'm still getting loss of a/v sync in my el7 box, more noticeable in
>> some recordings than others, but the fedora 30 system built at the same
>> commit has not yet done the same, using either NVdec or ffmpeg decoding.
>
> I'm assuming el7 is enterprise linux 7?
>
> What decoder/playback settings is that box using?
>
> Thanks, Mark

My original reply to this revealed many opportunities for system
misalignments that might be causing this drift, and I won't repeat them.

But here are lines from frontend startup and closedown that look as if
they are system specific and could perhaps underlie a slow drift if all
the digits are significant and the usage isn't quite right.

{{{

2019-11-23 11:35:57.867339 I DispResX: Created
2019-11-23 11:35:57.867956 N DispRes: Desktop video mode: 1440x900
74.984 Hz

2019-11-23 11:49:27.987070 I DispRes: Changing to 1440x900 75.000 Hz
2019-11-23 11:49:28.013150 I DispRes: SwitchToGUI: Switched to 1440x900
75.000 Hz

}}}

xrandr offers 59.89 + 74.98* at that (full) resolution of the only
attached screen; I'm using a 1024x576 window

The Std.Devs shown here look (unfeasibly?) large, and sync was very bad
while getting them. The CPUs look busy. BBC Four SD. Playback is fine
apart from the sync issue, and via DLNA on the TV it's excellent.

{{{
2019-11-23 12:11:19.873565 I Player(0): FPS: 25.88 Mean: 38642
Std.Dev: 28904 CPUs: 101% 101%
2019-11-23 12:11:20.890110 I Player(0): FPS: 24.60 Mean: 40647
Std.Dev: 25888 CPUs: 98% 97%
2019-11-23 12:11:21.903609 I Player(0): FPS: 24.67 Mean: 40528
Std.Dev: 26322 CPUs: 104% 97%
2019-11-23 12:11:22.894285 I Player(0): FPS: 25.24 Mean: 39615
Std.Dev: 25965 CPUs: 103% 102%

}}}

Cheers,

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 23/11/2019 12:31, John Pilkington wrote:
> On 18/11/2019 11:58, Mark Kendall wrote:
>> On Mon, 18 Nov 2019 at 11:47, John Pilkington <johnpilk222@gmail.com>
>> wrote:
>>> I'm still getting loss of a/v sync in my el7 box, more noticeable in
>>> some recordings than others, but the fedora 30 system built at the same
>>> commit has not yet done the same, using either NVdec or ffmpeg decoding.
>>
>> I'm assuming el7 is enterprise linux 7?
>>
>> What decoder/playback settings is that box using?
>>
>> Thanks, Mark
>
> My original reply to this revealed many opportunities for system
> misalignments that might be causing this drift, and I won't repeat them.
>
> But here are lines from frontend startup and closedown that look as if
> they are system specific and could perhaps underlie a slow drift if all
> the digits are significant and the usage isn't quite right.
>
> {{{
>
> 2019-11-23 11:35:57.867339 I  DispResX: Created
> 2019-11-23 11:35:57.867956 N  DispRes: Desktop video mode: 1440x900
> 74.984 Hz
>
> 2019-11-23 11:49:27.987070 I  DispRes: Changing to 1440x900 75.000 Hz
> 2019-11-23 11:49:28.013150 I  DispRes: SwitchToGUI: Switched to 1440x900
> 75.000 Hz
>
> }}}
>
> xrandr offers 59.89 +  74.98* at that (full) resolution of the only
> attached screen; I'm using a 1024x576 window
>
> The Std.Devs shown here look (unfeasibly?) large, and sync was very bad
> while getting them.  The CPUs look busy.  BBC Four SD.  Playback is fine
> apart from the sync issue, and via DLNA on the TV it's excellent.
>
> {{{
> 2019-11-23 12:11:19.873565 I  Player(0): FPS:   25.88 Mean: 38642
> Std.Dev: 28904 CPUs: 101% 101%
> 2019-11-23 12:11:20.890110 I  Player(0): FPS:   24.60 Mean: 40647
> Std.Dev: 25888 CPUs: 98% 97%
> 2019-11-23 12:11:21.903609 I  Player(0): FPS:   24.67 Mean: 40528
> Std.Dev: 26322 CPUs: 104% 97%
> 2019-11-23 12:11:22.894285 I  Player(0): FPS:   25.24 Mean: 39615
> Std.Dev: 25965 CPUs: 103% 102%
>
> }}}

Here, FWIW, are the corresponding lines for the F30 box, which has an
nVidia card driving a VGA monitor and an HDMI TV, using a single image
surface; again, on the monitor mythTV is using a 1024x576 window.

{{{
2019-11-24 14:37:47.305471 I DispResX: Created
2019-11-24 14:37:47.306061 N DispRes: Desktop video mode: 3600x1080
50.000 Hz
============
2019-11-24 14:38:13.380206 I DispRes: Changing to 3600x1080 nan Hz
2019-11-24 14:38:13.380213 E DispResX: Desired resolution and frame
rate not found.
2019-11-24 14:38:13.380223 E DispRes: SwitchToGUI: xrandr failed for
3600x1080 50.000 Hz
2019-11-24 14:38:13.380234 I DispResX: Deleted

Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 16384 x 16384
VGA-0 connected primary 1680x1050+0+0 (normal left inverted right x axis
y axis) 433mm x 271mm
1680x1050 59.95*+

HDMI-0 connected 1920x1080+1680+0 (normal left inverted right x axis y
axis) 698mm x 392mm
1920x1080 50.00*+ 60.00 59.94 23.98 60.05 60.00
50.04

}}}

I haven't noticed drift on either of those F30 screens, but won't say it
definitely isn't there. After a 1-hour uninterrupted playback in el7, I
got normal sync with a 3200 ms applied offset. Right ballpark...

Both running c794391ad

>
> Cheers,
>
> John
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

To continue...

I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
monitor, again running c794391ad. The only recordings at present are
from assorted iptv channels, but they show no obvious a/v drift.

The DispRes: Desktop video mode on frontend startup and the DispRes:
SwitchToGUI on exit are both clean 1920x1080 60.000 Hz

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 24/11/2019 22:41, John Pilkington wrote:
> To continue...
>
> I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
> monitor, again running c794391ad. The only recordings at present are
> from assorted iptv channels, but they show no obvious a/v drift.
>
> The DispRes: Desktop video mode on frontend startup and the DispRes:
> SwitchToGUI on exit are both clean 1920x1080 60.000 Hz

I commented earlier on the size of the timing StdDev shown in the
terminal log when the Playback Data OSD is active. It was around 25 ms,
with a frame interval of 40 ms. The SD appears to track the correction
increment set for AVSync2, which suggests that a correction is being
applied on every frame. I had 30 ms, and now have 2 ms. There is still
a drift, though.
>
> John

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

John

Apologies for the delay - I've been away with the fairies for a few days:)

Can you please post full logs for the working and non-working cases?
The snippets are useful but I need the 101 other pointers that the
logs might give.

Given the nature of the problem, I'd suggest with '-v playback,gpu
--loglevel=debug' logging.

If you want to go 'hardcore' as well then add timestamp and audio
options - though the logs will be fairly lengthy:)

thanks and regards
Mark

On Mon, 25 Nov 2019 at 23:57, John Pilkington <johnpilk222@gmail.com> wrote:
>
> On 24/11/2019 22:41, John Pilkington wrote:
> > To continue...
> >
> > I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
> > monitor, again running c794391ad. The only recordings at present are
> > from assorted iptv channels, but they show no obvious a/v drift.
> >
> > The DispRes: Desktop video mode on frontend startup and the DispRes:
> > SwitchToGUI on exit are both clean 1920x1080 60.000 Hz
>
> I commented earlier on the size of the timing StdDev shown in the
> terminal log when the Playback Data OSD is active. It was around 25 ms,
> with a frame interval of 40 ms. The SD appears to track the correction
> increment set for AVSync2, which suggests that a correction is being
> applied on every frame. I had 30 ms, and now have 2 ms. There is still
> a drift, though.
> >
> > John
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 26/11/2019 08:56, Mark Kendall wrote:
> John
>
> Apologies for the delay - I've been away with the fairies for a few days:)
>
> Can you please post full logs for the working and non-working cases?
> The snippets are useful but I need the 101 other pointers that the
> logs might give.
>
> Given the nature of the problem, I'd suggest with '-v playback,gpu
> --loglevel=debug' logging.
>
> If you want to go 'hardcore' as well then add timestamp and audio
> options - though the logs will be fairly lengthy:)
>
> thanks and regards
> Mark
>
> On Mon, 25 Nov 2019 at 23:57, John Pilkington <johnpilk222@gmail.com> wrote:
>>
>> On 24/11/2019 22:41, John Pilkington wrote:
>>> To continue...
>>>
>>> I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
>>> monitor, again running c794391ad. The only recordings at present are
>>> from assorted iptv channels, but they show no obvious a/v drift.
>>>
>>> The DispRes: Desktop video mode on frontend startup and the DispRes:
>>> SwitchToGUI on exit are both clean 1920x1080 60.000 Hz
>>
>> I commented earlier on the size of the timing StdDev shown in the
>> terminal log when the Playback Data OSD is active. It was around 25 ms,
>> with a frame interval of 40 ms. The SD appears to track the correction
>> increment set for AVSync2, which suggests that a correction is being
>> applied on every frame. I had 30 ms, and now have 2 ms. There is still
>> a drift, though.
>>>
>>> John

The recording has been through my usual demux by Project-x and remux by
mplex process, which has delivered good sync over seveal years. It has
speech to camera and shows the problem.

AVSync2 2 ms, Standard decode, 2 cpus, OpenGL, HQ deinterlace, no ticks

mythfrontend -v playback,gpu --loglevel=debug | tee lipsync.log

https://drive.google.com/open?id=1llzEU9b37okqiiNSNvm-JCuOrKZCOKqD

HTH
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

John

Is that the correct link? It's an android log...:)

On Tue, 26 Nov 2019 at 10:44, John Pilkington <johnpilk222@gmail.com> wrote:
>
> On 26/11/2019 08:56, Mark Kendall wrote:
> > John
> >
> > Apologies for the delay - I've been away with the fairies for a few days:)
> >
> > Can you please post full logs for the working and non-working cases?
> > The snippets are useful but I need the 101 other pointers that the
> > logs might give.
> >
> > Given the nature of the problem, I'd suggest with '-v playback,gpu
> > --loglevel=debug' logging.
> >
> > If you want to go 'hardcore' as well then add timestamp and audio
> > options - though the logs will be fairly lengthy:)
> >
> > thanks and regards
> > Mark
> >
> > On Mon, 25 Nov 2019 at 23:57, John Pilkington <johnpilk222@gmail.com> wrote:
> >>
> >> On 24/11/2019 22:41, John Pilkington wrote:
> >>> To continue...
> >>>
> >>> I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
> >>> monitor, again running c794391ad. The only recordings at present are
> >>> from assorted iptv channels, but they show no obvious a/v drift.
> >>>
> >>> The DispRes: Desktop video mode on frontend startup and the DispRes:
> >>> SwitchToGUI on exit are both clean 1920x1080 60.000 Hz
> >>
> >> I commented earlier on the size of the timing StdDev shown in the
> >> terminal log when the Playback Data OSD is active. It was around 25 ms,
> >> with a frame interval of 40 ms. The SD appears to track the correction
> >> increment set for AVSync2, which suggests that a correction is being
> >> applied on every frame. I had 30 ms, and now have 2 ms. There is still
> >> a drift, though.
> >>>
> >>> John
>
> The recording has been through my usual demux by Project-x and remux by
> mplex process, which has delivered good sync over seveal years. It has
> speech to camera and shows the problem.
>
> AVSync2 2 ms, Standard decode, 2 cpus, OpenGL, HQ deinterlace, no ticks
>
> mythfrontend -v playback,gpu --loglevel=debug | tee lipsync.log
>
> https://drive.google.com/open?id=1llzEU9b37okqiiNSNvm-JCuOrKZCOKqD
>
> HTH
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 26/11/2019 10:49, Mark Kendall wrote:
> John
>
> Is that the correct link? It's an android log...:)

Sorry:

https://drive.google.com/open?id=1-DFDeRMEfxq5wzY8mIjOMat2Og56b1nF
>
> On Tue, 26 Nov 2019 at 10:44, John Pilkington <johnpilk222@gmail.com> wrote:
>>
>> On 26/11/2019 08:56, Mark Kendall wrote:
>>> John
>>>
>>> Apologies for the delay - I've been away with the fairies for a few days:)
>>>
>>> Can you please post full logs for the working and non-working cases?
>>> The snippets are useful but I need the 101 other pointers that the
>>> logs might give.
>>>
>>> Given the nature of the problem, I'd suggest with '-v playback,gpu
>>> --loglevel=debug' logging.
>>>
>>> If you want to go 'hardcore' as well then add timestamp and audio
>>> options - though the logs will be fairly lengthy:)
>>>
>>> thanks and regards
>>> Mark
>>>
>>> On Mon, 25 Nov 2019 at 23:57, John Pilkington <johnpilk222@gmail.com> wrote:
>>>>
>>>> On 24/11/2019 22:41, John Pilkington wrote:
>>>>> To continue...
>>>>>
>>>>> I have a 'new' F30 box, i3 4-core with nVidia and a single VGA-driven
>>>>> monitor, again running c794391ad. The only recordings at present are
>>>>> from assorted iptv channels, but they show no obvious a/v drift.
>>>>>
>>>>> The DispRes: Desktop video mode on frontend startup and the DispRes:
>>>>> SwitchToGUI on exit are both clean 1920x1080 60.000 Hz
>>>>
>>>> I commented earlier on the size of the timing StdDev shown in the
>>>> terminal log when the Playback Data OSD is active. It was around 25 ms,
>>>> with a frame interval of 40 ms. The SD appears to track the correction
>>>> increment set for AVSync2, which suggests that a correction is being
>>>> applied on every frame. I had 30 ms, and now have 2 ms. There is still
>>>> a drift, though.
>>>>>
>>>>> John
>>
>> The recording has been through my usual demux by Project-x and remux by
>> mplex process, which has delivered good sync over seveal years. It has
>> speech to camera and shows the problem.
>>
>> AVSync2 2 ms, Standard decode, 2 cpus, OpenGL, HQ deinterlace, no ticks
>>
>> mythfrontend -v playback,gpu --loglevel=debug | tee lipsync.log
>>
>> see above for the right link
>>
>> HTH
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

I'm still seeing this slow drift in my el7 build of mythfrontend
version: devel/2019-render [v31-Pre-9dc72f3b810] www.mythtv.org

and it seems likely to be connected to
mythtv/libs/libmythui/DisplayResX.cpp tweaks at commit b8e27f1039 - and
perhaps the reported lack of NVCtrl on this system.

$ mythfrontend -v playback,libav

2019-11-27 13:40:22.479018 I DispResX: Created
2019-11-27 13:40:22.479852 N DispRes: Desktop video mode: 1440x900
74.984 Hz
.......
2019-11-27 13:40:27.454064 I DispResX: Raw/unsorted XRANDR modes:
2019-11-27 13:40:27.454090 I 1440x900 75.00 60.00
2019-11-27 13:40:27.454106 I 1280x1024 75.00 60.00
2019-11-27 13:40:27.454119 I 1280x960 60.00
2019-11-27 13:40:27.454132 I 1152x864 75.00
......

2019-11-27 13:40:27.454312 I NVCtrl: The NV-CONTROL X extension is not
available on screen 0 of ''
......
and on frontend closedown

2019-11-27 14:09:28.060362 I DispRes: Changing to 1440x900 75.000 Hz
2019-11-27 14:09:28.094487 I DispRes: SwitchToGUI: Switched to 1440x900
75.000 Hz
2019-11-27 14:09:28.094498 I DispResX: Deleted

$ xrandr
Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767
VGA1 connected primary 1440x900+0+0 (normal left inverted right x axis y
axis) 410mm x 260mm
1440x900 59.89 + 74.98*

=====

In contrast, a build for Fedora 30 at the same commit, with nVidia
graphics, shows DispResX rates that are the same as those from xrandr;
not, as above, truncated to the nearest integer. It also shows
CustomRate: to 4 decimal places.

This is probably not a blocker. DLNA doesn't show the drift. I
haven't yet found a logging option that does.

HTH

John P






_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

John

Are you using display resolution switching?

I've just noticed an issue with the display resolution changes I
pushed last week where it is creating/using display resolution
handling classes when it shouldn't be.

But I think your issues pre-date those commits??

I'll push a fix tomorrow.

Thanks for the perseverance:)
regards
Mark

On Wed, 27 Nov 2019 at 16:15, John Pilkington <johnpilk222@gmail.com> wrote:
>
> I'm still seeing this slow drift in my el7 build of mythfrontend
> version: devel/2019-render [v31-Pre-9dc72f3b810] www.mythtv.org
>
> and it seems likely to be connected to
> mythtv/libs/libmythui/DisplayResX.cpp tweaks at commit b8e27f1039 - and
> perhaps the reported lack of NVCtrl on this system.
>
> $ mythfrontend -v playback,libav
>
> 2019-11-27 13:40:22.479018 I DispResX: Created
> 2019-11-27 13:40:22.479852 N DispRes: Desktop video mode: 1440x900
> 74.984 Hz
> .......
> 2019-11-27 13:40:27.454064 I DispResX: Raw/unsorted XRANDR modes:
> 2019-11-27 13:40:27.454090 I 1440x900 75.00 60.00
> 2019-11-27 13:40:27.454106 I 1280x1024 75.00 60.00
> 2019-11-27 13:40:27.454119 I 1280x960 60.00
> 2019-11-27 13:40:27.454132 I 1152x864 75.00
> ......
>
> 2019-11-27 13:40:27.454312 I NVCtrl: The NV-CONTROL X extension is not
> available on screen 0 of ''
> ......
> and on frontend closedown
>
> 2019-11-27 14:09:28.060362 I DispRes: Changing to 1440x900 75.000 Hz
> 2019-11-27 14:09:28.094487 I DispRes: SwitchToGUI: Switched to 1440x900
> 75.000 Hz
> 2019-11-27 14:09:28.094498 I DispResX: Deleted
>
> $ xrandr
> Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767
> VGA1 connected primary 1440x900+0+0 (normal left inverted right x axis y
> axis) 410mm x 260mm
> 1440x900 59.89 + 74.98*
>
> =====
>
> In contrast, a build for Fedora 30 at the same commit, with nVidia
> graphics, shows DispResX rates that are the same as those from xrandr;
> not, as above, truncated to the nearest integer. It also shows
> CustomRate: to 4 decimal places.
>
> This is probably not a blocker. DLNA doesn't show the drift. I
> haven't yet found a logging option that does.
>
> HTH
>
> John P
>
>
>
>
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 27/11/2019 18:47, Mark Kendall wrote:
> John
>
> Are you using display resolution switching?

Not aware of it; only the use of a window. But I'm wondering about the
NVCtrl thing. libXNVctrl is installed but "not available on screen ''",
and I just added nvidia-settings, but no difference seen. I think
that's where the other box finds the precision rates, and maybe audio
uses one and video, deep in the works, another.
>
> I've just noticed an issue with the display resolution changes I
> pushed last week where it is creating/using display resolution
> handling classes when it shouldn't be.
>
> But I think your issues pre-date those commits??
>
> I'll push a fix tomorrow.
>
> Thanks for the perseverance:)

Thanks for the effort!

> regards
> Mark
>
> On Wed, 27 Nov 2019 at 16:15, John Pilkington <johnpilk222@gmail.com> wrote:
>>
>> I'm still seeing this slow drift in my el7 build of mythfrontend
>> version: devel/2019-render [v31-Pre-9dc72f3b810] www.mythtv.org
>>
>> and it seems likely to be connected to
>> mythtv/libs/libmythui/DisplayResX.cpp tweaks at commit b8e27f1039 - and
>> perhaps the reported lack of NVCtrl on this system.
>>
>> $ mythfrontend -v playback,libav
>>
>> 2019-11-27 13:40:22.479018 I DispResX: Created
>> 2019-11-27 13:40:22.479852 N DispRes: Desktop video mode: 1440x900
>> 74.984 Hz
>> .......
>> 2019-11-27 13:40:27.454064 I DispResX: Raw/unsorted XRANDR modes:
>> 2019-11-27 13:40:27.454090 I 1440x900 75.00 60.00
>> 2019-11-27 13:40:27.454106 I 1280x1024 75.00 60.00
>> 2019-11-27 13:40:27.454119 I 1280x960 60.00
>> 2019-11-27 13:40:27.454132 I 1152x864 75.00
>> ......
>>
>> 2019-11-27 13:40:27.454312 I NVCtrl: The NV-CONTROL X extension is not
>> available on screen 0 of ''
>> ......
>> and on frontend closedown
>>
>> 2019-11-27 14:09:28.060362 I DispRes: Changing to 1440x900 75.000 Hz
>> 2019-11-27 14:09:28.094487 I DispRes: SwitchToGUI: Switched to 1440x900
>> 75.000 Hz
>> 2019-11-27 14:09:28.094498 I DispResX: Deleted
>>
>> $ xrandr
>> Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767
>> VGA1 connected primary 1440x900+0+0 (normal left inverted right x axis y
>> axis) 410mm x 260mm
>> 1440x900 59.89 + 74.98*
>>
>> =====
>>
>> In contrast, a build for Fedora 30 at the same commit, with nVidia
>> graphics, shows DispResX rates that are the same as those from xrandr;
>> not, as above, truncated to the nearest integer. It also shows
>> CustomRate: to 4 decimal places.
>>
>> This is probably not a blocker. DLNA doesn't show the drift. I
>> haven't yet found a logging option that does.
>>
>> HTH
>>
>> John P
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org