>> So, for the ALSA client/driver, turning on "monitor" on a port means >> that it causes the data that other clients read from its port to also >> be sent to its output ports, causing the data to be audible at the >> same time. > >Does this include ports from other clients? I.e. will the engine monitor >an arbitrary port through the driver? That would be useful for debugging.
No. The "monitoring" stuff is intended, as I noted, to make efficient, easy, hw-independent access to h/w-level monitoring available. Right now, the ALSA client/driver will emulate h/w-level monitoring in software for its own ports, but I am inclined to remove that code. Whether that happens or not, the "engine" has no special access to any ports - monitoring is implemented by the clients, not the engine. --p
