nmedit-devel Mailing List for Nord Modular Editor

Under Linux, I think only the first midi port works. This used to be a
limitation of the midi implementation of java midi under linux. Maybe this
changed with newer versions.

2010/2/5 Marcus Andersson <kam...@gm...>

> Hi,
>
> I noticed that no matter which midi-port I select, nomad always uses the
> first in the list. I tried to find the class which is responsible for the
> change of midiplug on the synth ports, but I failed. Can anyone help me out?
>
> Marcus
>
>
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the
> business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Nmedit-devel mailing list - Nme...@li...
> http://nmedit.sf.net/
> https://lists.sourceforge.net/lists/listinfo/nmedit-devel
>
>

Hi,

I noticed that no matter which midi-port I select, nomad always uses the
first in the list. I tried to find the class which is responsible for the
change of midiplug on the synth ports, but I failed. Can anyone help me out?

Marcus

Hi,

as of now the osxmidispi directory and containing files has been removed
from CVS because of legal issues[1]. Please make sure you do not
accidentally check in your local copy.


Thanks

Christian


[1] http://electro-music.com/forum/viewtopic.php?t=29717

Hi,

the eclipse source folders changed. Please update the src/bin locations
for the jpatch and patchmodification library/plugin. See
http://nmedit.wiki.sourceforge.net/Eclipse for a working configuration.

Christian

