This is the same problem I had. There's a great post that helped me a lot:
http://www.gossamer-threads.com/lists/mythtv/users/170723?search_string= qam_256;#170723 Here's my attempt at an explanation of the columns in the channel table. First, if you're doing a sqldump to look at the tables, remember that there are some tables (dvb_channel, dvb_pids, dvb_sat, dvb_signal_quality) that are leftover from previous versions that you should ignore. (I used to think that my problem was that they were empty.) Now, back to the channel table. Here are the columns: chanid, channum, freqid, sourceid, callsign, name, icon, finetune, videofilters, xmltvid, recpriority, contrast, brightness, colour, hue, tvformat, commfree,visible, outputfilters, useonairguide, mplexid, serviceid, atscsrcid chanid is just a database index that gives each channel a unique number. This number can therefore technically be any number, as long as it doesn't conflict with another number. Channum needs to be a unique number that will identify the channel to you & in the program listings (i.e. the usual name of the channel, such as Channel 10). If you have an analog channel and a digital channel from the same station, these numbers need to be different. Some use 10 and 10_1. My cable provider uses 10 and 710. Freqid is the frequency of the channel. If you're tuning in analog, this will probably be the same as channnum. If you're tuning digital, it will be the frequency from the channels.conf file (e.g. 531000000). Callsign is the official name of the channel (e.g. XETV or XETVHD). Name is the full text name that you want to call it. Xmltvid needs to be set to the xmltvid from labs.zap2it.com. The way I did this was to first delete all channels, then select in zap2it the channels I had, then run a mythfilldatabase. It filled in all fields correctly except freqid, mplexid, serviceid, atscsrid. I then edited those. Mplexid is the unique number in the database assigned to the freqid you're using. You can match that up in the dvb_multiplex table. Not sure why they want both the frequid and the mplexid. I should try it. Perhaps the previous poster's right. Perhaps if you're doing digital, you only need this number. Serviceid is also discovered with dvbscan, and it refers to the subchannel on that frequency. Digital stations are actually all subchannels on a smaller number of frequencies. (For example, all six broadcast channels on Cox in San Diego are on 531000000 and 627000000. They each just have a different serviceid. This is the last column in the dvbscan output.) Useonairguide - is set to 1 to use the xmltv stuff from zap2it. Atscsrcid -- I'm not sure what that's for. I've seen it set to all sorts of stuff, and it doesn't seem to matter. Some set it to 0, I set it to the same as the serviceid, and channel scan sets it to some random five digit number. I don't think it's got anything to do with tuning in the station. The hardest part for me was that cox doesn't send station id info on the signal, so where most people get CBSHD:627000000:23:23:4, I get [0001]: 627000000:23:23:4. So I had to figure out on my own which stations I could tune equaled which real stations. Here's what I came up with for Cox HD San Diego: CBSHD:627000000:QAM_256:49:52:3 FOXHD:627000000:QAM_256:33:36:2 ABCHD:531000000:QAM_256:33:36:2 WBHD:531000000:QAM_256:49:52:3 NBCHD:531000000:QAM_256:65:68:4 To put all this together, this translates into the following SQL insert statements: INSERT INTO `channel` VALUES (1708,'708','627000000',1,'KFMBDT','KFMBDT (KFMB-DT)','none',NULL,'','21212',0,32768,32768,32768,32768,'Default',0, 1,'',1,16,3,3); INSERT INTO `channel` VALUES (1706,'706','627000000',1,'XETVDT','XETVDT (XETV-DT)','none',NULL,'','25019',0,32768,32768,32768,32768,'Default',0, 1,'',1,16,2,2); INSERT INTO `channel` VALUES (1710,'710','531000000',1,'KGTVDT','KGTVDT (KGTV-DT)','none',NULL,'','20377',0,32768,32768,32768,32768,'Default',0, 1,'',1,4,2,2); INSERT INTO `channel` VALUES (1705,'705','531000000',1,'KSWBDT','KSWBDT (KSWB-DT)','none',NULL,'','24028',0,32768,32768,32768,32768,'Default',0, 1,'',1,4,3,3); INSERT INTO `channel` VALUES (1707,'707','531000000',1,'KNSDDT','KNSDDT (KNSD-DT)','none',NULL,'','21213',0,32768,32768,32768,32768,'Default',0, 1,'',1,4,4,4); (The way I did it was to delete them all, use mythfilldatabase to put back just the HD channels, then dump the sql statements using "mysqldump -u root -p mythconverg," then take out the lines above, put them in a separate file, fix them like I'm talking about, then run "mysql -u root -p <thatfile," and voila! I had channels. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Len Reed Sent: Wednesday, January 18, 2006 4:00 PM To: Discussion about mythtv Subject: Re: [mythtv-users] Entering USA Cable channels into the DVB tables 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. Over in the dtv_multiplex table, the first column is the mplexid. The one with '4' as mplexid has the right frequency (669000000). 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. _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
