I add it to a mono track, save and restart, add it to a new mono track, save and restart, and so on.
Each time the plugin isn’t activated on the lastly added track; so after the first save/restart the single track isn’t working and after three tracks only the first two work.
If I then add a stereo track and restart it works on all tracks, but only on the right channel of the stereo track.
This is confirmed to be a locale bug, but the remaining instances of locale-dependent float parsing were in nlohmann’s json library. I have no idea why it deliberately uses the locale-dependent decimal separator and then tries to patch each float value from the .json to that locale before parsing it, instead of just parsing “.” directly.
Fixed in 1.3.4, tested with french locale which also uses “,” for decimals. Please tell me if any other problems remain / appeared.
I also fixed the calibration input samples to give the correct output levels. My calibration function measures RMS relative to -18dB while input calibration signal was -18dB peak to peak, which gave a few dB louder than target level.
Saw this feature request on the github page for tone3000’s plugin, and was already considering implementing this: the effect section, in addition to noisegate and phaser/resonator, now has chorus, delay, and reverb. Math is mostly “borrowed” from Rakarrack Plus (and super efficient) while using my existing c_biquad class for frequency filtering / damping.
So the signal chain with everything enabled is:
Input → noisegate → pedal bank → pre-EQ → amp bank → post-EQ → cab bank → phaser → chorus → delay → reverb → output
A WAH effect can easily be created by automating the frequency of one of the pre (or post) EQ bands or mapping it to a midi CC. What i’m considering is, as requested, an option to move pre-eq before or after the pedals… what do you guys think?
Yep, forgot to put a tremolo, which would be very simple to implement, though from a design point of view, would the UI become too confusing or bloated? How’s the new effects setup, and how could i improve it?
I have no idea because i’m creating this plugin primarily for my own use, and i’m getting nearly zero feedback on it.
The interface is very easy to use. The only thing I feel is missing is a model description when loading locally (similar to the one shown when loading online).
The Depth setting on the Phaser seems backwards.
I’d expect a depth of zero to give very little phasing and when it turn it up to 1 I’d get max effect, but right now it’s the other way around.
There’s no “depth” setting that will give you no phaser effect at all. Depending on other settings, one specific position on the “depth” (with LFO rate at zero) might sound similar to bypassed/off.
I pretty much just copied the math from Rakarrack plus, which iirc behaves the same way. The primary use of the phaser/resonator in this plugin however, is to be used with a static LFO (rate = 0) as a tone filter, like i did for ~= 20 years with an old Behringer rackmount unit, I was looking everywhere for a phaser plugin with that capability until i added it to rakarrack a few years ago
That would be a bit more difficult, because the descriptions are only available from the website/API, there’s no description embedded in the .nam files themselves other than gear type and a few other pieces of metadata - unfortunately, the description isn’t one of them.
But yeah i was thinking of “unifying” local vs online browsing into a more coherent UI.