I upgraded my Overloud TH-U to V2 shortly after the new release and have encountered an irritating problem.
In TH-U many of the internal parameters (e.g., amp gain, bass, mid, treb, etc.) are automatically mapped to parameters that we can link to widgets. Those still work fine.
However, there are some knobs and buttons that don’t have an automatic link to a host automation slot. For such cases Overloud gives us 16 “automation slots” that we can assign knobs, switches, etc. to by right clicking on the parameter in the plugin window.
In the past, any such assignments were saved as part of the “plugin state” and thus automatically saved as part of your rackspace.
In TH-U V2.0.1 these parameters are either not saved as part of the plugin state, or not properly restored upon reloading the plugin state.
I have reported this to Overloud, but have not yet gotten a response.
I’m running on Windows 11, and have the same issue whether I use the VST2 or VST3 version.
The same problem happens when used in Studio One, and I would assume every other DAW.
If anyone else is using TH-U v2 I’d be interested to hear if you have the same problem. Otherwise take it as a word of caution if this is a feature that you use in your rackspaces.
In the above I right clicked on the “Mode” toggle switch. You can see that I assigned that switch (within TH-U) to “Automation Slot 1”.
If I save the Gigfile, close, then re-open it TH-U V2 does not restore that assignment of the Mode switch to Automation Slot 1.
If I assign a toggle switch in GP to TH-U automation slot 1 GP will remember that. But TH-U forgets that automation slot 1 is assigned to anything, so even though my GP widget remains linked to slot 1 TH-U just ignores it because TH-U doesn’t remember that it’s linked to anything.
I also encountered the same problem but found that there are many predefined parameter options available down the list, and I managed to find the parameter I needed to assign.
Yes, the vast majority of what I want to control is available without having to assign to automation slots. The problem comes if you have a rackspace with two overdrive pedals, two amps, or basically two of anything.
I use that kind of thing in a lot of my rackspaces. I don’t usually have two drive pedals active at the same time, but I may have something like a Centaur and a BD2 in the same rackspace and have the different drives active in different variations.
I can get around it easily enough by just adding more instances of TH-U, but I don’t want to re-do all such rackspaces when it’s a bug I’m sure they’ll fix soon.
