First off, tend to your friends and their company, this stuff can wait.
But just so I don't forget, I have some things.
As MontzterMash said, you need to look at the data in at least a hex and ascii format.
I think you already have a hex dump though, that you exteneded to 64 bytes?
Anyway, I modified my hex dump for 64 bytes/line and I get what I believe is the same
as you described:
30 presets, 64 bytes/preset, 16 byte header.
My hex dump is output to a text file, I can post it if you like.
You need hex format to see if one or more parameters are being compacted into a single
byte. You might even need binary, if parameters are stored as single bits, or something
other than 4 bits. But because the parameters are entered and displayed as decimal values,
you also need a decimal dump. That's the easiest way to correlate the displayed values
in the pedal to the file values.
If you think it may help, I will see if I can get a chance to modify my hex dump program
to display decimal values. I can post that too.
If you are really set on going ahead with this, I would start in on the program itself.
You already have a lot of the information you need to get a major part of the program
working.
You know enough about the file to read it into the program and locate each preset.
You also know what each parameter is and what their ranges (upper and lower limits) are,
or at least they are easily determined.
So you can get that part of the editor set up. In fact, you can do the entire editor. All
that's missing so far is the translation from, and to, the .ofx file. You can add each of
the parameter translations into the program as you decypher them.
