On 5/27/06, Klaus Schmidinger <Klaus.Schmidinger@xxxxxxxxxx> wrote: > Anssi Hannula wrote: > > ... > > Okay, attached is a patch for nit.c that checks for all the frequencies > > in frequency_list_descriptor for the channel's frequency and if found, > > use it so that channel's frequency is not changed. > > > > Also in the detection of new transponders all frequencies are added for > > the EITscanner. > > > > I tested it by removing a transponder from channels.conf, and VDR found > > it again (though it took a while, as there are *many* frequencies in the > > frequency_list_descriptor). This too hasn't been working before on the > > DVB-T network of Finland. Just to be clear, of course it worked before in the Digita's (operator of the Finnish DVB-T) network too if you happened to be one of lucky ones whose center_frequency in delivery_descriptor happens to be the correct one. > I guess it's fair to assume that each TransportStream can contain > at most one FrequencyListDescriptor, right? Otherwise the above > loop could mix frequencies from different coding types, which would > lead to confusion later on. I guess it is. I can think of only one possible usage case when there could be multiple FrequencyLists: If the same multiplex is transmitted in multiple mediums in multiple frequencies, e.g. DVB-T and DVB-C, multiple lists could be used. But yes, that wouldn't make much sense as the bandwidth of DVB-T and DVB-C differs. -- Anssi Hannula
