#Midi patchbay mac full
#Midi patchbay mac software
#Midi patchbay mac windows

Didn't have a look at MTC sync after the 'fix', so maybe MTC was affected by rounding, too and thus the two instances could sync so perfectly against each other.

#Midi patchbay mac full

That was before they 'fixed' Live's Midi slave behavior though, from rough rounding to the next full integer BPMs to unrounded very bad calculation that's mostly off. Ableton support denies that this would be possible, but obviously it was back when I tested it. Now comes the interesting part: Both instances of Live were MTC slave synced to a single instance of Midi-Ox via MidiYoke running on the very same computer.Ĭomplete cancellation, which to me looks like sample accurate synchronisation. Both pairs were digitally summed via Totalmix for output.

#Midi patchbay mac windows

You may be interested in one of my many irrelevant but inevitable testings (I did this one last year when looking for trouble with Ableton, literally):Ģ x Ableton Live running on Windows Vista, each using their own stereo output pair of a FF400, both playing the same audio files, but one phase inverted. I know it's only got three ports, but still these occasions come up where you want to feed the same signal to more than one midi output. In MC's 'copious' spare time, it would be nice for him to make up a small router utility for the RME MADI Midi that would enhance its utility. The day will come.Īnd this brings up a point.

#Midi patchbay mac software

But it's good to have your references for software midi routers on the PC. Now I have my extra physical connection and no worry about software routing and reliability. I routed the MTC out of a spare port on my MOTU midi express (Mac) and boom, it's done. I ran another long midi cable from the studio into the machine room. However, yesterday I decided to take the hardware route because it is reliable and doesn't eat into any CPU cycles. Thanks to you I just visited the LoopB page and this appears to be so much more intriguing and simple yet powerful for my purposes than the overcomplicated MIDI-OX and MIDI-Yoke. LoopBe is quite interesting in that it offers upto 30 channels, looks actively maintained and the same developer also offers a Midi over Ethernet solution. Usually it works out quite well though.Īlternatives to MidiYoke are Maple Midi (which caused me trouble) and LoopBe. I had some minor stability troubles with the combination of MidiYoke and Ableton Live. Detection of Midi Feedback is configurable with three different methods being offered (including turning off). This can be quite useful if you are routing several inputs to a single virtual port or just sending lots of Midi events into software that can deal with it. Midi Yoke offer bandwidth upto 16x of what the Midi standard allows over the sum of all ports downto a single port.

The main drawbacks of both are that they seemingly are not actively maintained anymore and that they only support MME but not DirectMusic. Actually I know no other Midi software offering all that Midi-OX has to offer. MidiYoke (aka virtual Midi port driver) and Midi-OX (aka Midi routing, monitoring, Sysex, filter, Midi Sync and MTC) are more or less the standard on PC.