Do you have custom IRs, or did you add your own IRs, impulse responses, to Altiverb 7?
You have to copy these to the new location Altiverb 8 uses to ensure Altiverb 8 also finds these.
The new location is:
macos:
/Users/Shared/Audio Ease/Altiverb/Impulse Responses/User Created IRs
Windows:
C:\Program Files\Audio Ease\Altiverb 8\Impulse Responses\User Created IRs

Your custom (User Created) IRs could have been in these locations for Altiverb 7:
macos:
/Applications/Audio Ease/Altiverb 7/Impulse Responses/Third Party IR Libraries
/Users/Shared/Altiverb/Third Party IR Libraries
/Applications/Audio Ease/Altiverb 7/Impulse Responses/User Created IRs
/Users/yourusername/Library/Application Support/Altiverb/User Created IRs

Windows:
C:\Program Files\Audio Ease\Altiverb 7\Impulse Responses\Third Party IR Libraries
C:\Program Files\Audio Ease\Altiverb 7\Impulse Responses\User Created IRs

You can also verify Altiverb 8 uses this location, in the preferences tab in the plug-in:


And when you just moved the files, hit the folder icon and choose rescan to ensure all IRs get added. Then quit and start your DAW and retry opening the project using the custom IRs.

Altiverb 8 is backwards compatible with Altiverb 7.
The Altiverb 8 upgrade license replaces your Altiverb 7 license, and the Altiverb 8 plug-in will replace Altiverb 7 in your older sessions, sounding identical to Altiverb 7 (and Altiverb 6 and Altiverb 5).

more on 5.x instances from v7 to v8

Forward compatibility is limited: sessions made with Altiverb 8 don’t load reliably on systems with altiverb 7 installed because new functions may have been used in the Altiverb 8 session that are lacking in Altiverb 7.

If you used Altiverb 7 one of these DAWs, we recommend to request a temporary v7 license at support@audioease.com when you upgraded to v8. Then you can re-install Altiverb 7 and use Altiverb 7 and Altiverb 8 alongside eachother in these DAWs to make the transition from 7 to 8.

Transfer settings from v7 to v8
First re-install Altiverb 7, the Altiverb 8 installer has removed the Altiverb 7 plug-in. You can of course download this if you do not have the installer anymore. Then follow these steps:
1. Open your project made with Altiverb 7 and save presets for all Altiverb 7 instances.

2. The presets are saved here:
macos: /Users/yourusername/Library/Application Support/Altiverb/User Presets
Windows: C:\Program Files\Audio Ease\Altiverb 7\Presets\User

3. Insert Altiverb 8 on the same channel as the Altiverb 7 and then in the snapshot tab in the Altiverb 8 plug-in you can import the Altiverb 7 preset.

4. Now you can remove the Altiverb 7 plug-in and save your project.

This way you moved from the old to the new version while keeping the same settings.

While Altiverb 8 is backwards compatible with Altiverb 7 there are some big changes in the multichannel Altiverb 8 implementation that changes the output of the 5.x channel plug-in specifically.

There are three types of '5.x' Altiverb instances in use:
Type 1: the fivefold multi-mono type. Altiverb 8 sounds identical to Altiverb 7 in this one.
Type 2: Mono or stereo input to 5.x out: this instance is 3dB louder than Altiverb 7, and otherwise identical. We can no longer fix this without breaking more sessions than it fixes. A -3dB Trim after your Altiverb 8 will fix this.
Type 3: The 5.x in 5.x out version of Altiverb 8 does not sound the same as Altiverb 7.
It sounds similar at cloud-size maximum (loading the old quad IR with center beed and all), but the level does not match. A fundamental internal routing change that allows for the new cloud-size feature breaks this backward compatibility.

Only Type 3 is trouble when migrating from v7 to v8.
If you need to pick up an Altiverb 7 session with (type 3) 5.0 to 5.0 output reverbs then use Altiverb 7 to be safe (if on silicon, with pro tools in rosetta mode). A v7 license will be supplied if you ask for it. If you want to move forward and use Altiverb 8 anyway, check the level of the reverb and adjust it. While you are at it, it is best to change the chosen IR to one that is true 5.0, rather than load the old Altiverb 7 quad-with-center-bleed type.

The full note from the 8.0.7 update

note 1:
Levels are improved in Backward compatibility situations for the Altiverb 7 instances with input-output: quad to quad, 5.0 to 5.0 and 5.1 to 5.1.
Altiverb is a music and post reverb. The 5.0-in 5.0-out Altiverb, however is mainly targeting post. The 5.0-in 5.0-out Altiverb 8 loads new true 5.0 IRs by default, implements easy center-channel-only reverb with input pan following and adjustable cloud size. For Post this instance has undergone massive improvements and it was the most challenging to keep it backward compatible.

