Comments

rs170a wrote on 9/23/2008, 9:05 PM
There should be a Batch Render script that comes with Vegas.
Convert each event to a region (double-click it and press 'R'), run the script and select "Render Regions".

Mike
Laurence wrote on 9/23/2008, 9:15 PM
There is a "convert events to regions" script too. You can run the "convert events to regions" first and the batch render script with the "render regions" option selected.
kk5551 wrote on 9/24/2008, 6:58 AM
Any ideo where to find the "convert events to regions" script. Looked on Creative and vasst, but no luck. Thank you for your help.
rs170a wrote on 9/24/2008, 7:23 AM
It is on the VASST site.
It's called Add Regions to Events.

Mike
Jessariah67 wrote on 9/24/2008, 7:24 AM
Create Regions from Event Names

Batch Render with Regions option (I love this one because it doesn't give the long chain in the file name - the files will have the region name only).

KH
farss wrote on 9/24/2008, 7:29 AM
Assuming you haven't edited the clips or added any FXs to them the best tool for the job in the Multirenderer in Peachrock's Veggie Toolkit.
With it you can simply select all the clips you want to convert. Select an output folder, naming convention and codecs / templates and let it do it's things. I use it a lot to convert huge amounts of .wav files to .pca.
Of course you can also use it batch render any number of Vegas projects.
If something does go wrong in the midst of your rendering or you need to use the machine for something else for a while you can pause the process. The script keeps track of what's done etc for you.

Bob.
Robert W wrote on 9/24/2008, 7:45 AM
Am I alone in thinking that batch rendering is one of the most overdue features to be integrated into Vegas's core?
rmack350 wrote on 9/24/2008, 7:54 AM
No, you're not alone. This is an area where scripting has allowed SCS to put off adding a batch rendering tool. Comes a certain point where SCS ends up in competition with script programmers too.

Rob
Jessariah67 wrote on 9/24/2008, 8:03 AM
Since they're free, it would be nice to have ONE place where you can get them all. (At least, I don't know of a place like that).
farss wrote on 9/24/2008, 8:31 AM
Well the Veggie Toolkit isn't free but damn good value for money.
I have no problem paying people to write code that I make a dollar from using. I earn most of my income from writing code so I guess I have a vested interest in that concept.
At the same time I don't have a problem at all with those who donate their work to the community, I too have done that for my paying clients and even used the shareware model with some success.

VASST has a repository for free scripts.
The one I use most is Add Markers at Intervals. I've modified it so I have different scripts for different intervals, very handy.

Bob.
jetdv wrote on 9/24/2008, 10:59 AM
There are also many free scripts on my site as well.
kk5551 wrote on 9/24/2008, 11:58 AM
"Batch Render with Regions option" (I love this one because it doesn't give the long chain in the file name - the files will have the region name only).

How do you intall this as a script. I am used to just using the JS files. I agree with you that this would be great to not have the long chain file name. Thanks
jetdv wrote on 9/24/2008, 12:38 PM
All standard scripts can simply be placed in the Script Menu folder. These include .js, .cs, and .dll. Commercial scripts would have an installation program.
johnmeyer wrote on 9/24/2008, 1:10 PM
Years ago, I modified the Batch Render GUI script so the region names would be used as the file names in the resulting renders. Here's a link to the script:

Batch Render GUI

The link is good for seven days. Put this in your scripts folder, as Ed (jetdv) has recommended. It will do exactly what you have asked for. I just used it for several projects two days ago. I'm pretty sure it will work in Vegas 8.x. I still use 7.0d.
rmack350 wrote on 9/24/2008, 6:04 PM
Free is nice but it's definitely worth the money to pay for polished products that bring a lot of functionality to the table.

It just becomes a little awkward when a script does something that ought to be part of the core program (Like batch rendering, log importing, etc.)

Rob
johnmeyer wrote on 9/24/2008, 7:44 PM
It just becomes a little awkward when a script does something that ought to be part of the core program In what way is it awkward?

Once a script is installed, it operates as an extension of Vegas. In the case of the various batch scripts -- including the one I posted which is an extension of the one shipped with Vegas -- I honestly don't see how having it "built in" to Vegas would in any way feel, operate, or look any different at all. In addition, with scripts, we have dozens of alternatives to choose from instead of just one built-in option. In particular, there are scripts which will render all media files in a given folder; other scripts which will render all VEG files in a given folder; some will render just the regions; some render the entire project to as many different formats as you want.

Virtually no function built into Vegas -- or Premiere -- is going to do all these things. I don't use Premiere but I would bet that its batch feature doesn't do everything that I just described.
Rosebud wrote on 9/24/2008, 10:25 PM
Also, you can try my script (VP8 only) Proxy Stream.