Any software engineers or programming types out there?

[megafiddle]

If you're displaying in the form of text characters, and it's using unicode, each character
may be more than one byte.

Can you post a sample of what you are seeing?

Does the file size agree with the number of characters displayed?

[Munjibunga]

My mind is a raging torrent, flooded with rivulets of thought cascading into a waterfall of creative alternatives. And I'm getting a headache.

[NKUSigEp]

Originally Posted by Munjibunga

My mind is a raging torrent, flooded with rivulets of thought cascading into a waterfall of creative alternatives. And I'm getting a headache.

You sure do use your tongue purdier 'n a $2 whore!

[JehuJava]

I'll try to post a sample tomorrow. We have friends coming to visit tomorrow afternoon for the week, so my time may be spoken for.

[JehuJava]

Well, I guess posting these will let the cat out of the bag on which pedal...but here are some files.

The excel file is a list of the pedal presets as they appear in the pedal. The colored columns are ones that I think I identified with the locations listed below. The color corresponds to my hex editor bookmarks.

The txt file normally has an extension of .OFX so you may need to change that. TB won't let me post a .OFX file. Like I said the first 16 bytes appear to be the header and I deleted them from my working copy. Then I viewed the file in 64 byte line lengths and everything lined up nicely.

[MontzterMash]

Yeah, you're going to have a lot more fun looking at a proper hex dump of that file. Something like xxd (on a mac or linux machine). You want to see the hex, and the ASCII all at the same time.

xxd Queensryche--Rage_For_Order--10--Screaming_In_Digital.mp3 | head

0000000: 4944 3303 0000 0000 007f 5449 5432 0000 ID3.......TIT2..
0000010: 0016 0000 0053 6372 6561 6d69 6e67 2049 .....Screaming I
0000020: 6e20 4469 6769 7461 6c00 5450 4531 0000 n Digital.TPE1..
0000030: 000d 0000 0051 7565 656e 7372 7963 6865 .....Queensryche
0000040: 0054 414c 4200 0000 1000 0000 5261 6765 .TALB.......Rage
0000050: 2046 6f72 204f 7264 6572 0054 5243 4b00 For Order.TRCK.
0000060: 0000 0400 0000 3130 0054 434f 4e00 0000 ......10.TCON...
0000070: 0500 0000 2839 2900 434f 4d4d 0000 0007 ....(9).COMM....

Looks like there's a bunch of them for windows too.

[JehuJava]

I'm not entirely sure what you mean. I've been using 010Edit on mac and can see both hex and ASCII at the same time. Or binary or whatever. I just don't know enough to understand the hex or binary yet. The ASCII is just showing me similarities between presets right now. This way I can say if I change a parameter on the pedal (or in GUI down the line) I know which part of the hex file that change will effect. I figure out the value coding once I figure out all the locations.

[megafiddle]

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.

[megafiddle]

You posted as I was posting.

The preset data in the pedal is very likely in a form that is immediately accessable by the
pedal's processor. It needs to make sense to a computer, not to a human. The pedal's
"operating system" translates the data from the internal memory for display,and translates
the user input back into "native" data for the processors use.

Now it might be in exactly the same form, 1 is 1, 2 is 2, etc.
But that's what you have to determine. As long as there is simple function involved, and
there usually is, you can work backwards to it. And computers are especially good at such
things. Even if the coding is completely arbitrary, for example "off" is -1 and "on" is 1, the
total values are usually very small, and are also easily handled by a computer program.
These things are easly handled by a "lookup table".

If a parameter isn't correlating in a way that makes sense, post some values: minimum, maximum, and a couple intermediate values.

[megafiddle]

Data for VCFpeak parameter is attached in Excel form

http://www.talkbass.com/forum/attach...3&d=1351737896

[JehuJava]

I see what your are saying about the first 5 bits of the byte. I can now try to compare the 3 remaining bits against the other parameters, maybe grouped 2 & 1 like you mentioned. Let me dig into this. Thanks a lot. That really made me look at the presets differently.

[megafiddle]

I added two files:

byte14.xls is the 14th byte in the preset file expanded into the 3 bit fields, and their corresponding parameters.

dec_dump.txt is the preset file in decimal form.

byte14.xls

dec_dump.txt

[JehuJava]

This is the updated xls file. The Standard Preset tab show the binary work (well most of it since I'm still decoding a little bit of it). I've found just about every parameter.

The OFX tab is just the aligned hex dump. The yellow columns are confirmed parameters. The orange columns are highly suspected parameters but can't confirm till I decode the data. That's all the preset parameters! But, look how many unaccounted (white) columns of data there are on the OFX tab.

This is the data I need to figure out where it comes from. Funny, when I first started looking at this I thought there no way all the parameter data was going to fit in the OFX file lines. Now there's a lot extra.