someone broke the HDTV tuner between 11810-11820

[spamme@…]

My ATI HDTV Wonder worked perfectly till somewhere around 11816 release. I updated to 11820 and when the EIT Scanner starts it produces an error. In addition, I tried to schedule a HDTV recording, and the recording failed to record.

TVRec(1) Error: Failed to setup digital signal monitoring TVRec(1) Error: Failed to setup signal monitor

TVRec(2) Error: Failed to setup digital signal monitoring TVRec(2) Error: Failed to setup signal monitor

[Janne <janne-mythtv@…>]

I can't see how a commit after [11816] should cause this. [11815] is my first candidate.

Please attach the backend log with --verbose channel,record and the output of following sql cammand:

SELECT channel.mplexid,serviceid,atscsrcid,atsc_major_chan,atsc_minor_chan,sistandard FROM channel,dtv_multiplex WHERE channel.mplexid = dtv_multiplex.mplexid;

Please don't adjust the ticket's priority and severity.

[spam@…]

I had the same problem here. I had to delete/add the source (datadirect type) and rescan/get channels from listing source. Of cource now with the hozed zap2it DTV listing I get no sub-channel program data. My EIT-ONLY atsc source never had a problem.

mplexid serviceid       atscsrcid       atsc_major_chan atsc_minor_chan sistandard
6001    7       NULL    24      5       atsc
6001    6       NULL    24      4       atsc
6001    5       NULL    24      3       atsc
6001    4       NULL    24      2       atsc
6001    3       NULL    24      1       atsc
5998    3       NULL    2       1       atsc
5997    4       NULL    6       2       atsc
5997    3       NULL    6       1       atsc
5996    4       NULL    32      2       atsc
5996    3       NULL    32      1       atsc
5985    3       NULL    8       1       atsc
5984    7       NULL    24      5       atsc
5984    6       NULL    24      4       atsc
5984    5       NULL    24      3       atsc
5984    4       NULL    24      2       atsc
5984    3       NULL    24      1       atsc
5983    3       NULL    2       1       atsc
5982    4       NULL    6       2       atsc
5982    3       NULL    6       1       atsc
5981    4       NULL    32      2       atsc
5981    3       NULL    32      1       atsc
5980    3       NULL    12      1       atsc
5979    6       NULL    22      4       atsc
5979    5       NULL    22      3       atsc
5979    4       NULL    22      2       atsc
5995    3       NULL    12      1       atsc
5994    6       NULL    22      4       atsc
5994    5       NULL    22      3       atsc
5994    4       NULL    22      2       atsc
5994    3       NULL    22      1       atsc
5985    4       NULL    8       2       atsc
5979    3       NULL    22      1       atsc
5986    3       NULL    49      1       atsc
6000    3       NULL    8       1       atsc
6000    4       NULL    8       2       atsc

[spamme@…]

mplexid serviceid atscsrcid atsc_major_chan atsc_minor_chan sistandard 1 1 2561 10 1 mpeg 1 2 2562 10 2 mpeg 1 3 2563 10 3 mpeg 1 4 2564 10 4 mpeg 1 5 2565 10 5 mpeg 1 6 2566 10 6 mpeg 1 7 2567 10 7 mpeg 2 3 7681 30 1 mpeg 3 3 6145 24 1 mpeg 4 1 1025 4 1 mpeg 4 2 1026 4 2 mpeg 5 3 1537 6 1 mpeg 6 3 3073 12 1 mpeg 7 1 9217 36 1 mpeg 8 3 14081 55 1 mpeg 8 4 14082 55 2 mpeg 8 5 14083 55 3 mpeg 8 6 14084 55 4 mpeg 9 3 14849 58 1 mpeg 9 4 14850 58 2 mpeg 9 5 14851 58 3 mpeg 10 3 4609 18 1 mpeg 11 0 14852 58 4 mpeg 12 0 14853 58 5 mpeg 3 4 NULL 24 2 mpeg

[spamme@…]

