Sure, what I’m doing wrong. I’ve done this, I’m putting together a show real it’s not to make a CD. It’s just gonna be MP3 and I want to Crossfade the tracks. But for some reason, I’m getting a little audio glitch at each track marker. I can’t find what setting is creating a little glitch. I have the Pre and Post Gaps at Zero
this is the gap after importing to Nuendo
Usually this related to plug-in “warm-up” time and other things. If you’re rendering each album track with cold starts and hard stops to the plugin processing, glitches can occur and it’s not just a WaveLab thing.
This is why I first render the full montage as one long file, and then render the WAV files of each song/track after no plug-in processing is needed. This way, the renders are sample accurate at the track transition points.
There are some settings in the WaveLab Preferences that might prevent you from needing to do that but to be safe, I always render the full montage in one long render first.
With the right settings and options, WaveLab will create a new montage with all the markers and info carried over so you don’t have to redo anything.
Dam so it could be Ozone 12 !
There are no clip based plug plug-ins it’s just ozone 12 on the Master ? Could this still be the problem then?
Thx
Well, you could try a test render without any plugins but most likely it is a plugin.
Any time you’re asking something to do a hard stop and start with plugin processing involved, it’s an invitation for an error like this. Especially a CPU heavy plugin like Ozone.
There are some plug-in warm up settings/preferences but at the end of the day, rendering the full montage first and then a WAV of each track solves it for me so that’s how I always work.
Did you fully close the montage and reopen it to clear any latency reports?
No i’ll try it Thx , I don’t have any plug-ins running now
still have a gap , I’ve never read the full montage when I try to do that just to check, I get a naming scheme error , just watched your video, but you don’t seem to get the error LOl
Okay, so I bypass the plug-ins on the Master and I’m still getting the gap now. I’ve removed them and the gap has gone. Thank you !
just need to work out the full render name things now
Hmm. I have no idea but maybe others will. All I know is that if you try to render a WAV of each track with some or a lot of plugin processing involved, it’s not unsurprising to experience a tick or pop at the track transition points when you check the rendered WAVs in a new montage or test session.
It’s not something you notice when you have true silence between songs but when you have overlapping/gapless audio, the problem becomes apparent.
To get around this for years now, I simply render the whole montage as one long file to bake in the plugin processing, use the option to have WaveLab create a new montage from the resulting render, and then I render a WAV of each song/track from that new montage where no plugin processing is needed.
From here, I never experience a glitch or disruption with gapless album renders.
Also, bypassing a plugin is not enough. You need to fully remove it and for good measure, close and reopen the session so that latency values can be recalculated.
Thanks , I found that out the hard way .
any idea why I get this error , just watch your video and so long, but still I get this error
Okay, I have no idea why I’m getting that hair up, but I’ll just use one of your preset 00 initial montage render and that fixes it
You’re the man ! Thx
Andy
Not without any more context than that.
I usually name the initial full render manually as:
Artist-Name_Album-Title_V1
Nothing more, nothing less. Then part of that preset you found tells WaveLab to make a new montage from that render so all the makers and info are transferred over to the new processed montage.
Then when I render the WAV files for each song/track, I use a Render Preset that adds the two digit numerical prefix to the CD-Text Track Name to generate the “safe” file name such as:
01 Song Title
02 Song Title
03 Song Title
This avoids any special characters that might be part of the official song titles/metadata and can be problematic for file names, especially on Windows systems. macOS is more forgiving with characters in file names but it’s better to be safe than sorry.
Just a quick thank you, Justin for all your help on this.
Andy
Do you mean you render independent MP3 files and then you see a gap between them?
If yes, then try to do the same without creating MP3 files (create standard WAV files).
And if you don’t get the problem, that means the problem comes from MP3 file size quantization.
And I’m not at a computer now but there is a deep setting that helps WaveLab render gapless mp3 files.
It’s probably part of my render presets/settings.
Ok I will try that tomorrow, I also worked out the naming problem I had and exported and whole montage, then added Ozone 12 , I don’t see any any glitch (gap) on the whole montage Wav, then I export that to Mp3 with Ozone 12 , then playing it back in Apple Music (as a album) I hear a glitch .. very odd ..
Andy
Render the full montage with Ozone to bake that in before rendering the files for each track. That’s the whole reason for doing the full render first.
Lossy formats can add silence to the starts of the files. Look for the setting in WaveLab that fixes that for mp3 files.
iTunes/Apple Music can no longer be trusted for gapless testing. Try a new test montage or a prosumer app like J River Media Center.
