Modifying a plug-in during render

Hello,

When “All Titles”-rendering from an audio montage, I’m super stressed about touching anything during the render. In other DAW’s, it’s not even possible to touch plug-ins or almost anything during a bounce/render. When I’m rendering All Titles from WaveLab, I know that they are being processed by effects on the title track (track effects and output effects), but I’m still able to open and modify those effects during the render.

How do I know that anything I accidentally touch won’t end up on the file? It’s not like I would deliberately go around poking at effects during a render, but I’m just weary about accidentally misclicking something into e.g. bypass during the All Titles render, and then having to do all of it again just because I’m afraid.

Also, when doing a “Selected clips” render, I’m locked out of the effects and I can see them doing stuff if I happened to have the GUI open, but “All Titles” is letting me fiddle around with the effects and is not showing any activity in the plug-ins GUI’s.

1 Like

→ “Never touch a running system.”

Generally speaking, WaveLab makes a copy of all the settings before rendering, which allows you to safely do other things during the render.

3 Likes

@Justin_Perkins is right. When you start a rendering operation, this is not the montage that you see that is being rendered, but an invisible copy of it. You can safely work and modify the visible montage (and all plugins, including the Master Section plugins).

You could even start a second rendering before the 1st one is finished.

AFAIK, WaveLab is the only DAW capable of this (and since WaveLab 1.5 for audio files and WaveLab 3.0 for audio montages).

4 Likes

Yes. When I am rendering vinyl sides, I often start the render for side A, and then start the render for side B right away, and sides C & D if it’s a double LP. Multiple renders are happening at one time, and they take some time because plugins are involved.

Also, my downstream renders go fast due to how I work (plugin processing is already baked in at a higher sample rate) but after I start my 2444 render I can safely Save As…, change the dither plugin to 16-bit, and start rendering the 1644 files even if the 2444 version is still rendering.

In other words, it’s safe.

3 Likes

Ah, thank you so much @Justin_Perkins and @PG1 ! Exactly what I was looking for. The “ghost” montage for rendering is a brilliant solution for this. Cheers!

1 Like

When I render a bar in the center of the screen pops up that shows completeness - I think in percentages and I cant do anything else but wait. or his CANCEL

If I was able to render other renders while waiting, that would be fantastic.

Is this a setting in the Montage?

And if I am understanding correctly are you saying each “render process” takes to it’s own core, so there’s no change of any buffer underruns or bottlenecking with plugins? (I am definitely not a programmer and might be using the wrong terms)

Thanks all!

This will change in the next update :wink:

1 Like

So it’s not currently able to do that now. I see. I got my hopes up! :wink:

Next update, like WL 13.0 or the next smaller v12 update?

Are you using the “Bounce” feature?

The only render I do that locks me out of doing anything else is making a DDP. All other renders happen in the background and don’t block the screen.

What I am talking about is a big feature…

1 Like

May be you are rendering real time.

I usually print my analog loop from a reference track.

Then I duplicate it and BOUNCE it. Not render. Sorry about the terms. I got that wrong.

This is what I see and I am always wondering what to do while it’s BOUNCES.

To follow up, if I dont BOUNCE and just render out my PRESETS a la 1644, 2444, etc… I can do them concurrently with no issues with processor bottlenecking? If if there an issue will it stop?

Certain types of Render, like Clip Bouncing, require waiting before continuing editing in the montage.