On February 22, 2010 03:38:25 pm you wrote:
> On Mon, Feb 22, 2010 at 3:24 PM, Tim E. Real <termtech@email-addr-hidden> wrote:
> > On February 22, 2010 02:56:50 pm Paul wrote:
> >> On Mon, Feb 22, 2010 at 2:27 PM, Tim E. Real <termtech@email-addr-hidden> wrote:
> >> > 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.
> >
> > 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?
>
> there's currently no established mapping from JACK MIDI port names to
> ALSA client identifiers. Given that *any* client can create ports that
> represent such a mapping, and can name them as it wishes, it would be
> unwise to rely on any such mapping.
No problem.
Sorry about the fuss in the other list the other day. I belong in LAD, and
post in the other list only if it's really important. Ignorant of procedure.
Over-enthusiastic.
Y'all monitor the same lists anyway. This one is Jack's 'connection' to us...
Now, here, we can toss around all kinds of crazy ideas, eh?
Tim.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Tue Feb 23 00:15:08 2010
This archive was generated by hypermail 2.1.8 : Tue Feb 23 2010 - 00:15:08 EET