7/1/2023 0 Comments Midi patchbay macThen everything started to actually work. The solution was to hook up the Korg module to MIDI OUT A on the MIDI interface and change the routing in PatchBay accordingly. For some reason either the OMS driver for PatchBay or PatchBay itself cannot handle this and connecting the ports together in PatchBay doesn't cause the MIDI to flow. So I had connected the MIDI controller (my Roland JV35) to the MIDI A ports, and the module to the MIDI B OUT port. Edit #2: The trick to get everything working was the following: OMS expects that each MIDI device connected to the MIDI interface uses both an IN and OUT port.Save the patch so the settings don't get lost. Connect the OMS OUT port for the MIDI controller to the same IN port. Connect the AG Sound Editor OUT to the OMS IN port for the module. Double-click the OMS special driver icon, set the MIDI controller as a source, and the MIDI module as a destination. Use the "Test setup"-option to test the keyboard (OMS will play a message if it receives MIDI) and the module (module will play notes). Since the Korg module and my keyboard are not in OMS' library of devices, set them up manually. Connect MIDI controller and module to interface while everything is off. Then the interface needs to be set up properly in OMS.See interface show up everywhere properly. Add USB interface to OMS via "MIDI cards and interfaces"-option, reboot Classic. Start Classic, watch LEDs on interface flash. Boot Mac, observe how OS X can't see interface. Got it working as follows: Connect USB interface. Edit: Works with an old MIDIMan MidiSport 2x2 USB interface (the yellow and blue one).OMS will ask to be configured at that point. You do this by starting the AG Sound Editor after doing the previous step with the Opcode MIDI Manager Driver.
0 Comments
Leave a Reply. |