What about having a wizard when you try to edit the channel? It will show you a list with all stations on that frequency (all possible combinations) and you can choose which one you want from there. It won't give you the option to set NID, TID but the option to choose the right settings from a list. I suppose if the entry is correct it won't be changed by the autoupdate code. Regards, Ilariu On 11/2/05, Malcolm Caldwell <malcolm.caldwell@xxxxxxxxxx> wrote: > > On Tue, 2005-11-01 at 08:20 -0500, Jeremy Hall wrote: > > In the new year, Klaus Schmidinger wrote: > > > Sascha Volkenandt wrote: > > > The problem is that if you take an existing channel and change the > > > values in the "Edit channel" menu, you can't change the NID and TID > > > values. > > > > > Are you saying here you physically can't change it or you shouldn't > change > > it? > > > > > Just use this entry: > > > > > > Radio Horeb;Eurociel:10832:hC56:S19.2E > :22000:0:64=deu:0:0:61960:1:1057:0 > > > > > > I'm not sure if it makes much sense to offer the NID and TID in this > menu, > > > because normally the user only knows the transponder frequency. > > > Maybe these values should simply be set to 0 when saving an edited > > > channel record, because then VDR will automatically update them the > > > next time this transponder is tuned to. I guess I'll make it so. > > > > > I'd like to request this change not go into effect. I think it would > have > > unforseen impact on an already-stable codebase. I can even innvision > > somehow duplicate channels being added in some race condition because > the > > nid and tsid are part of the channel id. I believe the correct solution > > is to have the user set it right the first time and forget about it. If > > they don't know what it is they should set -1 or something that violates > > spec so that vdr understands this was deliberately set to "I don't know" > > > > Or > > > > you could add a bool to channels.conf to say whether you believe the > sid, > > nid, tsid, frequency, and other bits are accurate, but then again I > think > > that's a bit overkill. > > I have thought a bit about this issues (eg a flag in channels.conf). > > There are a number of channels in my channels.conf where the autoscan > information does not work - ie the provider has incorrect information or > NID and TID are the same as another frequency on that sat. > > The 'solution' is to use RID. Unfortunately that does not work either, > as the autoscan will still change the entry. > > Here is what I have to do: have two copies of the channel, one with > RID=0 and one with RID=1. The RID=0 one gets autoscaned to the > 'incorrect' values, and the one with RID=1 keeps the 'correct' values. > > IMHO, the functionality should be changed so if RID!=0, don't update > this channel at all. > > This would implement the flag, but not require the channels.conf format > to change. > > > > _J > > > > > Klaus > > > > > > _______________________________________________ > > > vdr mailing list > > > vdr@xxxxxxxxxxx > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > > > > > > > _______________________________________________ > > vdr mailing list > > vdr@xxxxxxxxxxx > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > _______________________________________________ > vdr mailing list > vdr@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.linuxtv.org/pipermail/vdr/attachments/20051104/a29bfe80/attachment.htm
