jsynthlib-devel — Mailing list for developers and users interested in improving the JSynthLib.

Re: [Jsynthlib-devel] New developers for JSynthLib

[Joachim <li...@sd...>]

Frankie,

I have added you as a developer.

Anyone willing to provide code can of course be added.
Just say so instead of discussing how dead the project is
and that you are thinking about a fork.

Cheers
Joachim


Am 01.09.2011 05:29, schrieb frankster:
> I found and fixed some errors in drivers for Yamaha01v, RolandJD800,
> NovationSBS which caused the auto scan feature to incorrectly detect any
> synth that responds as one of those.
>
> I have added a patch to the project patch queue and also uploaded it to
> the git repository I created:
> https://gitorious.org/jsynthlib-temporary-development/jsynthlib-temp
>
> cheers,
> Frankie
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

[Vladimir A. <vl...@gm...>]

On 09/01/2011 10:02 AM, Joe Emenaker wrote:
> 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.
>

I would suggests looking at plugin implementation in jedit. Plugins there are dynamically loadable, and there is a plugin manager that can download plugins directly from source forge site and install on the fly.

Regards,
Vladimir

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

[frankster <jsy...@te...>]

Hi,
Well I hope noone takes offence if I sounded a little critical of the 
jsynthlib project! :)

IMO if you have part of a synth driver working - e.g. single patch 
librarian - its good to submit that part and get it out there. then as 
you get more parts done to add them in as well. If noone's using the 
driver then noone's going to report any bugs (or fix them themselves!).

If by review you mean a code review by someone else, I could give your 
drivers a lookover if you think that would be useful, although I'm not 
mega familiar with the jsynthlib codebase yet,

cheers,
Frankie


On 09/01/11 16:46, Peter Geirnaert wrote:
> Hi there
>
> I'm the one the OP was talking about, who wrote two drivers and a wiki.
> Don't blame the JSynthLIb community for my code not being in SVN, I didn't
> ask for it because I feel like my code is not yet finished. I had to stop
> putting time in programming because I had to find a real job (meaning it
> makes money). I also didn't have internet at home for about a year. Now I've
> a job and internet so I'm thinking about picking up JSynthLib again. The
> work I've done on the drivers needs a good review too, I'm  not even sure
> where I put the last reviewed files.
>
> It's always nice to see this list wake up again, after a long sleep once in
> a while.
>
> Greetings from the Belgium
>
> Peter
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

[Peter G. <pet...@gm...>]

Hi there

I'm the one the OP was talking about, who wrote two drivers and a wiki.
Don't blame the JSynthLIb community for my code not being in SVN, I didn't
ask for it because I feel like my code is not yet finished. I had to stop
putting time in programming because I had to find a real job (meaning it
makes money). I also didn't have internet at home for about a year. Now I've
a job and internet so I'm thinking about picking up JSynthLib again. The
work I've done on the drivers needs a good review too, I'm  not even sure
where I put the last reviewed files.

It's always nice to see this list wake up again, after a long sleep once in
a while.

Greetings from the Belgium

Peter

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

[Joe E. <jo...@em...>]

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

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

[Vladimir A. <vl...@gm...>]

I think what the project is missing is releasing binary builds from svn for download on regular basis.

That would allow more extensive testing of experimental code by people without programming skills required to build themselves, but who really could use the program in real world.

That probably also would encouraged potential contributers to release code at main project site.

These sites that you found are really examples of creepy forking of the project, which just is washing out developers resources.

I hope those people are still subscribed to this list and will pay attention at this discussion and maybe would turn back to contributing here.

Regards,
Vladimir


On 09/01/2011 09: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!!
>
> He's been updating his driver for the SPD11 as recently as July this
> year judging by his github (
> https://github.com/freqrush/RolandSPD11_JSynthLib/ and
> https://github.com/freqrush/YamahaCS2x_JSynthLib ), so its a waste that
> he's going to all this effort and its not getting incorporated into the
> SVN repository.
>
> 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.
>
> My general feeling is that all this work should be taking part on the
> developer list, and all this work (the good stuff at least) should be
> getting brought into the main jsynthlib repository. So the project seems
> to have in recent times failed to engage with the developers that
> obviously want to help it advance! which is a shame really.
>
> 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 - if
> they're not getting used they're not going to get improved! Or at least
> update this web page so that it reflects the current state of the
> development branch.
>
> This is what I think anyway.
>
> Regards,
> Frankie
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] fixed build error in trunk

[Vladimir A. <vl...@gm...>]

Joe,

You are listed as project admin. Did you ever try adding anyone to svn access?

Few months ago you said you could add me to the project, but that ended with nothing. Did any other admins objected? Or it just did not work technically?

Regarding you experimental work:

The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use.

If you would put you refactoring effort on the branch 4 years ago, there would be a good chance someone could pick it up and help you finish it. When i was working on driver code, I was wondering on some design choices for class hierarchy, and I was very itchy myself to refactor the code. I decided to hold my horses until I could at least discuss that with main developers.

So, please, create a branch for refactoring and commit you work there. It would be a shame to waste that effort.

Regard,
Vladimir

On 08/31/2011 10:40 PM, Joe Emenaker wrote:
> On 8/31/2011 4:14 PM, Michael Hawkins wrote:
>> I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill!
> I don't think Bill is an "admin" (in the sense that he can't authorize
> people to upload to the svn repository); I think only Joachim and Brian
> are. The rest of us (about 15 others) have write-access to the svn, but
> we can't add people.
>
>> The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing!
> About 4 years ago, I started on a massive (for me) re-factoring of the
> code. I moved everything into packages which compartmentalized what
> everything did (ie, a package for low-level MIDI message handling, a
> package for the main GUI, a package for the widgets, etc.). The two big
> hurdles were:
> 1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling
> for MIDI signals was done with the GUI thread or something, so I made a
> new thread which would handle all queuing of MIDI messages and notify
> various sysex handlers that something had come in for them, etc. It made
> it so that I could write a little MIDI monitor window to watch incoming
> traffic, etc.
> 2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that
> the basic JSynthlib window was named something strange, which made it
> hard to get up to speed on how to make a new synth-lib module.
>
> Anyway, as you can imagine, with a huge refactor like that, there were
> tons of compile errors as I changed around the way things were invoked,
> etc. When I ran out of steam on it, I think there were still a handful
> of errors that I couldn't really figure out how to best solve... so I
> never committed the changes.
>
> Since the project is so dormant, I'm tempted to dig the code up again
> and commit it just to see if it generates some renewed interest...
>
> - Joe
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

[Jsynthlib-devel] synth support that's not made it into SVN!!

[frankster <jsy...@te...>]

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!!

He's been updating his driver for the SPD11 as recently as July this 
year judging by his github ( 
https://github.com/freqrush/RolandSPD11_JSynthLib/ and 
https://github.com/freqrush/YamahaCS2x_JSynthLib ), so its a waste that 
he's going to all this effort and its not getting incorporated into the 
SVN repository.

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.

My general feeling is that all this work should be taking part on the 
developer list, and all this work (the good stuff at least) should be 
getting brought into the main jsynthlib repository. So the project seems 
to have in recent times failed to engage with the developers that 
obviously want to help it advance! which is a shame really.

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 - if 
they're not getting used they're not going to get improved! Or at least 
update this web page so that it reflects the current state of the 
development branch.

This is what I think anyway.

Regards,
Frankie

Re: [Jsynthlib-devel] fixed build error in trunk

[frankster <jsy...@te...>]

On 01/09/2011 04:40, Joe Emenaker wrote:
> I don't think Bill is an "admin" (in the sense that he can't authorize
> people to upload to the svn repository); I think only Joachim and
> Brian are. The rest of us (about 15 others) have write-access to the
> svn, but we can't add people. 

Maybe you can have a look at the patches on the tracker and submit them
into cvs ;)
>
> Since the project is so dormant, I'm tempted to dig the code up again 
> and commit it just to see if it generates some renewed interest...

Sounds like a good idea to me.


Frankie

Re: [Jsynthlib-devel] fixed build error in trunk

[Joe E. <jo...@em...>]

On 8/31/2011 4:14 PM, Michael Hawkins wrote:
> I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill!

I don't think Bill is an "admin" (in the sense that he can't authorize 
people to upload to the svn repository); I think only Joachim and Brian 
are. The rest of us (about 15 others) have write-access to the svn, but 
we can't add people.

> The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing!

About 4 years ago, I started on a massive (for me) re-factoring of the 
code. I moved everything into packages which compartmentalized what 
everything did (ie, a package for low-level MIDI message handling, a 
package for the main GUI, a package for the widgets, etc.). The two big 
hurdles were:
1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling 
for MIDI signals was done with the GUI thread or something, so I made a 
new thread which would handle all queuing of MIDI messages and notify 
various sysex handlers that something had come in for them, etc. It made 
it so that I could write a little MIDI monitor window to watch incoming 
traffic, etc.
2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that 
the basic JSynthlib window was named something strange, which made it 
hard to get up to speed on how to make a new synth-lib module.

Anyway, as you can imagine, with a huge refactor like that, there were 
tons of compile errors as I changed around the way things were invoked, 
etc. When I ran out of steam on it, I think there were still a handful 
of errors that I couldn't really figure out how to best solve... so I 
never committed the changes.

Since the project is so dormant, I'm tempted to dig the code up again 
and commit it just to see if it generates some renewed interest...

- Joe

[Jsynthlib-devel] FIX: autoscan incorrect identification problems

[frankster <jsy...@te...>]

I found and fixed some errors in drivers for Yamaha01v, RolandJD800,
NovationSBS which caused the auto scan feature to incorrectly detect any
synth that responds as one of those.

I have added a patch to the project patch queue and also uploaded it to
the git repository I created:
https://gitorious.org/jsynthlib-temporary-development/jsynthlib-temp

cheers,
Frankie

Re: [Jsynthlib-devel] Jsynthlib-devel Digest, Vol 19, Issue 1

[frankster <jsy...@te...>]

Vladimir,

Although I understand the frustration, I'm a bit skeptical about forking
the project because it would potentially throw away a lot of useful
stuff this project has built up - e.g. the documentation such as the
"how to add a synth guides" which seems quite accessible, links to the
sourceforge website etc. However its useless if noone who has patches
available can get them shared with other people easily. Looking back
through the list, not only have there been several posts from people who
have offered code that doesn't seem to have been included for whatever
reason, but the build issue that I fixed in about 5 minutes was reported
back in 2009! So the SVN has been broken for 2 years!

I propose a temporary alternative repository that we can use to get some
changes done until someone with svn access takes interest in the project
again. To get the ball rolling, I have created a git repository over at
gitorious.org and I have uploaded my patched version of the svn trunk to
it. Perhaps you might want to upload your SY77 code to it? Its at
https://gitorious.org/jsynthlib-temporary-development/jsynthlib-temp

I plan next to start working on support for my Proteus 2000 - I note
that you also have this synth so maybe we can work together on it.


Regards,

Frankie

On 31/08/2011 23:16, jsy...@li... wrote:
> Message: 6
> Date: Wed, 31 Aug 2011 17:16:08 -0500
> From: Vladimir Avdonin <vl...@gm...>
> Subject: Re: [Jsynthlib-devel] fixed build error in trunk
> To: jsy...@li...
> Message-ID: <4E5...@gm...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Checking back archives of the list brings several offers from different people to contribute already made changes, like the one that started this thread. They all were "calmed down" all right because of absence of any activity from developers with svn access.
>
> In general, I would think Source Forge should allow creating branches in any project's repository by anyone, not just to registered developers of the project. That way actual changes can be published and tested by much broader audience, sort of wikipedia approach.
>
> I have deep respect to the work that have been done by creators of the project, but currently the project is not being improved, and does not accept any help being offered. And improvements can still be made in different parts of the project, not just adding drivers for new synths. Such state of affairs pretty much means dead project to me.
>
> I hope the project will be revived either as continuation of current line of development, or as a fork.
>
> As for doing something first - I already offered few months ago a librarian for yamaha sy77. Shall i dump it in form of patch onto the list?
>
> Regards,
> Vladimir
>
> On 08/31/2011 04:00 PM, Joachim wrote:
>> > Hi,
>> >
>> > there were already some speaking about taking over/forking.
>> > All of them calmed down pretty soon.
>> >
>> > My advise is: Develop something new first and then eventually
>> > start thinking about a fork.
>> >
>> > But I'm pretty suer there is no need for a fork: If you want to do something,
>> > simply do it and don't just talk about doing it.
>> >
>> > Cheers
>> > Joachim
>> >
>> > Am 31.08.2011 20:20, schrieb Vladimir Avdonin:
>>> >> Hi,
>>> >>
>>> >> The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project.
>>> >>
>>> >> I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Vladimir
>>> >>
>>> >> On 08/30/2011 08:37 PM, frankster wrote:
>>>> >>> Hi,
>>>> >>> I have downloaded the latest version of jsynthlib from svn and found
>>>> >>> that there are various problems with the code in trunk.
>>>> >>> * The RolandD10 driver seems to use features from Java 1.5 whereas the
>>>> >>> build.xml specifies version 1.4.2.
>>>> >>> * Some files are not encoded correctly causing warnings about unmappable
>>>> >>> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers.
>>>> >>>
>>>> >>> I have updated the build.xml to specify Java 1.5 - this seems better
>>>> >>> than rewriting some of the RolandD10 driver. I have saved the relevant
>>>> >>> files in the Yamaha drivers as UTF8.
>>>> >>>
>>>> >>> Is there anybody with SVN access that can put these fixes into the
>>>> >>> repository? Also if anybody wants a copy of these minor fixes off me
>>>> >>> before they find their way into SVN, then I can email the files that I
>>>> >>> have changed.
>>>> >>>
>>>> >>> Looking at the mailing list, this project seems dead lately but maybe
>>>> >>> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000
>>>> >>> and Roland U220) that are not supported by jsynthlib and I may be
>>>> >>> motivated to add support for them if there's anyone still interested in
>>>> >>> this project.
>>>> >>>
>>>> >>>
>>>> >>> Regards,
>>>> >>> Frankie
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> ------------------------------------------------------------------------------
>>>> >>> Special Offer -- Download ArcSight Logger for FREE!
>>>> >>> Finally, a world-class log management solution at an even better
>>>> >>> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>>>> >>> download Logger. Secure your free ArcSight Logger TODAY!
>>>> >>> http://p.sf.net/sfu/arcsisghtdev2dev
>>>> >>> _______________________________________________
>>>> >>> Jsynthlib-devel mailing list
>>>> >>> Jsy...@li...
>>>> >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>>> >>
>>> >> ------------------------------------------------------------------------------
>>> >> Special Offer -- Download ArcSight Logger for FREE!
>>> >> Finally, a world-class log management solution at an even better
>>> >> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>>> >> download Logger. Secure your free ArcSight Logger TODAY!
>>> >> http://p.sf.net/sfu/arcsisghtdev2dev
>>> >> _______________________________________________
>>> >> Jsynthlib-devel mailing list
>>> >> Jsy...@li...
>>> >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>>> >>
>> >
>> > ------------------------------------------------------------------------------
>> > Special Offer -- Download ArcSight Logger for FREE!
>> > Finally, a world-class log management solution at an even better
>> > price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>> > download Logger. Secure your free ArcSight Logger TODAY!
>> > http://p.sf.net/sfu/arcsisghtdev2dev
>> > _______________________________________________
>> > Jsynthlib-devel mailing list
>> > Jsy...@li...
>> > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better 
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
>
> ------------------------------
>
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] fixed build error in trunk

