![]() ![]() I had an old JL Cooper midi patchbay that finally gave out on me. I just ended a 4 month search for the same type thing. 4X4 MIDI PATCHBAY SOFTWARELots of features that make for a great "live rig" (i.e., software programmable, ability to create user defined settings that can be saved and accessed from front panel after the computer has been disconnected, good debugging tools that show ALL midi messages traversing the network) without having to spend for higher end video and audio synching features that I'll never use. My favorite MIDI interface is the Motu MIDIExpress XT. ![]() Unfortunately, rack mount MIDI interfaces are a bit removed from the beaten path and don't seem to be something that you see on Craigslist or Ebay all the time. If a deal is what you're looking for - you'll have to root around in the used market and hope you get lucky. There simply doesn't seem to be alot of room for negotiation - especially on gear that's a little off the beaten path (like MIDI interfaces). 4X4 MIDI PATCHBAY MOVIEI would strongly advise anyone thinking of purchasing it to not do so.When it comes to new gear - a quote lifted from the movie "Taken" that's recently been in heavy rotation on one/all of the cable channels seems fitting. 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 DRIVERIn 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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |