I can get the sysex data I posted prev.
Deciphering what the hex values/format is for the parameters data is what Im trying to figure out.
Then I've got to build some sort of algorithmic filter in C/JUCE to import it to the virtual controller.
I suspect most of the parameter data is in this section:
SYSX: 0F 00 00 00 01 00 00 00 00 00 00 00 00 00 07 01 0F 00
SYSX: 00 00 00 00 02 00 00 04 0B 00 0A 00 0A 01 00 00 00 05
SYSX: 05 00 00 00 01 00 00 00 00 00 0C 00 0C 00 01 00 00 01
SYSX: 0B 01 0F 01 0F 01 0F 00 03 00 00 00 00 00 00 01 0F 01
SYSX: 0F 01 0F 01 0F 00 03 00 00 00 00 01 03 00 05 01 0F 00
SYSX: 00 01 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Just cant see how that data would make decimal #'s like 31. Largest # I see in that group is 15....
There's got to be an easy way to decode this :/
--- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
>
> if you want to get the sysex data format message, you can
> do a 'handshake' by sending a data request message from a
> sequencer with a list editor, eg: cubase with midi in/out
> connected:
>
> set up cubase list editor with the data request message in the
> first line, having created a 'part' of? 4 measures?, with looping
> set to off; arm record, start play, and you should see the
> response from receiving device sent back and recorded in your
> list editor.
> i can't quite remember what the data request message is(or exactly
> what it is called), but i used this method successfully to get into
> boxes like alesis midiverbII/III and Quadraverb. you can then work
> out what the different bytes of the sysex are. essentially you
> only have one variable, the value LSB, unless the value range
> is above 0-127. (if the range is eg: 0-255 the value MSB will
> generally vary 0-1. i found this problematic with the cubase mixer
> map page, which doesn't offer any workaround.)
> all you need is one specimen message that sends a variable
> successfully, eg: cutoff etc, and then you know you have the right data format. eg: your virtual fader sends value LSB.
>
> --- In korgpolyex@yahoogroups.com, "bimmerfan222" <bperkins211@> wrote:
> >
> > I have an ongoing project for a custom GUI parameter/controller and found a way to make the app call for single patch dump code, then somehow decipher that code to set parameters for all the knobs/switches/etc. on the GUI.
> > So when you select Patch 11 Bank1 using the GUI, the GUI will request the Bank1 Patch 11 dump and then preset all the virtual controls to the proper settings.
> > So if it's in Chord Mode for Patch 11's last save, it will have Chord Mode set. If VCF is a value of 90, the knob for VCF will be set to 90.. and so on.
> >
> >
> > So taking a look at an example single patch dump-
> >
> > TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
> > 0008A01A 1 -- F0 Buffer: 256 Bytes System Exclusive
> > SYSX: F0 42 21 06 00 00 01 00 00 00 00 00 00 00 00 00 04 01
> > SYSX: 0F 00 00 00 01 00 00 00 00 00 00 00 00 00 07 01 0F 00
> > SYSX: 00 00 00 00 02 00 00 04 0B 00 0A 00 0A 01 00 00 00 05
> > SYSX: 05 00 00 00 01 00 00 00 00 00 0C 00 0C 00 01 00 00 01
> > SYSX: 0B 01 0F 01 0F 01 0F 00 03 00 00 00 00 00 00 01 0F 01
> > SYSX: 0F 01 0F 01 0F 00 03 00 00 00 00 01 03 00 05 01 0F 00
> > SYSX: 00 01 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 08 00 00 00 09 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 00 00 02 00 06 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00
> > SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > SYSX: 00 00 00 00
> > 0008A01A 1 -- F7 Buffer: 6 Bytes SysEx End
> > SYSX: 00 00 00 00 03 F7
> > 0008A268 1 -- F0 Buffer: 7 Bytes System Exclusive
> > SYSX: F0 42 21 7E 06 00 F7
> >
> >
> > The above is a single patch dump from my H800's Patch 11/Bank1.
> >
> > How do I narrow down what/where the values are for each parameter?
> > Is this even possible?
> >
> >
> > And if interested, I linked a couple pics of recent work I've done so far on the GUI H800 programmer. When complete, it will control every single parameter, CC# and Sysex that is possible with the H800.
> >
> > http://img.photobucket.com/albums/v207/abcSweep/Project%20Polygon/PolygonDemo2_zpsaf4e8b29.jpg
> >
> > http://img.photobucket.com/albums/v207/abcSweep/Project%20Polygon/PolygonDemo1_zps7f14d6e7.jpg
> >
> >
> > -Blaine
> >
>