AIR Studios Reverb Discussion Thread

[Noeticus]

Apologies for cross posting on both threads but I lost track of where I was asked about insert vs send!

A quick mess around on the clarinet with some of the controls, and I'm also showing the three ways to use this: insert, then pre and post fader send.

When do we get to buy the "Paul Thomson on Clarinet" library?

 

[HotCoffee]

Make sure to switch off the unused signals (they are turned down by default, but are not technically off). And try switching the input to Stereo. That gets best performance for me.

Mine are off by default though (I assume you mean the mixer signals?), are you running the latest version (1.0.5)?

 

[ricoderks]

Holy Smokes!
Quick short samplemodeling/infinite brass contextual test.
I completely turned off the IR's of infinite here so the input was as dry as samplemodeling.

@SpitfireSupport It keeps crashing my daw or komplete kontrol while switching to the different stretch modes. Also there's some weird things going on if you use a stereo input too wide. suddenly a left positioned instrument sounds super right or the opposite of where you placed them in the room.

 

[AudioLoco]

When do we get to buy the "Paul Thomson on Clarinet" library?

"On the Edge of Excitement"

 

[HotCoffee]

Thanks for that. For placement and early reflections, I currently use 17 instances of Berlin Studio. It barely makes a difference on my machine but I know that if I try the same with Pro-R for example, it brings my machine to its knees. Not on a Silicon Mac just yet, still on i9.

Yeah, Peter did a great job optimizing Berlin, that's for sure.

 

[sweeperxx]

It should not be evaluated good and bad with the current optimization problems. The new product will surely have problems. The important thing is how fast they will bring updates for both platforms and make improvements on performance and efficiency. This is more important.

 

[ibanez1]

Gotta say my stones sound really good in there, and yes, my own experiments with other reverbs confirm that having the far mics is really important on a source like this - a bit of distance without too much room information in the sound is key, I think. Might have to get this….

I think anyone who gets this or berlin studio should definitely invest in a depth/diffusion plugin of some kind for close dry recordings.. Proximity is a free plugin and works reasonably for this. Panagement or sp2016 will also work. Roomwidener from jdfactory. Basically it will give you the effect of pushing the sound back a bit so that when it's blended with these reverbs, it sounds more natural. @Joël Dollié has discussed this topic on his YouTube channel.

 

[Loerpert]

