-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meaning of the last 16 bytes at end of ZD2 file #49
Comments
The is only 1 (current) effect that matches the same value as AIR (v1.3)
|
For reference Air (V1.3) was in the G3n FW. |
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 ( 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....
The text was updated successfully, but these errors were encountered: