#Ableton live and hammerspoon code#

The following just lists the real and then the virtual midi devices.Īt first with the KK turned on as last device, then turning off and on the MMMK3: Even that is not listing both devices at the same time. I used hammerspoon (nice tool on OSX i use for my desktop which has also MIDI+virtual MIDI support) to get the devices. It seems that it's not possible to use both 'Bome.' virtual devices at the same time. Maschine Mikro MK3' device is marked as '!!! N/A: Enabled+Control'. Komplete Kontrol - DAW 1' is back (and listed as because it have disabled it for reaKontrol) but the 'Bome.

Then, when i turn the KKMK2 off and on (leading to KKMK2 be the last device turned on) and i re-enter 'MIDI Devices', The 'Bome. Maschine Mikro MK3' is listed as 'Enabled+Control'. Komplete Kontrol DAW - 1' device is listed as '' and the 'Bome. When the MMMK3 is turned on as last device, the 'Bome. KG - Maschine Mikro MK3Īnd now the interesting part. I then checked the REAPER Preferences => Audio => MIDI Devices.

#Ableton live and hammerspoon code#

I added some debug code to track the problem and i saw that 'getKkMidiInput() jumps out at the 'GetMIDIInputName(.) call because the device was not present. But i now have maybe an answer how this happens. Yesterday was a little different situation because the Machine2SW was running, but the main problem still exists. I think that NIHIA simply ignores the request to get into DAW integration MIDI message mode because it wrongly assumes it should somehow give preference/focus to you sure that really no MIDI events are coming in In short: I doubt that MMMk3 captures the 'Komplete Kontrol DAW - 1' device (as this would lead to errors or even cause Reaper to crash).

This seems to unlock a 'mistaken focus' which in turn can inhibit the DAW MIDI integration. One work around is to stop NIHIA and restart NIHIA. It might even be enough for NIHIA itself to get into this state depedning on the order in which it detects supported devices. I imagine that the NIHIA code is convoluted enough to reach this state in a situation like you describe. There is definitely a feature inside of NIHIA which does just that for a good reason: If, for example, you focus Maschine on the keyboard NIHIA will not send any DAW integration MIDI messages anymore until you remove the focus from Maschine. My theory is that if another NI application talks to NIHIA via the named pipes / mach ports they can 'accidentally' put NIHIA into a state that inhibits the DAW integration via MIDI mode. Again, many people have reported that DAW integration (Cubase, Ableton, Logic, Reaper) fails and can often be solved by restarting NIHIA. the MIDI connection is established properly but NIHIA refuses/fails to get into DAW integration mode via MIDI protocol. I think what might happen in your case is that NIHIA receives the HELLO command but fails to respond with the handshake. My suspicion is another one and relates to issues reported by many NI users irrespective of which DAW they are using: This->_midiOut = CreateMIDIOutput(outDev, false, nullptr) MIDI_eventlist* list = this->_midiIn->GetReadBuf() after the devices were created I have a hunch regarding related issues but this may be not at play in the case you describe.Īre you sure that really no MIDI events are coming in I'm not sure if the MMMK3 is taking over the 'Komplete Kontrol DAW - 1' virtual no, this is not a 'known issue' to me. TL DR: The KK have to be the last device turned on when a Mikro Maschine MK3 is connected. If this is done before the reaper start, then it's working as expected.

The only thing that helps is to turn my KK off and on, wait some seconds and then, the connection is successful (which of course is not working with 2 reconnects). I even changed the CONNECT_N to 20 for a test. ) are called but the call to _onMidiEvent() with CMD_HELLO is missing (which results in the timeout then). The callbacks (SetSurfaceSelected, SetSurfaceVolume, SetSurfacePan, SetTrackListChange. When my Maschine Mikro MK3 + Komplete Kontrol S61 MK2 are both connected (and the MMK3 is turned on/initialized as last device after the KK (while booting or just when i switch the devices on manually), reaKontrol finds my KK (setting KK_MIDI_FOUND) but then runs into the timeout (KK detected but failed.). Not sure if this is OSX specific or specific to a Reaper version. Found an issue with the current version of Reaper and reaKontrol,