MOTU MIDI Express 128 - Windows compat and questions?

[DevonB]

I currently have the EMagic AMT8 in my setup. I've heard the drivers for XP do NOT work with Vista or Windows 7. However, I know the MIDI Express 128 does have Vista drivers, and MOTU is at least a company that's still in business to boot. So my questions -

1) Are there Windows 7 drivers, and do they work *WELL* with Windows 7. MOTU has a rep for being Mac centric and working well on Mac. Does this apply to this interface?

2) The AMT8 driver allows me to change the device description for every input and output to whatever I want to be within Device Manager. Does the MOTU allow the same thing on Windows or not? This is huge for me as I would hate to try to remember that MIDI 7 is Synth A but MIDI 5 is Synth Y. With my AMT8 driver, I just simply label them Yamaha TG77 or Roland JV-2080 or whatever it is.

I really need to know this before I even start to think about purchasing these instead to prepare for an eventual upgrade to my DAW. Thanks!

Devon

[mike vee]

i have it...running on XP though. i like it a lot...installed fine and works flawlessly.

as far as naming the ports as synth names, i just do that in Cubase so I don't have to remember.

[XXXEsq]

I have a 128 running under W7/64. They don't actually have a W7/64 driver, they have a Vista 64 driver (from 2007!) they say works. I'm having some trouble with it loosing connectivity with the computer and with BSODs on some of my plugs that only happens when the 128 is attached. Do some web research and you will see I'm not alone. I've been dealing w/ their tech support and they say they will get back to me. (?!)

[Kuusooka]

I have a MIDI Express 128 using the 1.0.1.2 drivers, yes, the ones from 2007 designed for Vista, and they have been rock solid for me for over a year with extensive use under both Windows 7 64 and Vista 64.

Like Mike, I name the ports in Cubase 5 so I haven't had a need to try doing it any other way. I haven't seen anything to indicate that it would have a function like that though.

It looks like others have had problems, but for me it has been just what I want and expect from a good basic MIDI interface: I set it up and forgot it exists because it has always worked perfectly.

[DevonB]

I guess I'm so used to the driver being able to name the ports that I never thought to look in Cubase of where to change the name. A quick Google search lead me to how to rename them. Thanks for the tip!

Still looking for stability stories though, so bring 'em on! I really do't want to upgrade to Win7, but eventually I'm going to have to, and probably soon. :(

[XXXEsq]

Originally Posted by Kuusooka

Like Mike, I name the ports in Cubase 5 so I
haven't had a need to try doing it any other way.

FYI, I also named the midi ports in Cubase. When the connectivity issue occurs, which is about every 5-6 days, its like the interface suddenly disapears. If I open the divice manager under Windows, the MOTU device is gone. If I open the device manager in Cubase and look at the midi connections,the ports are gone. My Mackie control and extenders stop working and my midi ins and outs (from my various other midi devices) stop working.

In order to get everything back, I have to close Cubase, unplug the 128 USB cable, reattach it, then restart Cubase and then the ports are back. I've seen similar reports from others on-line.

To be fair, it appears that most people have no problems with the 128 under W7/64, but there are a few of us that do.

[DevonB]

Originally Posted by XXXEsq

FYI, I also named the midi ports in Cubase. When the connectivity issue occurs, which is about every 5-6 days, its like the interface suddenly disapears. If I open the divice manager under Windows, the MOTU device is gone. If I open the device manager in Cubase and look at the midi connections,the ports are gone. My Mackie control and extenders stop working and my midi ins and outs (from my various other midi devices) stop working.

In order to get everything back, I have to close Cubase, unplug the 128 USB cable, reattach it, then restart Cubase and then the ports are back. I've seen similar reports from others on-line.

To be fair, it appears that most people have no problems with the 128 under W7/64, but there are a few of us that do.

Ya, I've had the same issue with the AMT8 years ago. It was plugged into a non-powered USB hub. Once I either plugged it into the back of my PC, or powered the hub, I've never had the issue again. How is your hooked up? USB power is very finicky.

Devon

[lain2097]

That's strange. I never had such issues with my AMT8 but I guess the crappy usb hub could cause problems for this un-buffered protocol (midi). I doubt it was the un-powered aspect as the AMT8 must be powered by that wall-wart.

But just in case I always have it hooked directly to the computer, on its own port.

[DevonB]

Originally Posted by lain2097

That's strange. I never had such issues with my AMT8 but I guess the crappy usb hub could cause problems for this un-buffered protocol (midi). I doubt it was the un-powered aspect as the AMT8 must be powered by that wall-wart.

But just in case I always have it hooked directly to the computer, on its own port.

Oh, it was the hub alright. I had other devices that would disappear, like the dongles. Once I grabbed the wall wart from the box for the hub itself and started plugging it in, all my problems went away. In fact, this problem happened to me probably 7 years ago or so, and I'm still using the same hub problem free. It took me awhile to figure out it was the hub. I'd unplug the AMT8 from the hub and plug it back in and it would find it. This problem was from what I remember, always on bootup. Magically, it wasn't there at all. Unplug/replug, poof I had it back. The problem was never consistent either. Some days it worked fine all day, other days the problem woudl appear once. I've heard of similar issues with unpowered USB hubs as well. Keep in mind the hub is not a repeater, and any problems with insertion loss can screw with the devices too.

Devon

[arkon]

have you tried your amt under w7?

my unitor8 worked fine under vista

its worth a shot!

[DevonB]

Originally Posted by arkon

have you tried your amt under w7?

my unitor8 worked fine under vista

its worth a shot!

Really? People on this thread I started 6 months ago had issues -

Anyone tried Windows 7 and Unitor8/AMT8 XP drivers yet?

Right now I'm trying to plan more than try. I need a working system at all times. 'Playing' around I don't have time for. If it works, fine. If not, I need to replace my 3 MIDI interfaces then. I like having them in chain, as they take up only one USB port with the EMagic solution. Nothing else like that that I'm aware of.

Devon

[arkon]

Originally Posted by DevonB

Really? People on this thread I started 6 months ago had issues -

Anyone tried Windows 7 and Unitor8/AMT8 XP drivers yet?

Right now I'm trying to plan more than try. I need a working system at all times. 'Playing' around I don't have time for. If it works, fine. If not, I need to replace my 3 MIDI interfaces then. I like having them in chain, as they take up only one USB port with the EMagic solution. Nothing else like that that I'm aware of.

Devon

i had no problems at all with the u8 under xp or vista 32bit

64bit will not work but lots of stuff doesnt work under 64bit

plug it in under 7 and if it works it will work if it doesnt it wont

also what your describing with chaining is just a usb hub . get a 20$ hub if you do change interfaces and their not chained (which is usually just a hub built into the interface)

i am running edirol midi instead of the unitor . the um8 would fit your bill perfectly and may give better midi timing than motu which can be problematic on pc

[nofi]

interesting... I was thinking of upgrading my PC this year (it's turning 6 soon!) because windows 7 was looking really nice in terms of music stuff... but maybe I'll try and stay with XP for as long as I can. at least until weirdness is sorted out for the midi express 128... don't know what I'd do without my midi express 128.

[DevonB]

Originally Posted by arkon

i had no problems at all with the u8 under xp or vista 32bit

64bit will not work but lots of stuff doesnt work under 64bit

plug it in under 7 and if it works it will work if it doesnt it wont

also what your describing with chaining is just a usb hub . get a 20$ hub if you do change interfaces and their not chained (which is usually just a hub built into the interface)

i am running edirol midi instead of the unitor . the um8 would fit your bill perfectly and may give better midi timing than motu which can be problematic on pc

What I want is a MIDI interface that still has driver development. It seems MIDIExpress 128 is the only 8x8 interface that is in active prodution anymore. If I'm going to go to Win7, I probably should go 64 bit anyway.

The chaining bit was nice with the AMT8 as it wasn't treated as 3 different inerfaces. You literally modified the driver to accomodate how many ports you had; 8 through 64 when you had 8 chained together. 3 different inerfaces all with 8 ports makes it harder to track which device is on which interface when they all have a port 1. On the AMT 8, my port one would be port 1, then port 9 then port 17. No problem and each unique.

Devon

[XXXEsq]

Originally Posted by DevonB

Ya, I've had the same issue with the AMT8 years ago. It was plugged into a non-powered USB hub. Once I either plugged it into the back of my PC, or powered the hub, I've never had the issue again. How is your hooked up? USB power is very finicky.

Devon

DevonB,

Thanks for the input. I have it attached to a purpose built DAW and its connected to a powered USB port directly on the motherboard. As it draws power through the USB plug, it wouldn't work at all if the port was unpowered. One of the "potential fixes" MOTU suggested was hooking it to a different USB port which I did. Same result. Still waiting for a reply from MOTU. Thanks anyway for the suggestion.

[arkon]

Originally Posted by DevonB

What I want is a MIDI interface that still has driver development. It seems MIDIExpress 128 is the only 8x8 interface that is in active prodution anymore. If I'm going to go to Win7, I probably should go 64 bit anyway.


Devon

Lots and lots of stuff doesnt work under 64bit yet , 32bit vst plug ins in particular. I looked at going 64 when I did w7 upgrade but its just not there yet for my setup.

if you want current driver development then MOTU is your only option.

roland still make drivers for the um5/8 rack mount interfaces but not the units themselves. They are still making um1/2/3 so development for them should continue for a while

unfortunetly MOTU seems to be the least reliable option for windows users so your going to have to balance that off.

[blueflake]

Hey guys, don't forget the ESI M8U XL. I just upgraded to Windows 7 x64 and bought one of those to replace my Emagic AMT8. The ESI is class compliant and thus it doesn't need any drivers. Windows 7 x86/x64 is listed as supported on the website.

I haven't had time to plug it in yet, so I have no experience to share. Also, the feature of naming MIDI ports in the device manager was something I liked with the AMT8, but I doubt the ESI has that feature. One can at least name the ports in most DAWs nowadays, I think that ought to suffice.

[Nucleus]

Hi guys,

Some things to consider:

Emagic AMT8 drivers do not work under windows 7 32 and/or 64 bit (tried it myself)
I replaced the AMT 8 with a MOTU Xpress 128. I have now two MOTU 128 expresses running under Windows 7 32 bit without any problems.

Look out if considering the ESI M8U XL. I had to return it when I was still running XP, because the class compliant XP driver is not multi client, which is a must for me. But maybe this is resolved in later Windows versions.

Just me 2 cnts.

[DevonB]

Originally Posted by Nucleus

Look out if considering the ESI M8U XL. I had to return it when I was still running XP, because the class compliant XP driver is not multi client, which is a must for me. But maybe this is resolved in later Windows versions.

You just saved me a LOT of headaches, thanks a bunch for that. I also need more than one, so that's a not happenin' here thing for me.

Devon

[Nucleus]

DevonB, glad to help

Just to clarify:

A multi client driver can be used by two or more applications running simultaniously. In my case, I sometimes use my DAW together with MidiQuest (synthesizer librarian/editor app). With the ESI interface I was not able to do that and therefore I swapped it with the MOTU. However, using more then one interface is not a problem with the ESI.

[Lourson]

Originally Posted by XXXEsq

I have a 128 running under W7/64. They don't actually have a W7/64 driver, they have a Vista 64 driver (from 2007!) they say works. I'm having some trouble with it loosing connectivity with the computer and with BSODs on some of my plugs that only happens when the 128 is attached. Do some web research and you will see I'm not alone. I've been dealing w/ their tech support and they say they will get back to me. (?!)

I feel your pain - I have the exact same issues with my midi express 128 under win 7, disconnection and bsod's, only when the 128 is plugged into the system - Support made me re-install the driver, claiming my issue was ''a first''. I can understand and be patient with a lot of technical issue, but I can't stand when a company lies to you about a problem reported many many times, online and to them. Shame on you MOTU

[mjames4208]

same problem here. i'm running XP32 bit, and i have to constantly unplug and replug the USB cable from the MIDI Express 128. one minute it's working fine and the next minute it's like WTF happened!
one thing that i should try that i haven't tried yet is using all of the USB Midi input/outputs on my synths and synth modules and avoid using the
dfegadMIDI Express 128 all together.

[Ihsahn1981]

Damn.. I've been looking for a 8x8 midi interface and the Motu looked like a very good option.
Im still on XP but I plan to update to Win7 sometime in the future.
Is there really no stable Win7 drivers for this thing?

Some report problems, some dont. Thats a worry for me.
I always seem to be in the group that has problems

[WOLF424]

I've had it show up as disconnected in Cubase 5 / W7 on start up, fixed by exiting, repluggin etc, happens a few times a week. But I've also had a couple of mysterious BSODs (while doing for example audio edits) that I never connected with the MOTU, damn.

[Demokid]

I'm on W7 32bit and use two Steinberg Midex-8. I'm planning to upgrade to W7 64bit and need to replace the Midex interfaces.
Have anyone tested two MOTU MIDI Express 128 on W7 64 or 32bit?

Kind regards
Demokid

[accessvirus]

Originally Posted by Demokid

I'm on W7 32bit and use two Steinberg Midex-8. I'm planning to upgrade to W7 64bit and need to replace the Midex interfaces.
Have anyone tested two MOTU MIDI Express 128 on W7 64 or 32bit?

Kind regards
Demokid

I whould not recommend the motu midi express 128 due to the same reason mjames4208 is talking about. I bought a new 3960 on asus rampage extreme 4 with the same problems!

each pc has internal chips regulating the bandwith and amount of power for each device. It could be one of those 2 things or a driver confilct between one or more devices. So maybe all who have this device connect it to a bus which has a overrun at one of those points. SO it whould be nice to have everyone post their specs so we can compare.

This is my system

• corsair vengeace 16Gb
• 2011 asus rampage extreme 4
• 3960 i7
• asus 6950 3 slots videocard
• RME raydat (without breakout connected) on a lynx aurora 8

USB devices

• KORE 2
• Wacom intuos 3
• virus TI
• DELL 2711 (usb hub inside monitor)
• motu midi express 128

[Markyboard]

Originally Posted by accessvirus

I whould not recommend the motu midi express 128 due to the same reason mjames4208 is talking about. I bought a new 3960 on asus rampage extreme 4 with the same problems!

I'm operating 2 MOTU MTP-AVs used with Win 7 pro -64 bit - solid as a rock and I recommend them. I still have my Unitor II and AMT on the shelf - didn't know they had any drivers after XP. Using MOTU's latest WIN 7 drivers. Running Reaper 64 and a select set of plugins ( Ivory 2, EAG Steel STR , KOMPLETE 7)

I just completed a PC rebuild (my previous X58, I7 940 on win 7 64 pro configuration also used the 2 MTP-AVs with no problem):

ASUS Rampage 4 Extreme Extended 2011 X79
I7 3930 (OC to 4.5G)
2 Crucial 512G SSDs,
16G Corsair Vengeance DDR3 RAM,
Sapphire HD 7870 VGA card .
HT OMEGA ECLARO

I have the RME HDSPe AES into a LYNX Aurora 16 VT.

[kpsiegel]

My Midi Express 128 USB works like a champ under Windows 7 Pro 64 bit. I am using the latest drivers. I am probably going to buy another one cause I have it maxed out.

[ParanormalPatrol]

Did they create drivers for Windows 7 after all?

[audiohack]

I was running the MIDI Express 128 for about 5 months with a Windows 7 Pro 64 bit system. It would seemingly randomly lose its connection about once every 3-4 days of use. Unplugging the USB and plugging it back in would re-establish the connection ... but I finally got tired of it and got rid of it. I'm now rocking an Edirol UM-880 for my MIDI patching/merging needs.