Re: [ecasound] Ecasound and jack (and chains)

From: Claude Heiland-Allen <claudiusmaximus@email-addr-hidden>
Date: Tue Aug 17 2010 - 04:20:52 EEST

On 16/08/10 22:48, Philipp wrote:


> a) issue jack-list-connections


> Another smaller, related issue, jack-connect requires:
> jack-connect<outport> <inport>


Hm, `jack_lsp -cp` lists connections with port properties (like input,
output, etc) - maybe that's one option (but requires calling a command
that might not be installed). Or ecasound could be extended to add that
information too, but that might break other clients unless it's
optional. And even then, maybe it's not that useful as you know
ecasound's input/output port names anyway?

In any case, perhaps qjackctl's patchbay (or something similar is better
designed for this very sort of thing?

You can define regexp rules for connections and then when clients start
up they are connected appropriately. I don't know if there is an easy
way to clone the current state of the system into a set of patchbay
rules, however - maybe someone who's used it for more than 10 minutes
can tell you :)

The patchbay file format seems to be XML text, so it should be possible
for an external tool to take a snapshot of the current state into
something that the qjackctl patchbay can understand.

Some scenarious might want a qjackctl-style patchbay that runs without
X, but I don't know if that exists.


This email is sponsored by 
Make an app they can't live without
Enter the BlackBerry Developer Challenge 
Ecasound-list mailing list
Received on Tue Aug 17 08:15:02 2010

This archive was generated by hypermail 2.1.8 : Tue Aug 17 2010 - 08:15:02 EEST