[mythtv-users] HD Hiomerun works better in HDHomeRun viewer than MythTV
dlbrett at zoominternet.net
Fri Jan 25 17:17:48 UTC 2019
On 1/24/2019 6:58 PM, Peter Bennett wrote:
> On 1/24/19 6:52 PM, Jay Foster wrote:
>> On 1/24/2019 3:46 PM, Don Brett wrote:
>>> On 1/3/2019 1:42 PM, Gary Buhrmaster wrote:
>>>> On Thu, Jan 3, 2019 at 2:39 PM Don Brett <dlbrett at zoominternet.net>
>>>>> Thanks Gary; network questions and dropped packets seem to be the
>>>>> consensus so far. I tried the network test from the Silicon Dust
>>>>> thread; it worked perfectly, with zero errors. I assume
>>>>> hdhomerun_config is using TCP.
>>>> Nope, hdhomerun_config uses UDP, just like MythTV.
>>>> But it is *critcal* to run the test on the same system
>>>> as the MythTV BE. There are many issues with some
>>>> system(s) and their hardware and/or drivers and/or
>>>> configuration of the IP stack that can be a contributing
>>> Not sure why this test didn't work before, but it does now. I
>>> verified the pixelation was happening in myth, then ran the test on
>>> that same RF channel, directly on the be/fe box, for 104 minutes.
>>> Results are:
>>> don at nick:~$ hdhomerun_config FFFFFFFF set /tuner0/channel auto:36
>>> don at nick:~$ hdhomerun_config FFFFFFFF save /tuner0 null
>>> .........several row of dots..........
>>> -- Video statistics --
>>> 11,480,828 packets received, 0 overflow errors, 0 network errors, 0
>>> transport errors, 0 sequence errors.
>>> It looks like the test received over 11 million packets, with no
>>> errors. I'm not sure what this means....same hardware, same OS,
>>> same TCP stack...what's next?
>>> PS - Transmitter info is below; I've noticed that TV channel 21 is
>>> less bad than 27 and 33. I located my attenuator. I'll install it
>>> and see what happens.
>>> The local channels are 21, 27, and 33
>>> Distance Heading RF channel TV channel
>>> 4 mi 351 deg auto:20 21.1
>>> 4 mi 351 deg auto:20 21.2
>>> 2 mi 353 deg auto:36 27.1
>>> 2 mi 353 deg auto:36 27.2
>>> 2 mi 353 deg auto:36 33.1
>>> 2 mi 353 deg auto:36 33.2
>>> This email has been checked for viruses by Avast antivirus software.
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> MythTV Forums: https://forum.mythtv.org
>> Are you using software decode or hardware decode (VDPAU, VAAPI) in
>> MythTV? Note the decode option can be configured differently from
>> the rendering option (also software or hardware (VDPAU, VAAPI)).
> There is a bug with VDPAU rendering. Certain channels in the USA are
> using MPEG2 in a way that overloads VDPAU and causes pixellation every
> few seconds. This is nothing to do with HDHomerun, it happens with any
> type of equipment. The solution is to change to software decode and
> OpenGL Rendering for mpeg2 streams. If you are not using VDPAU ignore
> this email.
> mythtv-users mailing list
> mythtv-users at mythtv.org
> MythTV Forums: https://forum.mythtv.org
Sounds like we might be on-to something here, but I'm a bit confused on
Mythfrontend > Setup > Video > Playback (3/8):
-Current video playback profile = VDPAU Hight Quality
-if rez > 0 0 -> vdpau & vdpau
, then click on vdpau & vdpau "Edit" button
Match criteria: >
Match criteria: blank field
Decoder: Nvidia VDPAU acceleration
Video renderer: vdpau
OSD renderer: vdpau
Primary deinterlacer: None
Fallback deinterlacer: None
Custom filters: vdpaucolorspace=auto
Video renderer and OSD renderer only offers vdpau, unless I change the
Decoder. The decoder offers:
-Nvidia VDPAU acceleration
, then renderer options follow the selected decoder. Any suggestions on
what to pick?
Video hardware = GK208 [GeForce GT 730]
Nvidia driver version = 390.87
More information about the mythtv-users