KillVegas -- 2 simple apps for killing Vegas processes

wwaag wrote on 6/25/2019, 11:32 AM

Tired of killing Vegas using Task Manager, especially for those old processes that stay in memory? There was a recent thread discussing the problem https://www.vegascreativesoftware.info/us/forum/vegas-remains-in-memory-like-a-bad-smell--115656/?page=1

Until the problem is fixed in Vegas or for use with older versions, here's a simple app that may be of value. It kills all instances of Vegas that are running, including those that are running after Vegas has been closed. Although I haven't tested it, it can probably be used after a Vegas crash.No installation is required. Just copy it to a location of your choice and create a shortcut on your Desktop.

Here's a second app based on Grazies' suggestions (next post).

Here's what the script does: 1) saves the current project; 2) closes Vegas; and 3) waits 2 secs and then kills the Vegas process if it still remains. Note that this kills the process ONLY for the project that is being closed--not all Vegas processes like the first app. To use, download and unzip the 3 files into your Script Menu folder. E.g. for Vegas 16, it is usually found here: "C:\Program Files\VEGAS\VEGAS Pro 16.0\Script Menu". Please note that this script works only for Magix versions.

Let me know if there are problems.

Edited: 5/4/2020 Both scripts are now available for download in the HappyOtterScripts Free Tool library. Here's the link. https://tools4vegas.com/library/

Last changed by wwaag

AKA the HappyOtter at https://tools4vegas.com/. 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.

Comments

Grazie wrote on 6/25/2019, 11:44 AM

@wwaag - “Necessity is the mother of invention.” Erm, if it was connected to the Save function and then that grouped as a Script, we could even have it as a Toolbar of Keystroke. Waddyah fink peoples?

“Save and Kill”

Last changed by Grazie on 6/25/2019, 11:45 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Marco. wrote on 6/25/2019, 12:46 PM

Thanks a lot, wwag!

I now made an AHK script which starts the KillVegas app, clicks the OK button and then starts Vegas Pro. Works fine.

Grazie wrote on 6/25/2019, 12:58 PM

@Marco. - Yes please! 😍

wwaag wrote on 6/25/2019, 1:47 PM

@Grazie

It would be pretty simple to write a script as you suggested. Probably better to have the script save and close Vegas normally and then run the kill app after a set number of seconds (actually you launch the kill app before saving and closing). I have no idea how long Vegas usually takes to save and close normally. It's pretty easy to insure that the Vegas instance killed is the one that you are closing. The danger of the current app is that it kills ALL instances which may not be what the user wants.

If there is any interest, I can probably do this.

AKA the HappyOtter at https://tools4vegas.com/. 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.

Grazie wrote on 6/25/2019, 3:21 PM

@wwaag - Yes, the order of Vegas Leaving the Building is truly important and also "I have no idea how long Vegas usually takes to save and close normally".

 

karma17 wrote on 6/25/2019, 8:57 PM

This is great. Thanks for sharing.

wwaag wrote on 6/26/2019, 3:06 PM

A new tool has been added based on Grazie's suggestion. It has been added to the first post in this thread. Comments are welome.

AKA the HappyOtter at https://tools4vegas.com/. 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.

Grazie wrote on 6/26/2019, 11:10 PM

@wwaag - “Here's what the script does: 1) saves the current project; 2) closes Vegas; and 3) waits 2 secs and then kills the Vegas process if it still remains.”

@wwaag - I’m gonna give the S-C-K Script a twirl ‘n whirl this morning. Might I suggest something more than 2 Seconds? The initial Save might need to “give way” to the two other Saving Tools, The Vegas Auto Save and the one I use and that’s Edward Troxel’s AutoSave marvellous Script. Or maybe I’m making more out of this than is necessary. Does/will the Save procedure allow other active scripts to close? I worry 🥴 ! But in any event, Waggle, this is a great Utility to have, whilst the VegasPro Engineers try and kill this most “unfortunate” Bug.

Wayne, thank you.

Grazie wrote on 6/27/2019, 12:03 AM

@wwaag - Well, slap me sideways with a Bucket o Herring!'- Stunning. LicketySplit GAWN! OK, haven't yet tried multiple instances of VP, yet, but immediately after clicking on the big RED X , I was wanting to have that reassuring "Save Changes?" or "Do you wish to save changes?" coming straight into my face. Could you add that? Or should that appear from the SAVE routine of Exiting VP? - OOOooo, here's a thought, IF you assumed that this SHOULD or would've been there, is it possibly we've stumbled on the non-kill BUG itself?

So, that's a BIG FAT X from me:

Great work.

Grazie wrote on 6/27/2019, 12:10 AM
Probably better to have the script save and close Vegas normally and then run the kill app after a set number of seconds (actually you launch the kill app before saving and closing).

@wwaag - Ah, so you do believe that VP is closing "normally". And could "normally" also include that wish to Save Changes?

I have no idea how long Vegas usually takes to save and close normally.

@wwaag - Or just what routine is being used to give that Save Changes warning.

Interesting . . .

 

 

Last changed by Grazie on 6/27/2019, 12:10 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Grazie wrote on 6/27/2019, 12:41 AM

@wwaag - Bashing the SCK and your Script is working nicely. I have launched a Veg that has NewBlue Titler Pro which, although a Plug-in, has to function as a Standalone, closes neatly and disappears from Task Manager in an orderly way too. I haven't yet tested NBTP functioning and then SCK, but it appears stable on SCK.

wwaag wrote on 6/27/2019, 7:38 AM

@Grazie

At the moment, the dialog only appears if the project is "untitled". Otherwise it always saves, regardless if there are project changes or not. I'll take a look at adding the entire dialog. Its easy enough to change time, but to what? 5 sec?

AKA the HappyOtter at https://tools4vegas.com/. 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.

Grazie wrote on 6/27/2019, 8:28 AM

Yes, maybe 5 seconds. But I’d have no idea how long.

wwaag wrote on 6/28/2019, 10:02 AM

Just uploaded a new version. The save dialog is now always opened and the delay time has been changed to 5 sec.

AKA the HappyOtter at https://tools4vegas.com/. 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.

Grazie wrote on 6/28/2019, 4:08 PM

@wwaag - Is it not possible to do the "Save Changes?" dialogue thing? Because now there's the option to "Save As?" - even if I have or haven't made changes:

Cheers - G

wwaag wrote on 6/28/2019, 4:25 PM

There is no "Save Changes" dialog option in the scripting API. The SaveAs dialog pops up with the project name, unless it has never been saved--then "untitled". Just click "save". It will overwrite the existing project file, the same as clicking yes to "Save Changes" if you close a project with any unsaved changes.

AKA the HappyOtter at https://tools4vegas.com/. 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.

Grazie wrote on 6/28/2019, 4:35 PM

There is no "Save Changes" dialog option in the scripting API.

@wwaag - Oh bother . . . yeah, I guessed as much. Pity, 'cos sometimes I really DON'T make any changes, just Preview or stand-back in awe at my abilities - well, somebody has too. 😉

AlanMintaka wrote on 8/14/2019, 3:47 PM

...
Until the problem is fixed in Vegas or for use with older versions, here's a simple app that may be of value. https://www.dropbox.com/s/elyaf9s2b3sut59/KillVegas.exe?dl=0
...
Let me know if there are problems.

Hi wwaag,

I get an "Unhandled exception: index out of bounds" error when I try to run killvegas.exe.

Info:

killvegas.exe v. 1.0.0.0
VegasPro 16 build 424
Windows 7 Home Premium

The first time I ran it, the Task Manager was already open so I could monitor the status of the VegasPro process. After the error, I tried killvegas again without opening the Task Manager and got the same result, so it looks like having the Task Manager open didn't cause the error.

Any ideas what might be going wrong here?

Thanks for your time,
Alan Mintaka

wwaag wrote on 8/14/2019, 8:33 PM

@AlanMintaka

Sorry about that. The wrong file had been uploaded to dropbox. Here is the corrected link. https://www.dropbox.com/s/d06pv81u4qg01gm/KillVegas.exe?dl=0

Just be aware that this kills "all" open instances of Vegas. I've corrected the link on the first post on this thread. Thanks for alerting me.

AKA the HappyOtter at https://tools4vegas.com/. 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.

AlanMintaka wrote on 8/14/2019, 11:15 PM

@AlanMintaka

Sorry about that. The wrong file had been uploaded to dropbox. Here is the corrected link. https://www.dropbox.com/s/d06pv81u4qg01gm/KillVegas.exe?dl=0

Just be aware that this kills "all" open instances of Vegas. I've corrected the link on the first post on this thread. Thanks for alerting me.

Thank YOU, wwag for posting the new version! It works great for Vegas Pro 16.

BTW it also works for Vegas Pro 17. I just upgraded from 16.424 hoping that the memory-resident problem had gone away, but the bug remains..... At least your app is there to remove the hassle of constantly killing the process in the Task Manager.

So, Magix, I'm back where I started, now with Vegas Pro 17. Any fixes for the problem on the horizon?

 

Steve_Rhoden wrote on 11/27/2019, 9:48 AM

Hey Wwaag,

Not to be a bother, but could you please modify the "KillVegas" script so that when i click
the "X" on the toolbar it immediately kills all instances of Vegas. No save as dialogue pop-up,
no warning, nor anything, just immediately kills everything Vegas.
Thank you so much, would really appreciate this added tweak.......

Grazie wrote on 11/27/2019, 9:55 AM
No save as dialogue pop-up, no warning, nor anything, just immediately kills everything Vegas.

@Steve_Rhoden - Wanna borrow my Wrench?

 

Steve_Rhoden wrote on 11/27/2019, 9:57 AM

Sure Grazie, if you have it set that way, sure!

Grazie wrote on 11/27/2019, 10:08 AM

Ah! Mine is set for using with my Over-Priced GPU Card. . . . I'll turn off Acceleration and then get my people to talk to your people.