Luca Olivetti wrote: > > Thomas Bergwinkl wrote: > > >>I'll look into it. What about eit.c and nit.c? > >> > > > > > > eit is just for epg data (I think) so we don't need it for a channel > > scan. > > And for a fast channel scan I think it is not necessary to > wait for data > > of nit. When you look in nit.c you can see that just transponderdata > > (Source, Frequency, Polarization, SymbolRate, CodeRate) > will be updated. > > But if we have already tuned to this channel (for > scanning), we already > > know them. > > That's what I thought too. Now, I looked into pat.c but I > don't see an > easy way to know when all data has been received. > I attached a patch for pat.[hc]. I hope it works. Every time sdt.c adds a new channel it triggers the patfilter (patFilter->Trigger();), so that numPmtEntries will be set to 0. So when numPmtEntries == 'number of all available entries' the scan should be complete. Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: pat.diff Type: application/octet-stream Size: 1650 bytes Desc: not available Url : http://www.linuxtv.org/pipermail/vdr/attachments/20050327/c8f1468f/pat.obj
