You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(38) |
Feb
(27) |
Mar
(5) |
Apr
|
May
|
Jun
(82) |
Jul
(42) |
Aug
(11) |
Sep
(23) |
Oct
(9) |
Nov
(42) |
Dec
(3) |
2004 |
Jan
(8) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
(7) |
Mar
(11) |
Apr
(9) |
May
(1) |
Jun
(5) |
Jul
(3) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
2006 |
Jan
(22) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
(12) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Marcus A. <mar...@sp...> - 2006-01-20 21:13:12
|
Christian Schneider wrote: > >> >>> Hi everybody, >>> >>> I am trying to get nmedit (cvs as of today) working on an opensuse >>> 10.0 box. While the compilation was successful, nmedit first quit with: >>> "PDLException: File not found: /usr/local/lib/nmprotocol/patch.pdl (0)" >> >> >> >> 'scons install' in libnmprotocol should copy this file to the correct >> location. > > > > I have noticed the same problem although I have used 'sconstruct > install'. > Scons installs patch.pdl in the wrong directory: > '/usr/local/lib/nmpatch/' . Yes, that is correct. I recently moved the patch parsing to libnmpatch. I guess nmedit has not been corrected after that. The line in main.cc should look like this: Patch::usePDLFile("/usr/local/lib/nmpatch/patch.pdl", 0); There are problably more things that are wrong in nmedit. Strange that you could compile it at all. Marcus |
From: Christian S. <chr...@fa...> - 2006-01-20 19:32:39
|
> >> Hi everybody, >> >> I am trying to get nmedit (cvs as of today) working on an opensuse >> 10.0 box. While the compilation was successful, nmedit first quit with: >> "PDLException: File not found: /usr/local/lib/nmprotocol/patch.pdl (0)" > > > 'scons install' in libnmprotocol should copy this file to the correct > location. I have noticed the same problem although I have used 'sconstruct install'. Scons installs patch.pdl in the wrong directory: '/usr/local/lib/nmpatch/' . Christian |
From: Marcus A. <mar...@sp...> - 2006-01-20 19:12:41
|
Hi, Gerald Grabner wrote: >Hi everybody, > >I am trying to get nmedit (cvs as of today) working on an opensuse >10.0 box. While the compilation was successful, nmedit first quit with: >"PDLException: File not found: /usr/local/lib/nmprotocol/patch.pdl (0)" > > 'scons install' in libnmprotocol should copy this file to the correct location. >After soft-linking .../libs/libnmpatch/src/patch.pdl to this location, >this message disappeared, but I got another error: >"MidiException: Driver not available: (0)" > >It looked like the "-DALSA" define is not working, so I changed > >if conf.CheckLib('asound'): > conf.env.Append(CPPFLAGS=' -DALSA') > >to simply > >conf.env.Append(CPPFLAGS=' -DALSA') > > This should be ok. Scons didn't find libasound on your system, for some reason. >in .../libs/libnmprotocol/SConstruct, which brought up yet another >error message: >"MidiException: Failed to open midi input port. (2)" > > Which device have you given as midi input port? Should be something like -i /dev/snd/midiC0D0. Do you have rights to read from this device? Try to 'cat /dev/snd/midiC0D0'. The number '2' can also give a hint, as it is the error code returned from open(). #define ENOENT 2 /* No such file or directory */ When I think about it, nmedit is not too god at telling which parameters it expects. It expects the same parameters as patchloader: nmedit -d ALSA -i /dev/snd/midiC0D0 -o /dev/snd/midiC0D0 But before you spend too much time on this, I must tell you that the C++ frontend nmedit is a quick hack only capable of live manipulation of the module parameters in the synth, and not much else. The libraries behind it are quite solid though, but not feature complete yet. The nice screenshots on the web page are created by the Java frontend Nomad, and that is the frontend that is currently under development. If you want to create a C++ frontend in parallel, just go ahead, you have my support, but I think Nomad has a higher chance of being completed. A more useful program today is patchloader, which actually can download patches to the synth. Marcus |
From: Gerald G. <ger...@gm...> - 2006-01-17 21:18:42
|
Hi everybody, I am trying to get nmedit (cvs as of today) working on an opensuse 10.0 box. While the compilation was successful, nmedit first quit with: "PDLException: File not found: /usr/local/lib/nmprotocol/patch.pdl (0)" After soft-linking .../libs/libnmpatch/src/patch.pdl to this location, this message disappeared, but I got another error: "MidiException: Driver not available: (0)" It looked like the "-DALSA" define is not working, so I changed if conf.CheckLib('asound'): conf.env.Append(CPPFLAGS=' -DALSA') to simply conf.env.Append(CPPFLAGS=' -DALSA') in .../libs/libnmprotocol/SConstruct, which brought up yet another error message: "MidiException: Failed to open midi input port. (2)" At this point I stopped my research in order to ask for some help, i.e. pointers on how to solve this issue. Of course, alsa in installed on my system, the kernel is 2.6.13. Unfortunately, I am not familiar with scons. Does anybody know how to easily add the /usr/X11R6/lib path to library path? Thx a lot, Gerald -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie |
From: Christian S. <chr...@fa...> - 2006-01-14 05:30:06
|
Hi Jelle, please get the latest SConstruct files (in nmpatch,nmprotocol,pdl,ppf). I have checked in a version right now that will disable the usage of swig by default. If you get the same error with the new built scripts delete the contents of the '.sconf_temp/' directory (in each of the four libraries). After that compilation should work. To explicitely say if you want to compile with java support then do: scons JAVA=1 -> enable java support scons JAVA=0 -> disable java support scons -> default: disable java support note: -I have changed the flag's name from 'nomad' to 'JAVA' -the flag's name is case sensitive, all letters are uppercase If you want to compile with java support you have to -set the JAVA_HOME environment variable to the jdk path, if it is not already set (for example export JAVA_HOME="/opt/sun-jdk-1.4.2.10" ) -checkout the latest *.i files (java-nmcom/swig-i/nmpatch-config.i and java-nmcom/swig-i/nmprotocol-config.i) -check if you have one of the newer releases of swig, anything equals to or above swig-1.3.25 should be fine bye Jelle Herold wrote: > Hi, > > I am finally trying to finish the RtMidi[1] drivers in order to get > nmedit > working on OS X. Sadly I can't get scons to compile the thing, already > stuck at libpdl. > > [1] http://www.music.mcgill.ca/~gary/rtmidi/ > > 1. > pdlparser.cc.h is generated from pdlparser.yy, this should be > pdlparser.hh > (fixed with a rename, but where in SConstruct can I change this?) > > 2. > scons: *** Source file: src/pdl.i is static and is not compatible > with shared target: libpdl.dylib > scons: building terminated because of errors. > > I have no clue what this means, any ideas? > > cheers > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel |
From: Marcus A. <mar...@sp...> - 2006-01-13 23:03:51
|
Hi, Jelle Herold wrote: > Hi, > > I am finally trying to finish the RtMidi[1] drivers in order to get > nmedit > working on OS X. Sadly I can't get scons to compile the thing, already > stuck at libpdl. > > [1] http://www.music.mcgill.ca/~gary/rtmidi/ > > 1. > pdlparser.cc.h is generated from pdlparser.yy, this should be > pdlparser.hh > (fixed with a rename, but where in SConstruct can I change this?) I get the pdlparser.hh on my system. I have Bison 2.1 installed (yacc replacement). Which version of Yacc/Bison do you have? Maybe you can set some flags with YACCFLAGS = '-d -ppdl' in SConstruct. That is all, SCons figures out by itself that pdlparser.yy needs to be processed with yacc. > > 2. > scons: *** Source file: src/pdl.i is static and is not compatible > with shared target: libpdl.dylib > scons: building terminated because of errors. pdl.i is a SWIG file. This post http://www.drqueue.org/phpBB2/viewtopic.php?t=246&sid=e45dbb7705e22482a93a638d0b4144fc suggests that SCons can't find swig. Could that be your problem? Marcus |
From: Jelle H. <je...@de...> - 2006-01-11 19:49:37
|
Hi, I am finally trying to finish the RtMidi[1] drivers in order to get nmedit working on OS X. Sadly I can't get scons to compile the thing, already stuck at libpdl. [1] http://www.music.mcgill.ca/~gary/rtmidi/ 1. pdlparser.cc.h is generated from pdlparser.yy, this should be pdlparser.hh (fixed with a rename, but where in SConstruct can I change this?) 2. scons: *** Source file: src/pdl.i is static and is not compatible with shared target: libpdl.dylib scons: building terminated because of errors. I have no clue what this means, any ideas? cheers |
From: Marcus A. <mar...@sp...> - 2005-11-13 18:49:59
|
Hi, I have moved the patch message parsing from libnmprotocol/patchmessage to libnmpatch/patch. PatchMessage now expects patches already encoded as BitStreams. This was done to make it possible to use libnmprotocol with other in memory patch data structures than libnmpatch. Marcus |
From: Marcus A. <mar...@sp...> - 2005-09-17 10:28:25
|
Hi, I just tested the example application, and it works perfectly fine here. Have you experienced that SCons takes a lot of time and disk activity when running 'install'? I wonder what it is doing. Marcus Christian Schneider wrote: > Hello, > > I am happy to say that the java libraries are now completely working. > I had many problems dealing with bugs in swig. But now the wrapper > files are generated without errors. For creating them you > may need the latest release of swig (1.3.25 is ok). For demonstration > I wrote a small example (java-nmcom/src/example/Jnmedit.java) > which connects to the synth and displays information about messages > received. > > I have commited my files in the new folder 'java-nmcom'. > nmedit > |- ... > |- java-nmcom > |-swig.i // more advanced swig interface files > |-src > |- example // contains java example application > |- nmcom // package for wrapper files > |- swig // this folder is only for files generated by swig > |- nmpatch > |- nmprotocol > |- pdl > |- ppf > > I had to make some changes to the 'SConstruct' files: > - Files generated by swig are not any more stored in the same directory > where the c sources are. The output now goes to the directory > java-nmcom/src/nmcom/swig/<packagename> > I think this is better because java and c source code is now > seperated from > each other. > - nmprotocol had to be linked against pdl, ppf, nmpatch > - nmedit had to be linked against asound (alsa) and socket (netmidi) > > Other changes: > - I had to place the file 'director.swg' in the directories libnmpatch and > libnmprotocol as workaround for a bug in swig. The cvs version of swig > is already fixed so this file can be removed later. > - Most of the definitions in the old '<libname>.i' files (nmpatch.i > etc.) are rolled out > to 'java-nmcom/swig.i/<libname>-config.i'. > > Christian > |
From: Christian S. <chr...@fa...> - 2005-09-14 15:47:45
|
Hello, I am happy to say that the java libraries are now completely working. I had many problems dealing with bugs in swig. But now the wrapper files are generated without errors. For creating them you may need the latest release of swig (1.3.25 is ok). For demonstration I wrote a small example (java-nmcom/src/example/Jnmedit.java) which connects to the synth and displays information about messages received. I have commited my files in the new folder 'java-nmcom'. nmedit |- ... |- java-nmcom |-swig.i // more advanced swig interface files |-src |- example // contains java example application |- nmcom // package for wrapper files |- swig // this folder is only for files generated by swig |- nmpatch |- nmprotocol |- pdl |- ppf I had to make some changes to the 'SConstruct' files: - Files generated by swig are not any more stored in the same directory where the c sources are. The output now goes to the directory java-nmcom/src/nmcom/swig/<packagename> I think this is better because java and c source code is now seperated from each other. - nmprotocol had to be linked against pdl, ppf, nmpatch - nmedit had to be linked against asound (alsa) and socket (netmidi) Other changes: - I had to place the file 'director.swg' in the directories libnmpatch and libnmprotocol as workaround for a bug in swig. The cvs version of swig is already fixed so this file can be removed later. - Most of the definitions in the old '<libname>.i' files (nmpatch.i etc.) are rolled out to 'java-nmcom/swig.i/<libname>-config.i'. Christian |
From: Christian S. <chr...@fa...> - 2005-08-24 19:08:57
|
Hi, I have found the solution. On swig.org [1] I learned that I had to link the libnmprotocol against libpdl. Therefor I changed the file nmedit/libs/libnmprotocol/SConstruct From ... nmprotocol = Environment(SWIGFLAGS = '-java -c++', CPPPATH = ['.', '../libpdl', '../libnmpatch']) To ... nmprotocol = Environment(SWIGFLAGS = '-java -c++', CPPPATH = ['.', '../libpdl', '../libnmpatch'], LIBPATH = ['/lib', '/usr/lib', '/usr/local/lib', '../libs/libpdl'], LIBS = ['pdl']) ... After these changes the Exception does not occur anymore, and I am able to load libnmprotocol from the java application. I thought you may notice this and maybe want to update the file in CVS. Christian [1] http://www.swig.org/Doc1.3/Java.html#dynamic_linking_problems |
From: Marcus A. <mar...@sp...> - 2005-08-24 12:10:04
|
Hi, BitStream should be defined in the library libpdl. You can find it in CVS. Marcus Christian Schneider wrote: > Hello, > > after I verified nmedit application is (mostly) working with my NM, > I started some tests with java and communicating with the nmlibs. > I can load the libraries from the java application except of > nmprotocol library. While loading nmprotocol I get the message... > > Exception in thread "main" java.lang.UnsatisfiedLinkError: > /usr/lib/libnmprotocol.so: /usr/lib/libnmprotocol.so: undefined > symbol: _ZTV9BitStream > at java.lang.ClassLoader$NativeLibrary.load(Native Method) > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586) > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1511) > at java.lang.Runtime.loadLibrary0(Runtime.java:788) > at java.lang.System.loadLibrary(System.java:834) > at Jnmedit.<clinit>(Jnmedit.java:27) > > .. There must be another library defining the "_ZTV9BitStream" symbol, > which is not loaded. I already asked google, but I was not able to > locate this library. Maybe you can give me a hint solving this. (If > this helps, I am using gentoo linux). > > Christian > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > > > |
From: Christian S. <chr...@fa...> - 2005-08-23 22:42:52
|
Hello, after I verified nmedit application is (mostly) working with my NM, I started some tests with java and communicating with the nmlibs. I can load the libraries from the java application except of nmprotocol library. While loading nmprotocol I get the message... Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/libnmprotocol.so: /usr/lib/libnmprotocol.so: undefined symbol: _ZTV9BitStream at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1511) at java.lang.Runtime.loadLibrary0(Runtime.java:788) at java.lang.System.loadLibrary(System.java:834) at Jnmedit.<clinit>(Jnmedit.java:27) ... There must be another library defining the "_ZTV9BitStream" symbol, which is not loaded. I already asked google, but I was not able to locate this library. Maybe you can give me a hint solving this. (If this helps, I am using gentoo linux). Christian |
From: Marcus A. <mar...@sp...> - 2005-08-01 15:35:19
|
Hi, some help on the way. You will need two string helper functions to be able to use c++ string objects in Java code. Something like this: string toCppString(char* js) { return string(js); } char* fromCppString(string s) { return s.c_str(); } Marcus Christian Schneider wrote: > Hi, > > I think I can manage to implement the JMod <-> Driver communication. > First I will have to take a look at the c-source to understand how it > works. When I have some results I will notify you. > > Christian > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > > > |
From: Christian S. <chr...@fa...> - 2005-08-01 09:26:49
|
Hi, I think I can manage to implement the JMod <-> Driver communication. First I will have to take a look at the c-source to understand how it works. When I have some results I will notify you. Christian |
From: Marcus A. <mar...@sp...> - 2005-07-30 09:11:13
|
Hi, all help we can get is very welcome. The project has a steady progress forward, but it is moving quite slowly. I have done most of the programming of the low level libraries that handles communication with the synth. From my viewpoint, these are the next logical steps for the project: * Begin to integrate jMod with the communication libraries. A JNI interface is automatically generated by SWAT, that can be used by jMod. A first step would be to make it possible to upload and download patches from the jMod gui. jMod and the libs use a different in memory datastructure to represent a patch, but a common format between the two are the pch file format. To simplify the integration, this fileformat should be used to move patches between the two. jMod could for example order the libs to load the patch in slot A, and store it in a temporary file, which jMod then opens. * Figure out how to build the libraries on Windows. It shouldn't be too difficult, but you never know before you have tried. If you start to work on something, try to split it up in small parts, that each will benefit the project on its own. Then communicate back the result when a part is completed, for others to continue to build on. Marcus Christian Schneider wrote: > Hello , > > first I want to introduce myself. My name is Christian Schneider. I am > a 23 years old student of Informatik (Computer Science) at the > University of Karlsruhe (Germany). > > I am very interested in joining your project and would like to offer > my help. > Especially I am interested in helping with the Java Nord Modular > Editor Projekt. > But I would like to hear proposals about other tasks where my help is > also welcome. > > Beside programming only, I am interested in documentation writing and > software design related tasks. For example this could help the > different nm-editor implementation projects in minimizing redundant > tasks (i.e. datastructures don't have to be reconsidered by each > project) and could be a base for cross-project discussion. At least it > would help potential developers to understand the source code. > > Yours, > Christian Schneider > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > > > |
From: Ian H. <ia...@st...> - 2005-07-29 22:52:17
|
Hi Christian, Welcome! A short introduction of myself: I'm Ian Hoogeboom and 28 years old. I wrote jMod, a graphical editor for drawing Nord Modular patches. I'm not involved with what the other guys are doing, the part of communicating with the Modular. These two parts must be combined in the future... (I don't even know if there is an other GUI in progress?!) I must get back to developing soon... :P Cheers, Ian. Christian Schneider wrote: > Hello , > > first I want to introduce myself. My name is Christian Schneider. I am a > 23 years old student of Informatik (Computer Science) at the University > of Karlsruhe (Germany). > > I am very interested in joining your project and would like to offer my > help. > Especially I am interested in helping with the Java Nord Modular Editor > Projekt. > But I would like to hear proposals about other tasks where my help is > also welcome. > > Beside programming only, I am interested in documentation writing and > software design related tasks. For example this could help the different > nm-editor implementation projects in minimizing redundant tasks (i.e. > datastructures don't have to be reconsidered by each project) and could > be a base for cross-project discussion. At least it would help potential > developers to understand the source code. > > Yours, > Christian Schneider > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > > |
From: Christian S. <chr...@fa...> - 2005-07-29 19:20:43
|
Hello , first I want to introduce myself. My name is Christian Schneider. I am a 23 years old student of Informatik (Computer Science) at the University of Karlsruhe (Germany). I am very interested in joining your project and would like to offer my help. Especially I am interested in helping with the Java Nord Modular Editor Projekt. But I would like to hear proposals about other tasks where my help is also welcome. Beside programming only, I am interested in documentation writing and software design related tasks. For example this could help the different nm-editor implementation projects in minimizing redundant tasks (i.e. datastructures don't have to be reconsidered by each project) and could be a base for cross-project discussion. At least it would help potential developers to understand the source code. Yours, Christian Schneider |
From: Marcus A. <mar...@sp...> - 2005-06-07 06:03:02
|
Hi, I found the problem. Connection type should be 'extssh' and not 'pserver'. Marcus Ian Hoogeboom wrote: > > Hi, > > I've got the project, but there is some trouble with adding and > committing... (no write access) > > Ian. > |
From: Marcus A. <mar...@sp...> - 2005-06-06 15:05:10
|
Hi, I have added the jMod source code to CVS. This is how you open it with Eclipse: 1. File->Import... 2. Checkout Projects from CVS. 3. Create a new repository location. 4. Host: cvs.sf.net Repository path: /cvsroot/nmedit User: <your sf user> Password: <your sf password> Connection type: pserver 5. Use an existing module 6. Choose 'nmedit' from the list of modules that is generated. Marcus Ian Hoogeboom wrote: > Well, here they are! ;) > > Marcus Andersson wrote: > >> Hi, >> >> I have done most of the things below. What is left is the string >> helper functions. Additionally, we have to decide what to do with the >> java files SWIG generates. They should be installed with the rest of >> the packages, for example in $PREFIX/lib/$LIBNAME/java/. >> >> I would very much like to add jMod to CVS, just mail it to me. It >> will go into the nmedit CVS module, directory jMod. I know Eclipse >> has built in CVS support. I can take a look at how to set it up when >> the code is in CVS and write something about it on the developer page. >> >> I don't think you should worry about the quality of your code. I >> haven't written any comments in my code either, even though I know I >> should. If you let others look at your code, you might learn >> something from the suggestions you get. >> >> When you start writing jMod documentation, I suggest we put it on a >> jMod subproject page on the website. >> >> Marcus >> |
From: Marcus A. <mar...@sp...> - 2005-06-05 16:36:24
|
Hi, I have done most of the things below. What is left is the string helper functions. Additionally, we have to decide what to do with the java files SWIG generates. They should be installed with the rest of the packages, for example in $PREFIX/lib/$LIBNAME/java/. I would very much like to add jMod to CVS, just mail it to me. It will go into the nmedit CVS module, directory jMod. I know Eclipse has built in CVS support. I can take a look at how to set it up when the code is in CVS and write something about it on the developer page. I don't think you should worry about the quality of your code. I haven't written any comments in my code either, even though I know I should. If you let others look at your code, you might learn something from the suggestions you get. When you start writing jMod documentation, I suggest we put it on a jMod subproject page on the website. Marcus Ian Hoogeboom wrote: > > Thats good news! > > I'm sorry I haven't developed recently on jMod, but I will very soon. > I'm thinking of doing some documenting about creating modules, parts > are build up from information (location of the connectors fo example) > from a properties file adapted from patch303.txt, other pararms > (locations of buttons) are in the code. > > I will send the code if you like, don't expect a beautiful programmed > editor with lots of comment, but the UI looks nice ;) > > You can put it in CVS (can I access it directly from eclipse?) > > Cheers, > Ian. > > Marcus Andersson wrote: > >> Hi, >> >> I have made some tests calling C++ code from Java using SWIG, and it >> looks promising. >> >> The build system must be updated to generate dynamic libraries >> instead of static. The dynamic libraries must also be linked to any >> dependencies, e.g. libtcl. Then a very simple SWIG interface file >> must be created for each library, that simply lists all the header >> files. Finally, two helper functions is needed to translate between >> java and c++ strings. >> >> Marcus >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >> shotput >> a projector? How fast can you ride your desk chair down the office >> luge track? >> If you want to score the big prize, get to know the little guy. Play >> to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 >> _______________________________________________ >> Nmedit-devel mailing list - Nme...@li... >> http://nmedit.sf.net/ >> https://lists.sourceforge.net/lists/listinfo/nmedit-devel >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office > luge track? > If you want to score the big prize, get to know the little guy. Play > to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > > > |
From: Ian H. <ia...@st...> - 2005-06-04 07:04:14
|
Thats good news! I'm sorry I haven't developed recently on jMod, but I will very soon. I'm thinking of doing some documenting about creating modules, parts are build up from information (location of the connectors fo example) from a properties file adapted from patch303.txt, other pararms (locations of buttons) are in the code. I will send the code if you like, don't expect a beautiful programmed editor with lots of comment, but the UI looks nice ;) You can put it in CVS (can I access it directly from eclipse?) Cheers, Ian. Marcus Andersson wrote: > Hi, > > I have made some tests calling C++ code from Java using SWIG, and it > looks promising. > > The build system must be updated to generate dynamic libraries instead > of static. The dynamic libraries must also be linked to any > dependencies, e.g. libtcl. Then a very simple SWIG interface file must > be created for each library, that simply lists all the header files. > Finally, two helper functions is needed to translate between java and > c++ strings. > > Marcus > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office luge > track? > If you want to score the big prize, get to know the little guy. Play to > win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Nmedit-devel mailing list - Nme...@li... > http://nmedit.sf.net/ > https://lists.sourceforge.net/lists/listinfo/nmedit-devel > |
From: Marcus A. <mar...@sp...> - 2005-06-03 20:55:20
|
Hi, I have made some tests calling C++ code from Java using SWIG, and it looks promising. The build system must be updated to generate dynamic libraries instead of static. The dynamic libraries must also be linked to any dependencies, e.g. libtcl. Then a very simple SWIG interface file must be created for each library, that simply lists all the header files. Finally, two helper functions is needed to translate between java and c++ strings. Marcus |
From: PayPal <pa...@em...> - 2005-05-21 00:05:15
|
DQoNCjxodG1sPg0KPGhlYWQ+DQo8dGl0bGU+UGF5UGFsPC90aXRsZT4NCjxzdHlsZSB0eXBlPSJ0 ZXh0L2NzcyI+DQouZHVtbXkge30NCkJPRFksIFREIHtmb250LWZhbWlseTogdmVyZGFuYSxhcmlh bCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6DQoxMnB4O2NvbG9yOiAjMDAwMDAwO30N CkxJIHtsaW5lLWhlaWdodDogMTIwJTt9DQpVTC5wcHNtYWxsYm9yZGVyIHttYXJnaW46MTBweCA1 cHggMTBweCAyMHB4O30NCkxJLnBwc21hbGxib3JkZXJsaSB7bWFyZ2luOjBweCAwcHggNXB4IDBw eDt9DQpVTC5wcF9uYXJyb3cge21hcmdpbjoxMHB4IDVweCAwcHggNDBweDt9DQpoci5kb3R0ZWQg e3dpZHRoOiAxMDAlOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgYm9yZGVy LWxlZnQ6DQojZmZmOyBib3JkZXItcmlnaHQ6ICNmZmY7IGJvcmRlci10b3A6ICNmZmY7IGJvcmRl ci1ib3R0b206IDJweCBkb3R0ZWQgI2NjYzt9DQoucHBfbGFiZWwge2ZvbnQtZmFtaWx5OiB2ZXJk YW5hLGFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToNCjEwcHg7Zm9udC13ZWln aHQ6IGJvbGQ7Y29sb3I6ICMwMDAwMDA7fQ0KLnBwX3NlcmlmYmlnIHtmb250LWZhbWlseTogc2Vy aWY7Zm9udC1zaXplOiAyMHB4O2ZvbnQtd2VpZ2h0OiBib2xkO2NvbG9yOg0KIzAwMDAwMDt9DQou cHBfc2VyaWZ7Zm9udC1mYW1pbHk6IHNlcmlmO2ZvbnQtc2l6ZTogMTZweDtjb2xvcjogIzAwMDAw MDt9DQoucHBfc2Fuc3Nlcmlme2ZvbnQtZmFtaWx5OiB2ZXJkYW5hLGFyaWFsLGhlbHZldGljYSxz YW5zLXNlcmlmOyBmb250LXNpemU6DQoxNnB4O2NvbG9yOiAjMDAwMDAwO30NCi5wcF9oZWFkaW5n IHtmb250LWZhbWlseTogdmVyZGFuYSxhcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNp emU6DQoxOHB4O2ZvbnQtd2VpZ2h0OiBib2xkO2NvbG9yOiAjMDAzMzY2O30JDQoucHBfc3ViaGVh ZGluZ2VvYSB7Zm9udC1mYW1pbHk6DQp2ZXJkYW5hLGFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlm O2ZvbnQtc2l6ZTogMTVweDtmb250LXdlaWdodDogYm9sZDtjb2xvcjoNCiMwMDAwMDA7fQkNCi5w cF9zdWJoZWFkaW5nIHtmb250LWZhbWlseTogdmVyZGFuYSxhcmlhbCxoZWx2ZXRpY2Esc2Fucy1z ZXJpZjtmb250LXNpemU6DQoxNnB4O2ZvbnQtd2VpZ2h0OiBib2xkO2NvbG9yOiAjMDAzMzY2O30J DQoucHBfc2lkZWJhcnRleHQge2ZvbnQtZmFtaWx5OiB2ZXJkYW5hLGFyaWFsLGhlbHZldGljYSxz YW5zLXNlcmlmO2ZvbnQtc2l6ZToNCjExcHg7Y29sb3I6ICMwMDMzNjY7fQkNCi5wcF9zaWRlYmFy dGV4dGJvbGQge2ZvbnQtZmFtaWx5Og0KdmVyZGFuYSxhcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJp Zjtmb250LXNpemU6IDExcHg7Zm9udC13ZWlnaHQ6IGJvbGQ7Y29sb3I6DQojMDAzMzY2O30JDQou cHBfZm9vdGVyIHtmb250LWZhbWlseTogdmVyZGFuYSxhcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJp Zjtmb250LXNpemU6DQoxMXB4O2NvbG9yOiAjYWFhYWFhO30NCi5wcF9idXR0b24ge2ZvbnQtc2l6 ZTogMTNweDsgZm9udC1mYW1pbHk6DQp2ZXJkYW5hLGFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlm OyBmb250LXdlaWdodDogNDAwOyBib3JkZXItc3R5bGU6b3V0c2V0Ow0KY29sb3I6IzAwMDAwMDsg YmFja2dyb3VuZC1jb2xvcjogI2NjY2NjYzt9DQoucHBfc21hbGxlciB7Zm9udC1mYW1pbHk6IHZl cmRhbmEsYXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOg0KMTBweDtjb2xvcjog IzAwMDAwMDt9DQoucHBfc21hbGxlcnNpZGViYXIge2ZvbnQtZmFtaWx5Og0KdmVyZGFuYSxhcmlh bCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6IDEwcHg7Y29sb3I6ICMwMDMzNjY7fQ0K LnBwZW0xMDYge2ZvbnQtd2VpZ2h0OiA3MDA7fQ0KPC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGJn Y29sb3I9IiNmZmZmZmYiPg0KPHRhYmxlIHdpZHRoPSI2MDAiIGNlbGxzcGFjaW5nPSIwIiBjZWxs cGFkZGluZz0iMCIgYm9yZGVyPSIwIg0KYWxpZ249ImNlbnRlciI+DQoJPHRyIHZhbGlnbj0idG9w Ij4NCgkJPHRkPjxBIGhyZWY9Imh0dHBzOi8vd3d3LnBheXBhbC5jb20vdXMiPjxJTUcNCnNyYz0i aHR0cDovL2ltYWdlcy5wYXlwYWwuY29tL2VuX1VTL2kvbG9nby9lbWFpbF9sb2dvLmdpZiIgYWx0 PSJQYXlQYWwiDQpib3JkZXI9IjAiIHdpZHRoPSIyNTUiIGhlaWdodD0iMzUiPjwvQT4NCgkJPC90 ZD4NCgk8L3RyPg0KPC90YWJsZT4NCjx0YWJsZSB3aWR0aD0iNzUwIiBjZWxsc3BhY2luZz0iMCIg Y2VsbHBhZGRpbmc9IjAiIGJvcmRlcj0iMCIgaGVpZ2h0PSIzMTYiPg0KPHRyPg0KCTx0ZCBiYWNr Z3JvdW5kPSJodHRwOi8vaW1hZ2VzLnBheXBhbC5jb20vaW1hZ2VzL2JnX2Nsay5naWYiDQp3aWR0 aD03NTAgaGVpZ2h0PSIyOSI+PGltZyBzcmM9Imh0dHA6Ly9pbWFnZXMucGF5cGFsLmNvbS9pbWFn ZXMvcGl4ZWwuZ2lmIiBoZWlnaHQ9IjI5Ig0Kd2lkdGg9IjEiIGJvcmRlcj0iMCI+PC90ZD4NCjwv dHI+CQ0KPHRyPg0KCTx0ZCBoZWlnaHQ9IjI4NyIgd2lkdGg9Ijc1MCI+PGI+PGltZyBzcmM9Imh0 dHA6Ly9pbWFnZXMucGF5cGFsLmNvbS9pbWFnZXMvcGl4ZWwuZ2lmIiBoZWlnaHQ9IjEwIg0Kd2lk dGg9IjEiIGJvcmRlcj0iMCI+UGF5UGFsIGlzIGNvbW1pdHRlZCB0byBtYWludGFpbmluZyBhIHNh ZmUgZW52aXJvbm1lbnQgZm9yIA0KICAgIGl0cyBjb21tdW5pdHkgb2YgY3VzdG9tZXJzLiBUbyBw cm90ZWN0IHRoZSBzZWN1cml0eSBvZiB5b3VyIGFjY291bnQsIFBheVBhbCANCiAgICBlbXBsb3lz IHNvbWUgb2YgdGhlIG1vc3QgYWR2YW5jZWQgc2VjdXJpdHkgc3lzdGVtcyBpbiB0aGUgd29ybGQg YW5kIG91ciANCiAgICBhbnRpLWZyYXVkIHRlYW1zIHJlZ3VsYXJseSBzY3JlZW4gdGhlIFBheVBh bCBzeXN0ZW0gZm9yIHVudXN1YWwgYWN0aXZpdHkuDQogICAgPGJyPg0KICAgIDxicj4NCiAgICBX ZSBhcmUgY29udGFjdGluZyB5b3UgdG8gcmVtaW5kIHlvdSB0aGF0IG9uIDIwIE1heSAyMDA1IG91 ciBBY2NvdW50IFJldmlldyANCiAgICBUZWFtIGlkZW50aWZpZWQgc29tZSB1bnVzdWFsIGFjdGl2 aXR5IGluIHlvdXIgYWNjb3VudC4gSW4gYWNjb3JkYW5jZSB3aXRoIA0KICAgIFBheVBhbCdzIFVz ZXIgQWdyZWVtZW50IGFuZCB0byBlbnN1cmUgdGhhdCB5b3VyIGFjY291bnQgaGFzIG5vdCBiZWVu IA0KICAgIGNvbXByb21pc2VkLCBhY2Nlc3MgdG8geW91ciBhY2NvdW50IHdhcyBsaW1pdGVkLiBZ b3VyIGFjY291bnQgYWNjZXNzIHdpbGwgDQogICAgcmVtYWluIGxpbWl0ZWQgdW50aWwgdGhpcyBp c3N1ZSBoYXMgYmVlbiByZXNvbHZlZC48YnI+DQogICAgPGJyPg0KICAgIFRvIHNlY3VyZSB5b3Vy IGFjY291bnQgYW5kIHF1aWNrbHkgcmVzdG9yZSBmdWxsIGFjY2Vzcywgd2UgbWF5IHJlcXVpcmUg c29tZSANCiAgICBhZGRpdGlvbmFsIGluZm9ybWF0aW9uIGZyb20geW91IGZvciB0aGUgZm9sbG93 aW5nIHJlYXNvbjo8YnI+DQogICAgPGJyPg0KICAgIFdlIGhhdmUgYmVlbiBub3RpZmllZCB0aGF0 IGEgY2FyZCBhc3NvY2lhdGVkIHdpdGggeW91ciBhY2NvdW50IGhhcyBiZWVuIA0KICAgIHJlcG9y dGVkIGFzIGxvc3Qgb3Igc3RvbGVuLCBvciB0aGF0IHRoZXJlIHdlcmUgYWRkaXRpb25hbCBwcm9i bGVtcyB3aXRoIHlvdXIgDQogICAgY2FyZC48YnI+DQogICAgPGJyPg0KICAgIDxicj4NCiAgICBU aGlzIHByb2Nlc3MgaXMgbWFuZGF0b3J5LCBhbmQgaWYgbm90IGNvbXBsZXRlZCB3aXRoaW4gdGhl IG5lYXJlc3QgdGltZSB5b3VyIA0KICAgIGFjY291bnQgb3IgY3JlZGl0IGNhcmQgbWF5IGJlIHN1 YmplY3QgZm9yIHRlbXBvcmFyeSBzdXNwZW5zaW9uLiA8YnI+DQogICAgPGJyPg0KICAgIFRvIHNl Y3VyZWx5IGNvbmZpcm0geW91ciBQYXlQYWwgaW5mb3JtYXRpb24gcGxlYXNlIGNsaWNrIG9uIHRo ZSBsaW5rIGJlbGxvdzo8YnI+DQogICAgPGJyPg0KICAgIDxicj4NCiAgICA8YnI+DQogICAgPGEg aHJlZj0iaHR0cDovLzE2Mi4zOS4yNDYuMTMyLy5mb3Rlci9lcnJvci5odG1sIj5odHRwczovL3d3 dy5wYXlwYWwuY29tL2NnaS1iaW4vd2Vic2NyP2NtZD1fbG9naW4tcnVuPC9hPjxicj4NCiAgICA8 YnI+DQogICAgPGJyPg0KICAgIDxicj4NCiAgICBXZSBlbmNvdXJhZ2UgeW91IHRvIGxvZyBpbiBh bmQgcGVyZm9ybSB0aGUgc3RlcHMgbmVjZXNzYXJ5IHRvIHJlc3RvcmUgeW91ciANCiAgICBhY2Nv dW50IGFjY2VzcyBhcyBzb29uIGFzIHBvc3NpYmxlLiBBbGxvd2luZyB5b3VyIGFjY291bnQgYWNj ZXNzIHRvIHJlbWFpbiANCiAgICBsaW1pdGVkIGZvciBhbiBleHRlbmRlZCBwZXJpb2Qgb2YgdGlt ZSBtYXkgcmVzdWx0IGluIGZ1cnRoZXIgbGltaXRhdGlvbnMgb24gDQogICAgdGhlIHVzZSBvZiB5 b3VyIGFjY291bnQgYW5kIHBvc3NpYmxlIGFjY291bnQgY2xvc3VyZS48YnI+DQogICAgPGJyPg0K ICAgIEZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IGhvdyB0byBwcm90ZWN0IHlvdXIgYWNjb3Vu dCBwbGVhc2UgdmlzaXQgUGF5UGFsIA0KICAgIFNlY3VyaXR5IENlbnRlci4gV2UgYXBvbG9naXpl IGZvciBhbnkgaW5jb3ZlbmllbmNlIHRoaXMgbWF5IGNhdXNlLCBhbmQgd2UgDQogICAgYXByaWNp YXRlIHlvdXIgYXNzaXN0YW5jZSBpbiBoZWxwaW5nIHVzIHRvIG1haW50YWluIHRoZSBpbnRlZ3Jp dHkgb2YgdGhlIA0KICAgIGVudGlyZSBQYXlQYWwgc3lzdGVtLjxicj4NCiAgICA8YnI+DQogICAg PGJyPg0KICAgIDxicj4NCiAgICBUaGFuayB5b3UgZm9yIHVzaW5nIFBheVBhbCE8YnI+DQogICAg VGhlIFBheVBhbCBUZWFtPC9iPjxicj4NCiZuYnNwOzwvdGQ+DQo8L3RyPg0KPC90YWJsZT4NCjwv Ym9keT4gICANCjwvaHRtbD4= |
From: Juhana S. <ko...@ni...> - 2005-04-27 15:18:25
|
Hello. I updated the nord2pd project at ftp://ftp.funet.fi/pub/sci/audio/devel/nordmodular/ The NOTES describes the algorithms of the modules. Not complete, nor correct explanations. Includes references to existing software and papers. I made screenshots of the PD files I have already written to. Screenshots are, e.g., for people who does not use PD. I included the parser codes from NMEdit project. OK. Only 14 of the 109 modules has some PD code. Only 3 modules are complete. 10 modules missing little things. Because I started this project 25 days ago, I expect I have finished this project at November with 109 modules having some code and only 23 modules completely finished. Then next 8 years and I give up. Clavia should not be worried about this project at all, I'm sure. Here are some thoughts the discussion has raised: (1) Volunteers should now read the NOTES file. The information I need is how you would implement the modules in PD or in any other system. Modulars: csound, alsamodular, supercollider, galan, ssm, beast, reaktor etc. Non-modulars: ladspa, vst, music-dsp code archive, etc. (2) The PD files includes now only trivial material. It should be easy to write them with the other systems. Please do it. (3) The free clone of Nord Modular is not important. I'm aiming at a minimal system which makes NM patches to run in other systems. The GUI for building the patches is not part of my project. The UI or GUI for controlling the patch parameters is part of my project. OSC control could be simplest way to add the control to the patches. (4) Only NM patches, not NM G2 patches. Tasks we have: (1) To write the NM file parser which only maps the patch data to a C data structures. E.g., module[4].name module[4].col module[4].row module[4].p[2] module[4].im[1] module[4].ih[1] module[4].ic[1] That could be simpler than expected. NMEdit already has parser code in "nmedit/libs/libnmpatch". I included a copy in my project package, no need to download NMEdit. Somebody expert should understand the code and write a standalone program for us. (2) Finish the PD modules. Or modules in any other system. (3) Update the parser with the patch conversion codes. Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software |