On Fri, Mar 07, 2008 at 04:57:50PM +0100, Klaus Schmidinger wrote:
> On 03/07/08 16:31, VDR User wrote:
> > On Thu, Mar 6, 2008 at 11:37 PM, Klaus Schmidinger
> > <[EMAIL PROTECTED]> wrote:
> >> On 03/06/08 21:13, Timothy D. Lenz wrote:
> >> > Well, ".", "#", "*", something in the channels.conf. "0" is not a valid
> >> > notation because 0 is part of the number system. 40 won't work for KVOA
> >> > because 40 is KHRR. And when displayed it should be "."
> >> Well, 40 would become 400, accordingly.
> >> Just add a 0 to each channel number (or two zeros, if you have two digit
> >> sub channel numbers).
> > Klaus, come on, you know bastardizing the channel numbers like that is
> > a horrible idea! ;)
> "Bastardizing" channel numbers the way those "sub channels" do, that's
> a horrible idea!
> Channel numbers are *numbers*, *integer* numbers!
> There's a first channel, and a second one, and a third one,
> and they are numbered 1, 2 and 3. Now what's a "2.1" channel?
> Is that "ten percent more than the second channel"?
> VDR stores channel numbers as integers. So if you want to
> have a numbering scheme where you have channels "between" other
> channels, you need to make room for these additional entries.
> And the only way I see to do this is to shift all numbers one
> digit to the left.
I'm sorry if you don't see it the way the rest of us do, but the goal
here should be the user experience. The channels are advertised from
the channel makers as 2-1, 2-2, or 2.1, 2.2, or 2*1, 2*2 or whatever.
When users go to a channel, they are not thinking:
hmm what channel "number" shal I go to
no they know
if I want to watch WJLA, I go to 7*1 for the HD version, or 7*2 for
the SD version. They know this because that is how it is advertised
to them in their markets. They have accepted that channels are not
The other issue you have is that channels in their system have
well-known identifiers that are called "channels" for example NASATV
is called channel 213. This is something we have talked about in the
past both on and off-list. If you want to somehow map these
subchannels to some wierd integer that's say greater than a million,
that's fine, your channel numbers are integers, but the user needs to
be able to select the channel he wants. Is the goal here that the
user is able to use the program or that channels can continue to
antiquatedly be identified as ints?
> vdr mailing list
vdr mailing list