Valhalla Delay released

[s28]

I just automate the mix dial so I've never encountered this.

[Biome_Digital]

I find myself turning to this delay a lot. Love the different engines and character.

[Funkybot's Evil Twin]

I find myself turning to this delay a lot. Love the different engines and character.

I've used a few other delays since getting this, but if this were my only delay, I'd be good! Or this and Timeless 3 (for when you really want to go deep down the tweaking rabbit hole).

[mholloway]

Anyone else have the experience that when one switches ValhallaDelay on/off or change a Mode there is a heavy CPU spike and an unpleasant noise burst? Latest version of the Delay is running, as well as recent versions of Live and Win10. ASIO Driver by Yamaha (Steinberg UR242 interface). Can't say if it have happened before since I just lately get deep into the plugin. But I can't remember this behavior before so it may came with the latest update (Phaser and Quartz). Before I sent a ticket I would like to know it occurs to others too.

Have you tested this in a DAW other than Ableton? I've seen weird cpu spikes in Ableton regarding inserting new devices (that may apply to automating their on / off switch as well) that I don't see elsewhere...

That said, as has been noted by others in this thread, automating the on / off button of third party plugins is sort of Not Best Practice in general, turning third party stuff on and off frequently will open a lot of 'wild card' behavior re: CPU spikes and other 'unknowns.' I feel fine automating on/off on native Live devices, but with third-party I prefer to automate their mix / level controls (or even sometimes build more elaborate multi-chain FX Racks with 'dry' and 'effect' chains mixed inside them, and then automate the mix level of the effect -- but this is usually in cases when I have other, deeper uses for a parallel-chain FX rack).

[Biome_Digital]

I find myself turning to this delay a lot. Love the different engines and character.

I've used a few other delays since getting this, but if this were my only delay, I'd be good! Or this and Timeless 3 (for when you really want to go deep down the tweaking rabbit hole).

I enjoyed the demo of Timeless 3. If I didn't have all the delays I do I would have bought it too. I currently use about 10 delay plugins.

[elvisish]

Still waiting for the duck mode to have width settings, it's really unusable for most applications at 100%, unless you want to use it as a send and manually reduce the width.

[jens]

For me it's the timing of the ducking that's often a big problem... I think it has unreasonable settings for most scenarios and it feels like they didn't put enough effort into tweaking it into proper shape.

[cantaloupe]

Still waiting for the duck mode to have width settings, it's really unusable for most applications at 100%, unless you want to use it as a send and manually reduce the width.

The ducking GUI implementation was really dumb imo. Why not just add two more knobs and let the GUI and functionality be consistent between models. There is a point where desperately trying to be minimalist turns into bigger complexity than just adding what needs to be added.

[muki]

there is a new verson of valhalla delay, v2.5.0
but it seems not to be working in logic 10.5.1 under mojave (osx 10.14)

it does show up in plugin manager and is confirmed to be validated



but
it does not show up in any plugin menu dropdown list.... (???)




sort of superstrange

i did a re-login and a restart - but to no avail
still does not show up in the valhalla submenu

anybody else ?

p.s.:
it does show up in hostingAU
even more strange...

pps.:
the new supermassive does work and showup

[muki]

solved the problem:

went to all the plugin folders, components/vst/vst3, and deleted the valhallaDelay plugin manually
then, reinstalled
this worked

i had this behaviour with (very rarely) other manufacturer's plugins
so i thought to give it a try...

i leave this comments here, so that others with the same/similar problem have a solution to try

[bleen]

solved the problem:

went to all the plugin folders, components/vst/vst3, and deleted the valhallaDelay plugin manually
then, reinstalled
this worked

i had this behaviour with (very rarely) other manufacturer's plugins
so i thought to give it a try...

i leave this comments here, so that others with the same/similar problem have a solution to try

It's likely that the reinstall is what fixed your issue; Logic, being an AU-only host, has no idea what is happening in the VST3 folder.

[Neon Breath]

Man that new RichPitch mode is the perfect tool for some ethereal & sparkling shimmer reverb!

[digitalboytn]

Rich bitch mode

[whassup]

Very nice! Awesome gift for the season. Great delay plugin got even more better.

[chagzuki]

A question about the 'age' parameter on Valhalla plugins, at certain levels or on certain delay types, or in certain era modes (or a combination of all?) it emits a constant background noise whether there's any signal input into the delay. Is there a rule as to when this happens? I notice in some projects some noise during a silent passage and track it down to a Valhalla delay... I wonder, wouldn't it make more sense if the noise was only generated when there was actually a signal being processed/a delay occurring? I can't imagine a scenario where it would be desirable to have a constant background noise, but of course it's often desirable to add some noise to the actual delay.

Edit, it appears to only be the bucket brigade mode, but not the BBDuck... which I guess makes sense.