Valhalla Delay released

[Funkybot's Evil Twin]

I don't have Supermassive though, and don't have plans to download it.

[vitocorleone123]

Is there something similar for SuperMassive modes?

- Mario

I don't have Supermassive though, and don't have plans to download it.

Confirmed: People make strange and bad decisions all the time.

[BoogerSnot]

I don't have Supermassive though, and don't have plans to download it.

Is there something similar for SuperMassive modes?

- Mario

I don't have Supermassive though, and don't have plans to download it.

Confirmed: People make strange and bad decisions all the time.

Less is more. Already got that ground covered. Only thing are the hoarders with 29 cats and 57 reverb/delay plugins.

[Funkybot's Evil Twin]

If I pairing down everything in my collection, Supermassive would be one that survives the purge. But you do you!

[jens]

edit: never mind...

[concealed identity]

Cats are awesome, and so are reverb and delay plugins. I'm more into dogs and saturation plugins myself, but you can't go wrong with any of these.

[Vortifex]

Is there something similar for SuperMassive modes?

- Mario

I can never remember what they're all supposed to be. I find the algo names on Valhalla Delay quite intuitive and don't feel like I need a cheat sheet for them. But when you're choosing between algos called Orion or Virgo it's not quite as easy. It doesn't help that the plugin is quite finicky about displaying the algo tooltip. Sometimes it just refuses to display it.

[legendCNCD]

Listen with various sounds, fex. high transient attack like rimshot or such and then on slower sounds, how the models react. The transient test tells a lot.

[whassup]

FOMO is real. And missing out is real too. But nobody NEEDS the free nuggets. They are still nuggets though. Just sayin...

[Vortifex]

Listen with various sounds, fex. high transient attack like rimshot or such and then on slower sounds, how the models react. The transient test tells a lot.

Maybe it's my suboptimal brain, but I just can't retain the association between the Supermassive algorithm names and how they sound. With Valhalla Delay I know which algo to use to get the sound I want, but with Supermassive's 21 algorithms I always find myself randomly trying to discover which one works best.

[concealed identity]

Listen with various sounds, fex. high transient attack like rimshot or such and then on slower sounds, how the models react. The transient test tells a lot.

Maybe it's my suboptimal brain, but I just can't retain the association between the Supermassive algorithm names and how they sound. With Valhalla Delay I know which algo to use to get the sound I want, but with Supermassive's 21 algorithms I always find myself randomly trying to discover which one works best.

You're not the only one. I don't mean to complain about a free plugin, and a fantastic one at that, but I do use it less than I would otherwise when I don't want to spend a lot of time going through algorithms.

My hope is that they'll at least add arrows to switch algorithms like they did with Delay. Even that would greatly increase the usability of the plugin imo.

[noiseresearch]

I wish Valhalla DSP would solve the automation bug most (all?) products having since ages. Talking about VST3. Informed Valhalla about this bug already a couple of time over the years without response.

Win 10 64 bit, Live 12, Reaper 7. Valhalla DSP: Delay, UberMod, Supermassive, Spacemodulator, VintageVerb.

The issue I have is with automating (Live and Reaper), controlling Valhalla DSP plug-ins with Push 3 (Live), using the plug-ins within a macro-mapped rack (Live). A lot of value jumping / and or unresponsive parameters. It's buggy unlike any other VST3 I use.

See also my older post about this issue: viewtopic.php?p=9016117#p9016117

Out of curiosity I tried the VST2 version of Valhalla Delay. Slightly different but nearly similar issues. Automation is nearly unusable.

There is some kind of „known“ issue, that Live doesn‘t work corrext with plugins and automation. E.g. there are similar problems with HALion. Sounds pretty similar, because this is also an issue, where the parameter after reloading the project just goes from 0..1

The workaround for that was to put the plugin in a group and map a remote control macro to the according parameter. Of course it‘s not convenient, but at least it works.

Would that work for you either?

Thanks for your trying to help out. Unfortunately, mapping to macros does not work properly either. Again, only with Valhalla DSP plugins do I encounter this bug.

Valhalla DSP support did not answered my questions / bug report fully but at least partially . Here is what I got as a response:

"The behavior you are describing is due to the JUCE parameter classes we are using. Unfortunately, changing this to a more recent parameter class would break every single existing DAW project. For example, changing the parameter values in VST2 from 0.0-1.0 to real number values would cause the recalled instances to either have incorrect values, or values grossly out of range. Backwards compatibility is a primary goal of ours, with many of our professional users opening up projects from over a decade ago. So we are not going to be changing this anytime in the foreseeable future."

[whassup]

Listen with various sounds, fex. high transient attack like rimshot or such and then on slower sounds, how the models react. The transient test tells a lot.

Maybe it's my suboptimal brain, but I just can't retain the association between the Supermassive algorithm names and how they sound. With Valhalla Delay I know which algo to use to get the sound I want, but with Supermassive's 21 algorithms I always find myself randomly trying to discover which one works best.

Same here. Interestingly enough Supermassive is one of those tools where I don't care.
To me it is just a free extension.
Some more free algorithms for the other ones.
I once counted them and found that I have 70+ algorithms in my Valhalla reverbs (forgot the real number actually).
Do I know them all?
Absolutely not!
But I enjoy having those options.

[legendCNCD]

Listen with various sounds, fex. high transient attack like rimshot or such and then on slower sounds, how the models react. The transient test tells a lot.

With Valhalla Delay I know which algo to use to get the sound I want, but with Supermassive's 21 algorithms I always find myself randomly trying to discover which one works best.

That method works nicely too when in a hurry! when it sounds right it is the right one.