as far as I can see in the bluez package source, the midi option is enabled now, so it *could* be closed...
But even though it's on, I dont get it working, so I cannot confirm for sure. Expectation is: when connecting to a device, I get an alsa sequencer client, but I dont see that happening. But also I am not sure if I use it correctly, as i see nearly no documentation about it, despite one place that said what I mentioned above in what I expect to happen. I dont even know for sure if this direction is supposed to be unidirectional or bi-directional. (e.g. if my laptop can be the midi host, device or both). I'll keep trying. If anyone has a pointer to docs how it is really supposed to work, so i can confirm, it would be helpful and this ticket could be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
