[mythtv] [mythtv-commits] mythtv commit: r9482 by danielk

[Kevin Kuphal]

Daniel Kristjansson wrote:
> On Sun, 2006-03-26 at 17:19 -0600, Kevin Kuphal wrote:
>   
>> Daniel Kristjansson wrote:
>>     
>>> On Sun, 2006-03-26 at 12:39 +0200, Janne Grunau wrote:
>>>       
>>>> DTV info, ATSC maj(19) min(0), MPEG pn(-1)
>>>>         
>>> The minor channel number should never be zero with an ATSC channel,
>>> minor 0 is intended to be used to describe the NTSC channel licensed
>>> by the same broadcaster. Delete your channels on that source and
>>> rescan.
>>>       
>> I did this and the Myth scanner only picked up one transport which has 
>> only the SD broadcasted channels on the QAM signal.  None of the true HD 
>> channels were picked up by the scan.  I'm running an "atscscan" now also 
>> to see what it says. 
>>     
> So there are ATSC and non-ATSC channels on the same transport?
> That is certainly something the MythTV scanner doesn't handle.
> You can manually insert the non-ATSC channels so long as you
> leave the atscsrcid column set to zero.
>   
I don't think so.  It seems all the "SD" stations (I say this because 
the resolution is under 720p) are on the single transport 567000000.   
But more below...
>> The thing is, when Myth couldn't tune these channels and spat the error 
>> you noted above, mplayer could grab it just fine so I know the hardware 
>> is fine.  Is there another reason you might see the minor number as such 
>> or a way to work around it?  I know you say it should never be zero, but 
>> mplayer doesn't seem to care.   Would the mplayer output when tuning be 
>> helpful?
>>     
> MPlayer is not tuning to the ATSC channel, it is probably just playing
> something based on either the program number or the raw video and single
> audio PID spit out by atscscan. Tuning non-ATSC channels in MythTV just
> a matter of setting the serviceid column to the MPEG program number and
> leaving the atscsrcid column blank. If you use MythTV's import
> functionality for atscscan output, it will do this for you.
>   
You are, indeed, a genius.  I'm not sure why this was working before, 
maybe some recent change exposed this, but I dropped the atscsrcid to 
zero for a channel and it works.  I'm sure those were set by my initial 
channels.conf import from an atscscan.  Either way, it looks to be 
working well now.  Thank you for your help.

Just out of curiosity, based on this channels.conf, what exactly am I 
tuning?

# WBBM:567000000:QAM_256:2176:2177:1
## CHAN3:567000000:QAM_256:2240:2241:2
# WLS:567000000:QAM_256:2368:2369:4
WTTWDT2:567000000:QAM_256:2432:2433:5
# WYIN:567000000:QAM_256:2496:2497:6
WCIUDT:567000000:QAM_256:2560:2561:7
WPWRDT:567000000:QAM_256:2624:2625:8
## CHAN11:567000000:QAM_256:2752:2753:12
WGNDT:573000000:QAM_256:2304:2305:13
# WFLD:573000000:QAM_256:2368:2369:14
# WMAQ:573000000:QAM_256:2432:2433:15
WJYSDT:573000000:QAM_256:2496:2497:16
## CHAN19:573000000:QAM_256:2624:2625:18
## CHAN20:573000000:QAM_256:2112:2113:23
WBBMDT:735000000:QAM_256:2112:2113:1
## CHAN24:735000000:QAM_256:2048:2049:2
## CHAN25:747000000:QAM_256:1639:1638:1
WTTWDT:747000000:QAM_256:1636:1635:2
WTTWDT3:747000000:QAM_256:1632:1633:3
WFLDDT:753000000:QAM_256:2045:2044:2
WMAQDT:753000000:QAM_256:2041:2040:5
WMAQDT2:753000000:QAM_256:1639:1638:6
WLSDT:765000000:QAM_256:2045:2044:1
WGNDT2:765000000:QAM_256:2042:2041:2
WLSDT2:765000000:QAM_256:2038:2037:3
WLSDT3:765000000:QAM_256:1639:1638:4

I just assumed it was ATSC over QAM but am I mistaken in my terminology?

Kevin