Offline/background rendering?

michael-harrison wrote on 5/8/2020, 11:03 AM

Is there any wait to launch VP such that it will bypass all the gui startup and render a specified project using a particular render target from the command line?

I'd love a way to have a headless machine just be a render beast without my having to interact with the gui.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

Comments

michael-harrison wrote on 5/17/2020, 9:09 AM

I haven't had a chance to try these but while looking through the pdf manual I ran across this info. Putting it here in case anyone else is looking for something similar

 

RUNSCRIPT
Starts VEGAS Pro and runs the specified script.
Examples:
Vegas120.exe /RUNSCRIPT "C:\CustomScripts\ScriptName.cs"
—or—
Vegas120.exe /SCRIPT "C:\CustomScripts\ScriptName.cs"


SCRIPTARGS
Starts VEGAS Pro and passes the specified arguments to a script.
Example:
Vegas120.exe /SCRIPTARGS "
<argument>
" /SCRIPT "<script path>"
For more information about script arguments, please see the VEGAS Pro Scripting API.

 

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

jetdv wrote on 5/17/2020, 4:44 PM

I wrote a script used by Sony Music many years ago. They would fire off Vegas using the /SCRIPT option to also fire off my script. That script would read a text file off of their system, load the proper files, apply the proper effects as needed, and do a few other tasks they specified. Then it would render out the results, write another file for their system to read stating it was finished, and then exit Vegas. Their system would then put another control file in place and the process would start all over again. I can't tell you how many times that process was used. It was a fully automated process.