[mythtv-users] Guidance for phase 9
digitalaudiorock at gmail.com
Mon Aug 19 13:33:21 UTC 2019
On 8/19/19, Tom Dexter <digitalaudiorock at gmail.com> wrote:
> On 8/18/19, Allen Edwards <allen.p.edwards at gmail.com> wrote:
>> On Sun, Aug 18, 2019 at 1:11 PM Tom Dexter <digitalaudiorock at gmail.com>
>>> You can quickly find out if you have those bindings by just
>>> downloading that script and trying it. You can give it execute
>>> permissions with:
>>> chmod a+x mythtv-us-atsc-add-channel
>>> Then you can try this:
>>> ./mythtv-us-atsc-add-channel -h
>>> If you get the help text you're fine...otherwise you'll get this:
>>> Can't locate MythTV.pm in @INC (you may need to install the MythTV
>>> module)...etc etc
>>> If you don't have the bindings let me know...I've actually already
>>> made a version without that that has the database, user, and password
>>> directly in the script where you have to edit them in the script.
>>> If anyone's interested, I've attached another utility that to add a
>>> new ATSC channel that's worked well for me. Note that it can't add new
>>> frequencies, however you can do that with my first script using the -c
>> Thanks Tom
>> I get the help file with both ./mythtv-us-atsc-add-channel -h and
>> ./mythtv-us-atsc-freq-check -h so I guess all is good.
>> Now which one do I use to do the rescan? I thought it was freq-check but
>> then you sent the add-channel code and told me to use that.
> The only one you need for the rescan (changing existing frequencies)
> is the mythtv-us-atsc-freq-check. The only use anyone might have for
> the other is if you notice when scanning with hdhomerun_config that a
> transport now has a new channel you don't have at all.
Oh man...now I see why there was confusion there. In my examples as
far as testing for the perl bindings I meant to use
mythtv-us-atsc-freq-check and accidentally used the add channel script
instead. Sorry for the confusion.
More information about the mythtv-users