From owner-freebsd-multimedia Sat Jun 26 4:58: 6 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id C534014D8D for ; Sat, 26 Jun 1999 04:58:01 -0700 (PDT) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.3/8.9.1) id NAA41054; Sat, 26 Jun 1999 13:55:57 +0200 (CEST) (envelope-from frodef) To: freebsd-multimedia@freebsd.org Subject: Re: bt848 channel frequencies References: From: Frode Vatvedt Fjeld Date: 26 Jun 1999 13:55:57 +0200 In-Reply-To: Juha Nurmela's message of "Fri, 25 Jun 1999 23:28:42 +0300 (EEST)" Message-ID: <2hzp1n9nw2.fsf@dslab7.cs.uit.no> Lines: 19 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Juha Nurmela writes: > Meaning, the db would provide (customizable) defaults for vision > and sound, if none were provided by individual apps. Yep, agreed. > Also, the datatype for 'frequency' should be wide enough for > satellite and long-wave work, from few kHz to tens of GHz. I believe your typical "long" scales to 4.2 GHz if the unit is a single Hz. Does anyone know of tuning applications that would require a granularity smaller than one KHz? What about the different radio bands, for example? Or would it be better to use a 64-bit type to represent frequencies? Then we could go from uHz to GHz without problems.. :-) -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message