M3 EXB FW Firewire Not Working in Any Host I have.

Riley333 · Post by **Riley333** » Sat Feb 16, 2008 1:01 pm

Edit: changed the title to reflect the turn of the thread.

I have installed the EXB FW firewire expansion and it works using the stand alone editor but the plugin editor will not work with Ableton Live 7.02. I keep getting the error "M3 Hardware Not Found, Rescan?" I click OK but it does not do anything. It's really strange because I still get MIDI signals from the M3 with nothing but FW connected, so it's making some kind of connection.

I have my edirol UA101 set at 48k as well as Live.

Specs:
Windows XP, SP2. 1.6G dual core Dell M65, 2GB RAM. Edirol UA101.

I have all FW midi ins and outs turned on in Live for the M3 plugin editor. The M3 plugin editor just can't seem to find the M3 with all the roads open to it.

Please help....

Thanks! Riley

Riley333 · Post by **Riley333** » Sat Feb 16, 2008 3:40 pm

I have managed to get it to work if I have the USB cable pugged in at the same time, however there is a lot of latency and pops.

Does anyone know if you need to use the USB interface in order to use the Firewire interface?

Sounds kinda wacky.

Thanks! Riley

Twiddler · Post by **Twiddler** » Sat Feb 16, 2008 6:46 pm

You don't *have* to use the USB interface while using the EXB-FW, but you will want to. The USB connection is 20x faster (!!!) than the FW connection for transmitting MIDI data. When you are using the M3 editor this makes a big difference as program/combi information is transmitted, but doesn't matter nearly as much for normal Note and CC data.

I have used the M3 with the EXB-FW under Live 7.02 without any problems, but I am on a Mac, so the drivers are totally different.

Have you verified that your M3 standalone editor works correctly? In theory, none of the settings in Live should matter. The editor is not using the MIDI connectivity of the DAW host to talk to the hardware. They can't... the plug-in spec doesn't give them the flexibility that they would need to do that. So the editor establishes its own connection to the hardware.

Twiddler · Post by **Twiddler** » Sat Feb 16, 2008 6:48 pm

Oh... and yes I am seeing a lot of latency (~60ms) through the EXB-FW. That is why I am not using it any more. I hope that Korg fixes this. 60ms is way too much latency for anything but pads..

Riley333 · Post by **Riley333** » Sat Feb 16, 2008 7:29 pm

Twiddler wrote:Oh... and yes I am seeing a lot of latency (~60ms) through the EXB-FW. That is why I am not using it any more. I hope that Korg fixes this. 60ms is way too much latency for anything but pads..

60ms! wow, That's terrible.
I'm going to get on the phone with Korg Support next week, if the EXB FW isn't any better than this then it's going back to the store.

Thanks for the reply.

Riley

LivePsy · Post by **LivePsy** » Sat Feb 23, 2008 10:41 pm

Any chance of trying a different sequencer? It wouldn't surprise me if Live 7 has some part in this problem. I believe Access is writing updates created by Leopard OS X and Live 7 - not every sequencer, mind you, Live.

Cheers,
BF

Riley333 · Post by **Riley333** » Sun Feb 24, 2008 12:13 am

LivePsy wrote:Any chance of trying a different sequencer? It wouldn't surprise me if Live 7 has some part in this problem. I believe Access is writing updates created by Leopard OS X and Live 7 - not every sequencer, mind you, Live.

Cheers,
BF

I just tried Sonar 7 Producer and it just locks up. I had to reboot after loading the M3 Plugin.

Riley333 · Post by **Riley333** » Sun Feb 24, 2008 12:43 pm

I just tried it in FL Studio 7.0 and it loads up and acts like it's going to work but the sound is a garbled.

Did someone say the Korg is aware of these problems? I have not been able to call them because of the available support times they have and my Business Day Schedule.

Has any FW EXB owners called Korg Yet?

Thanks