[Vladimir A. <vl...@gm...>]

Well, after looking carefully at developer section of the project I discovered civilized way for occasional developer to submit changes. There is a patch section. The lonely patch that i found in there was molding  there since 2009. The patch added support for SY85.

So I added a couple of patches there. I suggest anyone with useful changes contribute through that interfaces as well. We will see how that would work.

BTW, there is also bug tracker for the project.

Lets try to bring the project to life in a civilized way using available tools. If all this activity would still be ignored by project owners, then it would be worth discussing other options.

I really would like the current project live and improve. There is a good website, decent  documentation, and even centralized patch archive. This all could be brought from good to great

Regards,
Vladimir



On 08/31/2011 06:37 PM, William Zwicky wrote:
> I'm not an admin, so I can't help.  That's why I threatened to fork.
>
> It looks like the developer docs are hard to find.  Do you know about the
> wiki?
> http://jsynthlib.wikispaces.com/
>
> -Bill Zwicky
>
>
> On Wed, Aug 31, 2011 at 4:14 PM, Michael Hawkins<pat...@ya...>wrote:
>
>> I ran into some rather tough jsynthlib admin's a couple of years back. I
>> think it was you Bill! But in retrospect, I understand why the admins were
>> tough on me because I now know that I then new nothing about what I was
>> doing. But my, my was it hard trying to get up to speed with jsynthlib with
>> that kind of newbie treatment.
>>
>> Well, that water has gone under the bridge so I do recommend opening
>> jsynthlib up for wider contribution. Basically, I think that anyone that
>> wants to join the development team should be permitted to submit changes. I
>> doubt that vandals will be all that interested in jsynthlib. Let's face it,
>> it's been almost impossible to get any developers interested! And I don't
>> think it's because of lack of functionality nor do I think it's because of
>> total lack of interest. A cross platform MIDI librarian is a wonderful thing
>> to my mind.
>>
>> The only thing that drives me nuts about jsynthlib is the maddening process
>> of laying out widgets. There simply has to be either better documentation on
>> it or a better way of doing it. But maybe I just still don't know what I am
>> doing!
>>
>> Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I
>> am quite sure we would get a bit more support from the wider community out
>> there.
>>
>> Please add me as a developer! I promise not to intentionally vandalize!
>>
>>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] fixed build error in trunk

[William Z. <wrz...@po...>]

I'm not an admin, so I can't help.  That's why I threatened to fork.

It looks like the developer docs are hard to find.  Do you know about the
wiki?
http://jsynthlib.wikispaces.com/

-Bill Zwicky


On Wed, Aug 31, 2011 at 4:14 PM, Michael Hawkins <pat...@ya...>wrote:

