Another Micro not working..

[monotremata]

Came home from work today excited cause I forgot to try it last night..
Downloaded the update from earlier today even..
Cant for the life of me get it to connect. The basics, Im running Leopard 10.5.2, with an Emagic AMT8 interface, latest midi driver, which Im assuming has been updated last time one came with Logic..

Lets see where to start.. With just the osxmidispi.jar and libosxmidispi.jnilib files in place, Nomad wont even recognize my Emagic AMT 8 interface. Cant select any In or Out ports at all everythings 'greyed' out.
If I drag the Plumstone jar back in to the Extensions folder, my interface is recognized fine.
When I go and select Port 7 for both my In and Out and then hit Apply I get the following:

net.sf.nmedit.jsynth.SynthException: Invalid plug MidiPlug[name=Port 7 (MidiIN:6),vendor=Emagic,description=Midi IN port:6] for net.sf.nmedit.jsynth.midi.MidiPort[name='pc-out',type=TRANSMITTER,plug=MidiPlug[name=Real Time Sequencer,vendor=Sun Microsystems,description=Software sequencer]].
at net.sf.nmedit.jsynth.midi.MidiPort.setPlug(MidiPort.java:110)
at net.sf.nmedit.jsynth.nomad.forms.SynthPropertiesDialog$PortSettingsDialog.applyPortSettings(SynthPropertiesDialog.java:248)
at net.sf.nmedit.jsynth.nomad.forms.SynthPropertiesDialog$PortSettingsDialog$MyAction.run(SynthPropertiesDialog.java:223)
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.pumpEventsForHierarchy(EventDispatchThread.java:180)
at java.awt.Dialog$1.run(Dialog.java:535)
at java.awt.Dialog$2.run(Dialog.java:563)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:561)
at java.awt.Component.show(Component.java:1302)
at java.awt.Component.setVisible(Component.java:1255)
at net.sf.nmedit.jsynth.nomad.forms.SynthObjectForm.showSettings(SynthObjectForm.java:1257)
at net.sf.nmedit.jsynth.nomad.forms.SynthObjectForm.trySetConnectedState(SynthObjectForm.java:947)
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)


Now I close the preferences window, and reopen it.. It appears my In port sticks to Port 7, but my Out port is still at Port 1.. Select it again, hit apply the same error. I can do it all day long. For the sake of curiousity, I closed the prefs window and hit the yellow diamond connect button and am greeted with this error:

