Valhalla VST Macro Mapping Bug

[doubleUG]

When a parameter of an Vallhalla VST is mapped to a macro, the min max values of the macro are wrong. Does anyone else have this problem?
It is very difficult to set the Delay Time of Vallhalla Delay exact. But this seems happen to all parameter.

VST3 Win 10 Live. 11.3.4

[jaschanarveson]

Yes! Very annoying.

When I map a parameter to a macro control I sometimes get a 0.0 - 1.0 scale, no matter what the unit is of the control (dB, %, Hz, etc) OR I get the right units, but the MIN and MAX are always the same, or sometimes behave weirdly.

Ableton Live 12 Beta 12.1.5b3, Mac OS Sonoma 14.7

[The Rabbits]

If you have a setup.txt file, make sure the option "-AutoAdjustMacroMappingRange" is not included.
Setup.txt is not installed or changed by the normal install process.

[[jur]]

Anyone ever told Valhalla about this?

[Calagan]

Yep, same here (Live 12.0.25 MacOs Sonoma).
It's actually the same with Sonimus plugins (I don't think any other devs have that issue).

And by the way there is another issue with parameter automation : on my machine it's like if the parameter's value was not updated when drawing the automation. Say if I set the valhalla delay mix knob at 50%, it keeps indicating 50% whatever I draw in the automation line. But if I move the playhead it shows the good value.
It's not a big deal but yes it makes setting automation lines a bit painful...

I guess we should send a little email to Valhalla...

[rhythmic88]

Hello everyone! I've solved the same problem! Did you write to Valhalla? Did they answer anything? Or maybe you managed to solve the problem in a different way? Thank you!

[Rivanni]

Hello everyone! I've solved the same problem!

Do you mean you 'have' the same problem, or did you actually solve it. If it's the latter, why don't you tell us how you did?

[distantnoise]

Anyone ever told Valhalla about this?

Yes. I did. Three times. Like four years ago, last year and this year. Never got an reply! Actually I decided to send one this week again. Let' see. But would be great if others also send a support request regarding this issue.

The main issue I have is that "Modes" are set in float (0-1) internally and not quantized. So while automating or using with Push I have a crackling sound which is not there using the plugins UI. I assume instead of "jumping" to the next value (mode) the in-between values are sent and causing the crackling.

There are also some other quirks I encounter – mainly in interaction with automation and/or using ValhallaDSP plugins with Push. This issue is not there with any of my other commercial plugins.

Disclaimer: I just assume and I'm not a coder myself but using computer since 1993

[distantnoise]

Take a look at the "Mode" sections of the plugins and the "generic live slider". Normally it should work like you can see with Sandman Pro. But no, not with ValhallaDSP (all plugins the same, at least the ones I use Ubermod, Delay, VintageVerb, SpaceModulator, Supermassive.

[rhythmic88]

Hello everyone! I've solved the same problem!

Do you mean you 'have' the same problem, or did you actually solve it. If it's the latter, why don't you tell us how you did?

I apologize for my English. I don't know how to fix this bug and I really want to find a solution.
If we all write letters to Valhalla, it's a good idea

[distantnoise]

Hello everyone! I've solved the same problem!

Do you mean you 'have' the same problem, or did you actually solve it. If it's the latter, why don't you tell us how you did?

I apologize for my English. I don't know how to fix this bug and I really want to find a solution.
If we all write letters to Valhalla, it's a good idea

I will send a support request at some point this week... Here is the link https://valhalladsp.com/support-request/

[distantnoise]

When a parameter of an Vallhalla VST is mapped to a macro, the min max values of the macro are wrong. Does anyone else have this problem?
It is very difficult to set the Delay Time of Vallhalla Delay exact. But this seems happen to all parameter.

VST3 Win 10 Live. 11.3.4

Did you ever sent a support request to ValhallaDSP? If yes, any answer?

[scg]

Just posting to add my experience to the thread. As of September 2025 I'm still seeing the behaviors described here with Valhalla plugins (some of them at least, including Room). In particular:

- Although automation nodes will sometimes display with the right units (e.g. percentage or hz), it appears you can only enter values in normalized form (0-1).

- Sometimes the displayed values for automation nodes aren't correct, even if the nodes are in the right position.

- As described earlier in the thread, specifying the range for macro mappings doesn't always work. As with automation nodes, even if the display units are correct, it appears you can only enter values in normalized form. Also, sometimes the 'fill bars' will change to reflect the correct values, but the displayed numerical value won't, and in other cases, while trying to change the min or max value by click-dragging the field, the numerical value will stop at arbitrary values. It does seem that the range indicated by the fill bars is correct, but the numerical values aren't always correct.

Of course it's possible some of these things could be Ableton bugs, or bugs that manifest only in combination with certain plugins.

I sent a tech support query to Valhalla, but after a week, like everyone else here seemingly, I haven't gotten a reply. So anecdotally at least it doesn't seem Valhalla tech support is active or operational.

Obviously Valhalla plugins are go-to's for a lot of people, and these issues aren't showstoppers per se, but it can make the plugins hard to automate, so I continue to wonder if these are known issues, and if there are any fixes or workarounds.

[Studio Sanctum]

I wonder why Valhalla is not responding to anyone? That's definitely not a good look!

[Calagan]

I wonder why Valhalla is not responding to anyone? That's definitely not a good look!

Just for information, I did send them an email, with some video displaying the issue, and they answered me (in last june).
The told me that they could reproduce the issue, and will look into it.

As they told me, their issue is fixing it while not breaking backwards compatibility. If they change this automation behavior, it could indeed break the recall of previous projects.
It may take quite some time to find a solution (if they ever find one).