View Issue Details

IDProjectCategoryView StatusLast Update
0009873ardourbugspublic2024-12-30 21:30
ReporterjCandlish Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
PlatformDebian GNUOSLinuxOS Version(any)
Product Version8.10 
Summary0009873: MIDI devices names are not unique for the JACK/Pipewire backend
DescriptionMIDI device names are inconsistent between the ALSA and JACK/Pipewire backend.

When using JACK/Pipewire it is not possible to differentiate Launchkey MIDI and DAW endpoints.
Steps To Reproduce. Connect a Launchkey device.
. Start Ardour with the JACK/Pipewire backend.
. Shift+Alt+M and see two devices with the same name.
TagsNo tags attached.

Activities

jCandlish

2024-12-30 14:11

reporter  

MIDI with JACK backend.png (50,793 bytes)   
MIDI with JACK backend.png (50,793 bytes)   
MIDI with ALSA backed.png (62,465 bytes)   
MIDI with ALSA backed.png (62,465 bytes)   

x42

2024-12-30 14:55

administrator   ~0029173

There's not much we can do about this; the "human readable" names is provided by JACK or pipewire to Ardour.

Under the hood there are unique port names (usually rather long), as a stopgap solution those could be shown.

Are you using JACK or pipewire? and which version?

You can check e.g.

ps ax | grep jack | grep -v grep
ps ax | grep pipewire | grep -v grep

jackd --version 2>/dev/null
pipewire --version 2>/dev/null

jCandlish

2024-12-30 16:03

reporter   ~0029174

> There's not much we can do about this;

Frustrating! I'm not above patching jack. I've puzzled several hours and can't see how best to begin.

--- version info ---
candlish@yoga-l13:~/Making_Music/Ardour/build/git/ardour$ jackd --version 2>/dev/null
jackdmp version 1.9.22 tmpdir /dev/shm protocol 9
candlish@yoga-l13:~/Making_Music/Ardour/build/git/ardour$ pipewire --version 2>/dev/null
pipewire
Compiled with libpipewire 1.2.7
Linked with libpipewire 1.2.7

Thanks

jCandlish

2024-12-30 21:27

reporter   ~0029175

This issue is resolved by replacing all jackd2 libraries with their pipewire replacements and issuing 'sudo ldconfig'

---
$ cat /etc/ld.so.conf.d/pipewire-jack-x86_64-linux-gnu.conf
/usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/
$ sudo ldconfig
---
MIDI with Pipewire backend.png (88,846 bytes)   
MIDI with Pipewire backend.png (88,846 bytes)   

jCandlish

2024-12-30 21:30

reporter   ~0029176

On Debian see /usr/share/doc/pipewire/README.Debian.gz

---

Using pipewire as a substitute for JACK
---------------------------------------

Install the pipewire-jack package.

JACK clients can be configured to output via pipewire instead of JACK.

To enable this:

* either run JACK clients using the pw-jack(1) wrapper, or copy
  /usr/share/doc/pipewire/examples/ld.so.conf.d/pipewire-jack-*.conf
  into /etc/ld.so.conf.d/ and run ldconfig as root.


Issue History

Date Modified Username Field Change
2024-12-30 14:11 jCandlish New Issue
2024-12-30 14:11 jCandlish File Added: MIDI with JACK backend.png
2024-12-30 14:11 jCandlish File Added: MIDI with ALSA backed.png
2024-12-30 14:55 x42 Note Added: 0029173
2024-12-30 16:03 jCandlish Note Added: 0029174
2024-12-30 21:27 jCandlish Note Added: 0029175
2024-12-30 21:27 jCandlish File Added: MIDI with Pipewire backend.png
2024-12-30 21:30 jCandlish Status new => closed
2024-12-30 21:30 jCandlish Resolution open => fixed
2024-12-30 21:30 jCandlish Note Added: 0029176