[mythtv] Re: mythtv commits (improperly dropping DVB channels)

[John P Poet]

On 6/9/05, John Pullan <john.pullan at gmail.com> wrote:
> On 09/06/05, John P Poet <jppoet at gmail.com> wrote:
> > On Tue, 2005-05-24 at 16:16 +0100, John Pullan wrote:
> > > On Tue, 2005-05-24 at 08:10 -0700, Wendy Seltzer wrote:
> > > > I'm still seeing this problem in current CVS, which is making it 
harder for
> > > > me to debug other issues I'm seeing there (namely, I can no longer 
skip
> > > > forward or get length info in SD shows that have been transcoded 
recently).
> > > >
> > > > An option to turn off the automatic updating of channels would work 
for me
> > > > until we can work out keeping the xmltvid in sync with the channels.
> > > <snip>
> > >
> > > In tv_rec.cpp you could try commenting out lines 104,105 the creation 
of
> > > the SIScan object and associated thread. (WARNING one by inspection)
> > > --
> >
> > I just had this happen to me. One of my digital channels just added a
> > sub-channel. The SIScan saw this and for some reason decided the
> > right thing to do, was to remove the primary channel from my database.
> > I, therefore, did not get a couple of "record on this channel" shows
> > recorded.
> >
> > I have commented out those two lines and recompiled my backend.
> > Hopefully this will keep that problem from happening to me again.
> >
> > Thanks John Pullan.
> >
> > John
> (Sigh) really are going to have to fix this aren't we.
> 
> --
> John
> 

If it help, I found this in my mythbackend log:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Error (Adding new DVB Channel):
Query was:
INSERT INTO channel (chanid, channum, sourceid, callsign, name, mplexid, 
serviceid, atscsrcid, useonairguide ) VALUES 
(3254,21,1,'KASA-DT','KASA-DT',6,3,3,1);2005-06-08 19:59:04.441 DVB#1 
Successfully tuned to channel 2_1.

Driver error wa2005-06-08 19:59:04.522 Changing from None to RecordingOnly
s [2/1062]:2005-06-08 19:59:04.578 DVB#1 Recorder: Card opened successfully 
(using TS mode).

QMY2005-06-08 19:59:04.586 DVB#1 Data read from DMX - This is for debugging 
with transform.c
SQL3: Unable to execute query
Database error was:
Duplicate entry '3254' for key 1

DB Error2005-06-08 19:59:04.808 MainServer::HandleAnnounce Playback
(2005-06-08 19:59:04.812 adding: topaz as a client (events: 1)
Adding new DVB Channel):
Query was:
INSERT INTO channel (chanid, channum, sourceid, callsign, name, mplexid, 
serviceid, atscsrcid, useonairguide ) VALUES 
(3254,21,1,'KASA-DT','KASA-DT',6,3,3,1);
Driver error was [2/1062]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate entry '3254' for key 1

DB Error (Adding new DVB Channel):
Query was:
INSERT INTO channel (chanid, channum, sourceid, callsign, name, mplexid, 
serviceid, atscsrcid, useonairguide ) VALUES 
(3254,22,1,'THETUBE','THETUBE',6,4,4,1);
Driver error was [2/1062]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate entry '3254' for key 1

DB Error (Adding new DVB Channel):
Query was:
INSERT INTO channel (chanid, channum, sourceid, callsign, name, mplexid, 
serviceid, atscsrcid, useonairguide ) VALUES 
(3254,22,1,'THETUBE','THETUBE',6,4,4,1);
Driver error was [2/1062]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate entry '3254' for key 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 

So, it looks like it tried to add the channel back in, but failed. My 
CHANNEL table looks like:

+--------+---------+----------+---------+-----------+-----------+---------------+
| chanid | channum | callsign | mplexid | serviceid | atscsrcid | 
useonairguide |
+--------+---------+----------+---------+-----------+-----------+---------------+
| 1019 | 19_1 | KWBQDT | 7 | 2 | 2 | 1 |
| 1002 | 2_1 | KASADT | 6 | 3 | 3 | 0 |
| 1007 | 7_1 | KOATDT | 3 | 3 | 1 | 1 |
| 1013 | 13_1 | KRQEDT | 1 | 3 | 1 | 1 |
| 1004 | 4_1 | KOBDT | 5 | 3 | 1 | 1 |
| 1005 | 5_1 | KNMEDT | 8 | 1 | 1 | 1 |
| 3005 | 5_2 | KNMEDT2 | 8 | 2 | 2 | 1 |
| 1050 | 50_1 | KASYDT | 10 | 2 | 2 | 1 |
| 3254 | 253 | LMN | NULL | NULL | NULL | 0 |
| 3261 | 261 | LRW | NULL | NULL | NULL | 0 |
+--------+---------+----------+---------+-----------+-----------+---------------+

When I first switched to the DVB driver, I copied the 
mplexid,serviceid,atscsrcid values from the DVB scan, to my pre-existing 
CHANNEL config. If I had, instead, copied my channum,xmltvid values to the 
entries created by the DVB scan, would that have prevented this problem?

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20050609/69ff553e/attachment.htm