Re: Monitor ports - why do I want this?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Oct 05, 2024 at 12:52:13PM +0000, D.T. wrote:

> Generally speaking, this is a good explanation:
> https://en.wikipedia.org/wiki/Monitor_engineer#Foldback

No, it isn't.

IIRC [1], a 'monitor port' in the Jack world is a readable
port that provides a copy of the signal(s) arriving at the
corresponding writeable port.

Suppose you want two (or more) apps to receive the same
signal(s), for example

A->X, B->X, C->X
A->Y, B->Y, C->Y

Without monitor ports, if the set A,B,C changes, you
have to modify the connections to both X and Y.

With monitor ports, you can do

A->X, B->X, C->X
XM->Y

where XM is the monitor port for X, and you need only
to change the connections to X.

The classical example is a recording or metering app
on your playback ports.


[1] Jack used to provide optional monitor ports until
they were removed some years ago (a bad idea IMHO).
It's difficult to find documentation on them these days.

Ciao,

-- 
FA


_______________________________________________
Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux