From: Joe E. <jo...@em...> - 2011-09-01 15:29:41
|
On 9/1/2011 7:09 AM, frankster wrote: > Looking on google there is a guy who has generated drivers for two of > his own synths, yet this is not part of the code in SVN. He's written > quite a lot of info about it here > http://sites.google.com/site/experimentalfrush/jsynthlib and apparently > started the WIKI that was linked to this list yesterday. What a waste!! Okay... in the interest of generating some renewed interest, I'll add any new synths/changes people send to me. I just checked out the SVN trunk, so I can add in whatever people want. Oh, and I just checked... it looks like I might be a project admin, so I can grant SVN access to people. > Google also reveals that there is also some refactoring effort or > something that someone was doing a couple of years ago: > https://github.com/jpcaruana/jsynthlib - dunno if this is the same > refactoring effort that Joe Emenaker was talking about earlier or if its > a different attempt. Must be different. I didn't share my code with anybody because I was changing so much.... > And as there are more synths in SVN than appear on > http://www.jsynthlib.org/synths.html, I wonder if there should at some > point be a release to make these drivers available to more people One of the things I'd like to see next is a mechanism to load just the synth drivers that you need. As things are now, compiling JSynthLib means compiling *all* of the synth drivers, and the same goes for distributing it. If we hope to add many more synth drivers, this is going to get out of control. So, we'll need to come up with a way where we can just compile/distribute the core JSynthLib app, and then have that app load the individual synth drivers from individual jar files or something. - Joe |