Hi Robert, On Sun, May 20, 2018 at 4:46 PM Robert Schneider <Robert.Schneider@xxxxxxxxx> wrote: > On 20.05.2018 14:14, Luiz Augusto von Dentz wrote: > [...] > > The info says: > >> [bluetooth]# info 60:F1:89:28:DA:1F > >> Device 60:F1:89:28:DA:1F (public) > >> Name: nanoKONTROL Studio > >> Alias: nanoKONTROL Studio > >> Appearance: 0x0080 > >> Icon: computer > >> Paired: no > >> Trusted: yes > >> Blocked: no > >> Connected: no > >> LegacyPairing: no > >> UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) > >> UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) > >> UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) > >> UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700) > >> UUID: Vendor specific (d0611e78-bbb4-4591-a5f8-487910ae4366) > > From the looks of it seems the device is not using the standard MIDI > > service but vendor specific ones which don't have support. > Hm, 03b80e5a-ede8-4b33-a751-6ce34ec4c700 seems to be the MIDI service, doesn't > it? It is listed up there, as a Vendor specific code, though. You are right: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/profiles/midi/libmidi.h#n32 Perhaps it is the MIDI_IO_UUID that is missing, we should probably add decoders for these so they are not shown as Vendor specific. > [...] -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
