17 Dec
2006
17 Dec
'06
8:38 p.m.
It seems that the qjackctl patchbay only works with clients as a whole -
you cannot selectively connect individual ports within a client. I'd
just like to verify that this is really true.
If the connections in the "Connections" dialog were saved as a
configuration file, that would help, but I think that this is not the case.
The reason for this question is that it seems that pd cannot generate
multiple jack clients, and I want to route more than one qsynth engine
into it.
In the meantime, I am setting up scripts that use jack_connect and
aconnect, but this is a bit tedious. I'm using DeMuDi 1.2 (I don't know
why I waited so long to try it!)
So, if anyone has suggestions or clarifications, I'd be very grateful.
Thanks as always to the list members for their unfailing help and
suggestions.
Larry
17 Dec
17 Dec
9:20 p.m.
New subject: [linux-audio-user] qjackctl patchbay - individual ports of a client?
On 12/17/06, Larry Troxler <lt(a)westnet.com> wrote:
It seems that the qjackctl patchbay only works with
clients as a whole -
you cannot selectively connect individual ports within a client. I'd
just like to verify that this is really true.
Not true. In the QJC connections window, if you click on the (+) next
to a client, it will expand a display of all its input or output ports. These
can be connected or disconnected individually.
If the connections in the "Connections"
dialog were saved as a
configuration file, that would help, but I think that this is not the case.
The QJC patchbay may be able to do what you want. Perhaps others
can explain how, I am not up on its use.
--
joq
9:34 p.m.
New subject: [linux-audio-user] qjackctl patchbay - individual ports of a client?
On Sun, Dec 17, 2006 at 07:20:44PM -0600, Jack O'Quin wrote:
The QJC patchbay may be able to do what you want.
Perhaps others
can explain how, I am not up on its use.
As I understood it, the OP's question was about the patchbay, not
the connection window.
--
FA
Lascia la spina, cogli la rosa.
9:31 p.m.
New subject: [linux-audio-user] qjackctl patchbay - individual ports of a client?
On Sun, Dec 17, 2006 at 07:37:40PM -0500, Larry Troxler wrote:
It seems that the qjackctl patchbay only works with
clients as a whole -
you cannot selectively connect individual ports within a client. I'd
just like to verify that this is really true.
No, it can connect individual ports, but the required incantations are not
very intuitive. I always forget the procedure so I never use it.
If the connections in the "Connections"
dialog were saved as a
configuration file, that would help, but I think that this is not the case.
There is command line app that provides this, called jsnap. Just use this
together with qjackctl instead of the patchbay.
--
FA
Lascia la spina, cogli la rosa.
18 Dec
18 Dec
6:51 a.m.
New subject: [linux-audio-user] qjackctl patchbay - individual ports of a client?
On Mon, December 18, 2006 00:37, Larry Troxler wrote:
It seems that the qjackctl patchbay only works with
clients as a whole -
you cannot selectively connect individual ports within a client. I'd just
like to verify that this is really true.
No it isn't.
If the connections in the "Connections"
dialog were saved as a
configuration file, that would help, but I think that this is not the
case.
The reason for this question is that it seems that pd cannot generate
multiple jack clients, and I want to route more than one qsynth engine
into it.
In the meantime, I am setting up scripts that use jack_connect and
aconnect, but this is a bit tedious. I'm using DeMuDi 1.2 (I don't know
why I waited so long to try it!)
So, if anyone has suggestions or clarifications, I'd be very grateful.
QjackCtl patchbay can do what you want, I'm almost sure ;)
Take note of this, when regarding your approach to the Patchbay model:
1) You group all _or_ just a sub-set of ports into a so called patchbay
socket. A socket is an ordered group of all or some client ports. You can
have as many sockets as you want pointing to the _same_ client, but it is
worthwhile to note that having duplicated sockets for the same client with
the very same set of ports is just redundant.
2) You declare to connect sockets, not clients. When two sockets are said
connected, that is regarded as a declarative rule to automatiically
connect those respective client-ports, one-by-one in that precise order.
Again, the rule states for connecting ports, not just clients.
3) You're probably relying on the bare snapshot that is created while you
set a new Patchbay definition. This snapshot is a rough and skewed image
of your current client-port connections, that you _must_ regard just as a
convenient starting point. Do not take it for granted OOTB. On most if not
all situations you'll need to duplicate some sockets, trim each socket
port list, reorder, and edit the connections between the intentional port
groups (aka sockets).
4) You can edit and add sockets that refer to client/ports that aren't
actually running, although it surely helps to get the client/port names
right. Client names can be entered as regular expressions while you edit a
socket definition. This is most convenient for matching those clients that
have some pseudo-random number in their name suffixes (e.g xmms-jack pid).
5) The Patchbay rules are then only effective after you save and activate it.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
6553
days inactive
6554
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Fons Adriaensen -
Jack O'Quin -
Larry Troxler -
Rui Nuno Capela