×
What's new
By:

AIR Studios Reverb Discussion Thread

  • Thread starter Thread starter syrinx
  • Start date Start date
  • Watchers Watchers 227
DVRGNTJoost said:
I am not at home right now but really curious, what says the release log?

Truly hope the Cubase crashing bug has been fixed forever now.
Click to expand...

Change Log - 9th October 2025
AIR Studios Reverb - v.1.3.4

Fixes
  • Resolved an issue where bouncing a project after saving/loading without opening the AIR Reverb UI would result in a silent bounce.
  • Fixed a problem causing silence or audio crackling when bouncing with the AIR Reverb UI open during calculation.
  • Corrected IR duplication in AIR Reverb — Tree & Outrig, Head & Ambient, Backs & Canopy, and Gal W & Gal B now use distinct impulse responses.
  • Fixed an issue where User presets did not correctly load Mixer, EQ, Mono/Stereo, Pre-Delay, Gain, and Output settings, instead inheriting these parameters from the previously loaded preset.
Known Issues
  • Bounce Issues: Mono output with GUI closed, reverb sounds wrong after IR calculation with GUI open
 
Okay, gave it a try after backing up the v1.2.14 component. Everything seems to be okay so far; switching user presets seems more stable, no issues bouncing.

Side note, the Spitfire Audio App lists the version number as 1.3.4, but the actual installed version is 1.3.3-59aa1ce - the same one that is shown in the screenshot Paul showed a few posts back.
 
Last edited:
I made the mistake of updating to the newest version and now I'm getting the issues that were supposedly fixed with the update.

I had no issues before updating and now I have a Logic project that's refusing to bounce unless I do it in realtime. And even when I do it in realtime the plugin seems to not have any of the settings loaded until I actually open it to view the settings. Even if I open all the instances to load the settings and go to bounce again it STILL doesn't bounce correctly.

If I turn off all instances of AIR reverb then the project bounces just fine as it had before... fun.

Is there any way to revert the update? Or do I need to get in touch with their support/wait until another fix gets put out?
 
ariatec said:
I made the mistake of updating to the newest version and now I'm getting the issues that were supposedly fixed with the update.

I had no issues before updating and now I have a Logic project that's refusing to bounce unless I do it in realtime. And even when I do it in realtime the plugin seems to not have any of the settings loaded until I actually open it to view the settings. Even if I open all the instances to load the settings and go to bounce again it STILL doesn't bounce correctly.

If I turn off all instances of AIR reverb then the project bounces just fine as it had before... fun.

Is there any way to revert the update? Or do I need to get in touch with their support/wait until another fix gets put out?
Click to expand...

Since the update, I’ve been having a similar issue in Nuendo on Mac. When I try to export (unless I do it in real time), the DAW freezes for a moment and shows the spinning wheel before anything happens. This only occurs with the full version of AIR Studios Reverb. If I use the Essentials version instead (which I don’t think has been updated), it exports immediately. It’s still manageable for now, but annoying and needs to be fixed.
 
ariatec said:
I made the mistake of updating to the newest version and now I'm getting the issues that were supposedly fixed with the update.

...

Is there any way to revert the update? Or do I need to get in touch with their support/wait until another fix gets put out?
Click to expand...
Sorry to hear you're having issues. Just an FYI, I just bounced a good sized project with ≈50 tracks using Air as a "room" send and didn't have any issues bouncing offline in Logic.

RE: Reverting. Do you have a recent TimeMachine or other backup? Simply swap out the new component file (1.3.4) with the one that was backed up. That should get you back up and running prior to the update.
 
Just tested the update in Logic Pro 11.2.2. Bouncing is definitely messed up for me now. I tested a small project with just two tracks and while the bounce initially hung for about 30 seconds, it did complete successfully eventually.

But then I tried it on a larger project (28 tracks, with 15 instances of AIR Reverb set to different presets) and it hung on the beachball when doing an "offline" or "automatic" bounce. I let it run for about four minutes, and it finally moved to the "Bouncing" screen but then it just stopped exporting, without any error message or any file created. This happened repeatedly.

