AriesVerb - Still Under Development

[Christian Schüler]

https://soundcloud.com/metalifuxx/a-tec ... c-creation

Back when it was an early alpha or beta, I used the " Temple" preset for the reverb on most the instruments in this track. Maybe all of them possibly. The previous or next reverb type preset from that might have also been used IIRC.

Nice! The alpha would have been much more grainy than this, so you in all likelihood you used the beta. The soundcloud page says it's 5 years ago which was when 0.7.6 was current.

[Christian Schüler]

This is indeed awesome news. Too bad this was one of my last "secret weapons" that almost nobody knew of. It's a ridiculously good sounding plugin and very fun to experiment with!

There never is security in obscurity. That is a programmer wisdom.

[mcbpete]

Really can't decide between this and Exponential Audio's Excalibur ( Link/Description ) ... HEEELLLPPP!

(Or am I just being lazy and can recreate either in MXXX and/or Mux Modular ?)

[Christian Schüler]

Totally depends on what you want to do!
AriesVerb can be described as an "algorithmic impulse response", due to the flexibility of its FDN. Long settings usually result in a reverb or delay. Very short settings result in a body resonance or make it like a filter. If you add modulation you get chorusing and flanging. If you add non-linearity you get weird stuff.

So, when it says "multi-fx", it does not mean that it comes loaded with an array of pre-built fx "modules", but rather that it can be shaped into being many different kinds of fx. Did this make sense?

EDIT: I recommend you browse the presets and see if there are things for you. Most people who bought AriesVerb have discovered for themselves some kind of "killer-application" for which they use it.

[sfxsound3]

Excalibur.

No you can't.

[mcbpete]

Totally depends on what you want to do!
EDIT: I recommend you browse the presets and see if there are things for you. Most people who bought AriesVerb have discovered for themselves some kind of "killer-application" for which they use it.

Having demo'd both I've come to the conclusion .... I think (maybe!) I need both ! On yours: Having decay times in micro seconds, and a really large half life leads to absolutely wild sounds - That combined with the waveshaping is leading to some absolutely horrific noises. In a good way

[Christian Schüler]

Having demo'd both I've come to the conclusion .... I think (maybe!) I need both ! On yours: Having decay times in micro seconds, and a really large half life leads to absolutely wild sounds - That combined with the waveshaping is leading to some absolutely horrific noises. In a good way

Thank you.

[stillshaded]

So happy this has been updated. It really is an unbelieveble sounding plugin. I've used the lexicon natives and Valhalla room but Ariesverb is still my favorite.

There is one small feature that's would really improve my workflow, and that is the ability to lock the wet and dry amount while choosing presets. Not sure how hard this would be to pull off, but as it is now, I have to readjust both the wet and dry volumes every time I switch presets.

Also being able to automate wet and dry amounts would get a fair amount of use.

[mcbpete]

Also being able to automate wet and dry amounts would get a fair amount of use.

Woah good shout - just tried mapping this to Ableton macro controls ... Is this just a demo restriction or can you not automate *any* of the parameters? That's a real big issue for me if that's the case

[Lesha]

Also being able to automate wet and dry amounts would get a fair amount of use.

Woah good shout - just tried mapping this to Ableton macro controls ... Is this just a demo restriction or can you not automate *any* of the parameters? That's a real big issue for me if that's the case

Just chiming in to say that the old free alpha version can be automated in Ableton, and can be mapped to macro controls.

[mcbpete]

Ah cool thanks, how far back do you have to go version-wise? Just searched the Ariescode KVR support forum and it looks like automation has been coming since at least 2010 !

http://www.kvraudio.com/forum/viewtopic ... 3#p4123633

Hi Echoes,

yes, a switch for wet and dry settings is on my list!

Please stay tuned.
Ariesverb development was halted due to me doing contracting work. But it's resumed again.

The next version will have AU compatibility, automation and an integrated save feature.

[Lesha]

Ah cool thanks, how far back do you have to go version-wise? Just searched the Ariescode KVR support forum and it looks like automation has been coming since at least 2010 !

I have 0.4a, I don't know if there were free versions later.

[Christian Schüler]

Alright, that's three questions in a row so I'll to my very best

