What are the top 3 things you want to see the development team focus on improving first? Keep in mind this is different than new feature requests, this is discussing improvements to what is already there.
@Howard-Vigorita This can already be done. You can tell VEGAS to run a script upon startup. You just start VEGAS from a batch file something like:
"c:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe" -SCRIPT:"d:\StartupScript.cs"
Plus, Custom Commands can monitor for "AppInitialized" which would occur on the startup of VEGAS and also monitor for "AppWindowClosing" and "AppWindowClosed" which might be useful for an exiting script. I'd have to do some testing to verify exactly how these event handlers work.
What are the types of things you're wanting to do on startup and exit?
Thanks... @jetdv Sure if there was a way, you'd know. If I knew how, I'd run a startup script to monitor the main Vegas app window and issue this command as soon as it closed:
@Howard-Vigorita A script is a run and done. A custom command stays running all the time. So it seems this would need to be part of a custom command instead of a script. However, the extension would need to really make sure VEGAS was exiting before trying to run this command.
What happens if you put both my line (don't even need the 'SCRIPT:... part) and my line in the same batch file? Then when you want to start VEGAS, start it using that batch file instead? Will the batch file wait until you exit VEGAS to run the next line? Or would it never run because it "thinks it's still running"? Looks like there's potentially a lot of variables here.
I do have a powershell script to start Vegas which 'almost' works. Problem is Vegas doesn't issue its exit code till it exits memory long after it closes the app window. Only seems to do this on my laptops with Nvidia+Intel igpus. This is the powershell script:
Start-Process -Wait -FilePath "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe"
echo program successful!!!!
Only complication I can think of is the perfect kill should only hit the one instance of Vegas if there were more than 1.
Ditto on Performance/stablity. (of course, and thanks fr0sty/team for "getting it.")
GUI: Key Commands forSelectnext/previous Eventand simlarly, Event above/below. So one can Keep a PanCrop/FX window open (you can do this with mouse select, but needs Key command). Also Programmable Mouse options.
Range select as in Samplitude - IOW, can lasso-select any time-line rectangle, verically/horizontally, without necessarily selecting whole events IOW, cuts on the frame, not event edge. Options for audio follow (selected range) or video only. That selected range can be deleted/copied/moved any direction, and maybe compressed/ expanded with/without time ripple
GUI: Key Commands for Select next/previous Event and simlarly, Event above/below. So one can Keep a PanCrop/FX window open (you can do this with mouse select, but needs Key command). Also Programmable Mouse options.
Would also be useful for color grading at the event level.
1] Ability to edit multiple keyframes in one go. (If VEGAS can already do this, how?)
2] Get rid of every instance of the Vista open/save dialog.
3] Use different variables for the import media and open/save project files. I keep having to navigate from my projects folder to where I keep my media, sometimes involving drilling down through several layers of folders.