Xref: utzoo comp.sys.amiga.tech:98 comp.sys.amiga:16536
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!udel!gatech!purdue!umd5!uvaarpa!hudson!vivaldi!pmy
From: pmy@vivaldi.acc.virginia.edu (Pete Yadlowsky)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: IPC and the Soundscape patch panel
Message-ID: <297@hudson.acc.virginia.edu>
Date: 23 Mar 88 17:54:39 GMT
References: <843@nuchat.UUCP> <1699@louie.udel.EDU>
Sender: news@hudson.acc.virginia.edu
Reply-To: pmy@vivaldi.acc.Virginia.EDU (Pete Yadlowsky)
Distribution: na
Organization: University of Virginia, Charlottesville
Lines: 29

>In article <843@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
>How about, when you register a port, providing an icon for it... and having
>the icon show up in a SoundScape-like patch panel? Probably be best to have
>it set up with a work area and an icon palette.
>The currently selected icon has its info displayed in the info area. The
>mechanics of moving them to the work area and connecting them up should
>be pretty simple. Rubber-band-lines would be good.

I have such a thing, and I use it in my small MIDI studio. With it, I can
start MIDI processes (delays, filters, etc) and (graphically) connect them
as nodes in a network. The "system" handles all message routing, merging and 
even some filtering. All communications with the outside world are
handled by a process which manages the serial.device, so that it may
be shared by virtually any number of other processes. The whole thing
is built on Bill Barton's (Plink: PEABODY) MIDI utility library, which
really amounts to being a MIDI extension to Exec. 

Rather than managing ports (and their icons), this system works with
whole processes, and the stringing of these processes into pipes (nets,
actually). Anyone interested in hearing more? I originally intended to
use this for musical applications, but it could certainly be extended
and generalized.



Peter M. Yadlowsky
Academic Computing Center
University of Virginia
pmy@vivaldi.acc.virginia.EDU