From owner-freebsd-multimedia  Tue Feb 11 22:02:20 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA03414
          for multimedia-outgoing; Tue, 11 Feb 1997 22:02:20 -0800 (PST)
Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA03406
          for <multimedia@freebsd.org>; Tue, 11 Feb 1997 22:02:17 -0800 (PST)
Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/8.7.3) id XAA06072 for multimedia@freebsd.org; Tue, 11 Feb 1997 23:02:11 -0700 (MST)
From: Don Yuniskis <dgy@rtd.com>
Message-Id: <199702120602.XAA06072@seagull.rtd.com>
Subject: broadcast video
To: multimedia@freebsd.org
Date: Tue, 11 Feb 1997 23:02:10 -0700 (MST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Greetings!
   Forgive my obvious ignorance but could someone give me
the 25 cent explanation of the issues involved in broadcast
video (i.e. mbone) technology?
   In particular:
* what types of compression rates are used in the video codecs
* what sort of network bandwidth is consumed
* is this "full motion" video (or something at a slower frame rate)
* how much involvement is required on the part of the processor
* to what extent can hardware (i.e. codecs) affect these values
* what are the hidden "down side" issues

   I'm looking into using such a scheme in an embedded application.
As such, I can control the other traffic on the network, etc.
But, is this stuff "real"?  Or, still too experimental??

Thanks for your time!
--don