18 Jan
2004
18 Jan
'04
7:23 p.m.
On Fri, 2004-01-16 at 16:06, Marcus Andersson wrote:
Dave Robillard wrote:
...
Like I mentioned earlier, having jack used for every connection in, say,
a modular synth, would make your jack patching too complicated to be
useful. This most definatley would not be easier to use.
Plugins in an app and connecting different apps is just different,
period. I can't think of any reason to pretend otherwise - it certainly
doesn't make things easier from a user perspective.
If you want a jack audio out somewhere in your synth.... put one there.
You can't possibly be arguing that this is too difficult?
-Dave
But you're mashing the ideas of modules in an
app and connecting
multiple apps together - different problems. A jack patch bay that
works like a modular would definately be cool, but a totally different
project.
From a user's point of view, why should it be different problems? I
would want an application that presents both Jack clients and LADSPA
plugins as modules, and let me connect them however I want. There is no
reason I should have to instantiate "Jack IO modules" to access other
applications. Those ports should be created implicitly by the program
when I connect a LADSPA plugin and a Jack application.
I understand that for efficiency, it is probably not a good idea to
route all signals through jackd, but the choice of routing path should
be handled automatically by the application and not by the user.