Is there a way to get rid of the reverb tails that sometimes appear in the beginning of a song in a render? I’m making a new song which starts very quiet and when the first note plays I get a BOOM from the reverb tails and it’s extremely annoying. I tried adding an empty pattern in front, but they tails only play when the first notes are played, so the only thing I can think of is play a single note with all the instruments in the beginning of an empty pattern and it’s really a hassle and shouldn’t be required.
I’ve also started to get snaps in the rendered wav, every now and then there are 1-2 loud snaps that you can clearly see in the waveform and you have to render it again and they’re either gone or moved to another place. Any idea about those?
I also experience this, to avoid these noises, I just stop the song and waits for all tracks to become quiet (I don’t use a lot of reverb btw) before starting the rendering.
(I never experienced snaps, maybe it’s a vst issue ? some doesn’t like to be rendered the fast way… maybe try realtime rendering ? Maybe you can isolate which track does this by rendering them separately… Good luck !)
workaround, but I always add a few empty patterns at the start of a song, besides handy for post processing in an external wave editor, reverse reverb ftw , if there is fx residue it can be easily cut without affecting the actual song.
I also experience this, to avoid these noises, I just stop the song and waits for all tracks to become quiet (I don’t use a lot of reverb btw) before starting the rendering.
Hmm, I’ll have to try this, I usually force stopped all sounds by pressing the stop button twice, maybe it has something to do with that, I always thought the stop button twice would reset all the settings but it might be that it leaves everything in some kind of limbo instead.
(I never experienced snaps, maybe it’s a vst issue ? some doesn’t like to be rendered the fast way… maybe try realtime rendering ? Maybe you can isolate which track does this by rendering them separately… Good luck !)
I have them every now and then, It’s weird since the render should be just processed and not recorded but there’s something that disagrees with this, no idea if audio interface buffers, bit depth or mixing rate affect it. Both of these bugs are annoying since they waste so much time.
workaround, but I always add a few empty patterns at the start of a song, besides handy for post processing in an external wave editor, reverse reverb ftw , if there is fx residue it can be easily cut without affecting the actual song.
I tried this but the tails only appear when the first notes are played, so if I add an empty pattern in front, it’s completely quiet until the first chord is played and then I get the tails on top of everything playing
Yup, I think when you hit twice, the engine is frozen and keeps whatever it has in stock for the moment it has to restart… I think you’ll get some result, it looks exactly like what I had !
I’m surprised that it waits for the first chord… Have you activated plugin automatic stop on idle or something like this ?
Have you tried changing the “autosuspend plugin when silent” toggle in the plugin options for the vst that causes the glitches? You can access these settings through this toggle in the plugin slot in the tracks dsp tab;
Perhaps changing the “use static processing buffers” option also influences the problem. Try changing one or both of these and render to see if the problem persists.
That’s what I always do, too. I still wonder if there’s another way.
I never had a problem with that, but since I layer instruments and process them in parallel, there are always ticks and clicks with reverb and delay at the beginning of a song. And I don’t want to check all 30-40 instruments every time to find out what’s causing this, provided if it’s a VST. Same regarding to all the effect devices in every track. Before I would do that, I rather would add an empty pattern at the beginning and cut it after rendering, just like I already do. It’s a matter of time.