Just FYI... Looks like there are several orphaned blocks (not linked to any file start-block) present in the original firmware update for quite a few pedal models. I checked G1 FOUR, G1X FOUR, B1 FOUR, G5n.
To be fair, there is not that much space wasted (tens of KB) in these cases. It's not clear if the firmware gets copied into the device memory verbatim or with some ordering to skip any "waste". This may mean that even with all patches and effects deleted, some internal file-system space would remain occupied.
Hopefully, this "bug" is not present in the device-side software as well...
For example, with G1 FOUR v2.00 some 9 file-blocks (34628 bytes) are orphaned. Apparently these are parts of BGMK3_1U.ZD2 named "BG MK3" (42808 bytes), the starting 2 blocks are missing. Well, this is an "add-on" effect, that is it's not installed by default, so no functional problems there. Still it's 40K of memory for nothing, should that matter, of course :)
Another observation is that there are multiple copies of some effects in the firmware. Not clear if this is on purpose or, again, is also an "artifact" of the system/update software. I don't think there is a known way to download the internal memory state of the device, well, other than just by executing a wildcard MIDI query to get the list of internal files but this only deals with addressable (that is listed in the index) files.
Just FYI... Looks like there are several orphaned blocks (not linked to any file start-block) present in the original firmware update for quite a few pedal models. I checked G1 FOUR, G1X FOUR, B1 FOUR, G5n.
To be fair, there is not that much space wasted (tens of KB) in these cases. It's not clear if the firmware gets copied into the device memory verbatim or with some ordering to skip any "waste". This may mean that even with all patches and effects deleted, some internal file-system space would remain occupied.
Hopefully, this "bug" is not present in the device-side software as well...
For example, with G1 FOUR v2.00 some 9 file-blocks (34628 bytes) are orphaned. Apparently these are parts of
BGMK3_1U.ZD2named "BG MK3" (42808 bytes), the starting 2 blocks are missing. Well, this is an "add-on" effect, that is it's not installed by default, so no functional problems there. Still it's 40K of memory for nothing, should that matter, of course :)Another observation is that there are multiple copies of some effects in the firmware. Not clear if this is on purpose or, again, is also an "artifact" of the system/update software. I don't think there is a known way to download the internal memory state of the device, well, other than just by executing a wildcard MIDI query to get the list of internal files but this only deals with addressable (that is listed in the index) files.