Re: [linux-audio-dev] Remote control is important

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] Remote control is important
From: Paul Winkler (slinkp23_AT_yahoo.com)
Date: Sat Nov 18 2000 - 22:34:59 EET


Paul Barton-Davis wrote:
>
> In message <3A1580B0.15B03544_AT_yahoo.com>you write:
> >Not sure where in the threads about Ardour etc this would go...
> >
> >How many of you designing studio apps right now are thinking about
> >running the user interface(s) from a remote machine? I don't mean
> >displaying them remotely, I mean RUNNING them remotely.
>
> i'm about to explain DISPLAY, but then i see:
>
> >desktop and view them remotely on the laptop - I do it all the time -
> >but then the desktop is still doing most of the work, isn't it? Unless
> >I'm completely misunderstanding the X client / server model.
>
> well, the DISPLAY host does nothing but satisfy drawing requests
> that come from the application and relay input events (kbd, mouse,
> etc) back to the application.

That's what I thought.
 
> why would you want it to be otherwise ?

Well, in your SMP box, why do you want to reserve one processor for
DSP?
Why do people often run a soft-synth on a separate system from the one
running the sequencer? (used to be pretty much mandatory.) I want to
squeeze out the most DSP I can, so if I can get the laptop to take
care of more than just the drawing requests that would be nice.
Especially if I'm doing something like, say, interactive algorithmic
music where the part of the system generating events is quite complex.

So there are several options:

1) MIDI ... works, universal, but rather stupid.

2) MCOP ... don't know much about it except reading Stefan's posts

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?

I'm not much good with C or C++ but I like to play around with
connecting things with pipes. That makes me wonder if there's a fourth
option:

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,
whatever. That would be perfect for my favorite insane pastime -
using python to generate realtime csound i-statements and piping them
to csound.

Does anything like that exist?
A suggestion to RTFM would be great if it specified which FM. :)

................. paul winkler ..................
slinkP arts: music, sound, illustration, design, etc.
           web page: http://www.slinkp.com
      A member of ARMS: http://www.reacharms.com


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Sat Nov 18 2000 - 23:09:17 EET