2C-Aether Reverb

[mellotronaut]

don't wanna annoy you, Andrew, but the cross platform thingie isn't clear for me yet. I'm about to prepare my macbook to take over for a while and i have no probs to pay a crossgrade, but i'd like to know what, when and how.

thanks

mellochris

[jensa]

We are investigating ways to minimize this more in future updates. We are also hoping to allow more parameters to be automated at fast rates without artifacts. Doing so may result in higher CPU usage however, so we must find a balance.

Or just do it like for example Native Instruments' Massive where you choose between 3 different CPU 'strain' modes. I would love to be able to use fast rates at automation and maybe bounce the live track to disk before shutting off the plugin to save cycles.

[Blackinfinity]

thanks guys.

The nature of the algorithm (and really most reverbs in general) result in some "discontinuities" when changing some parameters. This can result in a click or a pop for some parameters. This would barely be noticeable except for the fact that these click/pops are fed into the reverb engine, and so they can act like feeding an impulse (delta function) (single sample spike) into the reverb, and depending on the preset, this can translate to a fairly long decay.

We are investigating ways to minimize this more in future updates. We are also hoping to allow more parameters to be automated at fast rates without artifacts. Doing so may result in higher CPU usage however, so we must find a balance.

We do hope to offer various improvements to controller surfaces, MIDI controllers, mouse wheels, etc... We will provide more information as we are closer to completion of the 1.1 update.

Thanks for your reply, yeah I understand what you are talking about, to program this kind of software of this quality is certainly not easy. But what it is even better is that you are still improving the software, I really looking forward to the midi functions.

This reverb have a really promising future I think, and as I said before, I hope that within 1-2 years that it will compete with the Hardware reverb units on the market.

As I have said earlier, I think it would be a good solution if the user himself could decide the cpu usuage the quality of the reverb. Myself with my Core I7 (overclocked) have plenty of free CPU power, which is waiting to be used, it would be interesting to see the posibillties if this type of software would take full advantage of my I7.

Anyways thanks for filling the void on the market, I have tried really most reverbs that has been mentioned, for instance Arts Acoustica that so many people talked about, I can't really understand what they found good about this reverb, Aether is 1000 times better. I am still little bit interested to try Sanford Reverb, but it does not seem to work with Vista 64 bit.

[Andrew Souter]

don't wanna annoy you, Andrew, but the cross platform thingie isn't clear for me yet. I'm about to prepare my macbook to take over for a while and i have no probs to pay a crossgrade, but i'd like to know what, when and how.

thanks

mellochris

please send an email request to info [ a t ] 2caudio.com

[mellotronaut]

don't wanna annoy you, Andrew, but the cross platform thingie isn't clear for me yet. I'm about to prepare my macbook to take over for a while and i have no probs to pay a crossgrade, but i'd like to know what, when and how.

thanks

mellochris

please send an email request to info [ a t ] 2caudio.com

thank you very much!

[visa tapani]

I would also wish it did work better for real-time usage, sometimes when you change certain knobs you get certain unwanted digital noise sounds.

+1

This is also my biggest problem with Aether. I'm happy to hear that you guys at 2c/Galbanum are considering this issue.

It's true that it's a problem with most reverbs, but Aether seems to respond especially poorly to automation. The list of parameters that can't be automated according to the manual is very long indeed:

ER Position
ER Shape
ER Size
ER Space
ER Space
LR Mod Depth
LR Mod Period
LR Pre Delay
LR Shape
LR Size
LR Spread
LR Stereo Mode
LR Width

True enough, all of these cause severe glitching when changed during playback. But that list is not even exhaustive - I've noticed that also all of the following parameters can cause artefacts when changed/automated during playback:

ER Color
ER HF Soft
ER Width
LR Sustain
LR Reverb Time
IN EQ Frequencies
IN EQ filter Qs/Slopes
IN EQ filter gain
LR Decay Crossovers
LR Decay Qs
LR Decay Ratios

I understand that some of the parameters are probably very difficult to program to change silently. However, it's surprising that for instance all of the EQ parameters, ER Color and HF Soft and MOD depth/period also cause zipper noises when changed.

Anyway, I'm just rambling on - as I said I'm happy that you're investigating the matter. Since Aether has such grand potential for sound design and other more demanding reverb applications, I think it would be a huge asset for it if it could be better automated. Automatable Aether would be a huge monster effect with a vast sonic range - imagine modulating it with LFOs, (ADSR) envelopes, envelope followers etc...

[A.M. Gold]

I have a minor bug report: preset names don't load in saved instances of Aether (I am using the purchased version, not the demo) in Tracktion 2. If I start Tracktion, then open a project in which Aether has been saved, it will load all the settings but just say "untitled", even if it was an unedited Aether preset that was saved with the project. If I load a new preset in, it will show the title, but then if I close that project and open another one in which Aether is saved, it will still show the title of the previous preset from the previous project, even if it loaded a different preset when opening the second project.

