22 Feb
2010
22 Feb
'10
4:34 p.m.
On February 22, 2010 02:56:50 pm Paul wrote:
On Mon, Feb 22, 2010 at 2:27 PM, Tim E. Real
<termtech(a)rogers.com> wrote:
Back to the drawing board. I
thought that was the exception not the rule.
So there's no way to tell if a Jack system port actually belongs to (our own)
ALSA client?
I guess there's nothing technically wrong with listing our own ALSA ports.
Bizarre - It would allow feeding the app's own ALSA ports back into
the app as Jack midi ports. Might have its uses...
Good day...
Just coming to grips working with and learning the alias system...
Under what conditions might a Jack port not have any alias names?
When might I expect to encounter that situation?
You should never assume the existence of any aliases.