Valhalla Delay released

[noiseresearch]

That's weird because I use CSI in Reaper to control ValhallaDelay VST3 on my MIDI Fighter Twister and/or X-Touch and it works fine. It's basically tapping into the automation parameters/system via TrackFX_GetParamNormalized/SetParamNormalized APIs.

Can you create and share an otherwise empty .rpp project with ValhallaDelay VST3 on a track along with the automation lane(s) that reproduces the error? And if you can do that, then I'd also even suggest shooting an email to support@cockos.com with a link to said .rpp in case it's a Reaper thing. If they confirm it's not, Justin or Schwa may be able to respond with details about why it's happening that may be helpful for Sean.

Thanks for your try to help. I can automate and midi map the parameter. But they do not reflect the actual state of the plugins. It's happening within Live and Reaper so it's not a DAW problem. All my other plugins behave as expected.

Take a closer look at the values in the automation lane. They do not represent the actual state. This happens with Live and Reaper

ValhallaBug.gif

ValhallaBug2.gif

Here the VST2. The values are between 0 an 1 instead of the value of the plugin.

ValhallaBugVST2.gif

ValhallaBugReaper.gif

[Funkybot's Evil Twin]

Just curious: if the DAW transport is running, do the values then suddenly start to update?

[noiseresearch]

Just curious: if the DAW transport is running, do the values then suddenly start to update?

Unfortunately no

ValhallaBugTransport.gif

[noiseresearch]

More bugs: Valhalla Delay vs. Sandman Pro. Sandman Pro behaves as expected.

Take a look at the "Delay Mode"

MoreBugs.gif

[liquidsound]

Tested in Reason 13.2 and it works as it should...

[noiseresearch]

Tested in Reason 13.2 and it works as it should...

Thank you for this info. Vst3?. I wonder what's causing this issue in Reaper and Live.

[liquidsound]

Tested in Reason 13.2 and it works as it should...

Thank you for this info. Vst3?. I wonder what's causing this issue in Reaper and Live.

VST3
Problem in Bitwig as well for me.
Reason has been always reliable with Automations and lately the RS 13.2 is better at dealing with Serum 2 even better than Reaper

[mabian]

Additional issue found on many ValhallaDSP plugins - already reported a while ago... while automating parameters in REAPER it's no longer possible to type in parameter values with the keyboard (even those which are not being automated...)

- Mario

[liquidsound]

Tested in Reason 13.2 and it works as it should...

Unreal...
Now is no longer working... (Mode and Era only).
I have no idea why...

[Stirner]

I have no problems and just tested it with Delay, Room and Supermassive. Reaper and Win. Automation work, the real values are shown in the automation lane and I can also double click and keyboard enter values. I use Valhalla and Reaper for a long time and it always worked fine.

[mabian]

I have no problems and just tested it with Delay, Room and Supermassive. Reaper and Win. Automation work, the real values are shown in the automation lane and I can also double click and keyboard enter values. I use Valhalla and Reaper for a long time and it always worked fine.

Even when using reaper parameter modulation?

[Calagan]

My experience with Valhalla plugins and automation on a Mac (I'm on Sonoma, running the vst3 versions of my Valhalla plugins in Ableton Live 12), is that automation works fine (in the sound domain) but is displayed wrongly on the screen.

For exemple, let's say I automate the mix of a Valhalla plugin from 50% to 0%, then to 100%. Even if the curve looks fine and the mix knob is moving accordingly to the automation I did draw, when you follow the curve with your mouse it always shows the initial value (50% in this case). To me it's not a big deal when tweaking an automation, but it's definitely a bug.
There is also a huge issue when mapping a parameter (still in Ableton Live) : the max and min values displayed in the mapping window are wrong (kind of random), and it's a problem to be able to define them precisely. You actually need to tweak them blindly while monitoring the "real" value in the plugin.

To my knowledge, the only one plugin dev that has the exact same issues is Sonimus.

I think I did send an email to the Valhalla support (and to the Sonimus one) but so far no fix...
EDIT : Actually, to their defense, I checked and I didn't send them any email about that issue. I'll do that today... I'll also try to make a small video so they understand the issue.

[noiseresearch]

Good to hear I'm not alone. I gonna send a support request again soon too. Would be great if everybody encountering this bug contacting Valhalla DSP.

[Stirner]

I have no problems and just tested it with Delay, Room and Supermassive. Reaper and Win. Automation work, the real values are shown in the automation lane and I can also double click and keyboard enter values. I use Valhalla and Reaper for a long time and it always worked fine.

Even when using reaper parameter modulation?

If I use a LFO than obviously the value is constantly changing, but if I am fast enough than I can double click and can type something in, but then the LFO changes the value.
Using straight automation I can double click and type a value, but it's of course overriden by the automation lane after ENTER.

But I now understand the problem with not showing the actual automation curve values by following the mouse. Yes, other plugins behave better-

[MattLeschuck]

I just checked when automating parameters in Pro Tools it doesn't even show a value (from 0-100%). So there is a bug there with AAX as well. Compared it to Echoboy which displayed correctly.