@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"
if($?) {
echo program successful!!!!
pause
}

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 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.

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

@jetdv Took your hint to look at the application window in a powershell script that starts Vegas...

$myVegas=(Start-Process -FilePath "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe" -passthru).ID
if($?) {
Start-Sleep -Seconds 3 
while ( (Get-Process -id $myVegas).MainWindowHandle -ne 0) { Start-Sleep -Seconds 3 }
echo "Vegas has left the building!"
Stop-Process -ID $myVegas
}

Thanks for that!

EDIT... Updated script to end the entire Vegas Process tree... I also lengthened the startup delay before monitoring starts:

$myVegas=(Start-Process -FilePath "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe" -passthru).ID
if($?) {
Start-Sleep -Seconds 10
while ( (Get-Process  -ErrorVariable a -ErrorAction SilentlyContinue -id $myVegas).MainWindowHandle -ne 0) { Start-Sleep -Seconds 5 }
  function Kill-Tree {
      Param([int]$ppid)
      Get-CimInstance Win32_Process | Where-Object { $_.ParentProcessId -eq $ppid } | ForEach-Object { Kill-Tree $_.ProcessId }
      Stop-Process -Id $ppid
  }
Kill-Tree $myVegas
echo "Vegas has left the building!"
}

edit: increased sleep-delay in tree-killing loop to give Windows more time to complete terminations

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.

Make Vegas cheaper each time you renew or get the latest version (like a loyalty dependent scheme- the more versions you have purchased in the past, the bigger the reduction for a new version)

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.

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.

1. Ability to save Keyframe animation from...

A. Pan/Crop

B. Picture in Picture.

2. Better (larger, more prominent) display of 'In', 'Out' and 'Duration' time code / time

There seems to a bug - if you 'click and drag' the cursor it will display the above ('In', 'Out' and 'Duration' ).

BUT, after clicking and dragging - highlighting an area with the Yellow 'In' / 'Out' markers - I get great 'In', 'Out' and 'Duration' numbers. If I click anywhere the Yellow markers themselves remain and the cursor position (time code) shows the current position. Then, if I try to adjust one the Yellow 'In' / 'Out' markers by clicking and dragging, I get nothing. Not even the current position time shows.

3. I'll get back to you on the third.

Thanks

make it into a "it just works" kind of app.

There are probably a lot of us out there who would be brand ambassadors but feel it's impossible to recommend because it's so unreliable. We all know how often we click that save button, and no amount of "what are your system specs and have you updated your drivers..." can erase that reality.

I would guess truly fixing Vegas would involve rebuilding it from the ground up using a modern programming language & best practices.

Personally, I think Vegas is worth it. It's a testimony to the quality of the Vegas timeline editing experience (vs competitors) that I still put up with it given all the frustrations!

I am not a part of the "we" you are mentioning. For "me", I find Vegas just as stable as Resolve Studio or anything else I edit with.

I've recommended Vegas, and those that have tried it, switched. No editor is perfect. No editor is 100% reliable.

Even a total re-write, there is no guarantee it will be 100% perfect with the thousands upon thousands of line of coding.

I still keep hoping for the lock on the tracks , works faster ;-)

Also the pan and crop function could be better

and the Title editor ;-)

Is this still valid? I have a list of improvements to existing Vegas features. Nothing new, just fixes and improvements.

@m3lquixd you might want to wait for the next build/update to see if any/some/many of the fixes and improvements you'd suggest will be implemented.

>you might want to wait

Depends how long that wait is! 😉 New update keeps getting teased at the moment ...

The new update is indeed coming...we know it has been a long wait. We have been taking our time a bit more with updates to VEGAS Pro 20 to ensure what we release is solid. We had too many problematic updates for VEGAS Pro 19.

Less CPU and more GPU pls! (rendering, encoding, playback, plugins etc)

And a decent AI upscale plugin pls. (Coz current AI upscale is basically a pan/crop or zoom tool, not upscale)

For missing plugins: What if Vegas could offer a "safe mode" on opening where it could leave placeholders where the missing plugins belong? The "parameters" of the placeholder could be nothing more than the name & ID of the plugin. Even better if it could list some parameter names & values. Maybe not even a "safe mode", but default behavior which is otherwise harmless. (audio and video)

It is otherwise a real pain to resurrect a project with missing plugins. Just one example: I installed Izotope RX9 and uninstalled RX6. Izotope changed names or IDs for its plugins, so my projects using RX6 are broken.

@bvideo, a "safe mode" sans all plugins would be great! At least plugins can be eliminated from a possibly faulty install of Vegas.

I've had Vegas fail to launch when loading a specific plugin set and had to go to the plugin common folder and/or delete the plugin cache to have it rebuild.

It can be a little vexing for sure.

a) improved playback behaviour even for more professional codecs and raw

b) improved stability

c) improved HDR preview using I/O cards

d) improved grading tools, for both SDR and HDR

b

b!

b!!!

:)

I"m not sure what you call this, but being able to see the FX and composite option without adding the effect. being able to mouse over the option is so much faster then adding and playing back. (the mouse pointer doesn't show)

I"m not sure what you call this, but being able to see the FX and composite option without adding the effect. being able to mouse over the option is so much faster then adding and playing back. (the mouse pointer doesn't show)

+1