I'm using 1.0.0

BTW---very nice reverb. I think it does the "convolution" type thing (i.e. simulating real acoustic spaces) better than most convolution reverbs I've heard. CPU is high but, unlike a convolution effect, it doesn't introduce noticeable latency.

[A.M. Gold]

In short words: Aether is fatter than Redline to my ears.

I really like both and I think the compliment each other. Redline sounds more like good hardware and, at least in the ways I've used it so far, Aether sounds more like real acoustic reverberation.

[A.M. Gold]

My suggestion is that if you are on the fence with these 2, go ahead and join the Aether GB, and then sign up for the Redline 60 day evaluation license. Redline will always be this cheap, Aether will not.

Redline goes up in price after June 15th to $149 (but yea, that is still $200 less than Aether will eventually be).

[elxsound]

My suggestion is that if you are on the fence with these 2, go ahead and join the Aether GB, and then sign up for the Redline 60 day evaluation license. Redline will always be this cheap, Aether will not.

Redline goes up in price after June 15th to $149 (but yea, that is still $200 less than Aether will eventually be).

Actually, the GB is already done, so back to $249 until it goes up to $349.

After purchasing this and really getting to know Aether, even $249 is a good deal. Very, very nice.

I have plans to purchase Redline, but I'm getting less and less interested in that, the more I play with Aether. I'm also curious to see what the 1.1 update will bring. By then, I may change my mind completely on Redline, but we'll see.

[jensa]

I have a minor bug report: preset names don't load in saved instances of Aether (I am using the purchased version, not the demo) in Tracktion 2. If I start Tracktion, then open a project in which Aether has been saved, it will load all the settings but just say "untitled", even if it was an unedited Aether preset that was saved with the project. If I load a new preset in, it will show the title, but then if I close that project and open another one in which Aether is saved, it will still show the title of the previous preset from the previous project, even if it loaded a different preset when opening the second project.

I'm using 1.0.0

I can confirm the same bug. I'm using Reaper.

[Breeze]

This is for you Galbanum,

Is there any plans to make it possible to control the knobs via midi interface in the future ?

I would also wish it did work better for real-time usage, sometimes when you change certain knobs you get certain unwanted digital noise sounds.
I work mainly with big long reverbs, my work flow when I record music is mostly in real-time, and I wish to be able to form the reverb
more in real-time.

I hope this will be implanted in the future, and thanks again for creating this software.

I was thinking about this last night and its really quite a revolutionary idea! I'm aware of 2C's response to this. It would really be something evolutionary to be able to manipulate reverb parameters in real time, allowing things like space morphing.

But compute requirements of this would be extraordinary, much greater than a simple reverb because what would be required is no less than a off-line high-speed rendering of what the input signal would have created with the altered parameters and a smooth morphing of that result with the current results. In essence you'd have to quick travel into the past and fast forward to the current state and transition smoothly from one to the other.

The fundamental change in paradigm is that you'd go from a black box you drop things into to a transparent box you completely control. Keep those cores coming

But in the meantime, something like that would be possible by simply crossfading of acoustic space; you could kind of do that by using several instances of Aether and crossfading from one to another. Technically 2C could do something like that by muting the current input and feeding a second engine with the new parameters, but your compute goes up for every engine instance.

But the idea of an organic glitchless real-time controllable reverb: brilliant!

[Sequent]

As a start, you could also consider something like what the Flux plugins have - the morphing slider at the bottom center. This would be an 'easy' thing, I think, because it would essentially be like having two engines running internally? You come up with two settings that you like and then can morph between them in real time. Not as detailed as what people are talking about here, but maybe a good start. GRM Tools had that years ago.

[PaulSC]

But compute requirements of this would be extraordinary, much greater than a simple reverb because what would be required is no less than a off-line high-speed rendering of what the impulse would have created with the altered parameters and a smooth morphing of that result with the current results. In essence you'd have to quick travel into the past and fast forward to the current state and transition smoothly from one to the other.

Aether is not a convolution reverb; it doesn't use impulse responses (which makes its realism all the more impressive).

[Breeze]

But compute requirements of this would be extraordinary, much greater than a simple reverb because what would be required is no less than a off-line high-speed rendering of what the impulse would have created with the altered parameters and a smooth morphing of that result with the current results. In essence you'd have to quick travel into the past and fast forward to the current state and transition smoothly from one to the other.

Aether is not a convolution reverb; it doesn't use impulse responses (which makes its realism all the more impressive).

By "impulse" I was referring to whatever you feed into the reverb,-ie: the reverb input signal. I know it isn't convo Maybe a bad choice of words - will rephrase, thanks!