In a 5.0 input to 5.0 output instance of Altiverb 7 a stereo to quad output IR was loaded by default, mainly because no 5.0 IRs existed in Altiverb 7. Center reverb was created via the center bleed option, a delayed mix of the rear channels in the front. Altiverb 8 will load the IR that was chosen in Altiverb 7, including the center bleed. You may, as we do, prefer the native Altiverb 8 way: if you have just upgraded to v8 when opening your Altiverb 7 project or template we advise you to open your Altiverb 5.0 input to 5.0 output instances and load the true 5.0 Impulse Response in there. One should be available for most Impulse Responses in the Altiverb collection.

When cloud size is increased it gradually adds speakers which increases the total level. Cloud size did not exist in Altiverb 7. In Altiverb 8 5.0 input to 5.0 output Altiverb 7 settings are loaded with 60% cloud size, which may result in a higher output level than in Altiverb 7 produced, depending on different circumstances.

Similar measures have been taken in the quad input quad output and the 5.1 input 5.1 output instances. Please note that all of the above only applies to Altiverb 7 settings received by Altiverb 8.

Problem: Altiverb 8 XL is installed, however Altiverb 8 is only available in mono and stereo (no surround or multi-channel options).
Or opening sessions made with Altiverb XL results in inactive plug-ins.

This could be due to incorrect plug-in cache in Pro Tools.

Solution: Force a re-scan of the plug-in.
First make sure Pro Tools is Quit. Then please remove these files: /Users/Shared/Pro Tools/AAXPlugInCache/Altiverb 7.aaxplugin.plugincache
/Users/Shared/Pro Tools/AAXPlugInCache/Altiverb 8.aaxplugin.plugincache

Now open Pro Tools. Pro Tools should re-scan the Altiverb plug-in and it should discover the XL multi-channel surround options now.

There will be no MAS Altiverb 8 plug-in.
Before you upgrade to Altiverb 8 please save the settings of your MAS Altiverb 7 plug-in instances in your projects as Altiverb presets (irp files). You can do this in the Altiverb IR browser.
These will be converted by the Altiverb 8 installer but you can also choose to import Altiverb 7 presets in the Altiverb 8 plugin, in the snapshot panel. In case in a while you need to turn back to an old project where you have not done that we can provide temporary licenses so you can do this still.

All new parameters in Altiverb 8 are not automatically enabled for automation when you open a session that was started with Altiverb 7. Ensure to enable these if you rely on automation.

Of course when you insert a new Altiverb 8 instance all parameters do get enabled directly (if you have this enabled in the pro tools preferences).

If Altiverb 7 is gone after you updated Pro Tools to 2023.3 (or later) and you are on a Apple Silicon Mac (M1/M2/M3 ARM) then you have to open Pro Tools Using Rosetta to get Altiverb 7 working.

Altiverb 7 requires Open Using Rosetta on the Apple silicon (M1/M2/M3/etc) macs. Altiverb 8 adds native support for apple silicon. You can check your upgrade options here.
You need to open Pro Tools using Rosetta in order to use Altiverb 7.
To ensure Pro Tools opens using Rosetta:

• open the Finder
• go to the Applications folder
• select the Pro Tools app
• hit get info
• tick the box to Open Using Rosetta.

Problem: Non-readable text in the Altiverb 7 user interface.
Solution: Follow this guide to allow Altiverb to access the font again:
https://support.apple.com/en-gb/guide/font-book/fb34862/mac

Altiverb uses the system font Arial. Altiverb does not install this, it should be on your macOS by default. If your system does not have the Arial font or the macOS system prevents Altiverb somehow from using it, Altiverb could look like this:

Problem: Installed or updated Altiverb 7 and now it does not show up in Logic.
Solution: Restart your mac.

Somehow (we are still trying to find out why) the macOS ignores Altiverb 7 until the computer has been restarted. This is why Logic (or Ableton Live, or any other DAW that uses Audio Unit plug-ins) does not show the Altiverb

Altiverb 7 Regular and XL sound exactly the same and come with the same IRs.
There are three differences:

Altiverb 7 Regular supports

• up to stereo input and output
• sampling rates up to 96kHz
• plug-in formats on windows: aax native and vst, on mac: aax native, vst, audio unit, mas and rtas

Altiverb 7 XL supports:

• up to 5.1 surround in and output
• sampling rates up to 384 kHz
• all plug-ins formats Altiverb 7 Regular supports + TDM on Mac OS X

So, in short, if you do not have sessions on 192k and you work in stereo only, Altiverb 7 Regular will do just fine.
If, at a later stage, you would like to upgrade from Regular to XL this is possible. The upgrade cost is just the price difference so you won't loose any money going for Regular first.

Problem: The IR set gets downloaded when you click the download button in the NEWS section in the IR Browser. It starts downloading but then nothing happens, the set does not load or show up.

When this happens the Altiverb plug-in fails to copy/move the downloaded IR set to the Audio Ease IRs folder.
It could be Altiverb is not allowed to write in the Audio Ease IRs folder.

Solution: Try locating the folder in the finder (or explorer), hit get info and then verify your user (and the admin group) can read&write in the folder. If you make changes make sure to also apply to all enclosed items too. If this does not help, try using the default location as IRs folder:
/Users/Shared/Altiverb/IRs

