Hello everyone,
I’ve updated from Wavelab Elements 11.2 to Elements 13 a few months ago but ran into an annoying problem.
So I’m using Wavelab audio montages extensively to assemble pre-produced radio shows for community radio stations. Which means that I will usually have several stereo tracks with music and one mono track with my voice.
On said mono track, I use the voice exciter, EQ and a compressor plugin for some sound processing. I’ve tweaked the settings over time so I already know what exactly I need and can quickly dial them in.
Now I’ve encountered it several times that everything sounded fine when I assembled the audio montage, but in the rendered product my mono voice track suddenly sounded dull. Apparently the EQ and sometimes also the voice exciter had not been applied. This could be confirmed by saving and re-opening the montage: All of their settings were at zero again. So apparently Wavelab did not “remember” the settings and also not apply them during rendering.
Sometimes it could be fixed by just quitting Wavelab, re-opening everything and dialing in the settings again, but yesterday I couldn’t even get that to work. I also noticed that just changing the EQ values did not get registered by Wavelab as a change to the montage: It did not show a star in the title bar and did not offer me to Save, only Save as. Switching the EQ off and on again did get noticed as a change, but the values still were all at zero after re-opening the montage.
After fiddling with this for almost two hours, including many restarts of Wavelab and a full reboot of the computer, I finally found a workaround: When making another change to the montage, in this case slightly reducing the volume of a clip on a different track that was a little loud anyway, the correct EQ settings on the mono voice track also got saved and therefore rendered as intended. So it seems one needs to make other changes to the montage for Wavelab to actually notice and save/render the settings.
This is an issue I’ve never had with Wavelab 11.2, so I am quite disappointed that upgrading made things worse. I wanted some of the new features, but after all it seems I was better off with the older version.
My computer is an M1 Macbook Air running MacOS 15.7.5, Wavelab version is 13.0.10 (though it occured with 13.0.0 just the same), interface most of the time a Samson Studio GT (active speakers with integrated USB/XLR interface). I am running the native Apple Silicon version of Wavelab, trying the Rosetta version made no difference.
Searching the web for this issue gave me absolutely zero results, so it apparently is too niche and might not even be noticed by most users, hence my bug report.
I’d be very happy if this got fixed in one of the upcoming point releases, making Wavelab the reliable tool I know it as again.
Thank you!
