On Windows 7, I’ve recently started using Eiosis AirEQ and Izotope 7 Ozone/Maximizer and have similar problems with both of them when used as montage plugins (clip, track, or montage master) that do not happen when they’re used in the Master Section. I haven’t had problems like these with any other plugins when used in the montage for years (UAD, Waves, Sonnox, FabFilter). The problems are the same on two different Windows 7 computers, one Win 7-64 with Wavelab 8.5.30, 64 and 32 bit versions, the other Win 7-32 with Wavelab 8.0.4 32. One RME interface, one Lynx interface.
The main problem is with the AirEQ VST3 version, in that it has intermittent but consistent playback mutes (worse at 96K and 192K) when used as a montage plugin. The mutes don’t happen at all when the plugin is used in the Master Section. The mutes also don’t happen with the AirEQ VST2 version. To “fix” the VST3 version I have to max out the buffer in Wavelab, which I’ve never even come close to doing before.
The other problem is with Izotope Ozone, or the single Izotope Maximizer, when used as montage plugins. It can be recreated by starting a 96 KHz clip in play, going to the Maximizer module or plugin, and turning on “True Peak Limiting” while the track is playing. Here, on both computers, both interfaces, both Wavelab versions, the playback audio starts glitching and stuttering. Happens with the VST2 and VST3 versions, and no amount of buffer adjusting in Wavelab or the interfaces changes that. The only thing that changes it is to use the Izotope plugins in the Master Section, where this never happens.
I hope these plugins are tested for these things in the new version of Wavelab, and the difference in behavior between use in montage and master section is eliminated. Or, if anyone has time to try these things in the current version, that would be great too.