How to install

  • Shut down Vegas
  • Unpack the zip file into C:\ProgramData\Sony\Vegas Pro\
  • Start Vegas
  • Enjoy =)

A quick overview

The main piece is a little cutie called RegionRender. It’s (obviously) a batch renderer, but made for a multi-user environment. Any person who opens a RegionRender-enabled Vegas project and runs RegionRender will spit out the same files, in the right place, in the right format, without having to know anything about target files or directories. There are some companion functions to quickly “wrap” events on the timeline in regions, give them the correct name, and so on.

Setting a project up for use with RegionRender is as simple as going to the Scripts menu and running a script called Set up project for RegionRender. Please be aware that the markers for your settings will appear where you’ve placed the playback cursor.

RegionRender stores its settings as special markers along the timeline, plain for all to see. This enables you to render, say, 10 regions in mono to c:\sounds\mydir, and the next 20 regions to c:\sounds\myotherdir as 64 kbps mp3-files. RegionRender can also work in stem mode, grouping renders either on track name or bus name, so that you can quickly render songA-drums, songA-bass, songB-drums and so on. Stem mode is also a local setting, meaning you can switch it on and off for different parts of the same project.

Another set of tools deals with markers in files. If, like me, you have long wave files with several takes in one, you probably do what I do, which is to add markers saying “big,” “smooth,” “crackly” and so on at each take. In TeeVegas lingo, this is called MetaMarkers, and we can use this in a variety of ways: We can split events based upon metamarkers, “jump” between them (moving the offset), or randomize between them to quickly create variations. Additionally, if you have multiple recordings of the same event, TeeVegas can copy markes between media files. Risky, but useful.

Finally, a minor but helpful gem is a tool called Clone and replace media. In multi-user environments, you’re likely to encounter stock samples, stored on a central network drive, that you want to tweak destructively, but you don’t want to break any other projects that might be using the same file. Running “Clone and replace media” will create a new copy of the source media, and then re-direct all references in your local project to that media file. This creates a unique copy that only your particular project knows about, and you’re free to edit it in any way you want. As a bonus, your tweaked file will appear right next to the original, so that other users who browse the directory can get some extra inspiration.

Those are a few highlights of TeeVegas. Hope it sparked some intrerest =)