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

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

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

[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