From owner-freebsd-multimedia Sat Jun 26 20: 6:20 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 88CC714CC8 for ; Sat, 26 Jun 1999 20:06:18 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-70.dialup.rdu.ipass.net [209.170.132.70]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id XAA21955; Sat, 26 Jun 1999 23:06:13 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id XAA04502; Sat, 26 Jun 1999 23:08:03 -0400 (EDT) (envelope-from rhh) Date: Sat, 26 Jun 1999 23:08:03 -0400 From: Randall Hopper To: Frode Vatvedt Fjeld Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: bt848 channel frequencies Message-ID: <19990626230803.B3178@ipass.net> References: <3.0.6.32.19990626090820.007ad510@alicia.nttmcl.com> <2hemj0b617.fsf@dslab7.cs.uit.no> <2hzp2tfr3t.fsf@dslab7.cs.uit.no> <374AA5BB.7C87D8C2@cs.strath.ac.uk> <2hogj9f0p6.fsf@dslab7.cs.uit.no> <2hpv2kba67.fsf@dslab7.cs.uit.no> <19990625190008.A2443@ipass.net> <2hvhcb9ngw.fsf@dslab7.cs.uit.no> <19990626131127.A3726@ipass.net> <2hk8sqalej.fsf@dslab7.cs.uit.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <2hk8sqalej.fsf@dslab7.cs.uit.no>; from Frode Vatvedt Fjeld on Sat, Jun 26, 1999 at 08:04:20PM +0200 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frode Vatvedt Fjeld: |Randall Hopper writes: |> I only suggest the second mapping being managed by libtv because it |> is something that should be sharable across all TV/tuner/radio |> clients, or the user ends up duplicating this info in multiple |> places. | |I can't see any reason not to provide for the second mapping also, |even if there will be a larger number of mapping tables on a global |basis. For example, in the city where I live I'd guess there are less |than 5 usable such mapping tables, and I'd much prefer to chose |between the 5 than to manually locate and name every program. Not to |mention that whenver my cable-provider decides to change something, I |can probably get a new mapping table from someone else. And even if I |do need to manually make a mapping table, I'd prefer it to be done |such that it is consitently available from all my TV |applications. ..Or am I missing your point here? No, I think you've got it. I'm not sure of your use of the word "program" here, but that could be a language issue. Here, a program to me implies TV programming which is what shows are on at what times on a specific station/channel. That's close to what I'm talking about but not quite. For the second mapping, I'm talking about "stations" which are basically TV network affiliatations -- that is, what TV franchise is devising the programming for a channel rather than the programming (TV shows) on the channel. If that's what you meant, we're talking the same language :-) |> So in that station-name mapping table, it would be useful to be able |> to map to either frequencies or to frequency names. | |This is in agreement with the comments I made earlier that radios want |to map directly from program name to frequency. | |Like I said, this can be solved by introducing "special" |frequency-names, where the real frequency is inferred from the name |itself (like the mapping "129 MHz" -> 129000000). | |What do you think? Sounds good. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message