Comments

Former user 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.

 

http://vasstsoftware.com/freeware/

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 https://tools4vegas.com/.

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.

 

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

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

@Jessariah67
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

@Marco.

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

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

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 user 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.

http://johnrofrano.com/training/video-tutorials/multichannel-render-template-in-vegas-pro/

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.

ito-b wrote on 4/23/2020, 4:43 AM

Hey

Based on your inquiry, I added a track render option to the AudioTrim tool in HappyOtterScripts which can be found at https://tools4vegas.com/.

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.

 

Not sure if it is OK to revive this old thread.

But I have a problem, and even the tool above doesn't seem to fix it.

I have a mix of mono and stereo tracks...when I do a render audio tracks, they either all become stereo or become mono...which is not good.

Now using the tool above, the way I see it, maybe I can select all the MONO first and export as mono, then the stereo and export as stereo...But that implies that I know before hand if my tracks are stereo or mono...and if you have a lots of tracks, it becomes quite tedious....

Is there a way for Vegas to export the mono tracks as mono and the stereo as stereo?

Seems to me this is the way it should work from the start.

wwaag wrote on 4/23/2020, 11:31 AM

@ito-b

Interesting question. What render templates would you be using? If they are the defaults as defined when you first install HOS, it should be possible to do what you want in a single pass. It would be pretty easy to determine the whether a track is considered "mono" or "stereo" based on the number of channels in the first audio event and then use either the default mono or default stereo template.

If you want to select templates other than the default templates, then a two-pass approach seems best. E.g.--on pass 1, select Mono template, and then HOS would render all mono tracks. On pass 2, select Stereo template, and then HOS would render all stereo tracks. Actually, this approach is probably the best since it gives flexibility for the user to select exactly which template to use. E.g. sometimes you might want the 48Khz template or at others, the 44.1Khz template.

If you're still interested let me know and I'll include such an option in the next build.

Last changed by wwaag on 4/23/2020, 11:32 AM, changed a total of 1 times.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

ito-b wrote on 4/23/2020, 12:01 PM

@ito-b

Interesting question. What render templates would you be using? If they are the defaults as defined when you first install HOS, it should be possible to do what you want in a single pass. It would be pretty easy to determine the whether a track is considered "mono" or "stereo" based on the number of channels in the first audio event and then use either the default mono or default stereo template.

If you want to select templates other than the default templates, then a two-pass approach seems best. E.g.--on pass 1, select Mono template, and then HOS would render all mono tracks. On pass 2, select Stereo template, and then HOS would render all stereo tracks. Actually, this approach is probably the best since it gives flexibility for the user to select exactly which template to use. E.g. sometimes you might want the 48Khz template or at others, the 44.1Khz template.

If you're still interested let me know and I'll include such an option in the next build.

OK, here is my suggestions to you:

1. In the audio track selection list, use 2 colors. One for mono, one for stereo, or append (M) and (S) at the beggining, for example, "Track 1 [0, S] My Track", "Track 2 [0, M] My second track"
This will only serve as a visual guide.

2. Now what is *more important* is to have 2 checkoxes near the Audio tracks list with Mono, and Stereo.
Checking the stereo will select all the stereos in the list, checking the mono will select all the monos in the list
This way, the 2 pass approach will be easier.

3. In the audio render options, have a an option (checkbox) that sais "keep Mono and Stereo formats".

-If the user check the "keep Mono and Stereo formats", the extension will use the selected sample rate and bit depth but render mono tracks to mono and stereo to stereo.

The options 1 and 2 will allow the user to quickly identify Mono vs Stereo in the list and quickly select one group or another for processing.

I think this should pretty much cover all grounds.

wwaag wrote on 4/24/2020, 10:57 AM

@ito-b

Sent you a PM yesterday, but you may have not received it. Regardless, here's a screengrab of the latest version.

One button toggles between All, Stereo and Mono tracks.  The other button selects/deselects all.

Since the dropdown list of templates are Favorites that you create it should be easy to select the desired template for rendering.

If you (or anyone) would like to try it before I release the next build, let me know and I'll upload to DropBox for you to download and try and let me know if there are any bugs.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

ito-b wrote on 4/24/2020, 2:25 PM

@ito-b

Sent you a PM yesterday, but you may have not received it. Regardless, here's a screengrab of the latest version.

One button toggles between All, Stereo and Mono tracks.  The other button selects/deselects all.

Since the dropdown list of templates are Favorites that you create it should be easy to select the desired template for rendering.

If you (or anyone) would like to try it before I release the next build, let me know and I'll upload to DropBox for you to download and try and let me know if there are any bugs.

This seems perfect!

Did you ad an option to export to monos or to auto-detect?

Please check my msg in private.

wwaag wrote on 4/24/2020, 3:00 PM

"Did you ad an option to export to monos or to auto-detect?"


The script auto-detects if a Track is stereo or mono. To export in mono, you must select a mono Render Template and add it to the favorites list inside the script.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.