Julien Pauty schrieb:
> Hello,
>
> I committed a new version of the mutator. This version should act on
> the patches. I did not test yet with my nord.
Me neither but it seems to work - can't wait to try it with the Nord.
However we might face the same problem like with the randomizer. If too
many parameters are tweaked in a short period of time the synth dies and
must be switched off and on (I'll figure something out).
> Next step is to add crossing between father and mother patches.
> Currently father is useless. I must also add support for parameter
> filtering to control what is mutated and what is not.
>
> This code should probably be move out from the jpatch lib to a
> separated module. If someone can do this I'll be happy. I'm not that
> familiar with the plug in system.
Ok, I'll do it then.

> I also added support to closing the mutator window, but it seems that
> it sometimes breaks the pop up window that warn you if you quit with
> unsaved modified patches. Maybe it's not linked...
Strange, this works for me.


Christian

Hello,

I committed a new version of the mutator. This version should act on the
patches. I did not test yet with my nord.

Next step is to add crossing between father and mother patches. Currently
father is useless. I must also add support for parameter filtering to
control what is mutated and what is not.

This code should probably be move out from the jpatch lib to a separated
module. If someone can do this I'll be happy. I'm not that familiar with the
plug in system.

I also added support to closing the mutator window, but it seems that it
sometimes breaks the pop up window that warn you if you quit with unsaved
modified patches. Maybe it's not linked...

Julien

Hi Marcus,

I frequently find me refusing to update the website since it requires so
much effort. So yes I think we should migrate some (if not most) of the
documentation to the wiki.
We can keep larger documentation or documentation which should be
preserved over time on the forrest website (for example the PDL
documentation or the javadoc api references).

Christian

Marcus Andersson schrieb:
> Hi,
>
> should the wiki become the new developer site and relevant information 
> be moved from the old website to the wiki over time? A wiki is easier to 
> update than the current forrest setup.
>
> Marcus
>   

Hi,

should the wiki become the new developer site and relevant information 
be moved from the old website to the wiki over time? A wiki is easier to 
update than the current forrest setup.

Marcus

Christian Schneider wrote:
> Hi nmedit developers,
>
> I enabled the wiki for our project. The wiki can be found at
>     http://nmedit.wiki.sourceforge.net/
>
> The wiki should make it easier and faster for us to provide information
> which needs to be updated quickly or changes often. (It is not intended
> to replace the website docs !!!)
>
> For now I added a section containing information about bugs &
> workarounds in our releases  for Nomad-users.
>
> Aimed at us developers I added a guide how to setup the Nomad project in
> eclipse and a page describing coding practices for our project.
>
> Please, everyone who commits new source code should adapt to the coding
> practices described there. There are a lot of things done wrong in our
> project which make it unnecessarily hard to track down problems reported
> by our users (main problem right now is that the log file contains not
> much info) . Also I hope, common coding practices will make it easier to
> read and understand the source code of each other and to improve the
> quality of our code base.
>
>
> Cheers
>
> Christian
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nmedit-devel mailing list - Nme...@li...
> http://nmedit.sf.net/
> https://lists.sourceforge.net/lists/listinfo/nmedit-devel
>  
>
>   

Hi nmedit developers,

I enabled the wiki for our project. The wiki can be found at
    http://nmedit.wiki.sourceforge.net/

The wiki should make it easier and faster for us to provide information
which needs to be updated quickly or changes often. (It is not intended
to replace the website docs !!!)

For now I added a section containing information about bugs &
workarounds in our releases  for Nomad-users.

Aimed at us developers I added a guide how to setup the Nomad project in
eclipse and a page describing coding practices for our project.

Please, everyone who commits new source code should adapt to the coding
practices described there. There are a lot of things done wrong in our
project which make it unnecessarily hard to track down problems reported
by our users (main problem right now is that the log file contains not
much info) . Also I hope, common coding practices will make it easier to
read and understand the source code of each other and to improve the
quality of our code base.


Cheers

Christian

Nomad 0.3 pre-release announcement

Hi everyone,

the second release of Nomad - Nord Modular Editor is finally out.
After 1.5 years of developing since the first release we are happy
to announce that Nomad is almost feature complete.

Apart from the basic things we implemented some new features to
improve the experience with the editor:
- embedded file browser
- macros: create tiny template patches which can be inserted into other
patches
- module transformation: transform a module into another without loosing
parameter values and connections
- randomizer: randomize the parameters of a patch or a set of modules
- arbitrary number of Nord Modular/Micro Modular synthesizers supported

Requirements:
-------------
- Java Runtime Environment (JRE) 5.0
- platform: platform independent

OS X users might need to install a MIDI service provider (SPI). See
	http://nmedit.sourceforge.net/userpage/help.html#osx-midi

Starting Nomad:
---------------
OS X:
	start the nomad application file like any other application

other platforms:
	start nomad.jar like any other application
	or manually using the command
		java -jar nomad.jar 

Downloads are available at
	http://nmedit.sourceforge.net/

For support, questions, bug reports or anything else visit our forum at
	http://electro-music.com/forum/forum-138.html

Hi,

I am about to check in a new sourcefolder for the jpatch plugin. Those
who are using eclipse do not forget to set
nomad-source/plugins/net.sf.nmedit.jpatch/src
as source folder and use
nomad-source/plugins/net.sf.nmedit.jpatch/classes
as output folder (not the default output)


Christian

Hi,

the nomad build-script dist-target now validates the .classes files to
ensure they are J2SE 5.0 compliant. It does so by iterating over all
.class files (with the correct magick number) inside the nomad-dist
directory (including subdirectories and jar files) and examines the
class file version number.

If you get an error like for example:

Checking java .class files major version: <=J2SE 5.0
invalid major version: /home/christian/...some-path.../Main.class
major:50 (J2SE 6.0) minor:0

then class files are present which would require a newer JRE. Such an
error would indicate that something is going wrong in one of the ant
build scripts. For example if the ant-javac-target is missing the
attribute target="1.5" (See
http://ant.apache.org/manual/CoreTasks/javac.html ).

Christian

Hi,

I added a tool to the nomad project which checks .java-files for missing
license statements. It happens sometimes that someone checks in code
without the GPL statement. Now you can do the following

cd nomad
ant src-license

The program then runs over all .java files in nmedit/libs and
nmedit/nomad and looks for the strings
'Copyright'
'GNU General Public License'

If one of the strings is missing then it prints out the location of the
file.

Here is some example output
src-license:
     [java] Validating .java source license statements.
     [java] Skipping: /home/christian/dev/nmedit/nomad/./nomad-offline
     [java] ******************************************
     [java] processing directory: /home/christian/dev/nmedit/nomad/.
     [java] license missing:
/home/christian/dev/nmedit/nomad/./nomad-source/plugins/net.sf.nmedit.jsynth/src/net/sf/nmedit/jsynth/nomad/SaveInSynthFrm.java
     [java] ******************************************
     [java] processing directory: /home/christian/dev/nmedit/nomad/../libs
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jsynth/src/net/sf/nmedit/jsynth/worker/PatchLocation.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jnmprotocol/test/net/sf/nmedit/jnmprotocol/helper/GetPatchMessageReplyAcceptor.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jnmprotocol/test/net/sf/nmedit/jnmprotocol/AllTests.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jnmprotocol/test/net/sf/nmedit/jnmprotocol/ProtocolTester.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/PDLParseContext.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/format/PDL2ParserVal.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/format/PDL2Lexer.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/format/PDL2Parser.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/PDLBitstreamGenerator.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/impl/PDLMessageImpl.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/src/net/sf/nmedit/jpdl2/impl/PDLParseContextImpl.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/test/net/sf/nmedit/jpdl2/test/BitstreamParseTests.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/test/net/sf/nmedit/jpdl2/test/PDLParseTests.java
     [java] license missing:
/home/christian/dev/nmedit/nomad/../libs/jpdl2/test/net/sf/nmedit/jpdl2/test/PDLItemTests.java
     [java] ...
     [java] Done.
     [java] directories: 1176
     [java] .java-files: 677
     [java] missing license statements: 21
     [java] Validation failed, some .java-files have no license statement.

This tool is primitive but it works and I hope it is useful for you too.

Regards

Christian

Hi,

I am about to check in new versions of the jgoodies look and feel for
nomad. If you are using eclipse you have to modify the java build path
for your projects.

The new jar files can be found at
nomad-source/plugins/com.jgoodies.forms/lib/forms-1.1.0.jar
nomad-source/plugins/com.jgoodies.looks/lib/looks-2.1.4.jar

Christian

Thank you Christian, that bit of extra information makes things 'come alive'
much more than the picture on it's own. I think these are some good ideas for
the user interface. Probably  there will be more once 'release X' goes public
(and good to hear it's going strong still!)

Hoi Marije, Christian must be a clairvoyant :D

-- 
Jan.

nescivi schrieb:
> Jan,
>
> did you report the different ID code that the micromod sends?
> This was the one useful thing we figured out during the Chateau
> Sonore, since it will allow the autodetection of a Micromod vs. the
> big brother...
>   

Autodetection of Nord Modular, Nord Modular Rack, Micro Modular is working.
Only the available slots are shown.

Christian

Jan,

did you report the different ID code that the micromod sends?
This was the one useful thing we figured out during the Chateau
Sonore, since it will allow the autodetection of a Micromod vs. the
big brother...

sincerely,
Marije

On Feb 5, 2008 3:18 PM, Christian Schneider
<chr...@fa...> wrote:
> Hi Jan,
>
> nice to hear from you.
>
> Jan Punter :
> > Ok, some of my thoughts and questions :
> > I assume there will be multiple synth tabs for the lucky ones? Showing a micro
> > or a full icon.
> >
> Exactly.
> > What is the warning sign for?
> >
> The warning sign could be shown if for example DSP usage goes above 90%.
>
> > I assume the gear icon will open the synth menu?
> Yes.
> >  No probably it's the patch
> > menu, as it's near the DSP percentage ...
> The view is synth-centric so the DSP percentage is the sum of the DSP
> percentage of each slot.
>
> > maybe leave out the the word slot in
> > slot A, B etc and just say A, B etc that'd give maybe just enough space for
> > having a DSP percentage for each patch and a patch menu icon as well.
> >
> Agreed.
>
> > There seems to be some subtle difference between muted patches and paused
> > patches, I'm not sure what to make of that.
> >
> Don't try to interpret to much into the icons. They were just the best I
> could find :)
> The Start/Pause buttons are meant to enable / disable the slots.
> The warning sign in Slot C should not be there :)
> The warning sign in Slot D could indicate that the Patch requires more
> DSP power and is mutet.
>
> > I'd use "empty" instead of "not used", to have the same wording as in the synth
> > display.
> >
> ok
> > I'd bring the buttons for "Öffnen" etc. into the side bar, so the nearly empty
> > toolbar can go, leaving more height for the patch.
> Basically I agree, I always tried to maximize the space available to
> display a patches.
> I should probably  provide an option to toggle the visibility of the
> toolbar.
>
> >  And it would be very nice if
> > the side bar would be collapsable, but maybe it already is :D
> >
> The size of the side bar is not fixed. You can make it larger or
> smaller. But smaller only to
> a certain degree. I'll see what I do about this, perhaps I also add a
> menu entry to toggle the
> visibility of the sidebar.
>
> > For banks there will be a selector I guess, instead of the edit box it looks
> > like now?
> >
> Right now (and in the upcoming release) The synthesizer, its slots and
> its banks are shown in
> the tree where you can see the files.
>
> > BTW ... how are things going with the Nomad for Christmas release?
> >
> Well for the christmas release the signs are bad :) But in general they
> are very good.
> Right now, Manuel and I are fixing the remaining bugs. Probably in the
> next 2-3 weeks
> we are able to release.
> Future releases will be more frequently, perhaps each 2-3 months. This
> release was delayed
> so much because nomad was rewritten (almost) from scratch. The rewrite
> took much more
> time than expected. According to my own plans I wanted to release about
> a year ago :)
> Anyway the long time of waiting will definately pay off - I don't want
> to give away too much right now.
>
> Sincerely
> Christian
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nmedit-devel mailing list - Nme...@li...
> http://nmedit.sf.net/
> https://lists.sourceforge.net/lists/listinfo/nmedit-devel
>

