[Jsynthlib-devel] A dilemna about jsynthlib

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

Hi Jsynthlib people,

Some months
ago, I sent out an email to the list asking for some help with
Eclipse and CVS stuff and how to start my own device module. I got no
response from anyone on this list.

Now I have actually
finished building a retrofit kit for the Korg Poly 800 MK1 and EX-800
synth module. The new kit provides full sysex implementation along
with 4 LFO's instead of 1, portamento mono mode, full MIDI controller
implementation and a gazillion other new functions. And I am now
seriously looking at developing a patch editor/manager and I thought
jsynthlib might be a good candidate.

But here is my
dilemma.

This list and thus, this project looks almost dead.
It certainly is comatose and the patient is being wheeled down to the
morg.

Now I have a pretty good record for sticking to projects
I start. Who spends two years rewriting the 8085 assembler of a
synthesizer made in 1982?

But it seems to me that it might end
up being a bad idea to use jsynthlib as the platform for the editor.

Does anyone have some opinions on this?

If I do decide to take on jsynthlib, I
am going to need some help getting my head around CVS and the modules
involved in jsynthlib itself. Should I expect to have to do this
without help or is anyone/everyone out there willing to at least help this
sourceforge newbie find his way around the basics?

Any feedback is very much appreciated.

Anyone interested can check out my Poly-800 upgrade
kit at http://patrioticduo.tripod.com/hawk800

Cheers,

Mike

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com