linuxaudio.org

On Mon, Jun 14, 2010 at 12:47 PM,   wrote:

quoted text
> On Mon, Jun 14, 2010 at 12:06:21PM +0000, alex stone wrote:

>

>> Fons, a question. In the framework you've described, would it feasible

>> or possible to run the host and plugins as a "backend" on a headless

>> rig, and run the gui on the main daw box, in an attempt to offload

>> some of the grunt work?

>

> In the normal case the host would be e.g. the DAW which I

> suppose is running on 'the main daw box', so the plugins

> will run there as well - they run inside the host process,

> this is not a 'jack rack' even if it looks like it.

>

> It would be possible to make a 'jack-rack' style host

> (i.e. and app that does nothing but being a plugin host),

> and very probably the 'reference host' will be something

> like that. But even on the same machine that would mean

> extra latency, and if you go over a digital audio link

> or the network even more.

>

> The whole point of 'plugins' in contrast to e.g. standalone

> Jack apps, is that they run *inside* the host.

>

> In the current design the 'rack' (the GUI application) has

> to be on the same machine as the host (the DSP part). But

> you can always forward the X11 connection and have it display

> where you want it.

>

> Ciao,

>

> --

> FA

>

> O tu, che porte, correndo si ?

> E guerra e morte !

>

Aah, riight. I misunderstood the structure of what you're doing.
Alex.
--

www.openoctave.org
midi-subscribe@openoctave.org

development-subscribe@openoctave.org

_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev