[mythtv-users] Entering USA Cable channels into the DVB tables

[Len Reed]

Brad,

OK, you're getting OTA ("over the air") and I'm getting QAM-256 from 
cable.  I still don't see how freqid can matter if the frequency is 
getting pulled from the dtv_multiplex table.

If each of KQED's 5 multiplexed programs has a unique serviceid (to 
identify it within that frequency), then what is the unique atscsrcid 
for?  In your case, the atscsrid is unique within each frequency.  Also, 
surely common broadcasting is needed to multiplex within the same 
frequency (e.g., your 2-1 and 2-2 and then your 20-1 and 20-2).  I would 
guess that these are all up on Sutro tower in San Francisco.

Len

Brad Fuller wrote:
> Len Reed wrote:
> 
>>Brad Fuller wrote:
>>  
>>
>>>On 01/16/2006 01:55 PM R. G. Newbury wrote:
>>>    
>>>
>>>> >In the database, Fox digital is my chanid 3785. So I assume I should
>>>> >>
>>>> >>update channel set freqid = 4 where chanid = 3785;
>>>> >>
>>>> >>where '4' is the mplexid from the dtv_multiplex table for 669Mhz.
>>>> >>
>>>> >>
>>>> >>
>>>>
>>>> In my setup, the freqid is the same as the channum, that is, the number
>>>> in the EPG which you 'call' for the channel you want.
>>>>      
>>>>
>>>How do you do that when you can have the same freqid for a channel with 
>>>several subchannels.
>>>For instance, in my area channel 11 is freqid 207000000 and it has to 
>>>subchannels.
>>>atscsrcid 1 and 2 (for 11-1 and 11-2)
>>>
>>>Plus, the freqid is really big. Do you just truncate it to 207?
>>>    
>>>
>>
>>Don't confuse freqid with frequency.
>>
>>Mine's all working now (see other detailed posting).
>>
>>The channel table has freqid set to the cable channel my provider and 
>>zap2it schedules use.  For example, Fox digital (WAGADT) is chanid 3785, 
>>channum 785, and freqid 785.  I don't think the freqid maters, though, 
>>for digital channels.  (For analog channels, freqid are standard 
>>broadcast or cable channel numbers.) For WAGADT, mplexid is 4 and the 
>>serviceid is 2.  The atscsrcid is 0 on all my digital channels.
>>  
>>
> Hmmm.
> In my channel table "freqid" is the same as "frequency" in the 
> dtv_multiplex table, which is what I was referring to.
> 
> For instance, Fox Digital (KTVUHD) freqid is 725000000.
> 
> To reflect what you have above, Fox Digital:
> chanid:  2028
> channum: 2-1 (this is a number I gave it)
> freqid:  725000000
> mplexid: 19
> 
> atscsrcid on my digital channels are all different.
> Examples:
> name    channum   mplexid   serviceid   atscsrcid
> ------------------------------------------------
> KTVUHD    2-1     19        3            1
> KTVU-DT   2-2     19        4            2
> KBWB-HD  20-1     2         3            1
> KBWB-SD  20-2     2         4            2
> 
> I have 5 KQED (PBS) OTA HD channels. Their atscsrcid's are 1, 2, 3, 4, 5.
> Their mplexid's are all the same, as is their frequency 569000000
> Their serviceid's are 3, 4, 5, 6, 7 respectfully.
> 
> 
>>Over in the dtv_multiplex table, the first column is the mplexid.  The 
>>one with '4' as mplexid has the right frequency (669000000).
>>  
>>
> As I mentioned, that frequency value is the same as my freqid in the 
> channel table.
> 
> I bet this is because I'm OTA.
> 
>>So, when I want to tune WAGADT, which my provider calls channel 785, 
>>mythbackend pick adapter 3 and channel 785 to get chanid 3785.  It looks 
>>that up in the channel table to get the mplexid (4) and serviceid (2). 
>>It goes to the drv_multiplex table and looks up 4 to get the frequency 
>>(669000000 Hz).  Finally, it tunes the card giving it the frequency and 
>>the serviceid.
>>
>>None of this worked until I upgraded to the latest SVN and scanned the 
>>channels.  I'm guess that the dtv_multiplex table's transportid and 
>>networkid needed that step to get set properly; it's not clear to me
>>what those fields do.  If that's right, then those fields are involved 
>>in tuning or filtering somehow.