2C-Aether Reverb
-
- KVRer
- 15 posts since 30 Dec, 2008
Group buy! Group buy! Group buy!Galbanum wrote:You may try reducing the Width control of the ER and/or the LR section. You may try the same for Cross.Jay-Producer wrote: I did that but it still eats away my sounds. It really is a great reverb but it just drowns sounds too much. More suited for ambiance and trance riffs.
You may also try to reduce the LR gain on the particular preset. Or shorten the Time control. Or Decrease Spread. Or Decrease Sustain. Or try a more aggressive Freq decay profile that leaves some Freq space in your critical band.
...Also it sounds like you think "pre-delay" means adding a 3rd party delay FX to the sound before Aether?? (sorry if i misread you here.) That is not what PreDelay means here. PreDealy is a control above the time knob. This inserts additional time delay between your "bone dry sound" and the LR engine of Aether. This allows the attacks of your sound to be more dry basically....
- KVRist
- 352 posts since 15 Jan, 2009 from a skyrocket in flight...
http://www.kvraudio.com/forum/viewtopic ... 70#3528070rsantiago wrote:
Group buy! Group buy! Group buy!
-
- KVRist
- 299 posts since 15 Apr, 2004
This is a nice sounding reverb, I especially like the sound of the ER's.
Edit:
The problems I had as a send was due to I had two instances loaded at the same time. (the demo does not allow that
)
//L
Edit:
The problems I had as a send was due to I had two instances loaded at the same time. (the demo does not allow that
//L
Last edited by lazerkind on Tue Apr 14, 2009 6:59 am, edited 1 time in total.
-
- KVRian
- 619 posts since 15 Feb, 2004 from Birmingham, UK
Is there an academic/educational discount for Aether?
-
- KVRian
- 1035 posts since 4 Jan, 2005 from Traun Austria
I first thought I will join the group buy, but I did some CPU tests.
This Reverb take 7- 12 % on my AMD 3800+ dualcore.
Thats to heavy for me ! A real CPU Bomb
My main reverbs to compare:
Art Acoustics reverb 3,5 -5 %
2016 princeton 1,8 %
CSR reverb 2 - 3,6 %
This Reverb take 7- 12 % on my AMD 3800+ dualcore.
Thats to heavy for me ! A real CPU Bomb
My main reverbs to compare:
Art Acoustics reverb 3,5 -5 %
2016 princeton 1,8 %
CSR reverb 2 - 3,6 %
-
- KVRAF
- 5200 posts since 17 Aug, 2004
So what? Aether does use a lot CPU but it is sounding very different. You don't need 12 reverbs in project anyway. You can not have quality without some cost. That said i am not saying that more cpu is better quality but sometimes this can be indeed reason.echopark wrote:I first thought I will join the group buy, but I did some CPU tests.
This Reverb take 7- 12 % on my AMD 3800+ dualcore.
Thats to heavy for me ! A real CPU Bomb
My main reverbs to compare:
Art Acoustics reverb 3,5 -5 %
2016 princeton 1,8 %
CSR reverb 2 - 3,6 %
-
- KVRAF
- 1895 posts since 13 Oct, 2002
Does anyone know what the licensing terms for Aether are? I can't seem to find it. I have both a Mac and a PC in my studio and I'd like to run it on both: will one license allow me to run it on both?
TIA
TIA
-
- KVRAF
- 1895 posts since 13 Oct, 2002
...and does anyone know where I should submit a bug report? When I first load up Aether in Nuendo 4, the ENTIRE screen turns black, and a moment later the screen comes back but the plugin window only shows the round composite meter on a black background for a few seconds before the GUI finally appears.
-
- Banned
- 4072 posts since 7 Nov, 2007
This reverb reminds me a lot of KR Space, the concepts are similar, the sound is similar, and both verbs seem to be buggy.
I'm kind of sorry to be so critical of this software. I'm an avid user/owner of the architecture wave forms for Rapture. I most likely would have purchased any original, properly priced, well tested, and quality software from this company.
dissapointed...
sorry...
I'm kind of sorry to be so critical of this software. I'm an avid user/owner of the architecture wave forms for Rapture. I most likely would have purchased any original, properly priced, well tested, and quality software from this company.
dissapointed...
sorry...
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
Actually, you can. But every reverb is different, and CPU usage doesn't equal quality on either end. But there are a few great reverbs with a very low CPU footprint.kmonkey wrote:You can not have quality without some cost.
Brent
My host is better than your host
-
- KVRian
- 1119 posts since 29 Jun, 2004 from within you without you
Same problem here in REAPER. Ouch.Breeze wrote:...and does anyone know where I should submit a bug report? When I first load up Aether in Nuendo 4, the ENTIRE screen turns black, and a moment later the screen comes back but the plugin window only shows the round composite meter on a black background for a few seconds before the GUI finally appears.
Another bug - erratic mousewheel behavior. It never affects the dial I'm on even if I click on it. It dials a knob to the lower right somewhere.
Sorry. For this high cost it should be flawless.
-
- KVRist
- 299 posts since 15 Apr, 2004
Well, I hope you reported any problems to the devs?JeffSanders wrote:Same problem here in REAPER. Ouch.Breeze wrote:...and does anyone know where I should submit a bug report? When I first load up Aether in Nuendo 4, the ENTIRE screen turns black, and a moment later the screen comes back but the plugin window only shows the round composite meter on a black background for a few seconds before the GUI finally appears.
Another bug - erratic mousewheel behavior. It never affects the dial I'm on even if I click on it. It dials a knob to the lower right somewhere.
Sorry. For this high cost it should be flawless.
(There is a contact form in the galbanum shop. The 2CAudio web site is still a bit shaky)
It does take a second or two to load on my computers. But so does Ohmicide and that does not stop me from liking it.
Other than that I had no issues on either my laptop, main Daw or the ugly web machine I'm writing from now. All Reaper 2.5x, Win XP Pro SP2, AMD/intel, 1-3Gb Ram.
//L
-
- KVRian
- 1119 posts since 29 Jun, 2004 from within you without you
It does take a few seconds to load. Then, it annihilates my PC for a second with a crazy black death screen before it loads.
- KVRAF
- 2621 posts since 12 Sep, 2008
Thanks for the comments guys. I will make a few comments:
1) Load Time: load time is on the "long-ish" side of things on the first instance only. Loading the first instance can take around 10 sec for the large skin, and slightly more than 5 for the small skin. This is normal, and seemingly a bit of a trend when I compare to other new releases from various companies. Load time is long-ish b/c there are lots of GUI resources, and some other things we must load into RAM. The good news is once one instance is loaded, all other instances load instantly. You can not see this is the demo though, b/c you are limited to one instance.
2) CPU Usage: We feel that we offer a good balance between quality and CPU usage. I can easily get 90-100 instances on an 2008 8 Core Mac Pro. YMMV on older systems. In my personal music production I rarely use more than 4-8 different reverbs in a project. You may reduce CPU usage by running in Mono-Stereo mode for the Late Reflection engine. You may also disable ER and LR sections independently. In the future we may offer versions which are both lighter, and heavier on the CPU to meet the needs of various users...
3) Licensing is "single user". If you personally as a "single user" need to use more than one computer, that is not a problem.
4) GUI drawing issue: (i.e. black screen on first load--confined to the GUI window--not the entire computer screen). First, we had read all the reports of this and we are fervently investigating to try to find the cause and a solution. Second, to clarify, it is our current understanding that this is only a cosmetic issue that does not effect the audio/processing in any way. Oddly this issue seems more prevalent in the demo versions. We are exploring this. It should be noted that, while this bug may look extreme b/c if effects the GUI, it does not mean the processing/DSP code is effected. We assume this to be a simple fix once we identify the cause.
5) RE Bugs in software in general... ...well if they did not exist, no application would ever make it past the 1.0 version, right? Of course we test things, first internally, then in beta, then we even had a pre-release phase for this product. But now we have pretty high visibility and thousands of demo downloads, so it is only inevitable that some unknown will arise on some system/OS/Host combo. We did not see these things previously, but now that we are aware of them, you can be certain we are working to resolve them ASAP.
Thanks for the feedback. We appreciate it.
1) Load Time: load time is on the "long-ish" side of things on the first instance only. Loading the first instance can take around 10 sec for the large skin, and slightly more than 5 for the small skin. This is normal, and seemingly a bit of a trend when I compare to other new releases from various companies. Load time is long-ish b/c there are lots of GUI resources, and some other things we must load into RAM. The good news is once one instance is loaded, all other instances load instantly. You can not see this is the demo though, b/c you are limited to one instance.
2) CPU Usage: We feel that we offer a good balance between quality and CPU usage. I can easily get 90-100 instances on an 2008 8 Core Mac Pro. YMMV on older systems. In my personal music production I rarely use more than 4-8 different reverbs in a project. You may reduce CPU usage by running in Mono-Stereo mode for the Late Reflection engine. You may also disable ER and LR sections independently. In the future we may offer versions which are both lighter, and heavier on the CPU to meet the needs of various users...
3) Licensing is "single user". If you personally as a "single user" need to use more than one computer, that is not a problem.
4) GUI drawing issue: (i.e. black screen on first load--confined to the GUI window--not the entire computer screen). First, we had read all the reports of this and we are fervently investigating to try to find the cause and a solution. Second, to clarify, it is our current understanding that this is only a cosmetic issue that does not effect the audio/processing in any way. Oddly this issue seems more prevalent in the demo versions. We are exploring this. It should be noted that, while this bug may look extreme b/c if effects the GUI, it does not mean the processing/DSP code is effected. We assume this to be a simple fix once we identify the cause.
5) RE Bugs in software in general... ...well if they did not exist, no application would ever make it past the 1.0 version, right? Of course we test things, first internally, then in beta, then we even had a pre-release phase for this product. But now we have pretty high visibility and thousands of demo downloads, so it is only inevitable that some unknown will arise on some system/OS/Host combo. We did not see these things previously, but now that we are aware of them, you can be certain we are working to resolve them ASAP.
Thanks for the feedback. We appreciate it.
