* KORG nanoKONTROL Studio ... again
@ 2018-05-19 13:41 Robert Schneider
2018-05-20 12:14 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 6+ messages in thread
From: Robert Schneider @ 2018-05-19 13:41 UTC (permalink / raw)
To: linux-bluetooth
After pausing for some time and waiting for Ubuntu 18.04, I thought I give MIDI
over Bluetooth to my KORG nanoKONTROL Studio another try. However, to no avail.
Still I cannot make the device show up in the MIDI device list.
Here are some outputs from bluetoothctl. If anyone can help, I'd appreciate that.
Regards, Robert
The devices shows up:
[bluetooth]# devices
Device 60:F1:89:28:DA:1F nanoKONTROL Studio
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)
connect says:
[bluetooth]# connect 60:F1:89:28:DA:1F
Attempting to connect to 60:F1:89:28:DA:1F
[CHG] Device 60:F1:89:28:DA:1F Connected: yes
Connection successful
[NEW] Primary Service
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
[NEW] Descriptor
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d/desc000f
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010
0000180a-0000-1000-8000-00805f9b34fb
Device Information
[NEW] Characteristic
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0011
00002a29-0000-1000-8000-00805f9b34fb
Manufacturer Name String
[NEW] Characteristic
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0013
00002a24-0000-1000-8000-00805f9b34fb
Model Number String
[NEW] Primary Service
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015
d0611e78-bbb4-4591-a5f8-487910ae4366
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016
8667556c-9a37-4c91-84ed-54ee27d90049
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016/desc0018
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019
03b80e5a-ede8-4b33-a751-6ce34ec4c700
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019/char001a
7772e5db-3868-4112-a1a9-f2669d106bf3
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019/char001a/desc001c
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[CHG] Device 60:F1:89:28:DA:1F ServicesResolved: yes
Now info says:
[nanoKONTROL Studio]# 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: yes
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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KORG nanoKONTROL Studio ... again
2018-05-19 13:41 KORG nanoKONTROL Studio ... again Robert Schneider
@ 2018-05-20 12:14 ` Luiz Augusto von Dentz
2018-05-20 13:46 ` Robert Schneider
0 siblings, 1 reply; 6+ messages in thread
From: Luiz Augusto von Dentz @ 2018-05-20 12:14 UTC (permalink / raw)
To: Robert.Schneider; +Cc: linux-bluetooth@vger.kernel.org
Hi Robert,
On Sat, May 19, 2018 at 4:43 PM Robert Schneider
<Robert.Schneider@aramar.de>
wrote:
> After pausing for some time and waiting for Ubuntu 18.04, I thought I
give MIDI
> over Bluetooth to my KORG nanoKONTROL Studio another try. However, to no
avail.
> Still I cannot make the device show up in the MIDI device list.
> Here are some outputs from bluetoothctl. If anyone can help, I'd
appreciate that.
> Regards, Robert
> The devices shows up:
> [bluetooth]# devices
> Device 60:F1:89:28:DA:1F nanoKONTROL Studio
> 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.
> connect says:
> [bluetooth]# connect 60:F1:89:28:DA:1F
> Attempting to connect to 60:F1:89:28:DA:1F
> [CHG] Device 60:F1:89:28:DA:1F Connected: yes
> Connection successful
> [NEW] Primary Service
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c
> 00001801-0000-1000-8000-00805f9b34fb
> Generic Attribute Profile
> [NEW] Characteristic
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d
> 00002a05-0000-1000-8000-00805f9b34fb
> Service Changed
> [NEW] Descriptor
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d/desc000f
> 00002902-0000-1000-8000-00805f9b34fb
> Client Characteristic Configuration
> [NEW] Primary Service
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010
> 0000180a-0000-1000-8000-00805f9b34fb
> Device Information
> [NEW] Characteristic
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0011
> 00002a29-0000-1000-8000-00805f9b34fb
> Manufacturer Name String
> [NEW] Characteristic
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0013
> 00002a24-0000-1000-8000-00805f9b34fb
> Model Number String
> [NEW] Primary Service
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015
> d0611e78-bbb4-4591-a5f8-487910ae4366
> Vendor specific
> [NEW] Characteristic
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016
> 8667556c-9a37-4c91-84ed-54ee27d90049
> Vendor specific
> [NEW] Descriptor
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016/desc0018
> 00002902-0000-1000-8000-00805f9b34fb
> Client Characteristic Configuration
> [NEW] Primary Service
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019
> 03b80e5a-ede8-4b33-a751-6ce34ec4c700
> Vendor specific
> [NEW] Characteristic
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019/char001a
> 7772e5db-3868-4112-a1a9-f2669d106bf3
> Vendor specific
> [NEW] Descriptor
> /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0019/char001a/desc001c
> 00002902-0000-1000-8000-00805f9b34fb
> Client Characteristic Configuration
> [CHG] Device 60:F1:89:28:DA:1F ServicesResolved: yes
> Now info says:
> [nanoKONTROL Studio]# 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: yes
> 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)
> --
> To unsubscribe from this list: send the line "unsubscribe
linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KORG nanoKONTROL Studio ... again
2018-05-20 12:14 ` Luiz Augusto von Dentz
@ 2018-05-20 13:46 ` Robert Schneider
2018-05-20 14:29 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 6+ messages in thread
From: Robert Schneider @ 2018-05-20 13:46 UTC (permalink / raw)
To: Luiz Augusto von Dentz, linux-bluetooth@vger.kernel.org
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.
[...]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KORG nanoKONTROL Studio ... again
2018-05-20 13:46 ` Robert Schneider
@ 2018-05-20 14:29 ` Luiz Augusto von Dentz
2018-05-20 14:35 ` Robert Schneider
0 siblings, 1 reply; 6+ messages in thread
From: Luiz Augusto von Dentz @ 2018-05-20 14:29 UTC (permalink / raw)
To: Robert.Schneider; +Cc: linux-bluetooth@vger.kernel.org
Hi Robert,
On Sun, May 20, 2018 at 4:46 PM Robert Schneider
<Robert.Schneider@aramar.de>
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KORG nanoKONTROL Studio ... again
2018-05-20 14:29 ` Luiz Augusto von Dentz
@ 2018-05-20 14:35 ` Robert Schneider
2018-05-23 17:23 ` Robert Schneider
0 siblings, 1 reply; 6+ messages in thread
From: Robert Schneider @ 2018-05-20 14:35 UTC (permalink / raw)
To: Luiz Augusto von Dentz; +Cc: linux-bluetooth@vger.kernel.org
On 20.05.2018 16:29, Luiz Augusto von Dentz wrote:
I just figured, that the Ubuntu bluez seems to be build without midi support.
Its bluetoothd does not list libasound as a library. Isn't that an indicator
that midi was not compiled into it?
So I guess I need to create a build env first in order to build a bluez with
midi support.
> Hi Robert,
> On Sun, May 20, 2018 at 4:46 PM Robert Schneider
> <Robert.Schneider@aramar.de>
> 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.
>
>
>> [...]
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KORG nanoKONTROL Studio ... again
2018-05-20 14:35 ` Robert Schneider
@ 2018-05-23 17:23 ` Robert Schneider
0 siblings, 0 replies; 6+ messages in thread
From: Robert Schneider @ 2018-05-23 17:23 UTC (permalink / raw)
To: linux-bluetooth@vger.kernel.org
Hi all,
I did some more testing today, after compiling a bluetoothd that has MIDI
support, the device now shows up in the alsa MIDI devices list, however,
communication fails. As I am not savvy enough to interpret this, could someone
more technically involved shed some light on this for me?
I see that "bonding" fails with status 5. But that doesn't tell me anything.
Especially, I would be interested in how I could solve that issue.
Thanks in advance and regards,
Robert
bluetoothd[890]: src/device.c:device_probe_profiles() Probing profiles for
device 60:F1:89:28:DA:1F
bluetoothd[890]: profiles/midi/midi.c:midi_device_probe() MIDI GATT Driver
profile probe (60:F1:89:28:DA:1F)
bluetoothd[890]: src/service.c:change_state() 0x5649f05dc240: device
60:F1:89:28:DA:1F profile MIDI GATT Driver state changed: unavailable ->
disconnected (0)
bluetoothd[890]: src/device.c:device_set_auto_connect() 60:F1:89:28:DA:1F auto
connect: 1
bluetoothd[890]: src/device.c:device_set_auto_connect() Already connected
bluetoothd[890]: profiles/midi/midi.c:midi_accept() MIDI GATT Driver profile
accept (60:F1:89:28:DA:1F)
bluetoothd[890]: profiles/midi/midi.c:handle_midi_io() MIDI I/O handle: 0x001b
bluetoothd[890]: src/service.c:change_state() 0x5649f05dc240: device
60:F1:89:28:DA:1F profile MIDI GATT Driver state changed: disconnected ->
connected (0)
bluetoothd[890]: src/service.c:btd_service_ref() 0x5649f05dc240: ref=2
bluetoothd[890]: plugins/policy.c:service_cb() Added MIDI GATT Driver reconnect 0
bluetoothd[890]: src/gatt-client.c:btd_gatt_client_ready() GATT client ready
bluetoothd[890]: src/gatt-client.c:create_services() Exporting objects for GATT
services: 60:F1:89:28:DA:1F
bluetoothd[890]: src/gatt-client.c:service_create() Exported GATT service:
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c
bluetoothd[890]: src/gatt-client.c:characteristic_create() Exported GATT
characteristic: /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d
bluetoothd[890]: src/gatt-client.c:descriptor_create() Exported GATT
characteristic descriptor:
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service000c/char000d/desc000f
bluetoothd[890]: src/gatt-client.c:service_create() Exported GATT service:
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010
bluetoothd[890]: src/gatt-client.c:characteristic_create() Exported GATT
characteristic: /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0011
bluetoothd[890]: src/gatt-client.c:characteristic_create() Exported GATT
characteristic: /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0010/char0013
bluetoothd[890]: src/gatt-client.c:service_create() Exported GATT service:
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015
bluetoothd[890]: src/gatt-client.c:characteristic_create() Exported GATT
characteristic: /org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016
bluetoothd[890]: src/gatt-client.c:descriptor_create() Exported GATT
characteristic descriptor:
/org/bluez/hci0/dev_60_F1_89_28_DA_1F/service0015/char0016/desc0018
bluetoothd[890]: src/device.c:device_svc_resolved()
/org/bluez/hci0/dev_60_F1_89_28_DA_1F err 0
bluetoothd[890]: src/adapter.c:add_device_complete() 60:F1:89:28:DA:1F (1) added
to kernel connect list
bluetoothd[890]: src/device.c:gatt_debug() Registered handler for "Service
Changed": 1
bluetoothd[890]: profiles/gap/gas.c:read_device_name_cb() GAP Device Name:
nanoKONTROL Studio
bluetoothd[890]: profiles/gap/gas.c:read_appearance_cb() GAP Appearance: 0x0080
bluetoothd[890]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr
60:F1:89:28:DA:1F type 1 status 0x5
bluetoothd[890]: src/device.c:device_bonding_complete() bonding (nil) status 0x05
bluetoothd[890]: src/device.c:device_bonding_failed() status 5
bluetoothd[890]: src/adapter.c:resume_discovery()
bluetoothd[890]: src/adapter.c:dev_disconnected() Device 60:F1:89:28:DA:1F
disconnected, reason 2
bluetoothd[890]: src/adapter.c:adapter_remove_connection()
bluetoothd[890]: plugins/policy.c:disconnect_cb() reason 2
bluetoothd[890]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr
60:F1:89:28:DA:1F type 1 status 0xe
bluetoothd[890]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
bluetoothd[890]: src/device.c:device_bonding_failed() status 14
bluetoothd[890]: src/adapter.c:resume_discovery()
bluetoothd[890]: MIDI I/O: Failed to read initial request
bluetoothd[890]: src/device.c:att_disconnected_cb()
bluetoothd[890]: src/device.c:att_disconnected_cb() Software caused connection
abort (103)
bluetoothd[890]: src/service.c:change_state() 0x5649f05ce090: device
60:F1:89:28:DA:1F profile gap-profile state changed: connected -> disconnecting (0)
bluetoothd[890]: src/service.c:change_state() 0x5649f05ce090: device
60:F1:89:28:DA:1F profile gap-profile state changed: disconnecting ->
disconnected (0)
bluetoothd[890]: src/service.c:change_state() 0x5649f05dbe30: device
60:F1:89:28:DA:1F profile deviceinfo state changed: connected -> disconnecting (0)
bluetoothd[890]: src/service.c:change_state() 0x5649f05dbe30: device
60:F1:89:28:DA:1F profile deviceinfo state changed: disconnecting ->
disconnected (0)
bluetoothd[890]: src/service.c:change_state() 0x5649f05dc240: device
60:F1:89:28:DA:1F profile MIDI GATT Driver state changed: connected ->
disconnecting (0)
bluetoothd[890]: profiles/midi/midi.c:midi_disconnect() MIDI GATT Driver profile
disconnect (60:F1:89:28:DA:1F)
bluetoothd[890]: src/service.c:change_state() 0x5649f05dc240: device
60:F1:89:28:DA:1F profile MIDI GATT Driver state changed: disconnecting ->
disconnected (0)
bluetoothd[890]: src/gatt-client.c:btd_gatt_client_disconnected() Device
disconnected. Cleaning up.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-05-23 17:23 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-19 13:41 KORG nanoKONTROL Studio ... again Robert Schneider
2018-05-20 12:14 ` Luiz Augusto von Dentz
2018-05-20 13:46 ` Robert Schneider
2018-05-20 14:29 ` Luiz Augusto von Dentz
2018-05-20 14:35 ` Robert Schneider
2018-05-23 17:23 ` Robert Schneider
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).