> I ran into some rather tough jsynthlib admin's a couple of years back. I
> think it was you Bill! But in retrospect, I understand why the admins were
> tough on me because I now know that I then new nothing about what I was
> doing. But my, my was it hard trying to get up to speed with jsynthlib with
> that kind of newbie treatment.
>
> Well, that water has gone under the bridge so I do recommend opening
> jsynthlib up for wider contribution. Basically, I think that anyone that
> wants to join the development team should be permitted to submit changes. I
> doubt that vandals will be all that interested in jsynthlib. Let's face it,
> it's been almost impossible to get any developers interested! And I don't
> think it's because of lack of functionality nor do I think it's because of
> total lack of interest. A cross platform MIDI librarian is a wonderful thing
> to my mind.
>
> The only thing that drives me nuts about jsynthlib is the maddening process
> of laying out widgets. There simply has to be either better documentation on
> it or a better way of doing it. But maybe I just still don't know what I am
> doing!
>
> Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I
> am quite sure we would get a bit more support from the wider community out
> there.
>
> Please add me as a developer! I promise not to intentionally vandalize!
>
>

Re: [Jsynthlib-devel] fixed build error in trunk

[Michael H. <pat...@ya...>]

I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! But in retrospect, I understand why the admins were tough on me because I now know that I then new nothing about what I was doing. But my, my was it hard trying to get up to speed with jsynthlib with that kind of newbie treatment.

Well, that water has gone under the bridge so I do recommend opening jsynthlib up for wider contribution. Basically, I think that anyone that wants to join the development team should be permitted to submit changes. I doubt that vandals will be all that interested in jsynthlib. Let's face it, it's been almost impossible to get any developers interested! And I don't think it's because of lack of functionality nor do I think it's because of total lack of interest. A cross platform MIDI librarian is a wonderful thing to my mind.

The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing!


Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I am quite sure we would get a bit more support from the wider community out there.


Please add me as a developer! I promise not to intentionally vandalize!


Mike



________________________________
From: William Zwicky <wrz...@po...>
To: 
Cc: jsy...@li...
Sent: Wednesday, August 31, 2011 6:45 PM
Subject: Re: [Jsynthlib-devel] fixed build error in trunk

Any admins still around?  I think we should unlock the project so anyone can
check in at any time.  We might run the risk of having a vandal visit, but I
think it's more important to make life easier for the occasional developer.

If nobody responds, I may just do this myself.  I'll call it "JSynthLib
Anarchy". =^)

-Bill Zwicky
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Jsynthlib-devel mailing list
Jsy...@li...
https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] fixed build error in trunk

[Daniel R. <dr....@co...>]

Vladimir, are there any restrictions on forking (license-wise)? Are the
project owners alive and responding, at least?

JSynthlib is great, no doubt. I borrowed some code from there when I knew
even less of what I was doing in terms of MIDI in Java. Then I decided to
ignore JSynth entirely and I ended up writing
confusionists.com/handsonicwhich turned out to be a mildly popular
product. I have no point here,
really, but I think that the usability concerns for end-users are a causal
factor in the lack of interest.

Speaking of open-source projects with very little public development
interest, I have created confusionists.com/mjdj, a MIDI translator or
morpher engine and API framework. I mention this because if anybody out
there (with an interest in Java and MIDI) would be interested in taking a
run through the code, it would really help out.

Good luck with JSynthlib. This list hasn't produced any mail in months, so
you might be on to something by starting anew.

Best,
Daniel

Re: [Jsynthlib-devel] fixed build error in trunk

[William Z. <wrz...@po...>]

Any admins still around?  I think we should unlock the project so anyone can
check in at any time.  We might run the risk of having a vandal visit, but I
think it's more important to make life easier for the occasional developer.

If nobody responds, I may just do this myself.  I'll call it "JSynthLib
Anarchy". =^)

-Bill Zwicky

Re: [Jsynthlib-devel] fixed build error in trunk

[Vladimir A. <vl...@gm...>]

Checking back archives of the list brings several offers from different people to contribute already made changes, like the one that started this thread. They all were "calmed down" all right because of absence of any activity from developers with svn access.

In general, I would think Source Forge should allow creating branches in any project's repository by anyone, not just to registered developers of the project. That way actual changes can be published and tested by much broader audience, sort of wikipedia approach.

I have deep respect to the work that have been done by creators of the project, but currently the project is not being improved, and does not accept any help being offered. And improvements can still be made in different parts of the project, not just adding drivers for new synths. Such state of affairs pretty much means dead project to me.

I hope the project will be revived either as continuation of current line of development, or as a fork.

As for doing something first - I already offered few months ago a librarian for yamaha sy77. Shall i dump it in form of patch onto the list?

Regards,
Vladimir

On 08/31/2011 04:00 PM, Joachim wrote:
> Hi,
>
> there were already some speaking about taking over/forking.
> All of them calmed down pretty soon.
>
> My advise is: Develop something new first and then eventually
> start thinking about a fork.
>
> But I'm pretty suer there is no need for a fork: If you want to do something,
> simply do it and don't just talk about doing it.
>
> Cheers
> Joachim
>
> Am 31.08.2011 20:20, schrieb Vladimir Avdonin:
>> Hi,
>>
>> The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project.
>>
>> I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron.
>>
>> Regards,
>>
>> Vladimir
>>
>> On 08/30/2011 08:37 PM, frankster wrote:
>>> Hi,
>>> I have downloaded the latest version of jsynthlib from svn and found
>>> that there are various problems with the code in trunk.
>>> * The RolandD10 driver seems to use features from Java 1.5 whereas the
>>> build.xml specifies version 1.4.2.
>>> * Some files are not encoded correctly causing warnings about unmappable
>>> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers.
>>>
>>> I have updated the build.xml to specify Java 1.5 - this seems better
>>> than rewriting some of the RolandD10 driver. I have saved the relevant
>>> files in the Yamaha drivers as UTF8.
>>>
>>> Is there anybody with SVN access that can put these fixes into the
>>> repository? Also if anybody wants a copy of these minor fixes off me
>>> before they find their way into SVN, then I can email the files that I
>>> have changed.
>>>
>>> Looking at the mailing list, this project seems dead lately but maybe
>>> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000
>>> and Roland U220) that are not supported by jsynthlib and I may be
>>> motivated to add support for them if there's anyone still interested in
>>> this project.
>>>
>>>
>>> Regards,
>>> Frankie
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Special Offer -- Download ArcSight Logger for FREE!
>>> Finally, a world-class log management solution at an even better
>>> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>>> download Logger. Secure your free ArcSight Logger TODAY!
>>> http://p.sf.net/sfu/arcsisghtdev2dev
>>> _______________________________________________
>>> Jsynthlib-devel mailing list
>>> Jsy...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>>
>> ------------------------------------------------------------------------------
>> Special Offer -- Download ArcSight Logger for FREE!
>> Finally, a world-class log management solution at an even better
>> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>> download Logger. Secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsisghtdev2dev
>> _______________________________________________
>> Jsynthlib-devel mailing list
>> Jsy...@li...
>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] fixed build error in trunk

[Joachim <li...@sd...>]

Hi,

there were already some speaking about taking over/forking.
All of them calmed down pretty soon.

My advise is: Develop something new first and then eventually
start thinking about a fork.

But I'm pretty suer there is no need for a fork: If you want to do something,
simply do it and don't just talk about doing it.

Cheers
Joachim

Am 31.08.2011 20:20, schrieb Vladimir Avdonin:
> Hi,
>
> The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project.
>
> I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron.
>
> Regards,
>
> Vladimir
>
> On 08/30/2011 08:37 PM, frankster wrote:
>> Hi,
>> I have downloaded the latest version of jsynthlib from svn and found
>> that there are various problems with the code in trunk.
>> * The RolandD10 driver seems to use features from Java 1.5 whereas the
>> build.xml specifies version 1.4.2.
>> * Some files are not encoded correctly causing warnings about unmappable
>> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers.
>>
>> I have updated the build.xml to specify Java 1.5 - this seems better
>> than rewriting some of the RolandD10 driver. I have saved the relevant
>> files in the Yamaha drivers as UTF8.
>>
>> Is there anybody with SVN access that can put these fixes into the
>> repository? Also if anybody wants a copy of these minor fixes off me
>> before they find their way into SVN, then I can email the files that I
>> have changed.
>>
>> Looking at the mailing list, this project seems dead lately but maybe
>> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000
>> and Roland U220) that are not supported by jsynthlib and I may be
>> motivated to add support for them if there's anyone still interested in
>> this project.
>>
>>
>> Regards,
>> Frankie
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Special Offer -- Download ArcSight Logger for FREE!
>> Finally, a world-class log management solution at an even better
>> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>> download Logger. Secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsisghtdev2dev
>> _______________________________________________
>> Jsynthlib-devel mailing list
>> Jsy...@li...
>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>

Re: [Jsynthlib-devel] fixed build error in trunk

[Vladimir A. <vl...@gm...>]

Hi,

The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project.

I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron.

Regards,

Vladimir

On 08/30/2011 08:37 PM, frankster wrote:
> Hi,
> I have downloaded the latest version of jsynthlib from svn and found
> that there are various problems with the code in trunk.
> * The RolandD10 driver seems to use features from Java 1.5 whereas the
> build.xml specifies version 1.4.2.
> * Some files are not encoded correctly causing warnings about unmappable
> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers.
>
> I have updated the build.xml to specify Java 1.5 - this seems better
> than rewriting some of the RolandD10 driver. I have saved the relevant
> files in the Yamaha drivers as UTF8.
>
> Is there anybody with SVN access that can put these fixes into the
> repository? Also if anybody wants a copy of these minor fixes off me
> before they find their way into SVN, then I can email the files that I
> have changed.
>
> Looking at the mailing list, this project seems dead lately but maybe
> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000
> and Roland U220) that are not supported by jsynthlib and I may be
> motivated to add support for them if there's anyone still interested in
> this project.
>
>
> Regards,
> Frankie
>
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

[Jsynthlib-devel] fixed build error in trunk

[frankster <jsy...@te...>]

Hi,
I have downloaded the latest version of jsynthlib from svn and found
that there are various problems with the code in trunk.
* The RolandD10 driver seems to use features from Java 1.5 whereas the
build.xml specifies version 1.4.2.
* Some files are not encoded correctly causing warnings about unmappable
characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers.

I have updated the build.xml to specify Java 1.5 - this seems better
than rewriting some of the RolandD10 driver. I have saved the relevant
files in the Yamaha drivers as UTF8.

Is there anybody with SVN access that can put these fixes into the
repository? Also if anybody wants a copy of these minor fixes off me
before they find their way into SVN, then I can email the files that I
have changed.

Looking at the mailing list, this project seems dead lately but maybe
its just dormant ;) I have a couple of sound modules (Emu Proteus 2000
and Roland U220) that are not supported by jsynthlib and I may be
motivated to add support for them if there's anyone still interested in
this project.


Regards,
Frankie

Re: [Jsynthlib-devel] New user

[<mar...@fr...>]

Hi,

definitly I am still an active user of JSyinthLib, but traffic indeed is low on this list. I still have the idea to add a driver for the Roland JV-1080, but did not start by now. For the start I have downloaded the Java SDK, but not yet installed. For the Atari I wrote a small program in Basic for the Kawai K4, and have some experience in C on the PC, so I think Iwill undertstand thesourceof Jsynthlib at least on a leveltoadd a new driver by modifying an existingone.

Best regards,

Martin

> -----Ursprüngliche Nachricht-----
> Von: Martin Tarenskeen 
> Gesendet: Thu. 07.07.2011 08:45
> An: JSynthLib-devel ,
> JSynthLib-CVS 
> Betreff: [Jsynthlib-devel] New user
> 
> Hi,
> 
> I am new to JSynthLib and want to introduce myself with a few
> remarks:
> 
> 1. These mailinglists seem to be extremely low-traffic. Are there
> still
> any active users and/or developers around? I think JSynthLib is still
> a
> great project with lots of potential, but also with plenty of room
> for
> improvement.
> 
> 2. With such low traffic, do we really need 2 mailinglists ? Why not
> merge
> the CVS and devel lists ?
> 
> 3. I have downloaded beta version 0.20.0 and CVS alpha version
> 0.21.0.
> I could not compile the CVS version because (I think) an error in the
> Roland-GP16 driver. After disabling this driver in the Makefile,
> running
> "make" was succesful (on my Linux Fedora 15 system)
> 
> 4. In the CVS version the DX7 editor does not open, I am getting an
> error
> message instead. The DX7 editor is working fine in 0.20.0 version.
> 
> 5. I am an expert in DX21/TX81Z (etc.) SysEx. I am the author of the
> old
> ATARI program YSEDITOR (http://yseditor.atari.org) so I know what I
> am
> talking about.
> 
> I see room for improving the editor/driver. (For example: the EG and
> PEG graphs do not correctly represent the effect of the rate and
> level
> parameters. Please read the TX81Z manual, and/or compare with
> YSEDITOR)
> 
> But I have no Java programming knowledge. I have programmed in Atari
> GFABasic, a little C, and Python. I will try to teach myself some
> simple
> Java programming. Maybe somewhere in the near future I might start
> contributing to JSynthLib.
> 
> Hope to see some more life in these mailinglists!
> 
> Greetz, Martin
> 
> P.S.
> 
> DX7 (and compatibles) owners might want to try my latest project
> DXconvert. This tool is able to convert DX7 patches in virtually
> every
> fileformat that can be found on the internet to a fileformat that for
> example JSynthLib is able to import. (clean SysEX, or MID with
> embedded
> SysEx). It can also import/convert patches from FB01, TX81Z, V50,
> DX200,
> and convert them to DX7 files that can be imported with JSynthLib's
> DX7
> driver. You can download the current version here:
> 
> 
> http://members.tele2.nl/m.tarenskeen/download/sysex/DXconvert-1.1.3.zip
> 
> 
> 
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously
> valuable.
> Why? It contains a definitive record of application performance,
> security
> threats, fraudulent activity, and more. Splunk takes this data and
> makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
> 
> 
> -----Ursprüngliche Nachricht Ende-----





---
Nutzen Sie freenet Mail optimal angepasst für Ihr iPhone, Android oder Nokia Handy auch von unterwegs.
Alle Infos und Download unter http://mail.freenet.de/mobile-email/index.html

Re: [Jsynthlib-devel] [Jsynthlib-cvs] New user

[Martin T. <m.t...@zo...>]

Hi,

Sorry for posting to Jsynthlib-cvs, this was not intentional. I forgot to 
edit my "To:" field before clicking on "Reply".

-- 

MT

Re: [Jsynthlib-devel] [Jsynthlib-cvs] New user

[Martin T. <m.t...@zo...>]

On Thu, 7 Jul 2011, Martin Tarenskeen wrote:

> 4. In the CVS version the DX7 editor does not open, I am getting an error
> message instead. The DX7 editor was working fine in 0.20.0 version.

To be more specific: Only after I had compiled and packaged the latest SVN 
development trunk in a jar file the error was happening. Looking more 
closely I discovered the problem was that the gif images for the DX7 
algorithms were not found. But I could run "java JSynthLib" and then this 
problem did not happen.

I also managed to fix the problem:

1. I moved the gif images from synthdrivers/YamahaDX7/images/ to synthdrivers/YamahaDX7/common/
2. I edited synthdrivers/YamahaDX7/DX7FamilyVoiceEditor.java
(diff file attached to this mail)
3. I compiled, and packaged the results in a jar file

Now the DX7 voice editor works again.

Maybe someone with SVN write access can commit (or improve) my fix to the 
trunk ?

(BTW: I had to disable the RolandGP16 driver in the Makefile. Something is 
wrong there too, I could not compile without removing it from the list in the 
Makefile. Maybe someone is able to fix that one too ?)

-- 

MT

Re: [Jsynthlib-devel] New user

[Maciej Ł. <loz...@o2...>]

Hi Martin!

We could probably exchange knowledge, I am a professional Java programmer,
but I have a few questions about Yamaha programming. I started do develop
a driver for FB-01 but haven't finished yet, mostly because of these
doubts. I'll try to write exactly what I'm talking about as soon as I
return to programming it. Long live JSynthLib!

cheers
Maciek


On Thu, July 7, 2011 8:45 am, Martin Tarenskeen wrote:
> Hi,
>
> I am new to JSynthLib and want to introduce myself with a few remarks:
>
> 1. These mailinglists seem to be extremely low-traffic. Are there still
> any active users and/or developers around? I think JSynthLib is still a
> great project with lots of potential, but also with plenty of room for
> improvement.
>
> 2. With such low traffic, do we really need 2 mailinglists ? Why not merge
> the CVS and devel lists ?
>
> 3. I have downloaded beta version 0.20.0 and CVS alpha version 0.21.0.
> I could not compile the CVS version because (I think) an error in the
> Roland-GP16 driver. After disabling this driver in the Makefile, running
> "make" was succesful (on my Linux Fedora 15 system)
>
> 4. In the CVS version the DX7 editor does not open, I am getting an error
> message instead. The DX7 editor is working fine in 0.20.0 version.
>
> 5. I am an expert in DX21/TX81Z (etc.) SysEx. I am the author of the old
> ATARI program YSEDITOR (http://yseditor.atari.org) so I know what I am
> talking about.
>
> I see room for improving the editor/driver. (For example: the EG and
> PEG graphs do not correctly represent the effect of the rate and level
> parameters. Please read the TX81Z manual, and/or compare with YSEDITOR)
>
> But I have no Java programming knowledge. I have programmed in Atari
> GFABasic, a little C, and Python. I will try to teach myself some simple
> Java programming. Maybe somewhere in the near future I might start
> contributing to JSynthLib.
>
> Hope to see some more life in these mailinglists!
>
> Greetz, Martin
>
> P.S.
>
> DX7 (and compatibles) owners might want to try my latest project
> DXconvert. This tool is able to convert DX7 patches in virtually every
> fileformat that can be found on the internet to a fileformat that for
> example JSynthLib is able to import. (clean SysEX, or MID with embedded
> SysEx). It can also import/convert patches from FB01, TX81Z, V50, DX200,
> and convert them to DX7 files that can be imported with JSynthLib's DX7
> driver. You can download the current version here:
>
>
> http://members.tele2.nl/m.tarenskeen/download/sysex/DXconvert-1.1.3.zip
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>