epicVerb 1.5 released

[metalifuxx]

IMHO I hate reverbs with only the 2 faders for wet and dry mix. 1 mix knob is all that is needed. And you can always use something like the Sonalksis FreeG volume fader before or after.

[zeep]

*sorry double post*

[zeep]

Ofcourse in Send it's useless, but i never use sends, only inserts.

Do you open a new reverb every time you need reverb ?

Yes. I hardly ever use sends in Live 8, it's the way i work.

IMHO I hate reverbs with only the 2 faders for wet and dry mix. 1 mix knob is all that is needed. And you can always use something like the Sonalksis FreeG volume fader before or after.

Well i don't hate an fx wet/dry knob. Really, hate's too big a word for it.
For me, being able to mix dry and wet separate to 100% volume simply offers better mixing control. So that's what i prefer.

If you don't have to resort to plugin B to acomplish a particular sound from plugin A, then that's a plus for plugin A.

Having only a wet/dry knob works fine, but i have to raise the channel volume separate when i need more dry volume with the wet/dry knob set at 80% for instance. I'd rather have that functionality in the reverb so i can leave my channel volume at the same level.

[robenestobenz]

@zeep: I still don't get it though. There's a giant volume fader within the reverb. I don't find myself needing more than 12db of gain that often...

That said, I actually prefer separate controls myself, even though it's more effort for the same effect. People are strange.

[brok landers]

there's several benefits in having 2 seperate sliders for dry and wet, especially when using a reverb as an insert fx.
for example, you have the reverb set up to sound the way you like, but in the mix you want the dry signal more "in the room". all you have to do then is lowering the dry knob. that has the advantage to not be fooled by the reverb wet level to change, when changing the dry level.
or another example:
if you want the wet signal to be automated (i.e. faded in), with 2 sepearate sliders the dry signal doesn't change its desired level that you have set up in the mix. you just automate the reverbs wet slider to fade in the reverb itself. you can't do that with a dry/wet slider, as the dry signal gets lower in level when over 50% ...

another thing though:
if i remember it correctly, also in this thread (and various others) it has been falseley stated that a reverb sounds different when using it as an insert as opposed to when used as a send fx. that's pure nonsense. if it sounds different, then only because of user error (i.e. not set up the correct snd levels, etc). as soon as the reverb is hit by the same level that it has on insert, and the output/wet level is the same as in the insert, the reverb sounds absoluteley identical. the relation of the levels have to be the same, then it exactly sounds the same.
just wanted to point that out.

[zeep]

there's several benefits in having 2 seperate sliders for dry and wet, especially when using a reverb as an insert fx.
for example, you have the reverb set up to sound the way you like, but in the mix you want the dry signal more "in the room". all you have to do then is lowering the dry knob. that has the advantage to not be fooled by the reverb wet level to change, when changing the dry level.
or another example:
if you want the wet signal to be automated (i.e. faded in), with 2 sepearate sliders the dry signal doesn't change its desired level that you have set up in the mix. you just automate the reverbs wet slider to fade in the reverb itself. you can't do that with a dry/wet slider, as the dry signal gets lower in level when over 50% ....

Exactly.

[bootsie]

I think I've got your point now. This seems to be more of a workflow taste, working with Dry/Wet plus Volume controls opposed to separate Dry and Wet controls (plus channel fader).
For my own taste I do prefer the combined Dry/Wet solution exactly because in most cases I don't have to worry about output gain changes and don't have to touch the channels fader to correct that.

[ozmoz2008]

another thing though:
if i remember it correctly, also in this thread (and various others) it has been falseley stated that a reverb sounds different when using it as an insert as opposed to when used as a send fx. that's pure nonsense. if it sounds different, then only because of user error (i.e. not set up the correct snd levels, etc).

That is precisely one of the reason that it's better in the send, you can have the same ambience on different tracks set at different levels.

It doesn't sound different but way more easy to manage. (As we use to do on consoles BTW, I didn't saw a reverb in an insert back then often, just very rarely)

What would sound very different is the balance, and that is one thing people don't seem to manage well sometimes when comparing reverbs in insert. My 2 cents.

[bootsie]

Here is a short sample which shows the smoother density build up in version 1.5:
eV1.0
eV1.5

[dickiefunk]

Version 1.5 sounds smoother to my ears

[alteregoxxx]

Here is a short sample which shows the smoother density build up in version 1.5:
eV1.0
eV1.5

There is a slight "volume oscillation" in the first tail of EpicVerb V.1 that is absent in V. 1.5! V.1.5 is more "continuos" in this sense! Awesome work Bootsy!!!

[robenestobenz]

Lovely. The kind of rattling in the early reflection was the one thing I didn't like about the plugin, but the 1.5 sample sounds much better. Not only is the rattle gone, but the tail is noticeably smoother as well. Great stuff, I can't wait!

[Dandruff]

Looks like Bootsie fixed the crashes. He sent me a test version and I couldn't get these crashes anymore. But it introduced a different crash which causes Reaper to close without warning on the first usage of epicVerb. On the second time it works.

Good news Dandruff (Dstruct). Thanks for the info, I hope Bootsie fix this one too.

I'm working on it.

Any news on it? Also did you got a positive response from the SynthMaker guy(s) about the problem with buffer(s) not cleared properly after render process?

Will this be fixed in 1.5?

[Dandruff]

Bootsie,

the crashes in Reaper seems to be fixed indeed. Many thanks for this!


But this problem isn't:

epicVerb in Reaper:

render-burst.rpp (12.3kB)


-> load the project
-> file -> render -> render

=> once render is finished you hear this:
render-burst.wav (154.9 kB)

This shouldn't happen. There should be silence. When using Reaper's ReaVerb, there's no such sound after render is finished.

What about this? Fixed in 1.5?

[ozmoz2008]

Lovely. The kind of rattling in the early reflection was the one thing I didn't like about the plugin, but the 1.5 sample sounds much better. Not only is the rattle gone, but the tail is noticeably smoother as well. Great stuff, I can't wait!

Same here I like better 1.5, less rattle-distorsion in the first part of the sample and because of that I hear a smoother release, more washy.

Good job! Can wait to try it in a real situation now.