Hi Jan,

nice to hear from you.

Jan Punter :
> Ok, some of my thoughts and questions :
> I assume there will be multiple synth tabs for the lucky ones? Showing a micro
> or a full icon.
>   
Exactly.
> What is the warning sign for?
>   
The warning sign could be shown if for example DSP usage goes above 90%.

> I assume the gear icon will open the synth menu?
Yes.
>  No probably it's the patch
> menu, as it's near the DSP percentage ...
The view is synth-centric so the DSP percentage is the sum of the DSP
percentage of each slot.

> maybe leave out the the word slot in
> slot A, B etc and just say A, B etc that'd give maybe just enough space for
> having a DSP percentage for each patch and a patch menu icon as well.
>   
Agreed.

> There seems to be some subtle difference between muted patches and paused
> patches, I'm not sure what to make of that.
>   
Don't try to interpret to much into the icons. They were just the best I
could find :)
The Start/Pause buttons are meant to enable / disable the slots.
The warning sign in Slot C should not be there :)
The warning sign in Slot D could indicate that the Patch requires more
DSP power and is mutet.

> I'd use "empty" instead of "not used", to have the same wording as in the synth
> display.
>   
ok
> I'd bring the buttons for "Öffnen" etc. into the side bar, so the nearly empty
> toolbar can go, leaving more height for the patch.
Basically I agree, I always tried to maximize the space available to
display a patches.
I should probably  provide an option to toggle the visibility of the
toolbar.

