<br><div class="gmail_quote">On Thu, Oct 22, 2009 at 8:39 AM, Atte Andre Jensen <span dir="ltr"><<a href="mailto:atte.jensen@gmail.com">atte.jensen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi<br>
<br>
I've been using jsynthlib in that past to backup the patches on my<br>
jv-80. However after a long break I installedjsynthlib again, because<br>
now I wanna backup the patches of my new (old) xp-30 that should replace<br>
the jv-80. But jsynthlib doesn't seem to work with the xp-30, for one<br>
thing, jsynthlib (with the jv-80 driver) doesn't know about all the<br>
extra sounds available in the xp-30.<br>
<br>
Since I really don't need an editor, just a place to put patches, I'm<br>
hoping someone here could recommend a good way to go about this?<br></blockquote><div><br>Hi Atte,<br><br>Why not write a driver for JSynthLib? You can write drivers for library support only.<br>I've just checked the XP-30 manual,<br>
<a href="http://www.johannes-emmerling.de/xp-30/downloads/Roland_XP-30_Manual.pdf">http://www.johannes-emmerling.de/xp-30/downloads/Roland_XP-30_Manual.pdf</a><br>and it contains whole lists of names (at page +/-180).<br>
If you copy them in a text editor and use the "replace" function, you can make a string array to put in your JSynthLib driver's constants file. Maybe you can start your driver from the jv-80 driver.<br>For more info ... see the wikis I started about <br>
JSynthLib <a href="http://jsynthlib.wikispaces.com">http://jsynthlib.wikispaces.com</a><br>and Roland SPD-11 <a href="http://spd-11.wikispaces.com">http://spd-11.wikispaces.com</a><br><br>Rib Rdb also wrote a feature for JSynthLib to write drivers by describing the sysex in an .xml file.<br>
But that's still in an experimental stage and very undocumented.<br><br>Regards,<br>Peter<br><br>PS: I can't really help you with the librarian part as my drivers for SPD-11 can't send sysex back and I don't have any clue why.<br>
Maybe it will work when I install the next AVLinux that I just downloaded (my current install is messed up by too much experimenting). Maybe it's because I got something wrong in my driver.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
--<br>
Atte<br>
<br>
<a href="http://atte.dk" target="_blank">http://atte.dk</a> <a href="http://modlys.dk" target="_blank">http://modlys.dk</a> <a href="http://virb.com/atte" target="_blank">http://virb.com/atte</a><br>
_______________________________________________<br>
Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</font></blockquote></div><br>