ToneBoosters E.Q.4

[Tappistry]

Still no config option for changing mousewheel behavior of adjusting Q value of filters? For some reason, this EQ is still reversed in that behavior from almost every other EQ plugin I've tried, from stock ReaEQ to others.

Hmm not seeing that here?

In Logic Pro X, moving the mouse wheel up increases Q.
In Pro Tools, moving the mouse wheel up increases Q.
In TB EQ4, moving the mouse wheel up increases Q.

I'd say that's pretty consistent?

Just so we're clear on circuitry definitions: when you increase the Q value of a filter, the bandwidth decreases. Conversely, when you increase bandwidth, Q value decreases.
https://www.electronics-notes.com/artic ... ormula.php

So let's talk in terms of filter bandwidth because it's easier to visualize.

ReaEQ-- Moving mousewheel up increases bandwidth
Apqualizr-- Mousewheel up, increase bandwidth
Blue Cat EQ (built into many of their plugins)-- Same behavior as above

Toneboosters EQ-- Moving mousewheel up decreases bandwidth

I realize that on OSX machines, you can globally invert mousewheel behavior, but I don't think you can do this in Windows. Switching to EQ4 from another EQ plugin is confusing for this reason. It's just a weird choice in terms of workflow.

Still makes total sense to me for consistency... If the parameter is expressed as bandwidth, moving the mouse wheel up should IMHO indeed increase the bandwidth, and thus decrease Q.

If the parameter is expressed as Q (Logic, Cubase, Pro Tools, Toneboosters, and many others), moving the mouse wheel up should increase the parameter value (Q), and thus decrease bandwidth.

It's all very consistent to me. And yes you can invert the behavior on macOS.

OT: this is becoming one of the very best and most affordable EQs out there

At least it could be made as an option... though I agree that the most logical approach is the opposite compared to what happens now in TB EQ...

- Mario

I agree. I've written to Jeroen and he said he'd consider adding the feature. It's honestly the one hangup that prevents me from using it more often.

Maybe if he looks at the thread and sees the differences of opinion, he could at least add the option to change it. That would be the most sensible.


Oh and also, add FabFilter Pro-Q2/3 to the list of the mousewheel behavior I described earlier.

[Butwug]

I agree. I've written to Jeroen and he said he'd consider adding the feature. It's honestly the one hangup that prevents me from using it more often.

Maybe if he looks at the thread and sees the differences of opinion, he could at least add the option to change it. That would be the most sensible.


Oh and also, add FabFilter Pro-Q2/3 to the list of the mousewheel behavior I described earlier.

Im all for more options, but the most sensible approach of looking at the Parameter is as a function of Q, rather than how the bandwidth looks IMO. This EQ behaves just as every synth plugin does when using resonance. If you scroll down on the synths resonance, it decreases the resonance. If you scroll up, it increases resonance. Same goes for Q. Scroll up, increases Q. Scroll down, decreases Q. Seems weird to me to have it behave one way with synths/DAW, then another way with EQ. But hopefully you guys get the option to change it, if thats what works for you!

Im really liking the circuit drive. Tried it on one song and liked it quite a bit. Gave the low end a nice sound.

[Bouroki]

Every filter and filter type can run in pristine, analytical mode or using analog circuitry model. Not just the analog bell curve.

You can enable and disable the analog circuit model for every filter section independently. You'll find the enable/disable setting by opening the extended controls window (where you'll also find the settings for dynamic equalization).

On the drive value: this is the gain applied prior to running the circuit simulation in decibels. A higher value will therefore result in more pronounced non-linearities in the filter circuitry model.

High-quality mode is a global parameter (for all sections) and can be enabled using the 'HQ' switch at the bottom row. This will enable anti-aliasing and oversampling to remove any aliasing.

Hello Jeroen, I have a couple of remarks:

- It's a bit awkward to have to open the dynamic section just to access the drive. Please consider a more immediate placement for it that doesn't require opening the dynamics.

- How does the HQ mode interact with the latency/zero-latency modes? I've noticed some phase differences in Plugin Doctor - with full latency mode, HQ appears to introduce even more phase distortion than in zero-latency mode, but I'm not really sure what I'm seeing is accurate.

- Would it be possible to add an 18 db/octave HPF please?

EQ4 is the gift that just keeps on giving, so thank you

[DeathByGuitar]

Loving all the updates. I especially love being able to color each band, but the band colors no longer follow theme colors when changing themes. Seems like a bug.

[mabian]

Loving all the updates. I especially love being able to color each band, but the band colors no longer follow theme colors when changing themes. Seems like a bug.

Why should they follow theme colors?
In which way?

- Mario

[mabian]

Hello Jeroen, I have a couple of remarks:

- It's a bit awkward to have to open the dynamic section just to access the drive. Please consider a more immediate placement for it that doesn't require opening the dynamics.

Agreed. If the feature doesn't apply strictly to the dynamics section, the related controls shouldn't be there...

- Mario

[NeonNightflyer]

Based on what he's said in previous posts, Jeroen considers that section to be the extended controls section rather than just the dynamics section, so that's probably why the drive is there.

[imrae]

Just released: update for ReelBus to fix the label visibility.

Regarding Equalizer 4, why does boosting a high frequency band with drive enabled boost the low end too? Is this a bug or intended behaviour?

Am I the only one experiencing this?

I can reproduce it but only with a bell filter and when really smashing the signal. It's interesting.

[Vortifex]

..

[trackbout]

And if you solo that band you can't hear the drive, but if you solo another band you can.

Ya, this is def a bug. It seems that each filter's solo button is pre-circuit-drive for that filter, rather than post-circuit-drive. Should def be post-circuit-drive so you can tune the drive while solo'd.

[djeroen]

Just some quick replies:

- When instantiating a new equalizer section, it will follow the color of the theme. If you adjust that color afterwards, it will keep the user adjusted color.

- On soloing bands: there is no solo function. There's audition, but that's something else. It will allow you to 'listen' to the input signal that will be affected by the current filter section (auditioning). As such it shouldn't apply any 'drive' processing for that section as we're listening to the 'clean' input. At least that's the current thinking.

[djeroen]

On latency etc: you may have spotted that in normal mode the plugin latency is sample rate dependent, and amounts to about 1.5ms only. In zero latency mode that latency will be zero.

The high-quality mode adds a little bit of latency due to the anti-aliasing filters.

Latency of the compressor/dynamic EQ look ahead (the 1.5ms) will be compensated for by the host program if it supports plugin latency compensation. Same is true for the combination of look ahead and oversampling / anti-aliasing (HQ mode).

[trackbout]

- On soloing bands: there is no solo function. There's audition, but that's something else. It will allow you to 'listen' to the input signal that will be affected by the current filter section (auditioning). As such it shouldn't apply any 'drive' processing for that section as we're listening to the 'clean' input. At least that's the current thinking.

I can see the reasoning here, especially since there was no circuit drive until recently so the auditioning would naturally be dry. Now that there is a new "effect" essentially with the circuit drive feature, and since that effect is per filter (which is awesome!), it would be nice to be able to audition each filter's wet signal rather than the dry signal, in order to tune the effect.

[Bouroki]

The high-quality mode adds a little bit of latency due to the anti-aliasing filters.

Except that in no-latency mode it doesn't add (or at least report) any additional latency and stays at zero. Is that by design? Is it using different anti-aliasing filters between no-latency and latency modes?

I'm asking because there is definitely some phasing going on in both latency modes. In fact, in normal latency mode, despite the correct latency being added (verified that in Reaper) the phasing seems to be worse! That could have a negative impact on multitrack recordings for example.

[jens]

Yes, I can confirm that the HQ mode both with the no-latency and the normal mode doesn't report the correct latency it causes. in no-latency mode it doesn't report any, which is false and otherwise the one it reports is not correct (This is easy to verify with a phase-cancellation test).