From Vegas to HandBrake

Marco. wrote on 8/14/2014, 4:11 AM
A while ago I dropped some postings about a simplified workflow to involve HandBrake for an AVC encoding starting from a Vegas Pro project (see here).

I know there are some other valuable workflows which describe how to use x264 (using HandBrake or similar tools). I made this certain one for my personal use because it needs only one mouse-click in Vegas Pro to get the current project opened in HandBrake. See this short YouTube video which demonstrates the ease of use (intentionally there is no sound in the YouTube video):

After other Vegas Pro users said they like the way this workflow works I decided to share it with anyone who likes to test it – so if you do: See the description on (sorry for the poor English). It should work fine for Vegas Pro 13, 12 and maybe even 11 (64 bit). It won't work on Vegas Pro versions prior to 11 nor on 32 bit systems (64 bit only).



PeterDuke wrote on 8/14/2014, 5:11 AM
"sorry for the poor English"

Your English is excellent! I wish my German came even close to your English.

And thanks for the post.
Marco. wrote on 8/14/2014, 5:15 AM
Thanks for your kind words. :)
Grazie wrote on 8/14/2014, 6:00 AM
Marco - WELL DONE! - Stunning results you show. What are the Toolbar Bar Icons you are showing and clicking on? Your English is purfeckt! - Do change "risc" to "risk". Or is that IT speak?


Marco. wrote on 8/14/2014, 6:09 AM
These are the icons belonging to the Vegas scripts used for this workflow. The icons are in the folder "frameserver_scripts", so if you downloaded and copied the folder, these icons automatically will be coupled with the scripts "Send2HandBrake" and "unmount".

"Or is that IT speak?"

No IT thingy. I changed it now. Thanks for the hint.
musicvid10 wrote on 8/14/2014, 7:45 AM
I'm going to see if I can do this on VP8.
I think you should post the directions on the Handbrake forum in the Tiki Bar thread. The frame serving topic comes up from time to time over there.
Marco. wrote on 8/14/2014, 8:47 AM
Good idea. Will do that asap.

I think the core behind this certain workflow is rather simple: Frameserving. And because this arises two issues – video level and the length of audio: AviSynth for correction purpose. And because HandBrake don't take the pure FrameServer AVI nor the AVS file: File mounting.

The certain way I use it in "Vegas2HandBrake" is just because I'm incredibly lazy ;) So using a script and some batch files does rest of the magic.

There are some other useful combinations possible like serving from one Vegas instance to the next or from Vegas to DVD-A just for using a better (lanczos or spline) scaling (though there is another issue then because buildung the audio peaks will last veeery long time then).

wwaag wrote on 8/14/2014, 1:18 PM
Marco. Great work. This really will be a time-saver. Installed in V13--worked perfectly the first time. Your guide is very well-written and easy to follow.

One note. I did not install Avisynth 2.5.8. I already had version installed on my system. No problems.


Added: Just rendered a four minute job using 2-pass encoding in Handbrake. The audio was about 10 sec shorter than the video in the project. Everything was correctly encoded in Handbrake, except for the addition of a single frame at the end, which seems trivial.

AKA the HappyOtter at System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Erni wrote on 8/15/2014, 8:55 AM
Hi Marco, thanks for you work.

But, here no way.

Can´t see the scripts. I copy the files to many folders (folders in Vegas Pro, My Documents, App Data, etc when I see another script files). I enter in the Internal menu of Vegas Pro 13 and set the route manually, but no luck.

Maybe the problem is the spanish version of Win 7 Ultimatte. The folders are bilingual (Program files and Archivos de programa are the same)

I use an SSD (120GB) for partition C and the programs, but I route Documents to another disc. Maybe the problem is here. I don't now.

Thanks anyway.

Marco. wrote on 8/15/2014, 9:29 AM
Erni, to get the two scipts "Send2HandBrake" and "unmount" available for customizing the Vegas Pro toolbar there is only one valid path where the folder "frameserve_scripts" must be copied to. It's the folder "Script Menu" in the main program folder of Vegas Pro 13. It's where all the scipts listed via Vegas' menu "Extras/Scripting" are located. No other path would work.

Assumed you installed Vegas Pro onto C:\ – for Windows 8 the correct path is:

C:\Program Files\Sony\Vegas Pro 13.0\Script Menu\

I think it's the same for Windows 7 (the language used in Windows 7 differs here too so I can't be sure for the english version or other language settings). There's been a typo in the path description on the VegasVideo website which I just corrected (sorry for that).

Just to be sure:
Only copying the folder "frameserve_scripts" will not yet make the two scripts available in the toolbar. You also have to customize your toolbar via "Options/Customize Toolbar".
Byron K wrote on 8/15/2014, 4:24 PM
Hi Marco,
Trying to get this going on Vegas 12. I get to the Open menu "File/Render as" section and don't see it in the list.

