Well dvb_channel, and dvb_pids are no longer used. We wanted to delete them to avoid confusion, but that's another story.
So what happened when you scanned existing transports ? On Wed, 2005-02-16 at 01:11 +1100, Eyal Lebedinsky wrote: > John Pullan wrote: > > It kind of depends where it is in the scheme of things. I would suggest > > that maybe your best option is to get to the Advanced option edit the > > transport to your correct frequencies, then go and choose the "Scan > > existing transports" option. > > Did that. I now have what looks like a proper dtv_multiplex, with mplexid > and transportid inserted where necessary (I think): > > update dvb_channel,dtv_multiplex > set dvb_channel.transportid = dtv_multiplex.transportid > where dvb_channel.frequency = dtv_multiplex.frequency; > > update channel,dvb_channel,dtv_multiplex > set channel.mplexid = dtv_multiplex.mplexid > where channel.chanid = dvb_channel.chanid > and dvb_channel.transportid = dtv_multiplex.transportid; > > It seems top go further, close but no cigar: > > Starting up as the master server. > 2005-02-16 00:57:10.354 DVB#0 DVB SI Table Parser Started > 2005-02-16 00:57:11.135 DVB#0 Using DVB card 0, with frontend Zarlink MT352 > DVB-T. > 2005-02-16 00:57:11.136 DVB#0 DVB Signal Monitor Starting > 2005-02-16 00:57:12.187 DVB#0 Signal Locked > 2005-02-16 00:57:12.649 DVB#0 DVB signal dc3 | snr acac | ber 0 | unc 0 > 2005-02-16 00:57:12.650 DVB#0 Status: LOCK. > 2005-02-16 00:57:12.651 DVB#0 Multiplex Locked > 2005-02-16 00:57:18.651 DVB#0 Timeout Getting PMT > 2005-02-16 00:57:18.653 DVB#0 ERROR - Tuning for channel #9 failed. > 2005-02-16 00:57:18.676 Closing DVB channel > 2005-02-16 00:57:19.352 DVB#0 DVB Signal Monitor Stopped > 2005-02-16 00:57:19.396 DVB#1 DVB SI Table Parser Started > 2005-02-16 00:57:19.399 DVB#1 Using DVB card 1, with frontend Spase SP887x > DVB-T. > 2005-02-16 00:57:19.431 DVB#1 DVB Signal Monitor Starting > 2005-02-16 00:57:19.504 DVB#1 Signal Locked > 2005-02-16 00:57:19.783 DVB#1 Signal Lost > 2005-02-16 00:57:20.062 DVB#1 Signal Locked > 2005-02-16 00:57:20.426 DVB#1 DVB signal ffff | snr 73b7 | ber 303d | unc > ffffffff > 2005-02-16 00:57:20.427 DVB#1 Status: LOCK. > 2005-02-16 00:57:20.431 DVB#1 Multiplex Locked > 2005-02-16 00:57:27.140 DVB#1 Timeout Getting PMT > 2005-02-16 00:57:27.141 DVB#1 ERROR - Tuning for channel #9 failed. > 2005-02-16 00:57:27.158 Closing DVB channel > 2005-02-16 00:57:27.279 DVB#1 DVB Signal Monitor Stopped > 2005-02-16 00:57:27.478 mythbackend version: 0.17.20050130-1 www.mythtv.org > 2005-02-16 00:57:27.480 Enabled verbose msgs : important general > 2005-02-16 00:57:29.480 Reschedule requested for id -1. > 2005-02-16 00:57:29.510 Scheduled 7 items in 0.0 = 0.00 match + 0.03 place > 2005-02-16 00:57:29.542 Seem to be woken up by USER > > So, what is failing between "Multiplex Locked" and "Timeout Getting PMT"? > Any other table I need to fix? The old dvb_pids table should not change, > right? >
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
