Menu
▾
▴
Re: [Jsynthlib-devel] Wiki for writing XML drivers (was: A call for help from advanced Java users
|
From: Peter G. <pet...@gm...> - 2009-09-19 08:50:45
|
Hi, I've split up the YamahaMotif.xml<http://jsynthlib.wikispaces.com/YamahaMotif>file and written some comments to each part. Writing such a file for my SPD11 seems pretty easy now. Didn't try it yet as I'm finishing my editors written the standard java way, I go on dreaming about xml ... A nice window where a user can enter the info for each value ("name", "deviceID", "infoText" etc) in the list and a button "create device" to generate the .xml file would be the next step into wonderland :) Then another tab on that window that describes calculateChecksum methods, choose one from a list or define a custom method, click "Apply" to modify the .xml file. And so on for each "module" that exists in a device support. Then finally choose from the menu: "editorbuilder" and arrange the parameters. In the end, each driver would become a set of modules and a set of editorpresets, I'm thinking about SynthEdit, Synthmaker, Reaktor, but for Sysex instead of Vst. In SynthEdit, you can write your own dsp or GUI modules in C++, but then you still have to put the module in the visual editor, connect it to in/outputs and save that as a synthedit file. Btw, synthEdit can send Sysex messages too, but it doesn't have enough modules built yet to make a Vst editor/librarian like it can be done with JSynthLib. There was a thread about it on the SynthEdit mailing lists lately... Maybe that's a huge feature request, and I'm not sure if such feature requests are a good idea here, so I'll just call it "dreaming" ;-) I also think if you can learn somebody to write the right xml file about the sysex, that that person could as well have learned to write the right Java code, if we had more or better detailed examples and a better guide. It wouldn't really be writing the Java code, but just copy the code and change it to your needs. Now the code is presented to the new writer in full (complex) drivers that maybe even the authors don't understand anymore. It might be better to present the "example code" in blocks, or step-by-step parts. If your synth doesn't use a this-or-that, go to the next step, choose another code-module that suits your needs. The list of code-modules could be a library of all currently used techniques organized by point of view: device, singledriver, bankdriver and converter with their attributes and methods, as in the step by step wiki part <http://jsynthlib.wikispaces.com/Step-by-step> versus Menu actions from a library, scene or bank window and moving a sysexwidget in an editorFrame, as in the using synthlib wiki part<http://jsynthlib.wikispaces.com/Using_JSynthLib> -> why/how do they work, what code-modules do they require? Using such template code examples might also help to keep a standard way of doing things and find common methods between drivers. Maybe that's already something the xmldriver does. An advantage of the xml editorbuilder might also be that the user can combine his favorite parameters in one editorwindow with the fadernumbers assigned that he wants. I'm not sure if that still fits in the original vision of JSL... My SPD11PatchEditor has 256 knobs, and another 256 comboboxes. I can't assign all knobs to a different fadernumber now. Or am I wrong? Mmm, I could probably set an int variable in the user's prefs and use that variable to assign fadernumbers to the knobs. Did any other editor implement such a hack? How do I find that editor? A library of used techniques would be my preferred place to go looking for that editor. Now I'll have to go reading all editors and hope there's one that can inspire me. I'll stop here for now. Cheers :-) Peter On Wed, Sep 16, 2009 at 6:56 PM, Joachim <li...@sd...> wrote: > Hi, > > that's the best idea I've seen on this list for years. Therefore I'm > explicitly mentioning it > with a dedicated subject for those who don't read every message on this > list. > I must admit I never understood how to write an XML driver therefore > I've only written > Java drivers. That's the reason why I can unfortunately not contribute > anything the wiki. :( > > It would be even better if the complete www.jsynthlib.org would be > turned into a wiki > as Brian Klock (I think he holds the page) seems to have no time for > keeping it up-to-date. > > Cheers > Joachim > > Am 25.08.2009 um 19:17 schrieb Peter Geirnaert: > > > Ok, thanks, very nice, I'll surely give it some tinkertime. > > I started an XMLguide <http://jsynthlib.wikispaces.com/XMLguide> as > > part of > > the wiki, too bad that I've got troubles opening (and loading) the > > preferences (window), that way I can't do any testing so I have to fix > > that > > problem first. > > > > Walking the dog now ... > > Peter > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |