[prev in list] [next in list] [prev in thread] [next in thread]
List: mythtv-dev
Subject: Re: [mythtv] render2019 comments
From: Tim Pletcher <pletchtd () gmail ! com>
Date: 2019-10-22 22:10:14
Message-ID: CABBGYbHt4DruFED_rtQHPdXyU515oBuUnYxO2ggdpHRto6iRmg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, Oct 22, 2019 at 8:38 AM Mark Kendall <mark.kendall@gmail.com> wrote:
> On Tue, 22 Oct 2019 at 00:27, Tim Pletcher <pletchtd@gmail.com> wrote:
> >
> > I just gave the 2019-render branch (devel/2019-render
> v31-Pre-1095-gc7eabdaf86) a try on one of my frontend machines. The
> frontend is home-built Apollo Lake Celeron J3455 system running Xubuntu
> 18.04 with Vaapi version 1.10. The frontend is used almost exclusively for
> viewing NTSC LiveTV and the output is configured for a 1920x1080@59.94
> modeline. The frontend is configured with a VAAPI2 profile with Vaapi
> acceleration and opengl-hw High quality deinterlacing.
> >
> > Everything works great with the exception of one issue:
> > On 1920x1080i channels where deinterlacing is in use, any overlaid info
> flickers in the overlaid section in the top 1/4 or of the screen (see video
> here: https://youtu.be/PXospaUX1lo). The same flickering behavior is also
> observed if viewing a 1920x1080i@30fps recording so this doesn't appear
> unique to LiveTV. The overlay flickering is not present in any
> circumstance when viewing 1280x720@60 content where deinterlacing is not
> in use.
> >
> > To compare, I also tried the render branch on another machine with an
> Nvidia card (GT 1030 / driver version 390.116). Using VDPAU acceleration
> and opengl-hw deinterlacing on this frontend, the overlay flickering is not
> present with either interlaced or progressive content.
> >
> > Any hints on why I might be experiencing this with VAAPI acceleration on
> my Apollo Lake machine?
>
> Tim,
>
> Thanks for the video. Very helpful - though a curious issue.
>
> This can only be a performance problem as the OSD is the last thing to
> be displayed - certainly not a vsync problem as the video is fine. As
> a sanity check can you possibly produce a log with "-v
> playback,gpu,gpuvideo" logging.
>
> Also worth going into the detail of the display profile page, if you
> haven't done so already, and ensuring that you have everything setup
> properly - as previously mentioned, the display profiles aren't
> currently migrated completely. You'll need VAAPI acceleration then try
> setting deinterlacers to high quality and enabling both shaders and
> driver deints. If you still see the issue, try dropping the quality of
> the deinterlacers.
>
> Furthermore, again if you haven't tried it already, try to force EGL
> from the command line - which gives much better VAAPI performance.
> Something like:
>
> QT_XCB_GL_INTEGRATION="xcb_egl" mythfrontend -v playback
>
> I'm not sure how powerful that GPU is or what features it supports -
> so it may be falling back to some basic VAAPI deinterlacing or OpenGL
> shaders. Logs would confirm - or alternatively if you try a different
> theme (e.g. MythCentre-wide) it will show which deinterlacer is in use
> in the Debug OSD screen.
>
> All that said, on reflection I think this is an OpenGL flushing issue.
> Flushing is currently disabled - I'll add it back by default. I'm
> pretty sure that will fix the problem.
>
> Hi Mark,
Thank you for your response.
I tried the command you suggested to force EGL
(QT_XCB_GL_INTEGRATION="xcb_egl" mythfrontend) and that fixed the issue
entirely!
I also grabbed a couple of frontend logs with the suggested "-v
playback,gpu,gpuvideo" options and posted them here:
https://gist.github.com/pletch/eba2c199441604539b8627abdc48e219
Two logs are posted there with the first being a log captured with the EGL
force command line option on (no flickering) and a second without this
option (flickering present).
I'll use the force EGL option by default going forward.
Regards,
Tim
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr">On Tue, Oct 22, 2019 at 8:38 AM Mark Kendall <<a \
href="mailto:mark.kendall@gmail.com">mark.kendall@gmail.com</a>> \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On Tue, 22 Oct 2019 at 00:27, Tim Pletcher <<a \
href="mailto:pletchtd@gmail.com" target="_blank">pletchtd@gmail.com</a>> \
wrote:<br> ><br>
> I just gave the 2019-render branch (devel/2019-render v31-Pre-1095-gc7eabdaf86) \
a try on one of my frontend machines. The frontend is home-built Apollo Lake \
Celeron J3455 system running Xubuntu 18.04 with Vaapi version 1.10. The frontend is \
used almost exclusively for viewing NTSC LiveTV and the output is configured for a \
1920x1080@59.94 modeline. The frontend is configured with a VAAPI2 profile with \
Vaapi acceleration and opengl-hw High quality deinterlacing.<br> ><br>
> Everything works great with the exception of one issue:<br>
> On 1920x1080i channels where deinterlacing is in use, any overlaid info flickers \
in the overlaid section in the top 1/4 or of the screen (see video here: <a \
href="https://youtu.be/PXospaUX1lo" rel="noreferrer" \
target="_blank">https://youtu.be/PXospaUX1lo</a>). The same flickering behavior is \
also observed if viewing a 1920x1080i@30fps recording so this doesn't appear \
unique to LiveTV. The overlay flickering is not present in any circumstance when \
viewing 1280x720@60 content where deinterlacing is not in use.<br> ><br>
> To compare, I also tried the render branch on another machine with an Nvidia \
card (GT 1030 / driver version 390.116). Using VDPAU acceleration and opengl-hw \
deinterlacing on this frontend, the overlay flickering is not present with either \
interlaced or progressive content.<br> ><br>
> Any hints on why I might be experiencing this with VAAPI acceleration on my \
Apollo Lake machine?<br> <br>
Tim,<br>
<br>
Thanks for the video. Very helpful - though a curious issue.<br>
<br>
This can only be a performance problem as the OSD is the last thing to<br>
be displayed - certainly not a vsync problem as the video is fine. As<br>
a sanity check can you possibly produce a log with "-v<br>
playback,gpu,gpuvideo" logging.<br>
<br>
Also worth going into the detail of the display profile page, if you<br>
haven't done so already, and ensuring that you have everything setup<br>
properly - as previously mentioned, the display profiles aren't<br>
currently migrated completely. You'll need VAAPI acceleration then try<br>
setting deinterlacers to high quality and enabling both shaders and<br>
driver deints. If you still see the issue, try dropping the quality of<br>
the deinterlacers.<br>
<br>
Furthermore, again if you haven't tried it already, try to force EGL<br>
from the command line - which gives much better VAAPI performance.<br>
Something like:<br>
<br>
QT_XCB_GL_INTEGRATION="xcb_egl" mythfrontend -v playback<br>
<br>
I'm not sure how powerful that GPU is or what features it supports -<br>
so it may be falling back to some basic VAAPI deinterlacing or OpenGL<br>
shaders. Logs would confirm - or alternatively if you try a different<br>
theme (e.g. MythCentre-wide) it will show which deinterlacer is in use<br>
in the Debug OSD screen.<br>
<br>
All that said, on reflection I think this is an OpenGL flushing issue.<br>
Flushing is currently disabled - I'll add it back by default. I'm<br>
pretty sure that will fix the problem.<br><br></blockquote><div>Hi \
Mark,</div><div><br></div><div>Thank you for your \
response.</div><div><br></div><div>I tried the command you suggested to force EGL \
(QT_XCB_GL_INTEGRATION="xcb_egl" mythfrontend) and that fixed the issue \
entirely! </div><div><br></div><div>I also grabbed a couple of frontend logs with \
the suggested "-v playback,gpu,gpuvideo" options and posted them \
here:</div><div> <a \
href="https://gist.github.com/pletch/eba2c199441604539b8627abdc48e219">https://gist.github.com/pletch/eba2c199441604539b8627abdc48e219</a><br></div><div>Two \
logs are posted there with the first being a log captured with the EGL force command \
line option on (no flickering) and a second without this option (flickering present). \
<br></div><div><br></div><div>I'll use the force EGL option by default going \
forward. </div><div><br></div><div>Regards,</div><div>Tim</div></div></div>
_______________________________________________
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic