Valhalla FutureVerb

[Teksonik]

So basically what you're your saying is that any negative posts about any plugin from any developer are "disrespectful"?

It wasn't about negative posts about a plugin. He didn't even use the plugin, he listened to audio demos! It's posts where Jamcat's whining that these apples are not papayas. And that only papayas will do. And then he goes on to say only people with real tastebuds eat papaya, implying that people who eat apples have bad taste. He's not being censored. He's not a martyr. He's just fixating on something unrelated to the thread/topic. Sure, they're both fruit, but this is about apples! Not some obscure fruit that's very different. People would like him to STFU about it because it's a dumb place to make that argument, not because he's not allowed to make negative posts. I'd be more open to his argument and recommendations if he made them in an appropriate thread.
Maybe a post of, "I'm disappointed that something called Futureverb just seems like a refinement of past approaches versus being something truly new..." Sure. Valid point. But his whole "reverb has to be a real room simulation with exact placement of musicians in a room so I can make my fake SWAM instruments totally real sounding in a way that makes no sense" horse has been beaten to death by now surely.

The bottom line is you just posted your opinion. Is he not allowed to do the same even if you find it annoying? Are you not perhaps also beating a dead horse (and I as well)?

I'm not saying I agree with his points but I do think we should be allowed to post our opinions even if they trigger the fanbois. If the fanbois keep responding to the posts instead of ignoring them who is abusing the horse?

I would like a lot of people to "STFU" but on and on they go. Welcome to the internet I suppose...

[Funkybot's Evil Twin]

He's allowed. But insisting that plugin A work and have features of unrelated plugin B was entirely OT. Hit me up on PM if really want more of a response. Arguing about off topic posts is just as OT.

[jupiter8]

Is there any option to add ducking?

No.

We had a simple ducking algorithm in an earlier version, but it didn't sound very good. In order to get the sort of control that people expect from ducking, we would have had to add a lot of controls. At that point, anyone who knows how to use all those controls, knows how to put a reverb on a send and use the sidechained compressor of their choice to dial in the exact ducking behavior they want.

tl;dr - your favorite compressor is better at ducking than we are, and we wanted to keep the plugin as simple as possible.

[medienhexer]

FutureVerb will be an insta-buy.

Wait, an instant buy is happening immediately... but if it happens in the future... will you have to travel to the future to buy it? This post is almost as confusing as a fight scene in TENET.

ASCII violence? Oh, I thought you said TELNET. My bad.

[Funkybot's Evil Twin]

Is there any option to add ducking?

No.

We had a simple ducking algorithm in an earlier version, but it didn't sound very good. In order to get the sort of control that people expect from ducking, we would have had to add a lot of controls. At that point, anyone who knows how to use all those controls, knows how to put a reverb on a send and use the sidechained compressor of their choice to dial in the exact ducking behavior they want.

tl;dr - your favorite compressor is better at ducking than we are, and we wanted to keep the plugin as simple as possible.

On the one hand, I was disappointed at first when I didn't see ducking, but I totally get that rationale because I always want controls over the release speed of the ducking (I've run into scenarios in ValhallaDelay where I felt the speed wasn't right), not just the amount. And then I'm going to want some kind of visual indicator as to how much is taking place. If the goal is to keep the GUI simple and feature set less crowded, it makes sense in most instances to just let users do it themselves.

[chagzuki]

I use reverbs as inserts a lot, and in that case I need ducking built in, and I prefer being able to keep the dry signal at 100% while adding reverb. Hence I don't use Valhalla plugins that much.

[martinjuenke]

I use reverbs as inserts a lot, and in that case I need ducking built in, and I prefer being able to keep the dry signal at 100% while adding reverb. Hence I don't use Valhalla plugins that much.

I do not understand the difference between your preferred way and the send method of adding some reverb to the dry signal. May I ask to explain? Your way seems to be innovative and interesting.

[foosnark]

I use reverbs as inserts a lot, and in that case I need ducking built in, and I prefer being able to keep the dry signal at 100% while adding reverb. Hence I don't use Valhalla plugins that much.

I never really use sends, but I make frequent use of the Chain device in Bitwig which is functionally similar while remaining inline.

That lets me do things like use my preferred filter/EQ/dynamics/lofi/chorus/distortion whatever plugins on effects, then blend the total package with the dry signal however I wish. This is super nice for both delays and reverbs.

Bitwig also lets you use an envelope follower to modulate an effect parameter, which takes care of ducking quite easily without even needing to do the chain thing.

[catamorphism]

I bought it without demoing. We are very spoiled for good plugins these days and I've decided that I will just mostly buy from developers that I like and that have proved themselves as good and reliable over the years.

[chagzuki]

I do not understand the difference between your preferred way and the send method of adding some reverb to the dry signal. May I ask to explain? Your way seems to be innovative and interesting.

You mean the preference to use reverb (or delay) as an insert? For me it's a matter of project organisation and which elements need to be ducked (usually spectrally with something like trackspacer) by other elements. I often want quite specific reverbs on individual parts, EQ'd quite surgically to fit their role in the track, and I might want that signal path to be spectrally ducked by something else. It would make no sense to create loads of sends just for this purpose.
Also, I've found that DAWs seem to struggle more when there are loads of busses with complex routing, I guess it's a thread/core management thing.

[mi-os]

the gushing and fanboying is a bit too much.

Who’s doing that in this thread?

Sorry, i'm not biting. It would lead to nowhere good.

Gotcha. Keeping the peace.

Rather than making a bullshit claim you can’t back up.

Nice

My fact based opinion is the least of your problems, bro.

Also, try to avoid straw man arguments. That doesn't make you seem too bright.

[Constructed Identity]

Sounds epic, will buy when I get home.

[chagzuki]

I never really use sends, but I make frequent use of the Chain device in Bitwig which is functionally similar while remaining inline.

Ah, yes, that would be nice. Reaper can do that stuff too, but I use Logic more often.

[revvy]

My fact based opinion

[foosnark]

They aren't isolated units in series; the two modules interact with each other, even when Delay level is at 0.

It's simultaneously serial and parallel.

futureverb.png

For predelay: use Echo->Rev, turn Echo level to 0 and Reverb level to 100.

For grunging up the effect more: use Rev->Echo, turn Reverb level to 0 (to start) and Echo level to 100. Delay time still sets "predelay" but it's technically "postdelay".

For other character stuff: use Rev->Echo and 0ms delay, but mix levels as desired.

For "double tap reverb": use Rev->Echo, turn Reverb level to 100 and Echo level up as desired.

For just grunge or detuning: Echo->Rev, but leave reverb level and delay time at 0.