nomadbyte

@shooking Thanks! Is it from GCE-3 in G5n mode or the actual hw? I wonder if GCE-3 could respond to `[64 11]` for B3n as well.

@shooking Thanks. To summarize, the `Sysex:[64 11]` returns DSP-usage scaling factor: ``` F0 52 00 6E 64 10 (66 01):DSP-scaling (04 01 00):extra F7 ``` |model|DSP-scaling|extra-bytes |-----|-----------|----------- |G1 FOUR|230|`[04 01...

You mean the G2 FOUR, not the older G2. Do you have one and willing to explore?

@Licarde: Do you have a PC (preferably with Linux on it) or such to try out MIDI connectivity? At least to see if the pedal presents itself as a MIDI...

Cool! Can you dump these too? All these are info commands, no changes. ``` amidi -p hw:2,0,0 -S 'F0 52 00 6e 44 00 00 00 00 F7' -r temp.bin...

Thanks, lots of new details. Here's a bash script to list the files on the pedal's internal flash: ``` #!/bin/bash sig_int() { exit 2 } port=hw:2,0,0 # your B2 FOUR...

Wow! Thanks for the list, at least we now know what's in the box, so to speak. |extension|description |-|- .ZIC|effect icon (Zoom ICon format) .BDL|built-in effect module .ZD2|effect module .ZT2|effect...

B2 FOUR has 300 user patches, 10 patches per bank (30 banks). Here's how to dump a selected patch and the current edit buffer. For the test, you need to...

> ... it is responding to these commands suggests that it would work OK with the Python scripts as they are. Well, it's still a new device. So, it'd be...

@Licarde: So far B2 FOUR protocol appears very much similar to that of G1/B1 FOUR model family, but we still need to figure out some details, such as: 1. **patch...