I find that with some Acustica plugins (Scarlet and Coffee) when I render a montage (as a single file at 64 bit) I get a short fade-in during the first note of each song. If I bypass the Acustica plugins the problem goes away. A work around it to put a short burst of audio (a few ms) half a second before the first not of each song. This solves the problem, but it’s a real pain to set up and it has to be edited out later.
Has anyone found a way to work with Acustica avoiding this problem?
Thanks.
I usually open the WAV file, home the cursor, insert 2 seconds of silence with the silence editor, and drop a mark at the 2 second time so that I can easily trim the front of the file back to where it was in the montage. (I have a handy 2 second and 5 second preset set up on the silence editor-- MAAT linear phase plugins are also nasty about cutting off the front of the audio.)
You will need to be careful, because inserting silence at the front end will change the time length of every other instance of the WAV in any other montage. I usually wind up doing this on the initial setup of a project so there is only one edit version in existence, but during a time of working method transition you may want to clone the wav file, insert the silence, and then do a WAV substitution in the montage to the long-front version. That way, nothing else but the montage you’re working with will be affected.
My solution is to not use Acustica plugins. I don’t think they’re worth the hassle they impose.
1 Like
I know, I may end up having to do that. Acustica Scarlet does this really cool 3D thing though, somehow it just deepens the soundstage front to back which really helps some masters. I’d miss that. Strangely if I master in Cubase I don’t have this problem. But Wavelab is so much better for mastering I may have to give Acustica.
WaveLab does appear to be more sensitive to plugins that don’t follow the VST3 spec close enough than other DAWs, plus unlike Cubase and most DAWs, WaveLab has clip effects. Other DAWs have only track effects to worry about.
This, combined with what seems to be plugin developers being less likely/willing/able to test their plugins in WaveLab specifically, leads to a higher number of issues detected in WaveLab.
That said, it seems that 99% of the time, a plugin bug or performance issue in WaveLab must be fixed by the plugin developer if they care to do it.
Plus 1 on that … while they may sound good, way too many issues for a busy studio
1 Like