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