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

Stuart Morgan stuart at tase.co.uk
Tue May 17 13:48:38 UTC 2005


On Mon 16 May 2005 20:07, Taylor Jacob wrote:
> Quoting Stuart Morgan <stuart at tase.co.uk>:
> > On Mon 16 May 2005 18:56, Wendy Seltzer wrote:
> > > This or the previous commit on the DVB code seems to kick in even
> > > when a sub-channel is temporarily off-air, and even when I haven't
> > > requested a re-scan.  Plus, it's overwriting the existing channel set
> > > and losing the xmltvid.
> >
> > I've had the same problem.
> >
> > Upgrading to the latest CVS resulted in half the channels being
> > overwritten. Chanids changed lost resulting in broken schedules and
> > xmltvids/icon paths were lost. Major pain to re-enter that data and run
> > update queries on the data to incorrect chanids - although I accept that
> > is the hazard of running CVS code.
>
> If Mythfilldatabase corrected these would that solve the problem?

If the channel data wasn't overwritten that might solve the problem.

I can't see how Mythfilldatabase would be able to correct the chanids, let 
alone the lost xmltvids and other channel settings. Mythfilldatabase isn't 
run all the time either - so broken schedules would mean missed recordings 
until the next run of Mythfilldatabase 24/48 hours or 7 days later!

I don't know the inner workings of Mythfilldatabase though - perhaps I'm 
wrong. I'm certainly not the best person to ask :)

Right now I've seen no further loss of channel information since the upgrade 
problems. All of the channels on Multiplex 1 were overwritten and one channel 
from Multiplex 2 (UK). Possibly there were changes between the information in 
the database for these channels and that being broadcast at the time of the 
upgrade. If every time there is a small change in broadcast information 
channels data will be overwritten then this is going to cause havoc.
-- 
Stuart Morgan


More information about the mythtv-dev mailing list