I have a pedalboard I have been using for vocals, and I’ve recently had issues where sometimes the output becomes very boosted in the high-end and quite sibilant. The only beta plug-in I am using is the Calf Deesser, and due to the sound of the issue I’m having, I think that plug-in could be causing the issue.
The problem does not always happen, but when it does happen - I go through the plug-ins and turn them on and off, and somewhat randomly the issue goes away - it does’t always go away when the same plug-in is turned on or off, but somehow altering the signal path does knock things back to where they should be.
I can’t find any non-beta deesser in the plug-in library. So, is it likely that the Calf Deesser would make it out of beta? I assume some sort of tests are required, but lets say there is an issue with the plug-in (like I’m having), would that mean it will never leave beta? Does the Mod team fix plug-ins created by third parties?
I would prefer not to use a bunch of plug-ins to create an ad-hoc deesser.
After more troubleshooting, I found the issue and it wasn’t the Calf Deesser. Although I am still curious to know if/when it would leave beta, as I’m a bit afraid to use it live.
The issue is the Collision Drive plug-in. I have a button mapped to turn this plug-in on/off and even if I save my pedalboard with the plug-in turned off, it always loads with the plug-in turned on. The red light is off, but you can see the blue light used for the gate, is indeed active and the sound is processed.
Just for clarification I am using CV to turn the plug-in on and off. This works as expected, except that the plug-in loads up always processing audio, even though the red light is off.
I had also same issue with ChowCentaur plugin and other plugins. So looks it is not related to the plugins itself …
I think I solved the problem by saving individually each snapshot and then the pedalboard. But I don’t remember exactly, perhaps also renaming the pedalboard, or deleting the plugin and saving all again, before adding it again. Now I’m running a custom mod-ui, and it didn’t happen again since a long time.
My guess is something gets corrupted when playing with pedalboards - snapshots - connections (when adding and deleting plugins…)… In the standard 1.13 code for mod-ui, I think that when you add a plugin and save the pedalboard, this plugin is added automatically to all snapshots. But the same it is not happening when you delete a plugin and save the pedalboard. The snapshot still has the old plugin… Maybe after a while this get messed up. If you save a snapshot, it gets cleaned up, because only the existing plugins remains.
Imagine you you add a plugin and then delete it just for test. And after that you only save the pedalboard, because of course you think I don’t need to save all my snapshots before as long as nothing has changed for them… but not.
In this case ALL you snapshots for this pedalboard will have the info of the old deleted plugin. (to see this you have to connect to the moddwarf and check the file snapshots.json ), although your pedalboard has not this plugin (check file pedalboard.ttl)
To do a complete clean-up, you should go individually to each snapshot and press save. After that you should save the pedalboard.
Better think of a snapshot as a “stubborn child” of the pedalboard. Sometimes even though the “mother” pedalboard advises something, the “child” snapshot does something different
Ah, I think I understand what you’re describing better now. Yes, if you modify the pedalboard the snapshots are now out of sync, because they can include things that were added/removed from the pedalboard.
jaja yes exactly you found easier words. Sometimes my english is rusty…
Anyway my guess (I’m not 100% sure, as I didn’t find the exact bug) is that for the errors in this topics, saving all the snapshots again individually and then the pedalboard could solve it. Or perhaps first delete the problematic plugin do all the saving process and then add it again.
Somehow after working with one pedalboard long time, something gets corrupted is my guess. Hope the new 1.14 improves it…
Hmm, very interesting that the bug might not be specific to this plug-in.
However I don’t use snapshots. I just resave a new pedalboard when I make updates. So I’m unsure if the snapshot issue is what I am having, but there is indeed an issue of some kind.
Interesting - I will look at that. I didn’t realize that there was a separate snapshot save. I just assumed saving the pedalboard saved all snapshots, and there was no way to individually save them. But I will look at this and see if it fixes my problem. Thanks for the tip!
I have also made the experience, that if you add a new plugin to an existing pedalboard, you have to save all of your snapshots again. Otherwise the new plugin will keep its state because I assume that the old snapshots don’t contain any information of the newly added plugin.
Don’t forget to save the whole pedalboard after saving the snapshots.
Btw. for overdrive - I tried only yesterday the Centaur, and it’s insanely good. For me by far the best for boosting from the collection. It does take a lot of CPU though for some reason - in the “Traditional” setting even more so then in the “Neural” mode, I have no idea why that is. But seriously, it sounds incredible.
