The solution?
Well, I tried several configuration before finding the solution to my problem:
1- in the MIDI/Audio setup of the MAC, I have removed all the configurations. In fact, if you go to the pannel control of your mac, then utility folder, you find a software to configure MIDI connections -> I removed all the settings there.
2- I noticed that if my macintosh was in french, nomad does not work -> I am now working with an ENGLISH MAC instance
3- then...
3.1 - I don't plug the MOTU Firewire cable!
3.2 I launch NOMAD software,
3.3 I can see the Nord modular synth !!! I can communicate, etc!
3.4 I insert then the cable FIrewire from my MOTU to my computer
3.5 I launch ableton live
Everyhting is fine!

I guess that my time out issue is coming from the MOTU !!!

to resume, my advices would be:
- if you are on a mac -> setup the language to ENGLISH (important, otherwise it does not work!)
- disconnect all your USB/firewire connection before launching the nomad tool,
- once the nomad tool running and your Nord modular connection established, then,
- insert your firewire cable to your computer, switch on your MOTU and launch your favorite DAW.

Hi chupschups.
I once managed to use nomad on my mac but i cannot do it anymore as i always get midi time outs.
I'd like to ask more details about your configuration :
- what's your version of JavaVM ?
- have you put libosxmidispi.jnilib and osxmidispi.jar provided with nomad in /Library/Java/Extensions ??
- do you have this issue with the morph applying inverse ?
Thanks

- have you put libosxmidispi.jnilib and osxmidispi.jar provided with nomad in /Library/Java/Extensions ??
yes!
- do you have this issue with the morph applying inverse ?
arrf, I need to check this, sorry, can't answer! I didnot notice anything on this matter...

Not to beat a dead horse yet again but..
How did I miss this thread last time I was here troubleshooting???

My MOTU 828MKII turned out to be the culprit. Nomad always worked as it should up until around the time I finally replaced my G4 with a G5, which was like 2011 I think.. So at some point one of MOTU's updates did something to the MIDI driver that breaks communication with Nomad. Whatever they did is still going on today in the latest and greatest driver. Makes sense your MK3 and my MK2 do it since all the FW stuff uses the same driver.

Its weird, when I figured this out, I noticed that when the MOTU is off, and you select your MIDI port (I have an Emagic AMT8) the ports are all named appropriately like I have them setup in AudioMIDI Setup. When the MOTU's on, the port names revert to just Port 1(1), Port 2(2). Where before it was like AMT8 Port1: MicrowaveXT or something similar to that..

Either way problem solved. Fire up Nomad, connect to the Modular, THEN turn on the MOTU and noodle away.. Although occasionally it will lose communication at random and youll have to restart the whole process.

Now somebody pick up development cause I need the floating keyboard to test out patches I cant make noodles all the time!!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum

Please support our site. If you click through and buy from our affiliate partners, we earn a small commission.