epicVerb 1.5 released

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

epicVerb 1.5 definitely is a considerable improvement over 1.0, amazing as 1.0 already was one of the best reverbs available ITB imho, commercial or free. :love:
Ymmv,
susiwong

Post

susiwong wrote: Ymmv,
susiwong
:hihi:
"a confession without need of absolution, without need of redemption"

Post

dickiefunk wrote:I'm trying to put off going to Windows 7 64 bit as long as possible as I don't want to have to stop using these!!
These plugins won't stop working because you use Win 7 x64...

Post

tongsong wrote:well this reveb doesnt need to trade in a car :lol: too bad chinese gov seems to banned wordpress.com again,but heaven can wait,
:-o
Do you need a direct download link? The files are not on wordpress. Just PM me.
follow me on Image

Post

xx JPRacer xx wrote:
dickiefunk wrote:I'm trying to put off going to Windows 7 64 bit as long as possible as I don't want to have to stop using these!!
These plugins won't stop working because you use Win 7 x64...
Wow that's great news!!

I thought plugins needed to be updated to run on Windows 7 64bit?

Is anyone here using any of Bootsies plugins on Windows 7 64bit? I am hoping to use these with Cubase 5.1.1 64 bit.

Post

Most software issues in x64 are caused by installers, registry entries, paths and so on, none of that applies to Bootsie's plugs, or to any other dll-only plugins fwiw.
The real problems are driver related, that's what you have to investigate before jumping ship.
I'm using Bootsie's plugins on XP64 without the slightest glitch ever.
Ymmv,
susiwong

Asus P5K-E Wifi AP, Q9450 @ 3.2, Thermalright XP120/Papst, 4GB OCZ, 7600GS, HDSPe Digiface, 2 UAD-1 PCI, UAD-2 Quad, Duende PCIe, Antec P-182, Seasonic S500, XP64, C5

Post

susiwong wrote:Most software issues in x64 are caused by installers, registry entries, paths and so on, none of that applies to Bootsie's plugs, or to any other dll-only plugins fwiw.
The real problems are driver related, that's what you have to investigate before jumping ship.
I'm using Bootsie's plugins on XP64 without the slightest glitch ever.
Ymmv,
susiwong

Asus P5K-E Wifi AP, Q9450 @ 3.2, Thermalright XP120/Papst, 4GB OCZ, 7600GS, HDSPe Digiface, 2 UAD-1 PCI, UAD-2 Quad, Duende PCIe, Antec P-182, Seasonic S500, XP64, C5
Superb!! Happy Days!!!!

Post

thx bootsie! PM sent

Post

I downloaded an earlier version the other day - it's really nice, thanks :) I can't seem to find the v1.5 on your site though, am I being a bit stupid?

Post

dickiefunk wrote:
susiwong wrote:Most software issues in x64 are caused by installers, registry entries, paths and so on, none of that applies to Bootsie's plugs, or to any other dll-only plugins fwiw.
The real problems are driver related, that's what you have to investigate before jumping ship.
I'm using Bootsie's plugins on XP64 without the slightest glitch ever.
Ymmv,
susiwong

Asus P5K-E Wifi AP, Q9450 @ 3.2, Thermalright XP120/Papst, 4GB OCZ, 7600GS, HDSPe Digiface, 2 UAD-1 PCI, UAD-2 Quad, Duende PCIe, Antec P-182, Seasonic S500, XP64, C5
Superb!! Happy Days!!!!
Just noticed you're planning to use the 64bit version of Cubase - really ?
The bitbridge in Cubase is rather flaky to put it politely.
If 4Gb project size is enough (it sure is for me, including Superior 2, Jamstix 2, Kontakt with Scarbee bass and a few other instruments, various VSTi and audio tracks in every project) you'll be much better off with the 32bit version of Cubase in a 64bit OS.
I was talking about compatibility in that scenario, not in C5/64 :!:
That I don't know. :shrug:
Cheers,
susiwong

Post

susiwong wrote:Just noticed you're planning to use the 64bit version of Cubase - really ?
The bitbridge in Cubase is rather flaky to put it politely.
If 4Gb project size is enough (it sure is for me, including Superior 2, Jamstix 2, Kontakt with Scarbee bass and a few other instruments, various VSTi and audio tracks in every project) you'll be much better off with the 32bit version of Cubase in a 64bit OS.
I was talking about compatibility in that scenario, not in C5/64 :!:
That I don't know. :shrug:
Cheers,
susiwong
Thanks for the info. I think I'm getting a little confused here :help:

