Just a quick note on the way to establish an optimized workflow …
Now that Debugmode's FrameServer works pretty fine with Vegas Pro 12 and 13, I was looking for a way to feed HandBrake via the FrameServer. And it actually works if:
- You install AviSynth and make the FrameServer signpost AVI to an AVS AviSynth file.
- You install both AVS2AVI and Pismo File Mount and use these tools to turn the AVS file to an AVI which can be read by HandBrake.
To boost such a workflow I created a batch file which – once you exported a Vegas project via FrameServer – will automatically open HandBrake and feed HandBrake with the FrameServer's output.
Once I'll have optimized this workflow and if anyone interested in details, I could try to make a description translated into english and publish it on my website. Until then I just wanted to let you know: Yes, there is a way to send a Vegas project to HandBrake using the FrameServer. :)
Now that Debugmode's FrameServer works pretty fine with Vegas Pro 12 and 13, I was looking for a way to feed HandBrake via the FrameServer. And it actually works if:
- You install AviSynth and make the FrameServer signpost AVI to an AVS AviSynth file.
- You install both AVS2AVI and Pismo File Mount and use these tools to turn the AVS file to an AVI which can be read by HandBrake.
To boost such a workflow I created a batch file which – once you exported a Vegas project via FrameServer – will automatically open HandBrake and feed HandBrake with the FrameServer's output.
Once I'll have optimized this workflow and if anyone interested in details, I could try to make a description translated into english and publish it on my website. Until then I just wanted to let you know: Yes, there is a way to send a Vegas project to HandBrake using the FrameServer. :)