So happy this has been updated. It really is an unbelieveble sounding plugin. I've used the lexicon natives and Valhalla room but Ariesverb is still my favorite.

Thank you!

There is one small feature that's would really improve my workflow, and that is the ability to lock the wet and dry amount while choosing presets. Not sure how hard this would be to pull off …

Not hard at all. The devil is in the details. There are many programs for which the dry-to-wet ratio is an integral part of the effect. One example would be the program /Modulation/PWM-alzyer and derivatives thereof. This is a relatively simple program that imitates the trademark sound of pulse width modulation by subtracting a delayed version of the input from itself. For this to work, the dry and wet amount must be equal so that cancellation can occur. What would happen if there was some form of dry/wet locking enabled and you browsed through the program library onto the PWM-alyzer? Exactly what you think it would, a corruption of the intended effect.

Another example are the programs in the natural reverberation category. These are imitations of real impulse responses and formally are 100% wet. But they do not sound as if they are 100% wet because as a real impulse would, they already contain the direct signal from source to listener correctly delayed for the path distance. As it currently stands, if you were to add an additional dry amount to that with the dry slider, you'd get phasing since the dry signal is undelayed.

So to summarize, there is no magic bullet for the dry/wet topic yet. If your host provides an extra dry/wet control in the FX chain that you can apply on top of any effect (for example, Reaper has it and I think FL studio has it as well), you might want to use that. Of course AriesVerb could duplicate this functionality and provide internal (per effect) and external (front panel) dry/wet controls if the demand is there.

Also being able to automate wet and dry amounts would get a fair amount of use.

Woah good shout - just tried mapping this to Ableton macro controls ... Is this just a demo restriction or can you not automate *any* of the parameters? That's a real big issue for me if that's the case

Parameter automation is not implemented yet at all, and that's one reason the product is still labelled as beta, since any "one-point-oh" worth this designation would have to have automation! It is the #1 requested feature by far, with AU conversion being the runner-up (see also earlier in this thread).

Again the devil is in the details. People can be divided roughly into two camps:

• Camp 1: "I want the control, just give me ALL the parameters, please!"
• Camp 2: "The plugin is already so complicated, make some simple macro controls please!" (alternatively: "I just want to have the possibilities back that the alpha version had. I don't need fancier!")

Let's look at an example. The alpha version of AriesVerb had two parameters that are labelled "input rotation" and "output rotation", which lets you rotate all 4 input or output vectors synchronously with a single parameter. To get the same effect when the individual parameters are exposed, you would have to manually automate 4 parameters in lockstep.

So again it looks like there will be no magic bullet to satisfy both camps. Therefore, I have decided to introduce parameter automation incrementally, steered by user feedback. The next update is going have a first batch of automation parameters, likely the front panel parameters and the most uncontroversial internal ones.

Ah cool thanks, how far back do you have to go version-wise? Just searched the Ariescode KVR support forum and it looks like automation has been coming since at least 2010 !

I have 0.4a, I don't know if there were free versions later.

The version 0.4a is the last of the free alpha versions. Since there was no GUI, its parameters are trivially automatable as a side effect of the host managing them, but the plugin is not designed with this in mind and parameter changes are not de-zippered nicely. You can get it from here: http://ariescode.com/ariesverb-archive.

Versions 0.5 and 0.6 were non-public betas. Version 0.7 was the first public release after the 'great leap'

[mcbpete]

I have decided to introduce parameter automation incrementally, steered by user feedback. The next update is going have a first batch of automation parameters, likely the front panel parameters

I don't think we need any fancy things added to the GUI - Just that the parameters, like *any* parameter! - be made visible to the DAW so we can midi-map things, automate things etc.

Like I mention above you said 'the next version' would have automation back 8 years ago so just wondering quite how incrementally we might see these parameters getting added

I can't say as I can think of any effect VST - especially one over 100 dollars - that doesn't allow DAW automation of some kind !

[HunterKiller]

This is indeed awesome news. Too bad this was one of my last "secret weapons" that almost nobody knew of. It's a ridiculously good sounding plugin and very fun to experiment with!

I knew of it and have been using it since day one, on many things.