You hit the nail on the head.
And if you read the MIDI implementation chart for the HAWK, it states that the patch data is sent as high nibble first then the low one.
Mike
--- In korgpolyex@yahoogroups.com, Malte Rogacki <gacki@...> wrote:
>
> > 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....
>
> Looks like lo/hi (or vice versa) nibble encoding to me. This encoding puts
> four data bits in the first (SysEx) byte and the other four in the second
> byte. You just need to figure out which way around this happens.
> There are other types of encoding but this looks a lot of nibble encoding
> to me since the highest four bits of each (Sysex) byte are low.
>
> The reason for those types of encodings comes from the fact that SysEx can
> only transmit 7 bits per byte; however the internal data structure of most
> synths uses all 8 bits.
>