[Jsynthlib-devel] Feature requests

[Joachim B. <jba...@pi...>]

Hi,

> No... there's a *request* for S80 support. :) However, some=20
> of the JSL=20
> devels use the RFE's to signify that, if someone doesn't=20
> write a driver=20
> for it first, then they'll write one eventually.

Sorry Joe, that's wrong.

Normally the developer who is currently working on driver support
opens (or should open) a feature request for it to notify it to other
developers who want to write one, too.

It is not necessary to be a project developer for opening a feature
request.

Unfortunately I currently have no time to go on working on the drivers
I opened feature requests for (E-mu XL-7, Waldorf Q).=20
And the "Korg Triton" is not developed
but by Steven Schmidt and "JV1080" by daxav. They are just assigned
to me which means that I'm the one who will check the code into
CVS when finished.

Regards,
Joachim



> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im Auftrag von Joe
> Emenaker
> Gesendet: Samstag, 30. April 2005 08:40
> An: Daniel Lyons
> Cc: jsy...@li...
> Betreff: Re: [Jsynthlib-devel] Yamaha S80 development?
>=20
>=20
> Daniel Lyons wrote:
>=20
> >I just downloaded JSynthLib and noticed that there was a=20
> Yamaha S80 development going on according the the sourceforge=20
> RFE list.
> > =20
> >
> No... there's a *request* for S80 support. :) However, some=20
> of the JSL=20
> devels use the RFE's to signify that, if someone doesn't=20
> write a driver=20
> for it first, then they'll write one eventually.
>=20
> >so I was wondering if he (you? jemenake) might want me to go=20
> ahead and give the S80 a shot (I've got an S80 and am excited=20
> about having a patch editor GUI plus load/save).
> > =20
> >
> Go right ahead. I haven't seen the S80 sysex spec anywhere. If you've=20
> got it, I'd appreciate a copy.
>=20
> >I'm mainly a C++/PERL programmer, but I don't think it'll=20
> give me too many troubles.
> > =20
> >
> Famous last words. :)
>=20
> Seriously, though... I find the JSL API to be very=20
> counter-intuitive and=20
> awkward. I'm gradually figuring out the least-painful way to=20
> write for=20
> it... but it required looking at lots of the core code. To=20
> prevent this=20
> from happening to anyone in the future, I'm hoping to make a=20
> nice Wiki=20
> or, at least, a set of web pages called "JSL coding for=20
> dummies", which=20
> are a bit more explanitory about how to get things done in=20
> JSL and why=20
> it does things the way it does them.
>=20
> So, if you get stuck anywhere... don't hesitate to let me know.
>=20
> - Joe
>=20