Really nice product!
The only thing that would be cool to have is an additional close mic signal (which would basically be the dry input signal, but pannable (maybe based on the position of the instrument in the hall?).

 

[Loerpert]

@SpitfireSupport It keeps crashing my daw or komplete kontrol while switching to the different stretch modes. Also there's some weird things going on if you use a stereo input too wide. suddenly a left positioned instrument sounds super right or the opposite of where you placed them in the room.

@SpitfireSupport
Same here.

Also freezes my DAW every time I try to open it up from the mixer panel after I've placed the reverb on a Bus.

Windows 11
Studio One 6.5
Ryzen 3950X
128gb RAM

Also it takes quite a while to load for me: ~20 seconds. Is that expected?

 

[robgb]

Are you telling me that ALL other reverb makers got cracked this way? Because there is not a single one I can think of who's not offering a trial version.

It'll most likely get cracked anyway. I think not offering a demo is complete bullshit. But I feel that way about sample libraries, too.

 

[Paul Thomson]

Same here.
Windows 11
Studio One 6.5
Ryzen 3950X
128gb RAM

Also it takes quite a while to load for me: ~20 seconds. Is that expected?

Hi - we’ve been able to reproduce this and have a potential fix that we’re currently testing, should be able to push out Monday/Tuesday but we want to have time to test it properly before pushing it!

 

[Loerpert]

Hi - we’ve been able to reproduce this and have a potential fix that we’re currently testing, should be able to push out Monday/Tuesday but we want to have time to test it properly before pushing it!

That's amazing! Fingers crossed . Thanks!

 

[baptiste_palacin]

Until we have something from people who actually know what they are doing (i.e. not me), here are some examples using CSS with the spots and main mics, comparing Berlin Studio with AIR. Both reverbs are using the default settings, and used as sends at -3db pre-fader (track faders are set to -6db). In Berlin Studio, the source fader is muted. For AIR, I used the Solo "section" presets (e.g. one reverb per section), and tweaked the Solo Violin for Violins II a bit, in terms of position.

CSS spot mics:

Dry
View attachment sm_dry.mp3
Reverb A
View attachment sm_berlin_studio.mp3
Reverb B
View attachment sm_air_sections.mp3

CSS main mic:

Dry
View attachment main_dry.mp3
Reverb A
View attachment main_berlin_studio.mp3
Reverb B
View attachment main_air_sections.mp3

Do note that this is out-of-the-box sounds from each reverb. I have not tweaked them one bit other than what's mentioned above.

So which reverb do you prefer?

Spoiler

A = Berlin Studio
B = AIR Studios Reverb

Important note: The AIR presets have internal (patch) EQ applied, Berlin Studio does not.

Just for fun, I did a quick test with the stock Air reverb from Protools vs Air Studio Reverb vs Berlin Studio+ProQ3.

Reverb 1:
View attachment Reverb 1.wav
Reverb 2:
View attachment Reverb 2.wav
Reverb 3:
View attachment Reverb 3.wav

Spoiler

Reverb 1=AIR Studios Reverb
Reverb 2=AIR Reverb (not Spitfire)
Reverb 3=Berlin Studio+ProQ3

For AIR Studios Reverb, I recorded into Protools the Reverb B posted by @HotCoffee
For AIR Reverb (not Spitfire), I recorded into Protools the Dry version and added the plug-in after with this preset:




For Berlin Studio, I recorded into Protools the Reverb A and added ProQ3 with this preset:

 

[GoatTheWise]

Can we hear some demos using VWinds? I wanna get AIR Reverb to use with Sample and Audio Modeling instruments, wich are recorded very dry, like VWinds, I presume. I'd also love to hear how it sounds agains SSW if possible. I have very high expectations for it!

Hi, yes sure, I just did a this short test flute-piano improvised.
It is not a deep test, I improvised the SSO Flute first, then copied to VWinds Flute with custom parameters and redid the midi programming again (using a TEC Breath controller 2), then added the piano because I was kind of inspired.

I let the piano at the end be itself because I wanted to study how well it sounded with AIR Reverb.
The piano is the exceptionally magnificent CFX Concert Grand from Garritan, with only the close mic of the contemporary default recording.

Enjoy!

I did touched quite a lot AIR reverb to obtain a better result than the default patch I must admit! If you want I can describe all modified parameters for both flutes and the reverbs.

EDIT: for me, it sounds that SSW in general is better as woodwinds section, through doublings. VWinds is better at solo, but even then, I use them with custom settings as a section because of their expressivity which is unparalleled. Now we have AIR Reverb? Goodbye SSW Pro.

 

[hsindermann]

Just for fun, I did a quick test with the stock Air reverb from Protools vs Air Studio Reverb vs Berlin Studio+ProQ3.

Reverb 1:
View attachment Reverb 1.wav
Reverb 2:
View attachment Reverb 2.wav
Reverb 3:
View attachment Reverb 3.wav

Spoiler

Reverb 1=AIR Studios Reverb
Reverb 2=AIR Reverb (not Spitfire)
Reverb 3=Berlin Studio+ProQ3

For AIR Studios Reverb, I recorded into Protools the Reverb B posted by @HotCoffee
For AIR Reverb (not Spitfire), I recorded into Protools the Dry version and added the plug-in after with this preset:




For Berlin Studio, I recorded into Protools the Reverb A and added ProQ3 with this preset:

Interesting, I can barely make out a difference between 1 & 2.

 

[GoatTheWise]

Interesting, I can barely make out a difference between 1 & 2.

To me, the 2nd one sounds like it has more high frequencies than 1 and 3. That lush sound.
But I prefer 3 for this specific type of music. More "clean" to me.

Overall, AIR Reverb seems to be perfect if you want to have that British vibe out of chamber ensembles. For symphonic I don't know.

 

[clisma]

Holy Smokes!
Quick short samplemodeling/infinite brass contextual test.
I completely turned off the IR's of infinite here so the input was as dry as samplemodeling.

@SpitfireSupport It keeps crashing my daw or komplete kontrol while switching to the different stretch modes. Also there's some weird things going on if you use a stereo input too wide. suddenly a left positioned instrument sounds super right or the opposite of where you placed them in the room.

Yeah, THIS sounds great. When evaluating this, I completely forgot about SM Brass.

 

[StMichaels]

Something I'm not sure I get because there's no demo to try... Can this be used as a bus reverb? Can you set up sends to each microphone position? And what about positioning? If the verb is on a bus, the positioning feature is kind of pointless, isn't it?

I actually have no issue with putting it on every track, if that's necessary. These arm processors can handle quite a bit, but, like most people, I would prefer a bus/send situation.

So could anyone who has bought the plugin explain it for me?

I have the exact same questions as @robgb.

If anyone using this can be so kind to answer these questions based on using this product it would be much appreciated

 

[Jrides]

Just for fun, I did a quick test with the stock Air reverb from Protools vs Air Studio Reverb vs Berlin Studio+ProQ3.

Reverb 1:
View attachment Reverb 1.wav
Reverb 2:
View attachment Reverb 2.wav
Reverb 3:
View attachment Reverb 3.wav

Spoiler

Reverb 1=AIR Studios Reverb
Reverb 2=AIR Reverb (not Spitfire)
Reverb 3=Berlin Studio+ProQ3

For AIR Studios Reverb, I recorded into Protools the Reverb B posted by @HotCoffee
For AIR Reverb (not Spitfire), I recorded into Protools the Dry version and added the plug-in after with this preset:




For Berlin Studio, I recorded into Protools the Reverb A and added ProQ3 with this preset:

So you are saying I have to get ProTools now? This is getting really expensive. I think I’m going to eventually stop paying attention to this thread. SMH.

 

[jvms]

Hi, yes sure, I just did a this short test flute-piano improvised.
It is not a deep test, I improvised the SSO Flute first, then copied to VWinds Flute with custom parameters and redid the midi programming again (using a TEC Breath controller 2), then added the piano because I was kind of inspired.

I let the piano at the end be itself because I wanted to study how well it sounded with AIR Reverb.
The piano is the exceptionally magnificent CFX Concert Grand from Garritan, with only the close mic of the contemporary default recording.

Enjoy!

I did touched quite a lot AIR reverb to obtain a better result than the default patch I must admit! If you want I can describe all modified parameters for both flutes and the reverbs.

EDIT: for me, it sounds that SSW in general is better as woodwinds section, through doublings. VWinds is better at solo, but even then, I use them with custom settings as a section because of their expressivity which is unparalleled. Now we have AIR Reverb? Goodbye SSW Pro.

My god, VWinds sound absolutey magnificent, holy fucking shit! Thank you so much for the demo!