2006-11-25 16:29:33.786 Scheduled 11 items in 0.1 = 0.04 match + 0.03 place 2006-11-25 16:29:33.788 scheduler: Scheduled items: Scheduled 11 items in 0.1 = 0.04 match + 0.03 place 2006-11-25 16:29:33.790 Seem to be woken up by USER 2006-11-25 16:29:40.774 mythbackend: Running housekeeping thread 2006-11-25 16:31:18.215 TVRec(2): SetFlags?(EITScannerRunning,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:18.325 TVRec(2): SetChannel?() -- begin 2006-11-25 16:31:18.325 TVRec(2): ClearFlags?(RingBufferReady?,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:18.326 TVRec(2): Request: Program(no) channel(4_1) input() flags(EITScan,) 2006-11-25 16:31:18.326 TVRec(2): ClearFlags?(PENDINGACTIONS,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:18.327 DVBChan(1): Opening DVB channel 2006-11-25 16:31:18.327 DVBChan(1): SetChannelByString?(4_1): 2006-11-25 16:31:18.327 DVBChan(1): SetChannelByString?(4_1): Already on channel 2006-11-25 16:31:18.327 TVRec(2): Starting Signal Monitor 2006-11-25 16:31:18.327 TVRec(2): SetupSignalMonitor?(1, 0) 2006-11-25 16:31:18.327 DVBChan(1): Opening DVB channel 2006-11-25 16:31:18.376 SM(1)::AddFlags?: Seen() Match() Wait(Sig,SNR,BER,UB,) 2006-11-25 16:31:18.376 DVBSM(1)::constructor(): initial flags 0x7400000 2006-11-25 16:31:18.376 TVRec(2): Signal monitor successfully created 2006-11-25 16:31:18.376 TVRec(2): Setting up table monitoring. 2006-11-25 16:31:18.377 TVRec(2) Error: No valid DTV info, ATSC maj(4) min(1), MPEG pn(-1) 2006-11-25 16:31:18.377 TVRec(2) Error: Failed to setup digital signal monitoring 2006-11-25 16:31:18.378 TVRec(2) Error: Failed to setup signal monitor 2006-11-25 16:31:18.378 DVBSM(1)::Stop: begin 2006-11-25 16:31:18.378 SM(1)::Stop: begin 2006-11-25 16:31:18.378 SM(1)::Stop: end 2006-11-25 16:31:18.378 DVBSM(1)::Stop: end 2006-11-25 16:31:18.378 TVRec(2): SetFlags?(SignalMonitorRunning?,) -> RunMainLoop?,SignalMonitorRunning?,EITScannerRunning, 2006-11-25 16:31:18.378 TVRec(2): ClearFlags?(WaitingForSignal?,) -> RunMainLoop?,SignalMonitorRunning?,EITScannerRunning, 2006-11-25 16:31:18.378 TVRec(2): SetChannel?() -- end 2006-11-25 16:31:18.378 EITScanner: Now looking for EIT data on multiplex of channel 4_1 2006-11-25 16:31:29.983 TVRec(1): SetFlags?(EITScannerRunning,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:30.093 TVRec(1): SetChannel?() -- begin 2006-11-25 16:31:30.093 TVRec(1): ClearFlags?(RingBufferReady?,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:30.094 TVRec(1): Request: Program(no) channel(36_1) input() flags(EITScan,) 2006-11-25 16:31:30.094 TVRec(1): ClearFlags?(PENDINGACTIONS,) -> RunMainLoop?,EITScannerRunning, 2006-11-25 16:31:30.095 DVBChan(0): Opening DVB channel 2006-11-25 16:31:30.095 DVBChan(0): SetChannelByString?(36_1): 2006-11-25 16:31:30.097 DVBChan(0): 599000000 8vsb a auto auto a a auto a v 2006-11-25 16:31:30.097 DVBChan(0): Old Params: 557000000 8vsb a auto auto a a auto a v

DVBChan(0): New Params: 599000000 8vsb a auto auto a a auto a v

2006-11-25 16:31:30.097 DVBChan(0): Tune(): Tuning to 599000000Hz 2006-11-25 16:31:30.419 dvbchannel.cpp:wait_for_backend: Status: Signal,Carrier,FEC Stable,Sync,Lock, 2006-11-25 16:31:30.419 DVBChan(0): Tune(): Frequency tuning successful. 2006-11-25 16:31:30.419 DVBChan(0): SetChannelByString?(36_1): Tuned to frequency. 2006-11-25 16:31:30.419 TVRec(1): Starting Signal Monitor 2006-11-25 16:31:30.419 TVRec(1): SetupSignalMonitor?(1, 0) 2006-11-25 16:31:30.419 DVBChan(0): Opening DVB channel 2006-11-25 16:31:30.469 SM(0)::AddFlags?: Seen() Match() Wait(Sig,SNR,BER,UB,) 2006-11-25 16:31:30.469 DVBSM(0)::constructor(): initial flags 0x7400000 2006-11-25 16:31:30.469 TVRec(1): Signal monitor successfully created 2006-11-25 16:31:30.470 TVRec(1): Setting up table monitoring. 2006-11-25 16:31:30.470 TVRec(1) Error: No valid DTV info, ATSC maj(36) min(1), MPEG pn(-1) 2006-11-25 16:31:30.470 TVRec(1) Error: Failed to setup digital signal monitoring 2006-11-25 16:31:30.470 TVRec(1) Error: Failed to setup signal monitor 2006-11-25 16:31:30.471 DVBSM(0)::Stop: begin 2006-11-25 16:31:30.471 SM(0)::Stop: begin 2006-11-25 16:31:30.471 SM(0)::Stop: end 2006-11-25 16:31:30.471 DVBSM(0)::Stop: end 2006-11-25 16:31:30.471 TVRec(1): SetFlags?(SignalMonitorRunning?,) -> RunMainLoop?,SignalMonitorRunning?,EITScannerRunning, 2006-11-25 16:31:30.471 TVRec(1): ClearFlags?(WaitingForSignal?,) -> RunMainLoop?,SignalMonitorRunning?,EITScannerRunning, 2006-11-25 16:31:30.471 TVRec(1): SetChannel?() -- end 2006-11-25 16:31:30.471 EITScanner: Now looking for EIT data on multiplex of channel 36_1

[spamme@…]

this is mythbackend --verbose channel,record

[spamme@…]

results of the requested sql query

[Janne <janne-mythtv@…>]

Replying to spam@sma2.rain.com:

I had the same problem here. I had to delete/add the source (datadirect type) and rescan/get channels from listing source. Of cource now with the hozed zap2it DTV listing I get no sub-channel program data. My EIT-ONLY atsc source never had a problem.

Is it resolved for you? From your channel data I can't see a reason why it should fail.

[Janne <janne-mythtv@…>]

Replying to spamme@ecybernard.com:

mplexid serviceid atscsrcid atsc_major_chan atsc_minor_chan sistandard

4 1 1025 4 1 mpeg

4 2 1026 4 2 mpeg

It might work if change the sistandard of your multiplexes to "atsc". Rescanning the channels should work.

I'm a little bit puzzled why the failback to mpeg tuning doesn't work.

[danielk]

Janne, it's DB update 1168 that breaks ATSC. Your DB update sets all the ATSC multiplexes imported channels.conf information (before I fixed channels.conf import a couple weeks ago) to 'mpeg'. But this breaks tuning for anyone who later scanned for channels, because the MPEG program number is set to -1 when ATSC tuning information is available. I'll add another update to fix ATSC tuning in this case.

[anonymous]

Replying to Janne <janne-mythtv@grunau.be>:

Replying to spam@sma2.rain.com:

I had the same problem here. I had to delete/add the source (datadirect type) and rescan/get channels from listing source. Of cource now with the hozed zap2it DTV listing I get no sub-channel program data. My EIT-ONLY atsc source never had a problem.

Is it resolved for you? From your channel data I can't see a reason why it should fail.

rescan/get channels from listing source. Of cource now with the hozed zap2it DTV listing I get no sub-channel program data. My EIT-ONLY atsc source never had a problem.

Is it resolved for you? From your channel data I can't see a reason why it should fail.

Last night I deleted the capture cards, input connectors, and rescanned all channels on both tuners. However, I have not yet done the directdata type. If the other person solution hozed his zap2it DTV listings, the change is going to have to wait 3.6 hours until my backup copy records my favorite show.

The errors are in the other file:

---

2006-11-25 16:31:18.377 TVRec(2) Error: No valid DTV info, ATSC maj(4) min(1), MPEG pn(-1) 2006-11-25 16:31:18.377 TVRec(2) Error: Failed to setup digital signal monitoring 2006-11-25 16:31:18.378 TVRec(2) Error: Failed to setup signal monitor

[spamme@…]

FYI: When I revert to the released version it records just fine using the same database I have now.

[danielk]

(In [11821]) Fixes #2726. Properly labels existing ATSC multiplexes.

The old channels.conf importer mislabeled ATSC multiplexes as DVB multiplexes. When combined with the fix for mislabeled MPEG transports and tuning changes in [11815] this resulted in untunable channels for anyone in the US that had imported ATSC channels using the old broken channels.conf importer.

[anonymous]

Replying to danielk:

(In [11821]) Fixes #2726. Properly labels existing ATSC multiplexes.

The old channels.conf importer mislabeled ATSC multiplexes as DVB multiplexes. When combined with the fix for mislabeled MPEG transports and tuning changes in [11815] this resulted in untunable channels for anyone in the US that had imported ATSC channels using the old broken channels.conf importer.

---

That hosed my channels!!!!!!!!!! Channels 10_1,10_2,10_3,10_4,10_5,10_6,10_7 now have all exactly the same shows on them.

[danielk]

anon, rescan your inputs.

[spamme@…]

I deleted everything The capture cards input connections data source

Put everything back, and it still doesn't work.

[spamme@…]

I re-ran the SQL command listed above, and now the third column is all NULL, just like that other guy had earlier.

[danielk]

Mr. Spam, if you want this fixed you yourself and others in your position please reply in the mythtv-dev mailing list with everything you know about how you "put everything back" (channel scan? channels.conf import? Something scary I never thought to prevent people from doing?), also the third column of channel is freqid and the third column of dtv_multiplex is transportid, neither of those columns have any relevance to an ATSC channel, please explain what column you are referring to as the third column.

[spamme@…]

The third field is atscsrcid, which is in third position in the SQL query. Mythweb show the same programs shows for 10-1 to 10-7 when each channel really has different content. Another example 4-1 has regular programming, but 4-2 has weather all day everyday. However, now it shows the same shows as 4-1, when in fact 4-2 still has weather.