[mythtv-users] Indoor HD antenna question

[Stephen Worthington]

On Fri, 13 Apr 2018 20:32:52 +0000, you wrote:

>On Fri, Apr 13, 2018 at 2:16 PM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Fri, 13 Apr 2018 17:17:34 +0000, you wrote:
>>
>> >Seems that the driver doesn't seem to load - or that's what I am getting
>> >when I look in the dmesg.
>>
>> There is some confusion going on here.  MythTV is saying that
>> /dev/dvb/adapter0 is an "Air2PC v2" tuner, which is a USB ATSC tuner.
>> But the full dmesg does not show any sign of such a tuner.  Instead,
>> it shows messages that would be expected for a Avermedia AverTVHD
>> card.  But that card is not documented as being an ATSC tuner.  So I
>> have to guess that the Avermedia AverTVHD card that you have is
>> actually a variant of the card manufactured for the US market that
>> does ATSC instead of DVB-T.
>
>
>That would be strange but have seen stranger things - the reason I say that
>is because I used to use this card before Xfinity/Comcast started
>encrypting their channels here. For years I used this card to record my
>shows. So the card worked fine, I just stopped using that. Also, I haven't
>upgraded my myth - it's  still running on 0.27. So I guess I am surprised
>that without any changes, the drivers/cards stopped being compatible. But I
>guess it can happen...

This is not an incompatibility between MythTV and the tuners, as far
as I can tell.  The errors in the log come from an incompatibility
between the kernel and the V4L drivers for your card.  So has the
kernel been upgraded, even if MythTV has not?

>  Somehow MythTV seems to be giving the
>> card the "Air2PC v2" name instead of the correct name.  I do not know
>> where MythTV gets those names, so that is possible, but I would have
>> expected that it got the name from the hardware or drivers somehow, so
>> it is a worry that it has the wrong name.

If you were using the same card with the same version of MythTV and it
was working, the name showing in MythTV should not matter.  But was it
showing that name back when it was working?

>It also shows other stuff under dvb - here's what I get:
>
>ls /dev/dvb/adapter0/
>demux0  dvr0  frontend0  net0
>
>"dvr0" wouldn't be one of them?

The "demux0  dvr0  frontend0  net0" devices are all correct for a
normal DVB or ATSC tuner.  What we are not sure of now is if they all
work correctly.  Trying the "scan" command should tell us whether the
tuner works at a basic level, and then if that works, once scan has
created a channels.conf file, that can be used with an "azap -r
<channel name>" command to tune the tuner to one channel and make that
play on the /dev/dvb/adapter0/dvr0 device.  You leave azap running and
in another command prompt run a command line player program like
mplayer to play from the dvr0 device:

mplayer /dev/dvb/adapter0/dvr0

Mplayer should pop up a window and play the channel.  It will also log
to the console to show what is happening, and tell us what went wrong
if it can not play the channel.