Ticket #1793 (closed defect: invalid)
Opened 6 years ago
Last modified 4 years ago
Chan Scan fails on broken VCT
| Reported by: | davideshay@… | Owned by: | danielk |
|---|---|---|---|
| Priority: | trivial | Milestone: | 0.22 |
| Component: | channelscan | Version: | head |
| Severity: | low | Keywords: | dvb qam channels.conf scan |
| Cc: | Ticket locked: | no |
Description
I have a USB DVB HDTV adapter and am using it with a QAM cable source. Under 19 I had this working using channels.conf import, which is now disabled.
According to the commit log,I'm supposed to attach some info, so here goes:
Signal timeout, 500, Tuning timeout 3000
Log with siparser,channel,record output attached, as well as working channels.conf.
I get *WAY* too many channels using the myth scan and myth actually dies (error encountered displaying video) when I try to tune many of them.
Attachments
Change History
comment:1 Changed 6 years ago by danielk
- Owner changed from ijr to danielk
- Version set to head
- Milestone set to 0.20
comment:3 Changed 6 years ago by danielk
It looks like the cable provider is sending out bogus data:
Channel #0 name() 1008-0 mod(SCTE mode 2) cTSID(0x17) pnum(100) ETM_loc(0) access_ctrl(0) hidden(0) path_select(0) out_of_band(0) hide_guide(1) service_type(2) source_id(1102) Channel #1 name() 1008-0 mod(SCTE mode 2) cTSID(0x17) pnum(101) ETM_loc(0) access_ctrl(0) hidden(0) path_select(0) out_of_band(0) hide_guide(1) service_type(2) source_id(1104) Channel #2 name() 1008-0 mod(SCTE mode 2) cTSID(0x17) pnum(103) ETM_loc(0) access_ctrl(0) hidden(0) path_select(0) out_of_band(0) hide_guide(1) service_type(2) source_id(1106) Channel #3 name() 1008-0 mod(SCTE mode 2) cTSID(0x17) pnum(104) ETM_loc(0) access_ctrl(0) hidden(0) path_select(0) out_of_band(0) hide_guide(1) service_type(2) source_id(1108) Channel #4 name() 1008-0 mod(SCTE mode 2) cTSID(0x17) pnum(102) ETM_loc(0) access_ctrl(0) hidden(0) path_select(0) out_of_band(0) hide_guide(1) service_type(2) source_id(1112)
Notice that the major channel is always 1008, and the minor channel is always 0. This confuses the scanner which assumes the channel numbers are unique.
I've created a hack which will give you unique channel numbers, but you need to use "delete" for the existing channel treatment.
Please, try this patch.
Then send me the output of channel scan again and the output this from the database:
select chanid,channum,atscsrcid/256,atscsrcid%256,serviceid,networkid,transportid,frequency from channel,dtv_multiplex where channel.mplexid = dtv_multiplex.mplexid;
Also, please point out at least one channel you can't tune to after applying the patch.
comment:4 Changed 6 years ago by danielk
- Component changed from mythtv to dvb
- Summary changed from Problems with built-in scanner (channels.conf import used to work) to Chan Scan fails on broken VCT
comment:5 Changed 6 years ago by danielk
- Status changed from new to closed
- Resolution set to invalid
No response from ticket submitter, closing.
comment:6 Changed 4 years ago by myth@…
- Status changed from closed to new
- Resolution invalid deleted
I'm getting this same issue of the bogus 1008 channel numbers on 2.6.24 + linuxtv HG for my Pinnacle PCTV 800i (PCTV HD Card). The feed is from Cox cable in Tucson, AZ. A Mythtv 0.21 (debian-multimedia.org package) scan gives me 3 channels, #58-1, #58-2, and 1008, where as scan.sh from the wiki got me 35 playable channels. I'll try rebuilding the mythtv packages with the 1793.patch from above and see if it helps in a day or two.
comment:7 Changed 4 years ago by danielk
- Priority changed from minor to trivial
- Severity changed from medium to low
- Milestone changed from 0.20 to 0.22
This should work in the channel scanner branch, can you please check out that branch
svn co http://svn.mythtv.org/svn/branches/mythtv-channel-scan
compile and install then run:
mythtv-setup --scan
and let me know if that allows you to insert the 1008-0 channels?
Also I'd like some info from the DB after you do this so I can automate the conflict resolution, but lets see if manual resolution works first.
comment:10 Changed 4 years ago by danielk
- Status changed from infoneeded_new to closed
- Resolution set to invalid
no response from ticket reopener in 8 weeks, closing.
