Re: [Jsynthlib-devel] Help building drivers: first steps

[Christoph E. <ce...@ch...>]

Hi,


> Hi. Responses inline:

perfect with me.

[...]

> Did you get the updated makefile?  What errors are you getting?

yes I did. It started to build fine, but then I get 100 errors like the 
following:

$> make

javac -g -classpath .:jdom.jar:groovy.jar 
synthdrivers/RolandGP16/RolandGP16BankDriver.java

[...]

./synthdrivers/RolandGP16/RolandGP16SingleEditor.java:232: cannot 
resolve symbol
symbol  : class ExpLevScrollBarWidget
location: class synthdrivers.RolandGP16.RolandGP16SingleEditor
  addWidget(eq,new ExpLevScrollBarWidget("Low Level",patch,0,48,-24,new 
ParamModel(patch,0x2C+8),
                   ^

It's all about the RolandGP16 driver; Maybe a missing semi colon? But 
when looking in thte file I cannot see anything.

[...]

> Sounds like a good way to start.

So I did and wrote the steps to a text file for the documentation :) .

[...]

> http://www.borg.com/~jglatt/tech/midispec/identity.htm

Cool, never knew this before. Here's what I got:

Sent:
amidi -p hw:3,0,8 -S "f0 7e 7f 06 01 f7"

Received:
amidi -p hw:3,0,8 -d
F0 7E 7F 06 02 00 01 05 00 00 04 00 01 00 21 00 F7  

*Very* nice :) .

> That depends partly on how you send / recieve the data.  Is the
> global data sent separately from the patchbay definitions?

Yes. It can be requested and it gets sent as soon as one changes any 
setting via the front panel.

There are even separate request commands (and replies) for each 
individual patchbay definition (8 presets).

[lotsa XML stuff removed]

OK, got it, thanks a bunch. Next steps will be to create globals.xml and 
patchbays.xml => tomorrow.

Thanks for the help.

> The decoder and checksum will normally go inside the patch file.  If
> there is no checksum you will probably need to create a checksum
> plugin that does nothing.

OK, I will dive into other checksum plugins and see if I can get done 
anything by myself.


Best regards


ce