![4x4 midi patchbay 4x4 midi patchbay](https://4.bp.blogspot.com/-Ps-2VpSs1RI/XscP6z9jlMI/AAAAAAANKGs/Sb5d-SjSGT8H12d7OV3o731fEXh4qAqTQCNcBGAsYHQ/s1600/cspwiwaujhbq0d0kmn1c.jpg)
#4x4 midi patchbay Pc#
Neither is NOT AN IDEAL path since there would some MIDI signal delay (3 to 5 ms per in to out) by time signal got from PC to last device of about 15ms - so putting drums last was a dumb example on my part - but you get the "picture" MIDIsport Port 1 -> JV-30 OUT (not THRU) -> JV880 THRU out -> MVS-1 THRU out-> EMU Proteus FX THRU out -> MBD-1 Drum/Bass
![4x4 midi patchbay 4x4 midi patchbay](https://www.muzines.co.uk/images_mag/articles/sos/SOS_93_06_atari_notes_2_large.jpg)
When NOT connected to PC or the MIDISPORT is OFF: MIDIsport Port 1 -> JV-30 THUR out -> JV880 THRU out -> MVS-1 THRU out-> EMU Proteus FX THRU out -> MBD-1 Drum/BassĢ. When connected to PC for Sonar (or other DAW use): If the answer is NO you can not then maybe IF you put device THRU to next device IN then you could drive everything with the JV-30 even with MidiSport and PC off? You want to use the THUR's so you don't have to worry about control channels (as much)ġ. I would strongly advise anyone thinking of purchasing it to not do so.Before I can make suggestions - why do you have each MIDI device on separate MidiSport ports?Īlso I fairly certain the 4x4 doe NOT have a "merge" feature: i.e., when PC is off or not connected there is NOT WAY to route MIDI data from a controller, e.g., JV30 into the 4x4 and out to other devices - is there? An utter waste of money if you want to use it as a patchbay / router. I am not sure if it will make a difference.Īll in all, MOTU is the worst company I have ever dealt with and the MIDI Express XT the worst buy I ever made. On the website, they offer a new update: version 7.
#4x4 midi patchbay driver#
In fact, not only did they never reply, they eventually removed my request for support from Techlinks.Īs for the driver version, I am not sure about the numbers being mooted here, version 1.01 or 1.02. But, I could get absolutely no response from MOTU. MOTU simply must know that there is a problem in this regard and owe it to customers who have forked out big bucks for their products to do something about it. I came to realise that it was the XT which was the culprit - it in some way corrupts the information and renders it useless, shutting down the sequencer and drummachine in the process. At first, I thought I was doing something wrong, but I gradually ruled that out. I tried repeatedly and unsuccessfully to send sysex information (song files) from an old Alesis Datadisk to an old Alesis sequencer and drum machine (all of which are working perfectly). If you manage to find it, please let me know, thanks! then what you have saved on your hard drive is a useless pile of bytes.).Īs MOTU ignored all of my attemps to get support for this particular issue (and from what I've read, I am not alone in this), there is only one 100% working solution: Use a different MIDI interface for SysEx - I am currently using Edirol's FA66 and it works flawlessly, as do many others).įrom what I've read, the other solution is to use the old driver (version 1.01, version 1.02 allegedly introduced the SysEx bug), but I couldn't find it anywhere, so I can't confirm this.
![4x4 midi patchbay 4x4 midi patchbay](https://surplustronics.co.nz/product/TASUS4X4/18494-original.jpg)
#4x4 midi patchbay software#
I experienced the same issue as you and after exhaustive searching I've found the reason: the sad truth about MIDI Express XT is that it damages SysEx data coming thru it - and because software editors for our synths (I have the exact same problem with editors for Radias, Miniak, AN1X and Evolver, running Win 7 64bit) use SysEx for comunication, that's one way of how the error manifests (the other one possible is even more entertaining - imagine using SysEx dumps for backup of your precious patches.