What the difference between using Cubase 5 32bit and 64bit?

Post

dickiefunk wrote:Thanks for the info. I think I'm getting a little confused here :help:

What the difference between using Cubase 5 32bit and 64bit?
In this context all we're talking about is project size regarding RAM, this is not about sound quality.
-- In a 64bit OS, C5/32 can use up to 4GB of RAM per project including all loaded plugins, we're talking 32bit plugins here.
No ill side effects, stable as in a 32bit OS where your project craps out at ca. 1.3 GB (with 2GB installed). There are workarounds (3GB switch) but they are kinda hit'n'miss and are dependent of your hardware, board and expansion cards.
-- C5/64 however can only use 64bit plugins natively, all 32bit plugins are using some unholy kind of wrapper called bitbridge or similar. This is where you don't want to go if at all possible. Classical folks or movie composers with huge sample libraries will benefit from almost unlimited project sizes RAM wise, if you'll get by with up to 4GB (which is a lot as I wrote above) you have nothing to gain by using the 64bit version of Cubase.
-- That said, there's a 3rd party bitbridge called jbridge which is a lot better than Steinberg's own but still not perfect, some VSTi with unusual architecture like Jamstix with its unique MIDI and sync functions don't work reliably in that environment. This is not Ralph's fault.
-- All this is not to be mixed up with 64bit data path precision which will even work in a 32bit OS.
Confusing at first, sure, native 64bit is extremely overhyped atm imho, many folks campaigning for it have not fully understood this subject.
64, that's 32 more, gimme, gimme ! :love: :roll: :wink:
Cheers,
susiwong
Last edited by susiwong on Fri Jan 22, 2010 12:07 pm, edited 1 time in total.

Post

dickiefunk wrote:Thanks for the info. I think I'm getting a little confused here :help:

What the difference between using Cubase 5 32bit and 64bit?
When using a 64 bit host you need 64 bit plugins. You can use 32 bit plugins but you'll need a bridge and the one in Cubase is not very good apparently (I don't really know, I don't use Cubase).

But Windows 7 x64 don't have any problem with 32 bit apps. So you can install the 32 bit version of Cubase on Win 7 x64 and use all your 32 bit plugins with no bridge needed. The only advantage of using 64 bit Cubase is it can use more than 4 gig ram for itself.

But when using a 32 bit app in Win 7 x64 each app can have it's own 4 gig ram to itself. In Win XP 32 you can use ~3 gig ram total for all the applications running. Even if you use only 32 bit apps in Win 7 x64 each apps can use a full 4 gig ram for itself. That's great when multitasking with heavy programs.

ps: I think 32 bit version of Windows can use 4 gig for each process running but when doing this it's using virtual memory (slow) since it can't address more than 4 gig physical ram (but I can be wrong on this).

Post

xx JPRacer xx wrote:When using a 64 bit host you need 64 bit plugins. You can use 32 bit plugins but you'll need a bridge and the one in Cubase is not very good apparently (I don't really know, I don't use Cubase).

But Windows 7 x64 don't have any problem with 32 bit apps. So you can install the 32 bit version of Cubase on Win 7 x64 and use all your 32 bit plugins with no bridge needed. The only advantage of using 64 bit Cubase is it can use more than 4 gig ram for itself.

But when using a 32 bit app in Win 7 x64 each app can have it's own 4 gig ram to itself. In Win XP 32 you can use ~3 gig ram total for all the applications running. Even if you use only 32 bit apps in Win 7 x64 each apps can use a full 4 gig ram for itself. That's great when multitasking with heavy programs.

ps: I think 32 bit version of Windows can use 4 gig for each process running but when doing this it's using virtual memory (slow) since it can't address more than 4 gig physical ram (but I can be wrong on this).
Correct except for the last paragraph, as you yourself noted.
Cheers,
susiwong

Post

bootsie wrote:
Dandruff wrote:
Dandruff wrote:Bootsie,

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


But this problem isn't:
Dandruff wrote: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?
The crashes in Reaper are fixed. I will check about the buffer clearing after rendering ...
Not fixed yet in 1.5! Any ideas?
Last edited by Dandruff on Sat Jan 23, 2010 3:17 am, edited 1 time in total.

Post Reply

Return to “Effects”