>  And it would be very nice if
> the side bar would be collapsable, but maybe it already is :D
>   
The size of the side bar is not fixed. You can make it larger or
smaller. But smaller only to
a certain degree. I'll see what I do about this, perhaps I also add a
menu entry to toggle the
visibility of the sidebar.

> For banks there will be a selector I guess, instead of the edit box it looks
> like now?
>   
Right now (and in the upcoming release) The synthesizer, its slots and
its banks are shown in
the tree where you can see the files.

> BTW ... how are things going with the Nomad for Christmas release?
>   
Well for the christmas release the signs are bad :) But in general they
are very good.
Right now, Manuel and I are fixing the remaining bugs. Probably in the
next 2-3 weeks
we are able to release.
Future releases will be more frequently, perhaps each 2-3 months. This
release was delayed
so much because nomad was rewritten (almost) from scratch. The rewrite
took much more
time than expected. According to my own plans I wanted to release about
a year ago :)
Anyway the long time of waiting will definately pay off - I don't want
to give away too much right now.

Sincerely
Christian

Quoting Christian Schneider <chr...@fa...>:

> I made a Nomad mockup.


Looks good to me, despite all what I'll type hereafter, basically I think it's a
good idea. 

Ok, some of my thoughts and questions :

I assume there will be multiple synth tabs for the lucky ones? Showing a micro
or a full icon.

