{Question} Waveform Pro 13 - Rendering Separate Tracks with VST3 plugins

[OMQ-Raven]

Hello, I was wondering if anyone happens to know of a way to render separate tracks that uses VST3 plugins?

I've tried the obvious method of simply hitting render and selecting the render separately option, but most of the rendered audio files are blank.

The only workaround so far that I've found is manually muting and unmuting different tracks and rendering each individually manually but it's definitely a pain in the behind.

It would make sharing stems a lot easier if I could render the separate tracks automatically so here I am asking for help if possible.

Thank you in advance for the replies!

[OMQ-Raven]

Also, if it happens to change something, I use Falcon by UVI as my main synth plugin and I use it as a VST3 because for some reason the VST2 won't appear anymore nor install anymore.

[Watchful]

You can bounce a track or tracks pretty easily. We did this all the time back in the day, but it seems this is a forgotten technique. Here's how:

1. Create a track (name it something helpful to you...I call mine Bounce Track)
2. Set the track's input to receive audio from the track you want to bounce
3. Arm the bounce track to record
4. Record the track...either the whole track or just whatever section you need
5. Look in the project folder's Recorded Items, and you'll find your bounced track

Want to bounce two or more tracks?

2. Set the output of the desired tracks to the bounce track.

This will route all the audio from those tracks into one, bounced track. The other steps remain the same.

I don't render *anything* in Waveform...it seems to be problematic. I literally bounce ALL tracks into a single track at the end via recording. It's been 100% problem free for me that way.

[OMQ-Raven]

Ohhh I see, I'll have to give that a try. A huge thank you for the help!

[OMQ-Raven]

From what I could try so far using either freeze track or render track to a separate track, waveform doesn't seem to allow me to render with either vst3 or vst2 plugins.

I tried bouncing a bus track since it's just a normal track in the end like you suggested, that didn't work.
Then I tried bouncing the track with the midi information directly and it doesn't want to render anything either.

I think Waveform just has an issue at this point.

[Watchful]

Are you able to hear the output of Falcon when you play the track?

Are other plugins working all right?

[OMQ-Raven]

If i solo out the bus tracks no, for some reason anytime I route the audio waveform only allows me to hear it through the new target track.

Maybe it's because I'm using the main output on each tracks to reroute instead of the aux return and aux send plugin waveform provides?

[dysjoint]

In the render dialogue there should be an option to 'pass through plugins' Make sure it is on. Also a track that is routed to another track and is rendered will often deposit the rendered file into the 'output' track. A track that is routed to another track, and then that output track is routed to another track will produce silence. This is an annoying aspect of Waveform that can be worked around but makes it harder to render stems in one hit.

[OMQ-Raven]

Yeah that's exactly what happens.

I have instruments sending into a folder sending into a sidechain track, an effects track, sending into a mix bus, sending to the master. So I'm probably way past the silencing issue haha

I'll try to find a workaround but in the worst case I'll switch back to Ableton if I can't find anything. I've got a few annoying issues lately and I'm starting to get convinced into switching slowly with all the crashes and such haha

A huge thank you for the help!

[pough]

I'm able to render individual tracks with VST3 plugins on them. I guess it has something to do with complicated routings. Waveform takes you at your word when you tell it to render one track. It ignores all the rest. It would be nice to more easily do a "single" track that includes MIDI and audio from other tracks without their outputs outputting, but so far we seem to have to do complicated things to get complicated results.

[OMQ-Raven]

Exactly. As much as simplifying would fix that issue, it would create the problem of no longer having busses and such which makes mixing and mastering a lot easier for me and I spent a good amount of time getting that workflow in place which also happens to work on other DAWs. Of course it doesn't mean my workflow is correct or perfect, but having it being too simple in the past was becoming a pain to work with at times.

I wish it would allow for multiple routing but I guess I can only hope for it on Waveform 14 if it ever gets added before I switch to another DAW haha

[talby]

EDIT: If repeatedly needing it for the same set of tracks, how about then to group them, and then for this group configure that it only reacts on the MUTE and SOLO actions? You can have various groups, give each your own name to easily identify them. It also works to have grouped tracks which are not all in the same folder or submix. You can freely pick and group without interfering with your folder and submix organization. Then ISOLATE one of the tracks will also isolate all tracks which are member of any group the isolated track is member of, but only for those groups which have the mute/solo sensitivity set.
Use in the Browser the groups panel. Selecting there a group will show you the possible options in the Controls Panel, and also in the Actions tab of the Browser, and there is also the Actions Panel accessible as a separate view placed outside the Browser. They should all be synced and show the same. So, you can have the Group tab visible in the Browser, and the Actions Panel open in parallel and there right away change settings for a selected group, like adjusting the parameters the group shall be sensitive to and of course adding or removing a track to/from a group. Then select the next group and so on. Usually very quickly set up.
By the way, groups are also useful for toggling visibility of tracks, which can be helpful during arrangement but also in the Mixer.

[OMQ-Raven]

I've tried using groups, but it's not exactly what I was looking for.
It won't fix the routing issues as I still end up needing to route.

I could definitely also just chain the plugins directly the group to save a few routing, but from what I tested so far, anything above a one routing cuts the sound when rendering.

So it's definitely something going on with Waveform.
That and I have now ran into an issue where Waveform won't load a template properly because it has possibly too many tracks and such.

I might try to redo my setup slightly to help the problems, but it's definitely frustrating to have to redo it all every few weeks because a new issue appears. I might just change to a more stable DAW starting in May if too many issues happen again I'm thinking.

A huge thank you to everyone for the help!
Wishing you all the best!