ToneBoosters Reverb update

Gavinski

A very erudite reply as always, Samu, thank you!

DJB

@Samu said:

@Gavinski said:
Is there a technical reason why so many developers are very conservative when it comes to lfo speeds, or is it just that they're not thinking outside the box enough?

It could be related to buffer sizes and other optimizations?

As an example the LFO's in BM3 max out at 200Hz and it has something to do with the app internally working in 32 sample chunks instead of updating all the parameters on a per-sample basis which would slow things down as more tracks and samples get added.

The Drambo LFOs caps at around ~150Hz but there's no stopping one using a regular oscillator as the modulation since everything is calculated on a per sample basis and that's partly why feedbacks are always one buffer late as zero-delay feedback loops would tax the CPU too much.

Regarding LFO's in general I'm more worried about constant the lack of sync & start-phase control and bi/uni-polar switches not to mention some nice bit-reduction on the output to get stepped modulation values etc. etc.

Limited 'modulation depth' is also something unfortunately quite common as is custom LFO-waveforms which could be used as step-modulators and after passing thru variable 1-pole low-pass filter as custom waveforms.

Cheers!

Well said! Indeed complexity goes up with faster LFO frequencies (filter parameters will need to be calculated more often). And the 'step size' from one update to the next will be much larger as well, both causing challenges.

In DualVCF we've managed to come up with a hybrid (two-stage), and highly optimized interpolation scheme and we can therefore update everything very frequently without too much of a CPU penalty. But this took a lot of effort to develop and do right....!

craftycurate

@Gavinski said:
Is there a technical reason why so many developers are very conservative when it comes to lfo speeds, or is it just that they're not thinking outside the box enough?

I wonder if it’s to do with the the internal modulation calculation rate the app uses ie. if modulation values are only calculated at 100Hz then it only makes sense to offer LFO rates up to 50Hz (Nyquist rate etc) otherwise it could lead to some odd outcomes.

[Deleted User]

I don’t have this but I’m considering it. What is the double preset list for?
Also any experience with TB dual vcf? It seems good too.

DJB

In response to your requests, DualVCF has been updated:

• Peak limiter can be enabled or disabled
• Maximum LFO frequency is now 500 Hz (!) for crazily fast filter modulation
• Maximum LFO sequence length is now 999 beats (over 8 minutes at 120 bpm)

https://apps.apple.com/tt/app/tb-dualvcf/id1505169270

gusgranite

@DJB said:
In response to your requests, DualVCF has been updated:

• Peak limiter can be enabled or disabled
• Maximum LFO frequency is now 500 Hz (!) for crazily fast filter modulation
• Maximum LFO sequence length is now 999 beats (over 8 minutes at 120 bpm)

https://apps.apple.com/tt/app/tb-dualvcf/id1505169270

That’s a fantastic update. Thank you! 👊

anickt

@DJB said:
In response to your requests, DualVCF has been updated:

• Peak limiter can be enabled or disabled
• Maximum LFO frequency is now 500 Hz (!) for crazily fast filter modulation
• Maximum LFO sequence length is now 999 beats (over 8 minutes at 120 bpm)

https://apps.apple.com/tt/app/tb-dualvcf/id1505169270

🙏🏼 🙏🏼 🙏🏼

david_2017

Awesome! Thank you @DJB !!!!!

Gavinski

Great! @DJB 👍👍👍