What is the warning sign for?

I assume the gear icon will open the synth menu? No probably it's the patch
menu, as it's near the DSP percentage ... maybe leave out the the word slot in
slot A, B etc and just say A, B etc that'd give maybe just enough space for
having a DSP percentage for each patch and a patch menu icon as well.

There seems to be some subtle difference between muted patches and paused
patches, I'm not sure what to make of that.

I'd use "empty" instead of "not used", to have the same wording as in the synth
display.

I'd bring the buttons for "Öffnen" etc. into the side bar, so the nearly empty
toolbar can go, leaving more height for the patch. And it would be very nice if
the side bar would be collapsable, but maybe it already is :D

For banks there will be a selector I guess, instead of the edit box it looks
like now?

BTW ... how are things going with the Nomad for Christmas release?

-- 
Jan.

Hi,

I made a Nomad mockup. It shows a new way to show the synth in the user
interface. I think this is one is better as having the synth in the
explorer tree since you can see the info at once and don't have to
expand/collapse the tree nodes all the time.

http://christianschneider.fastmail.fm/pics/mockup/nomad-mockup-2008-02-05.png

Please let me know what you think about it .

Christian

P.S.:I intend to implement this or another approach after the next release.

Hey people,

I use OSX as development environment, so all the bugs that have to do  
with keyboard and mouse are probably OSX specific. I'll include that  
in future bug reports, but keep that in mind in case you can't  
reproduce them or so :)

Cheers, manuel

Hey people,

as you may have noticed, I'm swamping the bugtrackers. I'm pretty  
hyped that nmedit is working correctly on macosx now that I want to  
replace the clavia editor completely. So I'm trying to patch stuff,  
and writing down everything that comes up and bothers me. I'm not too  
fluent with the program right now so can only fix minor stuff, but  
I'll definitely have a go at it with christian's help. Hope you people  
don't mind the flooding :)

Thx for the beautiful work. It has a few rough edges that make it not  
really suited for full work right now, but it's mostly minor bugs (at  
least I guess they can be easily fixed).

The most bugging right now are:

- patch cables not drawing correctly
- nomad not storing settings (but maybe that's my fault)

Cheers, manuel

Hello there

I would greatly appreciate a small amount of your time to assist with
my doctoral research at The University of Newcastle. The research
concerns open source licensing and we're seeking developers working on
Java projects. The research is supervised, ethics-approved, anonymous
and results will be freely available. Participation will also provide a
custom licensing report for your project. To learn more, please visit:

   http://licensing-research.newcastle.edu.au

Thanks for reading this email, and I hope you'll consider participating.

Best regards
Ben Alex

(My apologies for being off-topic; this list will not be emailed again)

On 11 Nov 2006, at 18:14, Richard Commissione wrote:

> The NM editor only comes up with a blank screen when I launch it
> Here is the output from the terminal
> I am running Fedora Core 6 on a fairly gutsy machine.
> [...]
> java.io.FileNotFoundException: conf/properties.xml (Permission denied)

it seems that there is something wrong with the permissions of the  
conf/ directory
or the properties.xml file in that directory.

try from the same folder as running "java -jar nomad.jar" the  
following two commands

chmod 755 conf/
chmod 644 conf/properties.xml

if there is no properties.xml file, it might help to run

touch conf/properties.xml
chmod 644 conf/properties.xml

either way, to get good help you should really send emails to nmedit- 
de...@li...
or try the online forum http://www.electro-music.com/forum/ 
forum-138.html

nme...@li... is for CVS notifications only.

good luck

Jelle.


> ********************************************************************** 
> **********
> [user@computer nomad]$ java -jar nomad.jar
>
> ********************************************************************** 
> **********
> Nomad Version 0.2.1 (pre-release)
>
> [os]
> Linux \ 2.6.18-1.2798.fc6 \ i386
>
> [java vm]
> Java HotSpot(TM) Client VM \ Sun Microsystems Inc. \ 1.5.0_09-b03
>
> [java path]
> java.library.path=/usr/java/jre1.5.0_09/lib/i386/client:/usr/java/ 
> jre1.5.0_09/lib/i386:/usr/java/jre1.5.0_09/../lib/i386
> java.class.path=nomad.jar
>
> ********************************************************************** 
> **********
>
> property file:conf/application.xml
> [STATUS] Loading
> splash:file:/home/ric/Desktop/nomad/data/images/splash.jpg
> [STATUS] Starting application.
> [STATUS] [PROGRESS] Initializing
> [STATUS] [PROGRESS] Images
> [STATUS] [PROGRESS] Modules
> [STATUS] [PROGRESS] Module builder
> [STATUS] [PROGRESS] Themes
> [STATUS] [PROGRESS] Nomad - 0.2.1 (pre-release)
> [STATUS] Stopping application...
> java.io.FileNotFoundException: conf/properties.xml (Permission denied)
>         at java.io.FileOutputStream.open(Native Method)
>         at java.io.FileOutputStream.<init>(Unknown Source)
>         at java.io.FileOutputStream.<init>(Unknown Source)
>         at
> net.sf.nmedit.nomad.core.application.Application.storeProperties 
> (Unknown
> Source)
>         at
> net.sf.nmedit.nomad.core.application.Application.storeProperties 
> (Unknown
> Source)
>         at
> net.sf.nmedit.nomad.core.application.Application.storeProperties 
> (Unknown
> Source)
>         at
> net.sf.nmedit.nomad.core.nomad.NomadEnvironment.stopInternal(Unknown
> Source)
>         at
> net.sf.nmedit.nomad.core.nomad.NomadApplication.stopInternal(Unknown
> Source)
>         at net.sf.nmedit.nomad.core.application.Application.stop 
> (Unknown
> Source)
>         at net.sf.nmedit.nomad.main.Nomad.exitNomad(Unknown Source)
>         at net.sf.nmedit.nomad.core.nomad.NomadApplication
> $1.windowClosing(Unknown Source)
>         at java.awt.AWTEventMulticaster.windowClosing(Unknown Source)
>         at java.awt.AWTEventMulticaster.windowClosing(Unknown Source)
>         at java.awt.Window.processWindowEvent(Unknown Source)
>         at javax.swing.JFrame.processWindowEvent(Unknown Source)
>         at java.awt.Window.processEvent(Unknown Source)
>         at java.awt.Component.dispatchEventImpl(Unknown Source)
>         at java.awt.Container.dispatchEventImpl(Unknown Source)
>         at java.awt.Window.dispatchEventImpl(Unknown Source)
>         at java.awt.Component.dispatchEvent(Unknown Source)
>         at java.awt.EventQueue.dispatchEvent(Unknown Source)
>         at java.awt.EventDispatchThread.pumpOneEventForHierarchy 
> (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)
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Nmedit-cvs mailing list
> Nme...@li...
> https://lists.sourceforge.net/lists/listinfo/nmedit-cvs

-------- Original Message --------
Subject: 	Re: [Nmedit-devel] Nomad (latest version) on Micromodular
Date: 	Wed, 13 Sep 2006 18:53:13 +0200
From: 	Marcus Andersson <mar...@sp...>
To: 	ne...@gm...
CC: 	nme...@li...
References: 	<200...@gm...>



Hi,

nescivi wrote:

>Hi,
>
>I just tried out Nomad on Debian Linux, with my Micromodular and came to the 
>following results:
>
>  
>
--

>Are there any tools I could use to sniff the midi communication that is going 
>on to help you guys?
>
>  
>

I have used midiox - http://www.midiox.com - in combination with midi 
yoke from the same site. Correcly configyred it will give you a log of 
the bidirectional midi traffic, that can then be analyzed. It is not 
obvious, at least not to me,  how to connect all midiports in midiox, 
and I don't remember how from the top of my head. If you fail to get it 
to work, I can give you exact instructions.

Marcus