[AG-TECH] mute control.

[Lawrence A. Rowe]

Your message:
> Is the tcl server available?
>
> -randy

Randy -

Yes, the code is all in the Open Mash CVS archive.  It is not
well-structured or documented, but as I said it is pretty easy to learn
and modify.  We have built clients and servers that run as Open Mash
scripts and that run as Tcl/Tk scripts.  The mash scripts are in
mash-code/mash/tcl and the tcl/tk scripts are in mash-code/apps.  here
is a list of a couple of the applications:

1. mash/tcl/{rcc,rccd} - wei developed a camera client/server that
defined the model for a general camera server.  we use the Parkervision
controls here for webcasting classes from several classrooms.
2. apps/vcc3 - client/server app for controlling a canon VCC3.  i had a
student working on support for the newer VCC4 this semester, but i don't
think it got checked back into the archive.
3. apps/rswitch - gui for a routing switcher.  this is the client.  it
uses the nway server which i don't know where it is. 

(Peter, do you know where the nway server is and the other client that
we use for webcasting in Soda?)

4. apps/amx - server to execute operations in an AMX control computer
through an rs232 interface.
5. mash/tcl/applications/avswitch* - client/server for a routing switch.
6. mash/tcl/applications/powerswitch* - <not sure what this does, it
probably controls the lutron lighting system installed in our building>
7. mash/tcl/applications/camera-* - an early camera client/server.

some of these control apps were designed to work with the Director's
Control (dc) application we developed for producing a webcast.  As such,
they fit into a larger framework that included a service discovery
protocol and a soft-state protocol (Announce/Listen) that was very
reliable.  if you want to read about the research behind all this work,
the paper on Streaming Media Middleware surveys the systems and
requirements for building and maintaining it. The paper is at
	http://bmrc.berkeley.edu/papers/2001/159/
Other papers on dc and the automated control of webcasts are available
at http://bmrc.berkeley.edu/papers/.

So, which system/package should you start with.  I would recommend you
look at mash/tcl/rcc*.  the server is very simple and it shows how TclDP
is used to setup a client and a server and how RPC commands are done to
control things.

We have implemented a number of apps for our AG colab.  I am not sure
they are in the current archive.  We will do that shortly.

This code probably looks like a mess since it is all ad hoc.  We found
the dc implementation and model hard to extend to other applications, so
we began development of a middleware package for controlling distributed
media resources.  The goal was to simplify the development of
applications that required control of conventional a/v equipment and
streaming media applications.  Rather than building a bunch of
customized special-purpose apps, we wanted to create a common library
and infrastructure for doing a variety of control and automation tasks.
My biggest objective is to reduce the need for human operators because I
believe that limits the widespread deployment and use of this
technology.

The system we designed and began to prototype was called INDIVA, which
is described at http://bmrc.berkeley.edu/projects/indiva.

If you have any questions, send them to the Open Mash developers list
which you can join at http://www.openmash.org/.

Enjoy!
	Larry
-- 
Professor Lawrence A. Rowe          Internet:  Rowe at BMRC.Berkeley.EDU
Computer Science Division - EECS       Phone: 510-642-5117
University of California, Berkeley       Fax: 510-642-5615
Berkeley, CA 94720-1776            URL: http://bmrc.berkeley.edu/~larry
-------------- next part --------------
An embedded message was scrubbed...
From: "Lawrence A. Rowe" <Rowe at bmrc.berkeley.edu>
Subject: Re: [AG-TECH] mute control.
Date: Tue, 27 May 2003 12:57:32 -0700
Size: 5378
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20030529/cbab174f/attachment.eml>