Nomad MicroModular & Leopard

vyedmic · Joined: Nov 19, 2007 Posts: 10 Location: Bootle, UK

As you may know OS X Leopard doesn't support Classic applications anymore so Clavia's OS X Editor no longer works. Nomad is the only alternative.

I managed to run it with Mandolane, the Humatic Java Midi Subsystem(MMJ) didn't work for me. I could construct some basic patches and they worked - I could download them into the Micro but upload didn't work at all. Also when I changed any parameter I had to re-download the patch every time although cable connections weren't affected and I could mess with cables as I wanted without re-downloading.

This is not very usable at the time being but I have my faith in this great editor (at least it looks great Wink

).

Specs:
Intel Macbook Santa Rosa 2GHz 1GB RAM
Mac OS X Leopard 10.5.1
Edirol UM2-EX MIDI Interface
Nomad 0.2.1
Mandolane MIDI SPI 2.04

These are only first impressions I intend to test it more thoroughly.

Martin

vyedmic · Joined: Nov 19, 2007 Posts: 10 Location: Bootle, UK

Back on the case after couple of months Cool

. New Nomad prerelease looks great but when I try to setup connection settings I get this:

Poster · Joined: Jul 19, 2005 Posts: 27 Location: Netherlands

vyedmic · Joined: Nov 19, 2007 Posts: 10 Location: Bootle, UK

Am I stupid or what???

Sure it works....I feel embarrased Shocked

But that doesn't change the problems I have with Java midi extensions. Weak justification of the topic but at least something Wink

Cheers Poster

Poster · Joined: Jul 19, 2005 Posts: 27 Location: Netherlands

vyedmic · Joined: Nov 19, 2007 Posts: 10 Location: Bootle, UK

Did you have any problems with Java MIDI extensions or did you just use the ones bundled?

Poster · Joined: Jul 19, 2005 Posts: 27 Location: Netherlands

fransb · Joined: Jun 07, 2008 Posts: 2 Location: Netherlands

First of all, I am impressed by this piece of work!

After installing nm-edit 0.3 revision 2 on my Mac Book Pro, including libosxmidispi.jnilib and osxmidispi.jar, a connection with my micromodular couldn't be established. I got the following message:

net.sf.nmedit.jsynth.SynthException: net.sf.nmedit.jnmprotocol2.MidiException: timeout: 10000ms (net.sf.nmedit.jnmprotocol2.SynthSettingsMessage) [error=-1001]
at net.sf.nmedit.jsynth.clavia.nordmodular.NordModular.connect(NordModular.java:411)
at net.sf.nmedit.jsynth.clavia.nordmodular.NordModular.setConnected(NordModular.java:881)
at net.sf.nmedit.jsynth.nomad.forms.SynthObjectForm.trySetConnectedState(SynthObjectForm.java:958)
at net.sf.nmedit.jsynth.nomad.forms.SynthObjectForm$1$1.run(SynthObjectForm.java:599)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Caused by: net.sf.nmedit.jnmprotocol2.MidiException: timeout: 10000ms (net.sf.nmedit.jnmprotocol2.SynthSettingsMessage) [error=-1001]
at net.sf.nmedit.jnmprotocol2.NmMessageAcceptor.waitForReply(NmMessageAcceptor.java:111)
at net.sf.nmedit.jsynth.clavia.nordmodular.NordModular.connect(NordModular.java:400)
... 10 more

Is there anything I could try???

Thx, fransb

fransb · Joined: Jun 07, 2008 Posts: 2 Location: Netherlands

After enabling external midi clock, I got connected.

fransb