Open mungewell opened 2 years ago
The is only 1 (current) effect that matches the same value as AIR (v1.3)
zoom_fx_AllZDL7$ find -name "*.dump" -exec grep -A 1 -H "5F C5 17 C5 3E FC 33 63 C3 84 92 AB 08 A3 AA 3F" {} \; | grep "0000"
./B6/unzipped/SPRING88.ZD2.dump: 0000 5F C5 17 C5 3E FC 33 63 C3 84 92 AB 08 A3 AA 3F _...>.3c.......?
AllZDL7$ grep SPRING ./B6/unzipped/list_sorted.txt
0x0a090050 : Spring (v1.00, 13.07%), 0xd45faf8782d9348df71947d6cd3cf141, ./B6/unzipped/SPRING88.ZD2
For reference Air (V1.3) was in the G3n FW.
0x09000010 : Air (v1.30), 0xd340064af8e35a99133c72acc790b61b, ./G3n_v2.20_Win_E/effects/AIR.ZD2
Given there are 16 bytes, could these represent a MD5 checksum of something?
Notable that for "AIR.ZD2" versions 1.40 and 1.50 both have the same trailing 16-bytes. The only other differing parts are the checksum (#48), the bit-field after the checksum, and the version details (number and some additional bytes).
These bytes are the same for many different effects (uniq -c
count above).
There is some duplication in my dataset as effects are present on multiple pedals.... but these counts would be much lower count if these bytes were a checksum.
@nomadbyte asked on #48
seems that there is duplication of these byte sequences, which some being especially "popular", this suggest that they likely have some encoding in them.
The quoted sequence from #48 is actually 17 bytes, it really starts with
29 23 BE...
which super popular with 732 occurrences in my test set.Next is to figure out what those effects have in common....