Open nomadbyte opened 1 year ago
jll4065
commented
1 year ago @mungewell, @nomadbyte: I’m following your entries here to better understand how the Zoom system works. I’m not a programmer, but this may compel me to learn Python, as I own the A1XFOUR and want to maximize it for multiple acoustic instruments. Do you think there is a way to convert external IR files (such as WAVformat), to ZD2 files to create custom models?
nomadbyte
commented
1 year ago Do you mean finding a way to create more MDL-kind of ZD2 models but for instruments other than the acoustic guitar?
My understanding is that you'd need more than just Python skills for that, as a ZD2 file packs a binary ELF file compiled from Zoom's sources specific to each model. Simply supplanting an IR profile (provided it's possible at all by the implementation, as it's not apparent from the ELF data so far visible) would not change the rest of the ELF internals, which in case of MDL files would remain acoustic guitar (string) specific.
So, if I were into IR approach, then it would make more sense to get hold of another Zoom pedal (e.g. G6) which already has support for IR files processing, including the ability to load external IR files.
P.S. Said this, the MDL ELFs do reference some objects which may possibly be the ??raw IR data (4096 bytes in length, starting @0x29e0). For example, these object references:
MDL_O328.ZD2.elf: g_firCoe_OOO28
MDL_O318.ZD2.elf: g_firCoe_OOO18
MDL_UPBS.ZD2.elf: g_firCoe_UPRIGHTMy guess, that Coe stands for coefficients; FIR (finite impulse response) is about filters that can produce a 6 dB per octave slope (see 1 and 2). That is this could be FIR coefficients. It's hard to tell the format of this data (EDIT: well, it's a collection of 1024 floats, attached fir-upbs.txt for g_firCoe_UPRIGHT) and any audio parameters of the underlying IR sample (bit-depth, sampling freq, channels, length). It's far from being able to drop-in some other IR bytes, as the files do differ elsewhere, not just in name-strings. And fundamentally, it's a guitar model, the IR just transforms it somewhat.
Again, I believe that such effort may not be worth the possible benefits. It may be a lot more viable (practically and economically) to acquire the product which already has IR handling capability (eg. Zoom G6, which is ZD2 compatible). Though it's hard to quantify fun... :)
If you're interested in further pursuing this topic, you'd rather open a separate Issue to keep this one on its subject.
AlesZika
commented
1 year ago Please, where can I get effects ADL3SBAL.ZD2, B_MOCT.ZD2, DLY3SBAL.ZD2 and some others? I cannot find them in standard location www.zoom.co.jp/archive/GUITAR_LAB/ZDLF6/. Thank you
nomadbyte
commented
1 year ago BAL/BL effects are H8/R20 variants of respective "the-other-with-the-same-name" effects on the list -- they just relabel Mix parameter to BAL, which I guess makes it more clearer. So for all practical purposes the mentioned BAL effects are fully served by:
ANDLY_3S.ZD2 17548 1.10 DLY "0x08000021.AnalogDly"
DELAY_3S.ZD2 17329 1.10 DLY "0x08000011.Delay"B_MOCT.ZD2 is part of G6 and G11 set and practically is equivalent to:
B_OCTAVE.ZD2 11545 1.30 MOD "0x06800050.Ba Octave"That's the whole thing about this variety -- many effects are the equivalents or just subtle flavors of other variants. I understand the purpose for such variety, this serves well to segment the models and cover the latitude of classic gear. Meanwhile, for practical purposes this wide variety should be made more focused on function and flexibility to serve the immediate need of musician. More so that such versatile subset could fit into the meager 2.9MB (~100 modules at average 30KB each) and spare us or at least minimize the need to fiddle with upload dilemmas (keep this, remove that). For comparison, G1 FOUR pre-installed set is 78 modules with space left for some 4 more; in total 130 modules defined for this model.
I wonder if anyone cares to post here their "good-enough" or frequent-use subset list of effects they use with these G Series pedals?
Below is an aggregated list of effect modules (ZD2) defined across the G1/B1/A1(X) FOUR type of pedal hardware (as opposed to G5n hardware type).
The list mostly coincides with what Zoom references for H8/R20 devices but with a few additional delays, cabinets, and X-pedals (H8/R20 don't support that).
In the list,
wdenotes the wide-effects (take multiple pages of params),B:Bass,A:Acoustic sets, otherwise it'sG:Guitar implied, which includes common effects like ZNR. Effect name follows the effect's id; version, size, and DSP usage are also listed. It's possible to pull the effect descriptions but this would make the list excessively verbose. Instead, it may be more straightforward to refer to respective PDF effect references for G5n, B3n, A1X FOUR by the listed effect name.In case anyone wonders about the stats: 303 ZD2 modules, total size: 7.2MB.
DYN: 16 (343.1KB)
FLT: 44 (740.9KB)
DRV: 39 (977.2KB)
AMP: 25 (1090.3KB)
CAB: 35 (1092.1KB)
MOD: 45 (943.2KB)
SFX: 9 (180.1KB)
DLY: 23 (505.6KB)
REV: 17 (340.3KB)
PDL: 22 (393.3KB)
AGM: 28 (765.3KB)
B (Bass): 69 (1707.5KB)
A (Acoustic): 66 (1609.6KB)
As such this list would NOT fully fit into G1/B1/A1X FOUR pedals, which only allow for 2.9MB of internal block storage. Oh, well, this little memory won't even fully fit the specific model-defined set thus requiring users to manage uploads and make those "sacrificial choices" etc.
Perhaps, someone may find a way to crystalize/curate this list into a more concise but still versatile sub-list(s) which would fit fully into the 2.9MB (~100 modules at average 30KB each). I understand not everyone needs to carry the whole variety in each of the categories, apart from the similarities and emulation strength of certain effects.