I’ve had a Midihub in my setup for a long time and because I love it so much I bought a second one and am now trying to integrate it into my setup.
I have set up the midihub for the left studio side in the editor and one for the right studio side. although I have configured the settings correctly in ableton, it sends me all midi data imm only to the same midihub. do you have any experience with multiple devices in the setup? do I have to set anything else for this?
Hey Resonotter thanks for the fast answer. Actually I don’t really understand if I have to program each Midihub with the own editor. Cause if I open the editor I can choose the hub I want program on I was thinking this should be enough
Yes, that’s right…
…and often you’ll just use the Editor on one MH at a time:
The Terminal command is there if you want to look at presets on both at the same time.
I use this particularly when I’ve got the 2 boxes talking to eachother and want to monitor flow between the two.
I might also open 2 or 3 Editors if I want to compare .mhp patches I’ve got on disk…
…or to drag useful pipelines from one patch to another
Yeah thanks that’s a nice function and helped me a lot.
The Problem is that even if I program the second one it still send all the signals to the other one
I have a Thunderbolt Hub and there 2 more hubs where the MH is connected on the left side and right side. should be any problem I think technically cause all the hubs are with a separate power supply and the thunderbolt hub supported this hubs.
I tested it now separately. every individual MH works perfect if the other is not connected
When I plug the second one in. Ableton switches imidiatly to the other one and no signal will go to the second one. All Internal Instruments changed the midi channels to the one I plugged in.
Its in ableton 12 like that. I work with external instruments. Even when the MH from the left side is choosed. It sends the midi to the right one.
When i try to select the MH its automaticls switches to the other one. feels like one is the master one the slave and ableton route automaticly everything to the master
Are you talking about sending MIDI data to Midihub via USB from Ableton? Or receiving MIDI input for Midihub to Ableton?
First try to get a bare bones Ableton project to work - create a new project with 2 MIDI tracks, make one of them send to the first port on Midihub 1 and the other to the first port on Midihub 2. Observe the activity LEDs on each unit. We expect to see the USB LED and MIDI OUT A LEDs to flash on individual units when they receive data from Ableton. Let us know what you observe.
For this test, each Midihub unit should simply have forwarding of USB data to/from the matching DIN-5 ports. (As in ‘MIDI USB interface.mhp’ available from File → Open Example…)
I see Ableton shows activity for both device’s “Ch. 1”. This is weird - how is that possible? Do the Midihub devices interconnect each other via DIN-5 MIDI?
Could you post a screenshot of how this looks like when Track 1 has the MIDI clip activated and Track 2 is stopped?
the only connection they have is the midi out a from the oxi to the MH Left and the midi out b to the MH right. and the oxo is clocked via midi in over the midi clock. So no direct connection that could interact.
First picture simulate booth midi tracks work and booth signals go to the mh right
I heard from my studio neighbors that they have as well two midi interfaces in the studio and have as well some problem that sometimes the computer can’t make a difference from one to each other. do I need to program in the audio and midi setup something special?
when I disconnect one of the MH the other works perfectly and this in booth directions. Strange I really don’t understand that thing here cause technically almost impossible
I have seen such issue on Windows only, but never on Mac OS. Nevertheless, we could try and apply the same workaround as is sometimes necessary when using multiple Midihubs with Windows.
Let’s force a different USB Product Id on one of the devices:
Cycle the Midihub device off and on again. The OS will think it’s an entirely new device, and will have an easier time differentiating with the other device.
You’ll probably have to enable it all over again in the Ableton’s MIDI settings.
Ok, very interesting, I didn’t know Mac OS exhibited the same issue as Windows before, but it will be good to know that the same workaround works there too.
and helped me a lot.
