-
Notifications
You must be signed in to change notification settings - Fork 10
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
"DSP required" value per effect #46
Comments
Hi, As you suggest it's likely in the The overall load for a patch might also be included in the |
If you wanted to experiment, you could use |
I tried just matching the bytes for the percentage value but it's not clear in which representation it should be ( |
More progress on this puzzle. Looks like this value is sourced from the ZD2 For example, for However, the ToneLib reported "DSP required" value for this effect is 6.97%, which is 17.43/6.97 ~= 2.5 times lower. This 2.5 ratio (40%) mostly appears to hold for other effects/patches I checked. Yet, for a couple of effects the ratio is somewhat lower; for exampe:
There could be more discrepant effects. It's not exactly clear, what is the meaning of that INFO field and what's the reason for such scaling but it's quite likely that this is (?one) of the source values for the "DSP required" effect property reported in ToneLib. Any ideas about the "formula"?
|
Good news, the x2.5 could be that it is a value out of 255 - rather than out of 100. Construct (the 'language' used to define the blocks) as in built support for floats, you should be able to place a one line definition for the item:
And remove the 4 bytes from next 'blob' to keep every thing aligned. If you really wanted a % output, you can add |
What's curious also is that in ToneLib the aggregated "DSP Load" for a patch remains fixed and does not depend on whether patch effects are On on Off. For example, Patch 11 has EP_STOMP Off, yet the patch "DSP Load" remains the same 65% even when it's turned On.
This is unlikely, at least not on effect's level. As I showed above, most effects do consistently show the ratio 2.5; with 255 basis, the resulting "DSP reqired" values would be different. Not sure if this ratio is dependent on the pedal's model, as higher-end models have support for more effects in a patch chain; G1 FOUR supports only 5 effects. If anyone here has G5n (supports 9 effects) could you please check the reported "DSP required" values for the mentioned effects in ToneLib/Guitar Lab? |
It would make sense to use the "maximum load", as you don't want the pedal to crash(/glitch) when you turn all the effects in a patch on. I have a GCE-3 at my other house, maybe useful for experimenting... when I can get my hands on it. It's my belief that the extra sections for the |
Also, note that the actual effect files between those of the G1Four, G5 and H8 are exactly the same. I mined them and computed MD5SUMs for each... Where does the extra CPU power of the G5 come from, and why would more effects be possible? Is the 9 effects more related to the physical construction, with more screens? There are a couple of effect (ie Particle) which don't seem to run on the 'lesser' pedals, this could be related to linked libraries not available in the FW. There is now a |
My thinking is that if the pedal (or its config) allows more effect slots in chain, then this will allow for more of "DSP Load", which is aggregate of per effect "DSP required" value. G5n allows almost twice as many effects than G1 FOUR, thus by such calculation as in Patch 11, adding more of similarly "heavy" effects would bump the calculated "DSP Load" value to even closer to 100%, which won't be nice for users of the pedal to see. So I believe the effect's "DSP required" values are scaled to reflect the perceived capacity of the specific device model. The scaling would be chosen to allow the prepackaged patches to "moderately" load the DSP. Well, just a speculation. |
can the aux in be rerouted to have fx?
…On Wed, Oct 5, 2022 at 10:43 PM nomadbyte ***@***.***> wrote:
I wonder if anyone has figured out where does a "DSP requirement" value
per effect come from?
It could be seen in ToneLib per installed effect's properties. Also these
values aggregate for all effects in a patch and the result is reported as
"DSP Load" value (a percentage).
For example, for G1Four:
Patch 11
DSP Load: 65%
EP Stomp: 12.96%
MS 1959: 31.5%
ZNR: 4.35%
MS4x12GB: 9.2%
TapeEcho: 6.97%
---------------------------
64.99%
I'd guess this could be in a .ZD2 file, but not sure how this is being
encoded and at which offset.
—
Reply to this email directly, view it on GitHub
<#46>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOA5FJSFE47T3IICHSYQPGDWBWHXJANCNFSM6AAAAAAQ5UU7AM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Following up from my comment earlier, I parsed the effects from This makes a list exactly the same as before, however it's worth noting that 168 of the effects listed did not download for some reason... these are likely not seen before, and it's worthwhile figuring out how to get them. |
Decoding the last 4 bytes of the INFO block.
ie
|
Those effects seem to be specific for G6, B6, and G11 models, most of them have 88 suffix. The files may be in ZDLF7_2, I guess it's specific for GL 7. |
Also curious is that for the G6, B6, G11 models there's
Not exactly sure if it's more about "load" or "process", well, IR is about the impulse response, obviously. So assuming it's about load-capacity for processing the effects (which are modeled by their defined IR), then this value may describe the [??max] processing capacity of a given pedal model. This, in some way, may be an equivalent of the "scaling factor", which translates the ZD2 defined value into the "DSP required" as reported. In fact, this may just be the direct percentage factor. Similarly to G1 FOUR with supposed factor 40%. G1 FOUR supports only 5-effect chain, while G11 supports 9+1-effect chain. |
@nomadbyte You were right about "ZDLF7_2" - this got me all the effects, and many were also updated revisions. |
One thought on the processing power of effects, when comparing patches on different pedals ensure that the effect binary is actually the same. Or double check We already know that G1Four has effects which are customized for a single screen. It looks like the G6/G11 add another variant (unknown as to why). For example:
|
Thanks for the test. In this patch G5n and G1 FOUR very much use the same ZD2 files, except for "MS 1959" effect. G5n loads "MS1959.ZD2", which has somewhat lower Well, that leaves the question open for the proper naming and meaning of this value in ZD2. Another look at the "scaling" could be that the ZD2 value is normalized by 250 and then multiplied by 100% to result in the "DSP required" value (EP_STOMP.ZD2: 32.40/250 * 100 = 12.96%). That is there's "something" that maxes out at 250. |
Included 'DSP Load' in the
|
very late to the party here - but excellent work by you both as ever I wonder if the "scale factor" is real - that is Zoom kindly calculated that the G5n is much more powerful than a G1XFour. Or if it is about reducing the perceived power of the device. IE maybe changing this in a ZD2 will report lower CPU and consume less. I mean the GCE-3 can be all of the pedals ... is this a "super" processor compared to the other Zooms or just told that it can be more powerful? |
Just noticed, the 2.5 scaling factor apparently is ToneLib internal choice for G1 FOUR. However, Guitar Lab uses appears to use a different scaling factor: Not clear why this discrepancy is there. Maybe the 2.5 factor was applicable to some older Zoom pedals supported by ToneLib? The 2.3 factor should probably be applicable to MS series pedals. |
More details on the reported DSP Processor use scaling factor. First of all, apparently some DSP usage scaling data is reported back via Sysex: For example, G1 FOUR responds with
At this value, Now, we know that So, this does support the previous statement about the DSP scaling factor Again, this is for G1 FOUR. Not sure what is reported back in Sysex: Also, it's not clear what is the meaning of the other values in |
Hi sorry for late reply - I should subscribe to see issues :-( G5n & G3n
B1XFour
No response from B1On. |
@shooking Thanks! Is it from GCE-3 in G5n mode or the actual hw? I wonder if GCE-3 could respond to |
above is from a real G3n and G5n. I dont have a B3n. From a GCE-3 emulating a B3n
interestingly enough the last 3 returned HEX are different. |
@shooking Thanks. To summarize, the
It's not clear what those extra bytes are. Looks like the last byte could be |
I wonder if anyone has figured out where does a "DSP requirement" value per effect come from?
It could be seen in ToneLib per installed effect's properties. Also these values aggregate for all effects in a patch and the result is reported as "DSP Load" value (a percentage).
For example, for G1Four:
I'd guess this could be in a .ZD2 file but not sure how this is being encoded and at which offset.
The text was updated successfully, but these errors were encountered: