epicVerb 1.5 released

[zeep]

Please add separate Dry Wet controls!

[D.Wako]

I don't really understand why a company would make a freeware product and then make its usage conditional, it seems a heck of a lot less free in spirit that way - but I suppose it is their prerogative.

I guess that doesn't violate the DC rules, then?

The software itself isn't conditional, just the expanded library. They do, however, note that the expanded library is freely available on their web site, and I definitely took its sound into consideration when casting my vote as part of the package. I'm not sure whether it violates the rules or not, since the software itself is free - which is really the cool part, all told, it's not like there aren't great IR libraries around for free or very inexpensively. It is a very impressive IR loader with excellent features. I guess I should have been more attentive to the fine print, so to speak. Still would have ranked it high, though.

I wonder if anyone contacted the university that provides these IRs and what's the cost if you want to use it in a commercial project? Anyone know?

Also, I'm not sure i understand how this plugin is different of other convolution reverb in that it supposedly have the benefit of both convo and algo reverb. I don't get the algo part. I'm probably a little slow here. But i love this thing and want to be able to use it and it's IRs when ever i want. This seem to be very hight quality stuff.

P.S. Some if I'm off topiv here.

P.P.S. Cant wait to try the EpicVerb.

[susiwong]

Please add separate Dry Wet controls!

Just out of curiosity, what is it you can't do with the current Mix / Output controls, and imho do it quicker ?
The only possible improvement I could imagine being useful in the output section personally would be a "wet only" switch overriding the mix setting (similar to the Plate 140), but apparently that would open up a can of worms in several areas and is only a matter of convenience, so not essential.
Cubase users can use the vstpresets I converted from the original ones, adding versions with 25% and 50% mix for easier preview, available from Bootsie's DL area.
Ymmv,
susiwong

[steponeloops]

Which leads to the million dollar question to you: Would such a native "no-compromise" reverb be appreciated even if it consumes let's say a whole single core of a modern cpu or maybe 50% of the whole system or so? Where is the acceptance threshold level (cpu consumption wise) for such a device? Or is low cpu still the most important requirement?

I'm really interested in your opinion on that ...

nice weekend,
Bootsy

Hi Bootsy,

definitely yes! For rendering the "ultimate" reverb I would like to have it. With some automatic switching between playback and rendering mode it would be perfect for me. Playback: lower quality to hear what you're heading for. Rendering: full quality.

Shogger

+1. Having a "no-compromise-option" would be great for final renderings!

[Christian Budde]

Playback: lower quality to hear what you're heading for. Rendering: full quality.

Just thinking out loud: I wonder, why the audio engineer should get the lower quality during mixing, while the consumer will get the full quality.

I imagine this is motivated by graphics, where the designer work with a wire-frame and only after rendering every detail is visible.

Although I do not want to discuss the need for such a mode, I wonder if it might not lead to the problem that either the differences are not audible, which makes it senseless to offer this mode or the differences are huge, which makes mixing difficult, when you hear something completely different after rendering.

I can clearly see users fine tuning a parameter for hours, when that particular characteristic changes with the rendering.

Just getting my thoughs sorted,

Christian

[zeep]

Please add separate Dry Wet controls!

Just out of curiosity, what is it you can't do with the current Mix / Output controls, and imho do it quicker ?..

Simple it offers more/flexible/better mixing control.

One Wet/Dry knob at 50% doesn't offer me the gain a separate Wet 100% / Dry 50% setting does for example. I've become quite used to this functionality thanks to Tila and ArtsAcoustic.

Mixing reverb in the mix and not having to use the channel's volume fader at all is a plus.

[susiwong]

Playback: lower quality to hear what you're heading for. Rendering: full quality.

Just thinking out loud: I wonder, why the audio engineer should get the lower quality during mixing, while the consumer will get the full quality.

I imagine this is motivated by graphics, where the designer work with a wire-frame and only after rendering every detail is visible.

Although I do not want to discuss the need for such a mode, I wonder if it might not lead to the problem that either the differences are not audible, which makes it senseless to offer this mode or the differences are huge, which makes mixing difficult, when you hear something completely different after rendering.

I can clearly see users fine tuning a parameter for hours, when that particular characteristic changes with the rendering.

Just getting my thoughs sorted,

Christian

Exactly my thoughts.
For similar reasons I prefer using S2.0 in real time, forgetting about the render option altogether.
I need to hear the complete picture during mixing.
Ymmv,
susiwong

[shogger]

Playback: lower quality to hear what you're heading for. Rendering: full quality.

