nomadbyte
nomadbyte
> ...What is the "0x01000008.Comp" 0x01000008 is the hex effect-id (high 1 byte is CategoryId:0x01, DYN), it's encoded in the patch (well, the lower 29bits of the full 32bit effect-id)....
> ... Is there something I could read to understand what you say? Read @shooking code (C++) or @mungewell zoom-zt2 code (Python) to get an idea of the 7-to-8bit unpacking....
> ...How do we convert the 11 00 00 02 (found in unpacked sysex) to 0x01000008 There are many ways to analyze binary data, you're probably applying your own. I...
@dkts2000 A lot of work you've done, I guess you have better view of the details now. If I understand your code correctly, the intent is to list the effects...
The `SND-RET` effects (`IR` as well) must be tied to the hardware (`G11/G6/B6`), so I would __not__ expect these effects to function on `G1/B1/A1 FOUR` nor `G5n/G3n/B3n`, as these lack...
Not sure if this quest got any way practical but adding here a few findings. It seems that the "160 Comp" effect is a ZNR (noise reduction) BDL module. So...
Regarding the nomenclature `{effect-name-tag}{suffix}.ZD2`: |suffix|meaning|details |------|-------|----------- | 1U | single unit (screen)| on one-screen units the wide-effects, which have 8 parameters (controlled by 4 knobs), need to be paged over...
> Or would we need to look deeper in the .text to find where space/memory is alloc'ed for the maximum allowable 'time'. Reaching the stage of the diminishing returns here......
Regarding OnOff values encoding, what I find peculiar is the use of base 256. For example, ``` [ca 0b] = 0xca + 0x0b*256 = 3018 = 0x0bca [e7 04] =...
Never mind. It's just the normal unsigned integer (little-endian). I got thrown off by the explicit use of 256 in your code. Thanks.