Subject: Re: [linux-audio-dev] Remote control is important
From: Paul Winkler (slinkp23_AT_yahoo.com)
Date: Mon Nov 20 2000 - 08:05:20 EET
Paul Barton-Davis wrote:
> the GUI work that is *not* related to drawing requests consumes an
> almost immeasurable fraction of CPU power.
Cool, I will stop caring about it, except when...
> > ... I'm doing something like, say, interactive algorithmic
> >music where the part of the system generating events is quite complex.
>
> yeah, now this part i can see the point of.
> >3) libsig++ when it's network transparent ... don't know much about it
> >except reading PBD's posts. Just to clarify: Does this mean I'll be
> >able to run, say, Quasimodo's engine on one box while its UI is on
> >another box?
>
> you can already do that (modulo any current compile-time issues). its
> called server-quasimodo, and it has a command-line parser which can be
> controlled by a (G)UI on another system. stephane conversey was
> responsible for most of this, and he had a Python-GTK GUI that he ran
> on one machine while server-quasimodo ran on some other system.
>
> but this has nothing to do with libsigc++ being thread and/or network
> transparent.
Nice.
One of these days I'll actually get Q running. :)
> >4) something much like a unix named pipe, only working over TCP/IP
> >(e.g. over ethernet). That would be a LOT of fun for even a
> >know-nothing like me. And it wouldn't care what kind of data you were
> >sending - MIDI, ASCII, audio data,
>
> its called a socket. it takes a couple of extra calls to set up
> compared to a pipe. see "man socket(2)".
Thanks for the FM!
--
................. paul winkler ..................
slinkP arts: music, sound, illustration, design, etc.
web page: http://www.slinkp.com
A member of ARMS: http://www.reacharms.com
This archive was generated by hypermail 2b28 : Mon Nov 20 2000 - 08:51:13 EET