net.sf.nmedit.jsynth.SynthException: net.sf.nmedit.jnmprotocol2.MidiException: Communication timed out: 1205293824104 [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: Communication timed out: 1205293824104 [error=-1001]
at net.sf.nmedit.jnmprotocol2.NmProtocol.heartbeatImpl(NmProtocol.java:5
at net.sf.nmedit.jsynth.clavia.nordmodular.NordModular$SchedulingProtocol.heartbeatImpl(NordModular.java:252)
at net.sf.nmedit.jnmprotocol2.AbstractNmProtocol.heartbeat(AbstractNmProtocol.java:154)
at net.sf.nmedit.jnmprotocol2.NmMessageAcceptor.waitForReply(NmMessageAcceptor.java:114)
at net.sf.nmedit.jsynth.clavia.nordmodular.NordModular.connect(NordModular.java:358)
... 10 more

Not sure if this is any different than the previous people having trouble with it.. At first I DID have Internal Midi Clock on so after reading the posts here, I opened up Clavia's editor (which works just fine by the way) and turned it off. Reopened Nomad, still same deal.

Only things in my extensions folder are the midi drivers provided with Nomad and the Plumstone server, as well as a shortcut to a lib file that was placed there by Apple. When I started today I still had the jnmprotocol.jar and jpdl.jar files in there as well but removed them when I saw the suggestion to take everything out. All of the above errors also happen with Plumstone whether the Nomad provided midi files are in the Extensions folder or not.

For what its worth Ive never been able to make any of the pre-releases connect so Im not sure if its something to do with the AMT8 driver or what. But Im gonna keep persisting cause it looks awesome and dammit people are out there using it why cant I??

Any ideas, suggestions, etc?? Please tell me its something really simple I forgot to do??

[chresan]

[monotremata]

[JLS]

Not working me - micro and winXp

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(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
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)
... 11 more

[chresan]

[JLS]

SORRY - WORKING FINE

Many THANKS this GREAT JOB

Kamil

[monotremata]

Holy crap it works now!!!

Im home from work today so decided to give it another go after spending like 3 hours making a new patch in the Clavia Editor the other night.
Just a bit ago, I downloaded mmj 0.85, removed Mandolane/Plumstone/etc and just used mmj..

Fired up Nomad, selected AMT Port 7 for I/O, IT CONNECTED!!!!!

Just finished loading up various patches and listening to noodles INSIDE NOMAD!!!!

However, it does still timeout when I open it if I forget to set the MIDI Clock back to external before quitting..

And I am havning one wierd issue Ill have to go check around the forums for and see if its common.
When I select any patch the Nord loads them up fine, unless its patch #1. For some reason, it will load patch 1 into the Nord but will not update and display it on screen. Verified its in there by manually triggering the micro. It just doesnt open up in Nomad when its loaded.
If I move to any other patch they load up on screen properly and all is well..

One last question in case anyones still following my off topic ranting..
How the heck do you guys with racks and micros trigger it inside Nomad??
Am I blind or is there no keyboard floater like in the Clavia editor??
Guess its time to go dig through the docs eh??

Nice work guys especially since its only version 0.3!! It looks a hell of a lot cleaner and prettier than Clavias left over OS 9 style graphics and damn so far no crashes when I right click haha!!

Confident this app is only going to get better with time.. Looks like I better resume my hunt for a full modular now!!

[chresan]

Monotremata, I am glad Nomad works for you now. Thanks for reporting the #1 Patch problem (this is the first time I hear about it). I'll look into it.

About the keyboard floater, currently there is no way to trigger notes from within Nomad but this will be possible in a later version.

[monotremata]

Playing around the last few minutes... I think its the particular patch that is the trouble so sorry for causing any alarms..

I went into the Clavia editor, saved the patch by itself, and trying to reload it into the micro gives this error:

net.sf.nmedit.jpatch.clavia.nordmodular.parser.ParseException: error@143:10: invalid cc number 120
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.emiterror(PParser.java:160)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.emiterror(PParser.java:178)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.error(PParser.java:140)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PatchBuilder.emiterror(PatchBuilder.java:92)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PatchBuilder.ctrlMapDump(PatchBuilder.java:362)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.ctrlMapDump(PParser.java:518)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.section(PParser.java:379)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.sections(PParser.java:269)
at net.sf.nmedit.jpatch.clavia.nordmodular.parser.PParser.parse(PParser.java:206)
at net.sf.nmedit.jsynth.clavia.nordmodular.utils.NmUtils.parsePatch(NmUtils.java:453)
at net.sf.nmedit.jpatch.clavia.nordmodular.NMPatch.createPatchFromFile(NMPatch.java:521)
at net.sf.nmedit.nordmodular.NmFileService.openPatch(NmFileService.java:80)
at net.sf.nmedit.nordmodular.NmFileService.open(NmFileService.java:137)
at net.sf.nmedit.nomad.core.Nomad.openOrSelect(Nomad.java:946)
at net.sf.nmedit.nomad.core.swing.explorer.FileNode$3.run(FileNode.java:380)
at net.sf.nmedit.nmutils.swing.WorkIndicator$WrappedRunnable.run(WorkIndicator.java:60)
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)


So for kicks, I went back to Clavia's editor, saved patch #2, and then in Nomad, saved this patch into Bank 01.. Now when I click on it, it opens up just fine.. Whats wierd is why does that first patch work fine in Clavia's editor but not in Nomad?? Maybe someone can guide me by the error message above.. The patch still works fine, but it would be nice to see it in the editor and know its ok hehe. I think its a patch I got from the archives years ago anyways (its called VocFilt Transwave) so Ill go track down another copy and see if mines corrupted somehow! Come to think of it, I better go put it back in bank 01 in the Clavia Editor cause I use this patch alot hehe.

[chresan]

This exception is because an invalid cc number (>=120 or =32) was assigned to a parameter. Currently the patch parser is very strict about 'wrong' patch files. It is on our todo list to change this.

[monotremata]

Awesome! Just noticed that in the error log and thought 'I wonder if that means a MIDI CC??' hehehe.

So yeah I removed the filter resonance set at CC 120, resaved to the Micro and to hard drive..
Re-opened Nomad, as well as opened the patch file from the browser in Nomad.

NOMAD IS GOOD TO GO!! YEEEEEEAAAAAAAAAAAAH!
Not a big deal, I have to move about 10 controllers down a few spots in the patch itself but shouldnt be any trouble.. And itll get me used to Nomad's GUI while 'fixing' it!

So is this some sort of error on Clavia's part or is it just Nomad needing some 'fixing up'?? Wonder if I have more patches like that but at least now I know it can be fixed and I can work trouble free in OS X now!!

Today was a GREAT day to stay home from work hahahaha!

[chresan]

Monotremata,

according to http://www.borg.com/~jglatt/tech/midispec/ctllist.htm the controller numbers >=120 are used for things like "All sound Off" messages. I can't test it right now but these controller numbers are probably not assignable from within Clavias editor. Perhaps someone wrote them into the patch file using a text editor ???

Anyway I am glad staying home worked out for you

Christian

[monotremata]

Perhaps its an overlooked bug in the old Clavia Editor???
Just opened up a blank patch and checked with an oscillator, 120 itself is the highest number you can assign.
I better start checking my own patches cause I know I used the upper range for the controller assignments from my oxygen 8.. oops!!

i gotta sticky note on my monitor now reminding me to keep doing new patches in Nomad to avoid this kinda stuff hehe.

[blue hell]