Just thinking out loud: I wonder, why the audio engineer should get the lower quality during mixing, while the consumer will get the full quality.

I would hear it before the customer.

I imagine this is motivated by graphics, where the designer work with a wire-frame and only after rendering every detail is visible.

Huh? Did you ever see someone doing some serious 3D work? You do exactly what you just described. In 10 years from now this might be different when my laptop can do it all in realtime.

Although I do not want to discuss the need for such a mode, I wonder if it might not lead to the problem that either the differences are not audible, which makes it senseless to offer this mode

Yes, but no one wants a senseless mode, right?

or the differences are huge, which makes mixing difficult, when you hear something completely different after rendering.

I'm interested in things between your two extremes. Basically hearing what I'm going for and getting it in a better quality when it's rendered.

I can clearly see users fine tuning a parameter for hours, when that particular characteristic changes with the rendering.

Hehehe, we audio guys are not used to that. In 3D graphics you do this very often when useing things like e.g. transparancy or radiosity.

Shogger

[susiwong]

Please add separate Dry Wet controls!

Just out of curiosity, what is it you can't do with the current Mix / Output controls, and imho do it quicker ?..

Simple it offers more/flexible/better mixing control.

One Wet/Dry knob at 50% doesn't offer me the gain a separate Wet 100% / Dry 50% setting does for example. I've become quite used to this functionality thanks to Tila and ArtsAcoustic.

Mixing reverb in the mix and not having to use the channel's volume fader at all is a plus.

Sorry, I still don't get it.
When used on a send, dry or mix controls will not be touched anyway, you want 100% wet, period.
And in an insert I don't see the advantage either, to me it's easier for me to set the amount via Mix and then adapt the Output Level as opposed to having to balance two faders to get the desired level.
Ymmv,
susiwong

[covalent]

An important major update for the epicVerb digital reverberation simulator is (almost) done and will be released in the beginning of December 2009. It not only features some bugfixes and major stability improvements but also some re-worked algorithms which supports way more dense and three-dimensional reverberation processing.

Having just recently discovered your wonderful epicVerb, I can say that this is the best news I've heard in weeks.

Thanks for continuing to enhance this already-great plugin.

[bootsie]

Anyone know if the SynthMaker issue that was closing hosts has been eliminated?

I'm just checking to see if anyone has had better luck with any of Bootsie's latest releases before I start testing them. Tessla 2 caused me so much stress while I was trying to delete it from my projects that I'm afraid to do anything more with any SM plug-ins until it's pretty evident that they are fixed in that area.

Not sure if it is common knowledge already if the prob is solved but some time ago Bootsie released several plugins which are made with a new Synthmaker version which is supposed to solve the prob. I didn't encounter any of those crashes anymore. Check it out.

Shogger

Yeap,
TesslaSE (v1.2.1)
TesslaPRO (v1.0.1)
Density mkII (v2.0.2)
FerricTDS (v1.0.2)
already benefits from the compiler improvements and BootEQ and epicVerb comes next.

I don't see any benefit from a separate dry and wet control. In the Send it's senseless and in the Insert the combined dry/wet does everything within one single knob (except if you "mix by numbers" ).

In the case of reverb I'm a little undecided concerning the preview/render mode but anyway thats not an issue to me for now. v1.5 handles all improvements at roughly similar CPU costs (little increase though).

Will post an audio snippet or so, tomorrow.

peace and thanks for all the appreciation!
bootsy

[ozmoz2008]

Playback: lower quality to hear what you're heading for. Rendering: full quality.

Just thinking out loud: I wonder, why the audio engineer should get the lower quality during mixing, while the consumer will get the full quality.

I can clearly see users fine tuning a parameter for hours, when that particular characteristic changes with the rendering.

Christian

Good post, and it's totally what I think too. You need to hear what you do when mixing.

[zeep]

..I don't see any benefit from a separate dry and wet control. In the Send it's senseless and in the Insert the combined dry/wet does everything within one single knob (except if you "mix by numbers" )..

I'm finding it hard to believe that noone sees the benefits from a separate wet/dry, let alone the fact that i'm asked to explain it's use. I'm sure you can see the benefit in having 2 faders instead of one to control any sound source. Ofcourse in Send it's useless, but i never use sends, only inserts.

Regardless your work is appreciated bootsie.

[A.M. Gold]

Thanks for the updates, Bootsie, I'll give them a try when I feel brave.

Sorry to sound so timid, but the last time I used anything with the earlier
Tessla Pro version in the project it was a serious hassle (not just host crashes, but having to restart my whole machine to get the host to work right again).

[olepro]

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

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