You can change the IR folder location in the preferences tab in the Altiverb plug-in:

Altiverb 7 supports loading your own files as IRs.
Any wav audio file can be used as impulse response.

Simply add your file(s) to your User Created IRs folder, the default location is:
/Users/yourusername/Library/Application Support/Altiverb/ *

Your third party impulse responses folders, libraries can be loaded through:
/Users/Shared/Altiverb/Third Party libraries

If you have recorded the Altiverb sine sweep to create an IR, then drag your mono or stereo recordings as wave file onto the drag and drop import window in the Altiverb plug-in. You can choose to save your IR into the User Created IRs folder.

There is a little trick you need to pull off to get this to work:

• open the add fx window in Reaper on the 6 channel track
• then right click on the Altiverb plug-in and make sure this option is checked:
• ☑️ inform plug-in when track channel count changes

When you then insert Altiverb 7 it should become 6 in 6 out and you will be able to choose the surround IRs in the IR Browser.

Most likely you were working with old older (version 7.0/7.1) IR set before and you recently installed the latest Altiverb 7 plug-in updater. This new Altiverb 7 plug-in however requires the latest core IR set.
To fix this please download the latest first time full Altiverb 7 installer and run this.
Once you installed this you will have all IRs again.

> You can request a link to the latest downloads at:
www.audioease.com/download

Altiverb 7 Windows Authorization Error: Altiverb 7 Regular cannot run because it is corrupted please try reinstalling the product

This error means the graphics card driver on your system is not up to date. Even when Windows states this is up to date, Altiverb 7 can generate this error and you will find there is a newer driver available (and this will solve this error).

Please try to update your graphics card driver.

Find out what graphics card you have in your system (right click on your desktop, choose change screen resolution, hit advanced settings, that would show you the manufacturer’s name and the model).
Then please go to the manufacturer’s website, hit support/drivers and find the latest driver for your graphics card and download and install this.
Restart your computer.
The problem should be gone now.

There is a situation where the Altiverb plug-in can revert to default settings when loading a project in Digital Performer.

This is caused by the fact the Digital Performer (DP) supports three plug-in formats: MAS, AU (audio unit) and VST.

How?
Example: When you save a project with the Altiverb MAS plug-in. And you then change the default plug-in type in DP to AU and re-open this project. DP will load Altiverb, but DP fails to transfer the saved Altiverb MAS plug-in settings to the now Altiverb AU plug-in, and Altiverb then reverts to loading the default settings (which is the Teldex IR).

When this suddenly occurs you are most likely using a different plug-in format then you used before. Try to find out what you used before, force DP to load this Altiverb plug-in from the plug-in settings in the DP preferences and then restart DP and re-open your project. The right settings should load again then.

If you need any help with this let us know. Send us for instance a project file that will not open correctly, then we can quickly help you out.

The macOS Altiverb 7.4.3 installer currently fails to install the screen saver. You can download the screen saver and copy it to:/Library/ScreenSavers/

Screensaver

What is the difference between the mono to stereo and the stereo to stereo options in a stereo out Altiverb ?

Best way to understand this is to go back with me to our sampling session when we recorded to room's acoustics for the IR in Altiverb.

mono to stereo
We put a single speaker in the center of the stage and two mics in the audience.

This results in a mono to stereo IR.
When you playback your audio through this IR in Altiverb, it will sound like your audio comes out of that single speaker from the center of the stage (mono!) picked up with two microphones (stereo!).
This IR gives a stereo reverb, however the input is (mixed to) mono, as there is only a single source on stage.

When you want to process a vocal (mono) or direct recorded electrical guitar or something where the panning is not important the mono to stereo IR will do just fine (pro: costs half of the processing then a stereo-to-stereo IR, so it is more efficient in cpu and memory).

stereo to stereo
back to recording the room
this time we put two speakers on stage, one on the left and one on the right side of the stage and we record again with the two mics in the audience.

When you playback your stereo audio through this IR in Altiverb your stereo signal comes out of these two speakers.
Easy to picture here that your original panning will be maintained using a stereo to stereo IR.

So basically it comes down to this:
is your input stereo or is it panned in stereo ?
use a stereo - stereo IR, else you will loose the stereo information in the reverb (although the reverb is stereo).

Sometimes even when using stereo panned sources a mono to stereo IR can be preferred as you do not want the panning to be reflected in the reverb levels. But this is a mixing decision which depends on taste mostly (and music style) and I dare not to advice on that :-)

We have removed some sets from the Altiverb IR library (mainly user submitted IR sets) that do not meet up to our current standards. The Speakers and Phones set is one of these. You can copy the original set from your Altiverb 6 Impulse Responses folder (if you still have this) to the Third Party IRs folder in the Altiverb 7 Impulse Responses folder.
Then you can then load these IRs again in Altiverb 7.

You can also download the original set from:
http://fokkie.home.xs4all.nl/IR.htm