When I tried bouncing using "Realtime" there were no issues and it exported fine (just, you know, slower). Bouncing the same track without the AIR Reverbs successfully completed in about 40 seconds in offline / automatic mode.

I am on a M3 Max MacBook Pro with 128GB of RAM on MacOS 15.6.1, FWIW.

Any advice @SpitfireSupport ?
 
rockstarjoe said:
I am on a M3 Max MacBook Pro with 128GB of RAM on MacOS 15.6.1, FWIW.
Click to expand...
Same config here, but I'm still on macOS 14.8.

It does take a while for the bounce to initiate offline, but it's working with just the one instance of Air.

EDIT: Response to below - Should have clarified, only using Logic.
 
Last edited:
Finniiss said:
Same config here, but I'm still on macOS 14.8.

It does take a while for the bounce to initiate offline, but it's working with just the one instance of Air.
Click to expand...
Same here, it works if I only use one instance of the plugin. But multiple tracks with multiple instances seem to cause it to hang.

EDIT - also I just want to note, this only seems to be an issue in Logic Pro. Everything is working normally in Ableton. I tried both the AU and the VST3 plugin in Ableton and both bounced with multiple instances with no issue. Also worked fine in Cubase LE 12.
 
Last edited:
rockstarjoe said:
Same here, it works if I only use one instance of the plugin. But multiple tracks with multiple instances seem to cause it to hang.

EDIT - also I just want to note, this only seems to be an issue in Logic Pro. Everything is working normally in Ableton. I tried both the AU and the VST3 plugin in Ableton and both bounced with multiple instances with no issue. Also worked fine in Cubase LE 12.
Click to expand...
I have this issue where it freezes for a moment when exporting with the newest full version, unlike the Essentials version. This happens in both Nuendo (see above) and (just checked) Ableton Live. I would speculate that whatever happens under the hood is the same thing that causes the issues in Logic.
 
Finniiss said:
Sorry to hear you're having issues. Just an FYI, I just bounced a good sized project with ≈50 tracks using Air as a "room" send and didn't have any issues bouncing offline in Logic.

RE: Reverting. Do you have a recent TimeMachine or other backup? Simply swap out the new component file (1.3.4) with the one that was backed up. That should get you back up and running prior to the update.
Click to expand...
I got in touch with support via their chat and they offered to send over files of the previous version and check on my system if installation went correctly.. And then nothing afterwards, no replies and nothing sent over. Also ironically in their reply they said they haven't had any reports of issues with the newest version.

I don't think I have a recent backup but I'll need to check, praying that I do because this has thrown a wrench in my workflow and I'd rather not reconfigure my template to use a different reverb across multiple projects but it might be necessary at this point just to get these files bounced :(
 
Well, I tried uninstalling and re-installing everything and I still had the same issues, so I rolled back to an older Time Machine backup. Now the exports are working fine in Logic again. Guess I will wait to see if Spitfire has an update on the update LOL
 
So they still can't get the core function to work correctly after 1.5 years. This plugin has become such a massive shitshow, highlighting how incompetent the spitfire developer team is.

And anyone still remembers Paul's old promise "we'll look into surrounding"? I may see that before the end of the world ... And of course it's going to break the software again!

I'll mark this thread to use as evidence in the future, to convince anyone wanting to buy anything from spitfire to think twice and think two years before buying anything.
 
locture said:
So they still can't get the core function to work correctly after 1.5 years. This plugin has become such a massive shitshow, highlighting how incompetent the spitfire developer team is.

And anyone still remembers Paul's old promise "we'll look into surrounding"? I may see that before the end of the world ... And of course it's going to break the software again!

I'll mark this thread to use as evidence in the future, to convince anyone wanting to buy anything from spitfire to think twice and think two years before buying anything.
Click to expand...
I don't get why their state of the art reverb, a product they never ever made before is so poorly quality checked before release, or updated faster. Its quite a shame since the concept is very nice. But mistakes like swapping a microphone pair is SO easy to check and fix on their end...
 
You must log in or register to reply here.
Back
Top Bottom