-
Notifications
You must be signed in to change notification settings - Fork 3
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
Decoding GCE-3 mode switch #1
Comments
Line 14 appears to be a 'ZSPF' file, a format I have not seen before but looks like a list of effects. Block continues in next packets. In packed form
|
Line 432 appears to be reading back the FLTS_SEQ file In packed form
|
Line 10 looks like its declaring
|
Offsets are different again, but you can rebuild the file from the logs.
|
model.zip I zipped the model. |
So in the model file I see ZIF - I have found a source of such files ... not sure if it is related. Then patches loaded accordingly. Basically I have all of the model's for all of the pedals (everyone does if they know how to look). I really need to get more into "construct" - what you do there is magic. My older pull from original zoomzt2 was getting confused because it looked for 5 IDs. Your modified code seems to be decoding G5n, B3n etc patches - awesome. I seem to recall the older pedals also had this "preamable, N FX, volume etc patch name, checksum, end" format. |
I should have update here that I captured the mode switch sequence for the GCE-3 and added scripts to change modes - I must make the time to add it to my GUI. The traffic is checked into GIT. Probably under GCE-3 Derived Data. |
Line 44 is sending a patch, similar to G1Four but offsets different.
https://github.com/shooking/ZoomPedalFun/blob/main/GCE-3/InitialModeChangingExperiments/ChangeToG1Four.txt#L44
ChangeToG1Four_line44.py.txt
The text was updated successfully, but these errors were encountered: