Open paum3 opened 2 years ago
I would like to see such a feature implemented as well. I think of something more general, like this example:
cadence-jackmeter \
--client-name meters \
--color-scheme cyan \
--add-connect system:capture_1 \
--add-connect system:capture_2 \
--color-scheme green \
--add-connect system:monitor_1 \
--add-connect system:monitor_2
Proposed semantics, in that order:
meters
.--color-scheme cyan
shall use the "cyan" color scheme. (Think of that color theme as the one used when, currently, you pass -in
.)system:capture_1
.system:capture_2
.--color-scheme green
shall use the "green" color scheme. (Think of that color theme as the one used when, currently, you pass no args.)system:monitor_1
.system:monitor_2
.This should give me one JACK client called meters
with four input ports, each one connecting to the respective client's port, affecting four meters, displayed from left to right in the order added, using different color schemes as described.
What you currently get when simply calling cadence-jackmeter
(but generalized to all playback ports instead of just two) might then look like this:
cadence-jackmeter \
--client-name M \
--color-scheme green \
--watch '*:*' 'system:playback_*'
And what you currently get when calling cadence-jackmeter -in
(but generalized to all capture ports instead of just two) might then look like this:
cadence-jackmeter \
--client-name Mi \
--color-scheme cyan \
--watch '*:*' 'system:capture_*'
The idea expressed in both cases is similar: Watch all clients ('*:*
) for connecting to or disconnecting from system:playback_*
and system:capture_*
, respectively, and connect and disconnect the meters accordingly.
Hi,
It would be great if
cadence-jackmeter
could respond to number audio channels. It seems two ins and outs are hardcoded. thank youpaum