Video Pro x4 sometimes can't open becuase it says it's running aready...but i closed it....?

kw_petey wrote on 3/24/2012, 8:39 AM

it seems after closing vpx4, when i started the program the next day it said it was running,  but i had closed it.  this has happen almost every close and open.    any updates. or is the x after saving the project not the way to close the program

Comments

emmrecs wrote on 3/24/2012, 11:53 AM

I've seen this message a couple of times after I've closed the program following a project crash (and the message asking the user to save the project using the .mvd suffix.)

The solution was to open Task Manager (I'm on Win 7) highlight the videoprox.exe entry and use the "End Task" button to close the unwanted running version.

However, I certainly do not see this message as often as your post suggests.  Do you literally mean you receive it every time you restart the program, even the next day?  If so, I would seriously suggest completely rebooting your computer; even do a total shut-down, wait about 20 seconds and then re-boot.  That should clear any still-running version of the program!  If you still see the message, and you're sure the program actually is running (check in Task Manager) then VPX must be set to start up with Windows!  I don't know if that's even possible.

Your method of closing the program (via the red X) is what I use almost all the time so should not be causing this.  In the worst case scenario you may have to Repair or completely  uninstall and reinstall the program.

Jeff 

Last changed by emmrecs on 3/24/2012, 11:53 AM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

johnebaker wrote on 3/24/2012, 1:17 PM

Hi

To add to Jeff's reply - also look in the  Processes tab for videoprox running.

Often the task is finished but the process has not stopped and this will cause the problem you are having - I sometmes get this happening with Firefox for no explained reason.

John

Last changed by johnebaker on 3/24/2012, 1:17 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

kw_petey wrote on 3/24/2012, 1:46 PM

I've seen this message a couple of times after I've closed the program following a project crash (and the message asking the user to save the project using the .mvd suffix.)

The solution was to open Task Manager (I'm on Win 7) highlight the videoprox.exe entry and use the "End Task" button to close the unwanted running version.

However, I certainly do not see this message as often as your post suggests.  Do you literally mean you receive it every time you restart the program, even the next day?  If so, I would seriously suggest completely rebooting your computer; even do a total shut-down, wait about 20 seconds and then re-boot.  That should clear any still-running version of the program!  If you still see the message, and you're sure the program actually is running (check in Task Manager) then VPX must be set to start up with Windows!  I don't know if that's even possible.

Your method of closing the program (via the red X) is what I use almost all the time so should not be causing this.  In the worst case scenario you may have to Repair or completely  uninstall and reinstall the program.

Jeff 

I should have known better,   X hits the spot.  Jeff, thanks Because our system is running 24/7 never thought to reboot it.   REBOOTING Solved the problem.

gandjcarr wrote on 3/24/2012, 6:35 PM

Hi, Both johnebaker's and emmrecs's answers are spot on.  If you are reluctant to go and stop the process, just reboot your system, and all will be fine again.