Michael Hawkins wrote: > Hi Jsynthlib ppl, > > I have been sending emails to admin's to try to get me added as a developer > but no one is home. I am not even sure the lights are on. LOL > I got an email a while back from *someone*... don't know if it was you... and they asked to be a developer and I responded by asking them to describe their Java and/or CVS experience. Never heard back. > Can someone help me get added as a developer? > *I* can. But, again, what's your Java experience? Have you worked on any other Sourceforge projects before? > And should we get someone who is current added as an admin? > Yeah... we should probably have more than one admin who's provably alive... especially since I fly a lot. :)
Are you the one who just petitioned to take over the project on SourceForge? > First question: > > Should I create the device driver as KorgHawk800 (where HAWK-800 is the name > of my upgrade kit)? > So, you're proposing that as a new driver name? There isn't a KorgHawk800 already that you're planning on adding to? > All of my SYSEX code use Korg's manufacturer ID and Poly-800 device ID codes, > so I think it should go in as KorgHawk800. But that's just my opinion. > Well, if you use the same codes as a stock 800, then that could be an issue. I /think/ JSL just queries the Sysex ID and then asks each driver if they know how to deal with that device. I don't remember what it does if multiple drivers claim to be able to drive it. Ideally, it would give the user a choice of the drivers... however, it might just use the first one that claims it can do it. What might be preferable is to write/ammend a Korg800 driver so that it could detect (via additional Sysex commands, perhaps) the presence of the HAWK-800. > Second, a the moment, the sysex implementation includes single patch dump > sends and receives as well as a bulk dump command but I have not yet > implemented any sysex for the operating patch memory. I have implemented MIDI > controllers that can edit the operating sound in real time. > > Does jsythnlib support using MIDI controllers to edit/change real time sound > memory? Or do I need to implement a SYSEX to control the operating memory? > I wouldn't think that it would support changing stuff via controllers, since those CC messages would be seen by all devices on that channel, no? The original developers were kinda paranoid about stuff like that. It's probably best to change the current patch parameters via Sysex... like most other devices do. - Joe ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