- Open menu "File/Render as".
- On top of the renderer list select "DebugMode FrameServer" as encoder and "Project Default" as render preset.

When I install the Vegas 12 version, the installation Options has a bunch of check-boxes, do I select Sony Vegas (64-bi) Plugin?

winrockpost wrote on 8/15/2014, 5:03 PM
Thank you Marco, not sure how the inner workings come together.... but works great!! Only tried it in v13 , not using 13 for editing yet, but can open my v12 finished product in 13 and use your toolbar icon and boom!! awesome !
thanks so much for sharing, amazing work.
musicvid10 wrote on 8/15/2014, 5:19 PM
Byron, Debugmode is an AVI format.
Marco. wrote on 8/15/2014, 6:49 PM
Yes, it frameserves as AVI, but the FrameServer will be listed as its own separate renderer in Vegas Pro.

"When I install the Vegas 12 version, the installation Options has a bunch of check-boxes, do I select Sony Vegas (64-bi) Plugin?"

Yes, exactly.

Byron K wrote on 8/16/2014, 7:30 PM
I uninstalled it and re-installed as administrator but still dont see Debugmode in the Render As menu:

Is the default Vegas plugin path OK?

Thanks in advance for any assistance.
relaxvideo wrote on 8/17/2014, 1:26 AM
But i prefer ripbot264.
Any tips, how should i modify your method?

Frameserver 2.15 doesn't work with Vegas11?
This audio bug drives me crazy :(


#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas21 latest

Marco. wrote on 8/17/2014, 5:18 AM
Mmh, maybe first check musicvid10's hint. Though the latest FrameServer version should work different, maybe in some cases it appears the former way (as regular AVI codec).

Then the FrameServer renderer would be hidden at "Video for Windows (*.avi)" in the renderer list. Select one of the AVI presets, open the "Video format" drop-down list and check if it is there. If so – the given Vegas2HandBrake workflow would not work.

Are you sure you installed FrameServer version 2.14 (because you use Vegas Pro 12)? If you installed FrameServer version 2.15 it would not appear in Vegas Pro 12.
Also be sure you selected to correct path (to Vegas Pro 12) when installing the FrameServer.
musicvid10 wrote on 8/17/2014, 7:29 AM
My memory was faulty. Shows up as its own format in pro 8.
Marco. wrote on 8/17/2014, 8:09 AM
According to Satish's info you need FrameServer version 2.14 for Vegas Pro version 12 and below. 2.15 is for Vegas Pro 13 only.

If you only want to correct FrameServer's audio bug, maybe you only need to involve AviSynth. I don't know if ripbot264 can read the AviSynth AVS file. If not, also involve file mounting via Pismo File Mount and AVFS.

If you want to adapt the automated workflow to ripbot64 instead of HandBrake – don't know if this would work. Referring to my Vegas2HandBrake workflow, at least there should be no need to modify the Vegas scripts, AviSynth file nor the EXE files. Only the batch file "start_vegas2handbrake.bat" needs some modifications. It's these two lines:

start handbrake "C:\frameserver\vegas.avs\vegas.avi"
tasklist | findstr /i "Handbrake.exe"

But I don't know how exactly you would need to replace the commands. Maybe only replace "handbrake" by "ripbot264" (first line) and "Handbrake.exe" by "ripbot264.exe" (second line).

Also that command of the second line (thus the last part of the automation workflow) would only work if there is a way to let ripbot264 automatically shutdown the way HandBrake does. Maybe for ripbot264 it would need quite a different approach.
musicvid10 wrote on 8/17/2014, 9:53 AM
Is this script working on 64-bit only?
I am running Pro 8 on Vista 32 with Frameserver 2.14 installed and working.

relaxvideo wrote on 8/17/2014, 9:53 AM

" I don't know if ripbot264 can read the AviSynth AVS file"

Yes, it can :)
I always use my AVS file, for correct colorspace handling:



#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas21 latest

Marco. wrote on 8/17/2014, 10:00 AM
Mmh, I never checked with 32 bit. I think it only works on a 64 bit system. Sorry.
Marco. wrote on 8/17/2014, 10:05 AM
Then to overcome the FrameServer's audio bug, all you need to do is to add 1 second to your current Vegas Pro project and add this line into your AviSynth script (which will trim that 1 second frameserve garbage again):

Trim (0, FrameCount-1-Floor(FrameRate))
musicvid10 wrote on 8/17/2014, 10:18 AM
Well, I guess I'll find something else to do this morning . . .
If you compile it for 32 bit I'll be interested to try.
Marco. wrote on 8/17/2014, 11:02 AM
I just see it's not only the 32 bit version which prevents the two EXE files from working, it is also the Vegas Pro renderer which works different in versions before 11. So you could use this workflow only on 64 bit systems with Vegas Pro 13, 12 and maybe 11.

But maybe at least you could benefit from using AviSynth and Pismo File Mount to frameserve from Vegas Pro to HandBrake.