Re: [Jack-Devel] WinMME latency test

> 
> I think I have names and aliases reversed (the first four entries are
> from the ALSA audio driver):
> 
> devin@development:~/sandbox$ jack_lsp -A
> system:capture_1
>  alsa_pcm:hw:0:out1
> system:capture_2
>  alsa_pcm:hw:0:out2
> system:playback_1
>  alsa_pcm:hw:0:in1
> system:playback_2
>  alsa_pcm:hw:0:in2
> system:2-1 ESI M8U XL 1 in
>  system:midi_capture_1
> system:2-1 ESI M8U XL 2 in
>  system:midi_capture_2
> system:2-1 ESI M8U XL 3 in
>  system:midi_capture_3
> system:2-1 ESI M8U XL 4 in
>  system:midi_capture_4
> system:2-1 ESI M8U XL 5 in
>  system:midi_capture_5
> system:2-1 ESI M8U XL 6 in
>  system:midi_capture_6
> system:2-1 ESI M8U XL 7 in
>  system:midi_capture_7
> system:2-1 ESI M8U XL 8 in
>  system:midi_capture_8
> system:2-1 ESI M8U XL 1 out
>  system:midi_playback_1
> system:2-1 ESI M8U XL 2 out
>  system:midi_playback_2
> system:2-1 ESI M8U XL 3 out
>  system:midi_playback_3
> system:2-1 ESI M8U XL 4 out
>  system:midi_playback_4
> system:2-1 ESI M8U XL 5 out
>  system:midi_playback_5
> system:2-1 ESI M8U XL 6 out
>  system:midi_playback_6
> system:2-1 ESI M8U XL 7 out
>  system:midi_playback_7
> system:2-1 ESI M8U XL 8 out
>  system:midi_playback_8

This is "incorrect" ((-:, here is on OSX:

magellan:~ letz$ jack_lsp -A
system:capture_1
  dummy_pcm:dummy:out1
system:capture_2
  dummy_pcm:dummy:out2
system:playback_1
  dummy_pcm:dummy:in1
system:playback_2
  dummy_pcm:dummy:in2
system_midi:capture_1
  coremidi:Bus 1:out1
system_midi:capture_2
  coremidi:Bus 2:out2
system_midi:capture_3
  coremidi:VMidi 1:out3
system_midi:capture_4
  coremidi:VMidi 2:out4
system_midi:capture_5
  coremidi:VMidi 3:out5
system_midi:capture_6
  coremidi:VMidi 4:out6
system_midi:playback_1
  coremidi:Bus 1:in1
system_midi:playback_2
  coremidi:Bus 2:in2
system_midi:playback_3
  coremidi:VMidi 1:in3
system_midi:playback_4
  coremidi:VMidi 2:in4
system_midi:playback_5
  coremidi:VMidi 3:in5
system_midi:playback_6
  coremidi:VMidi 4:in6
magellan:~ letz$ 

I would prefer if you switch again for two reasons:

1) consistency between all backends

2) QjackCtl can be configurated to display port aliases...


> 
>> I think we should use the same strategy everywhere.
> 
> I'll change it if you want.  Is there a reason that 'names' are
> generic and 'aliases' are more detailed?


This is a simple (already working on QjackCtl Windows complied version), just go in "Setup/Display", then on the right "JACK client/port aliases" to "first"

et voila!

Stéphane

1303466823.16685_0.ltw:2,a <D4A72B93-3598-4D70-9162-7C66797A19EF at grame dot fr>