Midi patchbay os x 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):Setup:2 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.And this brings up a point.
Midi patchbay os x software#
Now I have my extra physical connection and no worry about software routing and reliability.īut it's good to have your references for software midi routers on the PC.
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. I've taken note of LoopB.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.Alternatives to MidiYoke are Maple Midi (which caused me trouble) and LoopBe. Detection of Midi Feedback is configurable with three different methods being offered (including turning off).I had some minor stability troubles with the combination of MidiYoke and Ableton Live. 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. Actually I know no other Midi software offering all that Midi-OX has to offer.The main drawbacks of both are that they seemingly are not actively maintained anymore and that they only support MME but not DirectMusic.Midi Yoke offer bandwidth upto 16x of what the Midi standard allows over the sum of all ports downto a single port. 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. In other words, a 'MIDI y cord' OR a software utility that will allow me to route MTC to two destinations, the first out MADI midi port 1 and the second out a virtual port that I can read on another application.I found something called midi-ox and midi-yoke but would like some recommendations before experimenting with the unknown, if possible.Thanks,Bob Katz. I'd simply like to route MTC out from Sequoia out two MIDI ports at once. And the ability to turn that processor/filter on and off easily, so I can disable the surface's motorfaders when I need it to be absolutely silent.Īnd because control surface messages doesn't go through tracks in a typical DAW (barring complex contortions - sure), a VST MIDI processor won't help.īome's MIDI Translator does all this (although a maximum of 5 virtual ports is a bit cheap), but it is too buggy for the heart of my workstation it needs to I would love to beta test your products.Can anyone recommend a simple software MIDI patchbay (for Windows XP) that will work with the RME MADI MIDI. The most urgent application for that would be: set a virtual port as surface control in my DAW -> filter out fader messages coming from the DAW to that port -> forward the resulting MIDI to the actual surface control's hardware port. I need a MIDI processor (a the very least a MIDI filter) I can insert between ports.
Midi patchbay os x Patch#
Thus, each application could open a different virtual port, and then the patch would merge the virtual ports to one hardware port (or split an hardware port to several virtual ones) So, I would need a matrix patch that can also create (many) virtual ports. That was no problem on Mac, but it is one of Windows' limitation that really bothers me.
That is a problem for several reasons - suffices to say I need several applications to recieve from or send to sometimes the same hardware port at the same time. However the issue would be the same if I had only one: in Windows, not two applications can open the same port simultaneously. I have many (and I mean many) hardware MIDI ports because my studio is a fat hardware synth orgy. What I need to do is this - basically 2 things :
0 kommentar(er)
