Dot wrote on 6/7/2019, 7:08 PM

Trackalizer supports Vegas 8-12. I don't know if it goes to higher versions or not, but it is free so worth trying.

wwaag wrote on 6/8/2019, 12:52 AM

Based on your inquiry, I added a track render option to the AudioTrim tool in HappyOtterScripts which can be found at

Here's the UI.

Also a short demo.

HOS is in beta at the moment through 1 Aug. If you would like to try it, let me know and I'll make the revised AudioTrim tool available to you for download since the current version on the website does not have this update.


Marco. wrote on 6/9/2019, 4:55 AM

There's already a default script ("Render Audio Tracks") available via Tools/Scripting which does this.

wwaag wrote on 6/9/2019, 8:47 AM


Thanks for the info. Looks like I wasted a few minutes of my time adding that to HOS. Your knowledge of Vegas is invaluable.

Jessariah67 wrote on 6/9/2019, 1:49 PM

Thanks for all the input. Getting my mind wrapped around a work flow that involved other contractors who are not in Vegas is a bit of a challenge. I will certainly be checking out Happy Otter (I hadn't heard of that before). Thanks for the heads up!

Former users wrote on 6/11/2019, 7:21 PM

I liked that option that was added in Audio Trim.

I know there is a script in vegas that does this, however it renders all existing tracks and not always the user wants it this.

The way you did is better because the user has the option to choose the tracks that he wants to render.

What I liked the most is that the rendered tracks are identified with the project name and also the individual tracks names. This helps a lot in identifying and organizing.

Rednroll wrote on 7/29/2019, 8:59 AM

I haven't tried this recently but in the past here's how I would do it. I would essentially route the audio tracks that I wanted in separate files to separate audio buses and then render as described.

No scripts needed, it's already built into Vegas.

Rednroll wrote on 7/29/2019, 10:16 AM

Only problem....I'm attempting the above method I just outlined in VP16 for the 1st time, and it doesn't seem to be working for some reason.

Marco. wrote on 7/29/2019, 10:44 AM

Where is the knot? In configuring the bus tracks or in configuring the multichannel export?

Rednroll wrote on 7/29/2019, 11:52 AM

Where is the knot? In configuring the bus tracks or in configuring the multichannel export?

In the render portion but I may need to revisit and try again....could be user error. When I rendered, I selected MainConcept .Wav 44.1/16bit Stereo. I had the master bus and 3 additional buses (A,B,C). I selected Master, A,B,and C stereo. I only saw one file rendered and was expecting multiple files to be created. What I didn't check was to see if that rendered .WAV file was multi-channel or not, since I recall doing this in the past and it rendering out as separate multiple stereo .Wav files (ie 1 file per stereo bus). So I was expecting 4 stereo files to be rendered out, but it's been a long time since I last had to use this.

I had to do this in the past for advertising studio work where I would layout what were referred to as mix "Splits". Basically Full audio Mix, Sound FXs mix split, Music mix split, and VO mix split.

The splits could be transferred between studios without having to be concerned with DAW/NLE incompatibility issues. So if the client wanted to just replace the voice or section of the voice within an ad spot, they could go to any studio house, just load in the Sound FX, Voice over and Music Mix split tracks and record a new voice or section of voice to go along with the pre-existing music and sound fx mix tracks. It's a pretty common practice in that industry.

Marco. wrote on 7/29/2019, 12:50 PM

This method of multichannel rendering of various audio bus tracks does not output multiple files. It outputs one file with multichannel audio streams.

Using one of script solutions (internal script, HOS, Vegasaur, Trackalyzer) is the only way I'm aware of to output the audio tracks to multiple files.