[Question] MIDI into MidiMonster on Mac OS X? #116

Activity

1. Spacelord09

   added

   backendBackend issuesBackend issues

   KnowledgeBase

   question

   on Jun 15, 2022
2. Spacelord09 commented on Jun 15, 2022

   

   Spacelord09

   on Jun 15, 2022

   Collaborator

   More actions

   Hey @grahamhr,
   I think you mean our rtp-midi backend that can communicate directly with apple's midi subsystem over the network.

   If you want, you can share a working tutorial at our KnowledgeBase that can help users with the same Problem!

   If you need more help, just ask here ;-)
3. grahamhr commented on Jun 15, 2022

   

   grahamhr

   on Jun 15, 2022

   Author

   More actions

   @Spacelord09 Thanks for the tip!

   I didn't realize that rtpmidi is the default/normal Mac OS MIDI backend - is that true?

   I thought rtpmidi was for a more-esoteric multi-computer IP network situation, and not for a single computer MIDI -> MidiMonster -> anything, e.g. Midi out of Live into Art-Net/DMX.

   Once I get this working, I'm happy to contribute a detailed tutorial - I suspect Ableton Live on Mac (or any other MIDI source on Mac) to Art-Net/DMX is a pretty common use-case for MidiMonster.
4. Spacelord09 commented on Jun 15, 2022

   

   Spacelord09

   on Jun 15, 2022

   Last edited by Spacelord09

   Collaborator

   More actions

   @Spacelord09 Thanks for the tip!

   @grahamhr No problem, glad that I can help you ;-)

   I didn't realize that rtpmidi is the default/normal macOS MIDI backend - is that true?

   I'm not a Mac user myself, so I can't say 100%.
   But I think that it is currently the only possibility to interact directly with the (you called it:)"Core MIDI" on Apple devices. (Speak without installing jack.)

   I thought rtpmidi was for a more-esoteric multi-computer IP network situation, and not for a single computer MIDI -> MidiMonster -> anything, e.g. Midi out of Live into Art-Net/DMX.

   It can be used for multi-computer setups, but it's not a requirement. It should work on any single-pc setup.

   Once I get this working, I'm happy to contribute a detailed tutorial - I suspect Ableton Live on Mac (or any other MIDI source on Mac) to Art-Net/DMX is a pretty common use-case for MidiMonster.

   That would be perfect 👍🏻

   If you want you can join our Discord.
5. cbdevnet commented on Jun 19, 2022

   

   cbdevnet

   on Jun 19, 2022

   Owner

   More actions

   Hi @grahamr, sorry for replying so late and thanks for your interest in the MIDIMonster!

   Indeed on OSX currently jack is the best-supported option (as it is usable cross-platform), along with rtpmidi for networked Apple devices. For input from the local host (as with Ableton), the jack backend would probably be best-suited.

   A dedicated Core MIDI backend for OSX might eventually be the best option, but I currently don't have the Hardware to do that.
6. grahamhr commented on Jun 19, 2022

   

   grahamhr

   on Jun 19, 2022

   Author

   More actions

   @cbdevnet Thanks for the guidance - I really appreciate it! I'll keep moving forward with both Jack and rtpmidi and see where I can get to.

   Do you happen to know anyone who has setup a working MIDI >> MidiMonster setup on OSX?
7. Solander commented on Nov 21, 2022

   

   Solander

   on Nov 21, 2022

   Last edited by Solander

   Contributor

   More actions

   @grahamhr Did you get this to work? I've tried installing Jack, but no MIDI devices are showing up so I'm pretty stuck.. :/
   A native MIDI backend for OSX would be preferable but I get that it's an open-source project and that may take a while.
8. emmaworley commented on Nov 21, 2023

   

   emmaworley

   on Nov 21, 2023

   Last edited by emmaworley

   More actions

   I got this working today. Here's an example config:

   [backend jack]
   errors = on
   
   [jack j]
   name = MIDIMonster
   midi_in = midi in
   midi_out = midi out
   
   [map]
   j.midi_in.ch{0..15}.note{1..127} > j.midi_out.ch{0..15}.note{1..127}
   

   The key is to connect MIDIMonster's ports to autogenerated Core MIDI ports. Run MIDIMonster, then inspect with jack_lsp:

   ~ jack_lsp -Ac
   system:capture_1
      coreaudio::out_1
   system:playback_1
      coreaudio::in_11
   system:playback_2
      coreaudio::in_22
   system_midi:capture_1
      coremidi:TRAKTOR X1 MK3:out1
   system_midi:capture_2
      coremidi:virtual1:out2
   system_midi:capture_3
      coremidi:virtual2:out3
   system_midi:playback_1
      coremidi:TRAKTOR X1 MK3:in1
   MIDIMonster:midi_in
   MIDIMonster:midi_out
   system_midi:playback_2
      coremidi:virtual1:in2
   system_midi:playback_3
      coremidi:virtual2:in3
   

   Then make connections:

   ~ jack_connect 'coremidi:TRAKTOR X1 MK3:out1' MIDIMonster:midi_in
   ~ jack_connect MIDIMonster:midi_out coremidi:virtual1:in2
   

   Now in my case, MIDIMonster is forwarding notes from the TRAKTOR X1 MK3 device to the virtual1 device.