AIR Studios Reverb Discussion Thread

[pegotico]

It's true, I recorded myself farting into it and I got shortlisted for the Grammys

You need to practice a little bit more getting the legatos out. Sure that will get you nominated for next year grammy awards...

 

[SamTheAudiocrat]

You need to practice a little bit more getting the legatos out. Sure that will get you nominated for next year grammy awards...

He has to work on EQ. He has to scoop out a lot of the bottom end...

 

[Henrik B. Jensen]

If the sound is too quiet, he can add Oxford Inflator!

 

[alcorey]

Most importantly, after utilizing all of the above techniques and resources he'll have to finish up with a little Oeksound Soothe

 

[Petrucci]

Most importantly, after utilizing all of the above techniques and resources he'll have to finish up with a little Oeksound Soothe

To clean out... those nasty resonances)))

 

[clisma]

Really people? Fart jokes? You are letting all the Air out of this thread.

 

[Henrik B. Jensen]

The air is getting kinda stale by now

 

[galactic orange]

On the contrary, this thread needs a second wind.

 

[pegotico]

Really people? Fart jokes? You are letting all the Air out of this thread.

You can always use some compression.... a little bit dangerous though

 

[Petrucci]

You can always use some compression.... a little bit dangerous though

Yeah.. careful with that threshold..

 

[MusicMinor]

Does anyone here swear by the Pro version of this reverb versus the Essential version? I have been using the essential version for a while now and think it’s great, just wondering what I’m missing, as I have no desire to upgrade, which is rare for me

 

[Raphioli]

Noticed that the thread had a lot of new posts. Thought the plugin got a new feature or update.
But I didn't expect to see a page full with fart jokes lol

 

[Allen Constantine]

Does anyone here swear by the Pro version of this reverb versus the Essential version? I have been using the essential version for a while now and think it’s great, just wondering what I’m missing, as I have no desire to upgrade, which is rare for me

With the Pro version you get a lot of control in shaping the reverb. The essential version is good if you don’t plan to get into details.

 

[holywilly]

We bought AIR studio reverb to mix our current film scores and it works very well with live instruments, the only downside is the plugin does not support surround channels, yet.

 

[James Brecknell]

I've just done some basic testing, but I have not noticed any improvements regarding CPU usage. Now that some more (all?) critical bugs are out of the way, perhaps they will focus on that.

It seems not all critical bugs are out of the way. Was it believed that preset recalling was fixed?

The Known Issues page at https://spitfireaudio.zendesk.com/h...sues-and-Support-Guide-for-AIR-Studios-Reverb only goes up to v1.1.2. It acknowledges a known issue as "Custom user presets recall Mixer, EQ, Mono/Stereo, Pre-Delay, Output incorrectly. Parameters get inherited from previously loaded preset."

We're now on v1.214-e4ed537, but there's no Release Notes update for it, and the custom preset recall problem still exists. There's slightly more parameters it affects than what the v1.1.2 note acknowledges, and for the two DAWs I use - Cubase and Reason - the problem is different depending on the DAW and how the preset is used. And it's intriguing that the problems are virtually the opposite in each case.

In Cubase 13, when a saved user preset is saved in a project, I find that it recalls correctly when the project is reopened. In Reason it is not.

In Cubase, I find a saved user preset doesn't recall correctly when loaded into a project. In Reason, it does.

In Cubase, I find if you change the reverb settings and don't save the changes as a preset, the settings are properly saved and recalled when you save the project and reopen it. In Reason, they are not.

The opposite discoveries between Cubase and Reason were confusing to work out, so I hope I've got that right without having to go back through everything again, but I'd be curious to know what other people are experiencing.

 

[locture]

Saw this when searching info for Air reverb full.



Can someone with the full version of air reverb verify if the mic signal between tree and outriggers actually null?

 

[locture]

FWIW I did my own testing and confirmed that in air studio full version the tree and outrigger mics (and also a few other pairs of mics) generate exactly the same audio output which could cancel out.

I consider this as a very serious issue. Audio cancelling out means the same IR and source positioning. In an IR based reverb where the IR collected from a real stage, audio response from different mic positions should literally NEVER cancel out. So it's either a critical bug got past SF internal QA and has been lurking there unfixed for about a year, or SF intentionally faked some mic positions to make the plugin look better and more competitive.

Strictly speaking, failing to offer the actual number of mic positions advertised is misleading marketing, no matter whether it's a mistake or intentional. I have reported this to SF and requested a refund. We'll see what happens next.

 

[HotCoffee]

FWIW I did my own testing and confirmed that in air studio full version the tree and outrigger mics (and also a few other pairs of mics) generate exactly the same audio output which could cancel out.

I consider this as a very serious issue. Audio cancelling out means the same IR and source positioning. In an IR based reverb where the IR collected from a real stage, audio response from different mic positions should literally NEVER cancel out. So it's either a critical bug got past SF internal QA and has been lurking there unfixed for about a year, or SF intentionally faked some mic positions to make the plugin look better and more competitive.

Strictly speaking, failing to offer the actual number of mic positions advertised is misleading marketing, no matter whether it's a mistake or intentional. I have reported this to SF and requested a refund. We'll see what happens next.

What other pairs null?

 

[OleJoergensen]

FWIW I did my own testing and confirmed that in air studio full version the tree and outrigger mics (and also a few other pairs of mics) generate exactly the same audio output which could cancel out.

I consider this as a very serious issue. Audio cancelling out means the same IR and source positioning. In an IR based reverb where the IR collected from a real stage, audio response from different mic positions should literally NEVER cancel out. So it's either a critical bug got past SF internal QA and has been lurking there unfixed for about a year, or SF intentionally faked some mic positions to make the plugin look better and more competitive.

Strictly speaking, failing to offer the actual number of mic positions advertised is misleading marketing, no matter whether it's a mistake or intentional. I have reported this to SF and requested a refund. We'll see what happens next.

Thank you for testing and sharing. This is disappointing news but I find it hard to believe it's done on purpose. Lets hope Spitfire will come with an explanation and update .

 

[locture]

What other pairs null?

Each pair of mics (tree/out, ambient/head, etc.) null, but mic responses do not null across pairs (tree and head do not null).

I find it hard to believe it's done on purpose. Lets hope Spitfire will come with an explanation and update .

I own quite a few SF products and I don't want to believe it's done on purpose either. But given that the way this issue appears (four pairs of mics null in pair) it feels highly suspicious.

In an IR based reverb plugin, this is one of the things that mistake cannot be used as an excuse. You do it wrong once, get caught, and it's the end. Because:

1. This nulling issue requires both the IR algorithm and the source positioning fail at the same time and fail four times in a row between each pair of mics but not between tree/ambient etc.. Sounds super weird - who writes code like that?

2. Even if it's done intentionally, as the users cannot look into the fine detail of the software, it's also super easy to insist this as a bug and fake the mic responses again to make things look more reasonable. The users have no way to tell.

For a $300 reverb this kind of issue is beyond ridiculous. Anyway I feel that we need some immediate actions from SF, like an official and public explanation. And before that is done, the current air reverb webpage is plainly misleading marketing. I don't know about UK laws, but in a number of countries, any misleading marketing behavior, whether mistake or not, leads to not only refunds but also compensations. We'll see what happens with SF.