Unable to Exit or Terminate ProX 13

Audrey2 wrote on 11/22/2021, 8:48 PM

After updating to Pro X Vers. 19.0.1.123 (UPD3) I cannot exit the program - Clicking on "Exit" or alt F4 closed the Time Line area and locks the rest of the program. I can load and use other programs over the top of ProX13. The only way to exit is to turn off computer. Prior to the update I updated Windows 10 and all drivers. I am using

Dell XPS 15 (9500) laptop ,  Intel i7-10750H CPV , 16Gb memory
1Tb SSD ,  NVidia GTX 1650 Ti 4Gb

Thanks

Comments

Audrey2 wrote on 11/22/2021, 10:55 PM

Just found this problem was brought up by Niels-Srensen on 8/3/2021, was it resolved by Magix or is it still ongoing

Thanks.

emmrecs wrote on 11/23/2021, 3:49 AM

@Audrey2

For some, though not all users, this problem still exists! Magix is aware but is struggling to find the cause, apparently.

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Sound Forge Audio Cleaning Lab, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

Audrey2 wrote on 11/23/2021, 4:58 AM

Thanks Jeff, I will contact Magix and let them know I also have this problem , was beginning to think it may have been yet another problem with the laptop. Thanks

 

browj2 wrote on 11/25/2021, 2:18 PM

@emmrecs

Hi Jeff,

I have the same problem with VPX13 v19.0.1.123. The only way to close VPX, short of rebooting, is with the Task Manager. Thus trying to update to 19.0.1.128 is impossible as ending the task also closes the window for updating after having done the download.

Is there somewhere that I can look for the downloaded patch file and run it?

Otherwise, I can't see how Magix can fix the problem. If a patch can't be run, the problem can't be fixed.

Thanks,

John CB

John C.B.

VideoPro X(12); MEP2022 PPremium; MM2022 Premium; see About me for more.

Desktop System - Windows 10 Pro 21H1; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; dual monitors - LG 4K 27" main, HP 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2

CubeAce wrote on 11/25/2021, 3:11 PM

@browj2

Hi John.

Try temporarily changing your project import folder and drive and then don't save the project you have open. Then reboot VPX and see if it clears the problem. I say this because the problem seems to be linked to older projects that have already been loaded and come up in the opening list. I'm not sure it will work but may be worth trying.

Ray.

 

Windows 10 Enterprise. Version 21H1 OS build 19043.1348. Direct X 12.1 Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 30.0.101.1069 with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for C: drive backup 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal projects 1 for Library clips/sounds/music/stills./backup of working projects. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 472.39. 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.104. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

browj2 wrote on 11/25/2021, 3:58 PM

@CubeAce

Hi Ray,

I tried that without success.

I also tried deleting the ini file so that there are no existing MVP files on the list. Normally, a new ini would be created automatically. However, I still can't exit, so no new ini file.

Any other suggestions?

Thanks,

John CB

John C.B.

VideoPro X(12); MEP2022 PPremium; MM2022 Premium; see About me for more.

Desktop System - Windows 10 Pro 21H1; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; dual monitors - LG 4K 27" main, HP 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2

CubeAce wrote on 11/25/2021, 4:37 PM

@browj2

Hi John.

Afraid not. I only got out of that problem by making an old project able to close in the new version of MEP or opening a new project that allowed me to fully close the program. I was wondering if changing the import or export folders would work as well as it would have (I thought) made the program forget opening previous projects.

Obviously my thought process is wrong.

Ray.

Windows 10 Enterprise. Version 21H1 OS build 19043.1348. Direct X 12.1 Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 30.0.101.1069 with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for C: drive backup 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal projects 1 for Library clips/sounds/music/stills./backup of working projects. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 472.39. 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.104. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

Audrey2 wrote on 11/26/2021, 12:21 AM

Hi John, Ray & Jeff.

Contacted Magix Support and received the following suggestion which as yet I have not tried but will do in the coming day, will post the results once done. AudreyII

"Please try the following workaround:

Please delete the video_pro_x.ini. You can find it under the following path.
C:\Username\AppData\Roaming\MAGIX\Video_Pro_X13
Important! Please only delete the "video_pro_x.ini.

Also delete the cache folder. You can find it under the following path:
C:\ProgramData\MAGIX\Common\Cache

Then open your program and create a new empty project . Then switch to your program settings, accessible with keyboard shortcut "y" . Click on device options and change "import/processing/export" to your graphics card.

Exit the program again. Important! Do not close via the Task Manager."

browj2 wrote on 11/26/2021, 9:06 AM

@Audrey2

Hi,

As I indicated, I did the first one, delete the ini files, and it took a couple of tries before succeeding. I did not delete the Cache, but it's a good idea to do so.

I was finally able to update to the latest patch.

John CB

John C.B.

VideoPro X(12); MEP2022 PPremium; MM2022 Premium; see About me for more.

Desktop System - Windows 10 Pro 21H1; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; dual monitors - LG 4K 27" main, HP 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2

emmrecs wrote on 11/26/2021, 10:12 AM

@Audrey2 @browj2

Following installation of the latest patch, the problem of the failed closing of the app seems to be resolved for me. I didn't follow any of the advice about deleting the .ini file or cache but so far, so good. (Keeping ALL my fingers and toes firmly crossed.)

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Sound Forge Audio Cleaning Lab, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

CubeAce wrote on 11/26/2021, 11:01 AM

@Audrey2

Hi.

Thanks for the official feedback.

It's obvious from the last line they had never suffered this problem because the project closes and saves. Just not the program.

Ray.

Windows 10 Enterprise. Version 21H1 OS build 19043.1348. Direct X 12.1 Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 30.0.101.1069 with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for C: drive backup 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal projects 1 for Library clips/sounds/music/stills./backup of working projects. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 472.39. 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.104. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

tpolakov wrote on 11/27/2021, 3:24 PM

Hi John, Ray & Jeff.

Contacted Magix Support and received the following suggestion which as yet I have not tried but will do in the coming day, will post the results once done. AudreyII

"Please try the following workaround:

Please delete the video_pro_x.ini. You can find it under the following path.
C:\Username\AppData\Roaming\MAGIX\Video_Pro_X13
Important! Please only delete the "video_pro_x.ini.

Also delete the cache folder. You can find it under the following path:
C:\ProgramData\MAGIX\Common\Cache

Then open your program and create a new empty project . Then switch to your program settings, accessible with keyboard shortcut "y" . Click on device options and change "import/processing/export" to your graphics card.

Exit the program again. Important! Do not close via the Task Manager."

Just an FYI - these steps did not resolve the exit issue for me.

I do have Video Pro X installed on 2 PCs - one is an Intel notebook with integrated graphics - this one has the issue.
The other one is an AMD desktop with AMD RX 580 GPU - this one has no issue exiting the program.

Main editing machine (Desktop): CPU: Ryzen 9 3900X, GPU: AMD RX 580 4GB, 48GB RAM, System drive: 512GB M2 SSD, several other SSD data drives, Windows 10 Pro

Secondary machine (Notebook): CPU: Intel i5 8350U, integrated Intel UHD 620 graphics, 16GB RAM, 256 GB M2 SSD, Windows 10 Enterprise

johnebaker wrote on 11/27/2021, 4:18 PM

@tpolakov

Hi

. . . . one is an Intel notebook with integrated graphics - this one has the issue . . . .

What is the computer specification? See this topic for what is required and please quote processor and graphics card make/model in full - I would suggest you put this information, and your other computer spec, in your profile signature so we do not have to keep asking for it.

John EB

Last changed by johnebaker on 11/27/2021, 4:18 PM, changed a total of 1 times.

VPX 13, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2022.

PC - running Windows 10 Professional 21H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom, 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, Contour HD 1080 and Sony HDR-AS30V Sports cams.

tpolakov wrote on 11/27/2021, 6:09 PM

@tpolakov

Hi

. . . . one is an Intel notebook with integrated graphics - this one has the issue . . . .

What is the computer specification? See this topic for what is required and please quote processor and graphics card make/model in full - I would suggest you put this information, and your other computer spec, in your profile signature so we do not have to keep asking for it.

John EB

Hi John,

I updated my signature with the specs.
After some more testing, the issue is very strange.
I completely uninstalled VPX (cleaning cache etc.) and reinstalled/updated upto the latest version (19.0.1.128).
I was able to create a project in it which I am able to repeatedly open and close without an issue.
However, when I create a new project, even without importing any footage into it, I get the problem (the program hangs on exit).
I also get the issue when I import the same footage - as in the working project - into a new project.

So at this point it seems only the very first project can be opened/closed, everything afterwards fails to close properly.

Thanks

Tomas

Last changed by tpolakov on 11/27/2021, 6:10 PM, changed a total of 1 times.

Main editing machine (Desktop): CPU: Ryzen 9 3900X, GPU: AMD RX 580 4GB, 48GB RAM, System drive: 512GB M2 SSD, several other SSD data drives, Windows 10 Pro

Secondary machine (Notebook): CPU: Intel i5 8350U, integrated Intel UHD 620 graphics, 16GB RAM, 256 GB M2 SSD, Windows 10 Enterprise

johnebaker wrote on 11/28/2021, 4:50 AM

@tpolakov

Hi

Thanks for the specs.

Are the Intel UHD 620 drivers up to date - the latest version is 30.0.101.1069 ?

John EB

 

VPX 13, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2022.

PC - running Windows 10 Professional 21H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom, 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, Contour HD 1080 and Sony HDR-AS30V Sports cams.

tpolakov wrote on 11/28/2021, 5:22 AM

@tpolakov

Hi

Thanks for the specs.

Are the Intel UHD 620 drivers up to date - the latest version is 30.0.101.1069 ?

John EB

 

Hi John,

just updated the driver, unfortunately no difference in behavior.

Some more interesting steps:

1. Created a copy of the first(working) project file in Windows explorer. The copy works as well. The recent list now contains only these two and both can be opened and closed ok.

2. Creating a new project from scratch in VPX, importing the same footage (it's just one mp4 file) hangs on exit.

Observation - the first(working) project and the new project from step 2 (non working), differ considerably in size - 272K vs 375K, while they only contain the same single clip with 2 cuts.
It appears VPX is adding some garbage to the non working project, suggesting memory leak or similar issue.

Last changed by tpolakov on 11/28/2021, 5:32 AM, changed a total of 1 times.

Main editing machine (Desktop): CPU: Ryzen 9 3900X, GPU: AMD RX 580 4GB, 48GB RAM, System drive: 512GB M2 SSD, several other SSD data drives, Windows 10 Pro

Secondary machine (Notebook): CPU: Intel i5 8350U, integrated Intel UHD 620 graphics, 16GB RAM, 256 GB M2 SSD, Windows 10 Enterprise

tpolakov wrote on 11/28/2021, 5:48 AM

OK, I think I figured it out - sort of.

I just realized that the working project had two movies in it. The first one was empty, the second one contained the actual footage. Not sure if I did this deliberately when creating the first project.

So, with the working project open, I opened another project and chose to add it instead of closing the current one. After saving this one, this project worked.

So I created a new project from scratch, but did not use the default movie, rather I added a new one right away and imported footage into it. This project worked (closed ok) as well.

So it seems I have a workaround for now, but truly a weird one. There has to be an empty movie in the project for it to close properly.

Main editing machine (Desktop): CPU: Ryzen 9 3900X, GPU: AMD RX 580 4GB, 48GB RAM, System drive: 512GB M2 SSD, several other SSD data drives, Windows 10 Pro

Secondary machine (Notebook): CPU: Intel i5 8350U, integrated Intel UHD 620 graphics, 16GB RAM, 256 GB M2 SSD, Windows 10 Enterprise

johnebaker wrote on 11/28/2021, 12:34 PM

@tpolakov

Hi

Thanks for the update.

This is beginning to sound like there may be an issue with the VPX initialisation file.

Try moving or deleting the video_pro_x.ini file located in C:\Users\Username\AppData\Roaming\MAGIX\Video_Pro_X13 then start VPX.

A new ini file will be created - however do note this will remove any customisation to folder paths, additional links you have created and the recently used files list.

John EB

VPX 13, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2022.

PC - running Windows 10 Professional 21H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom, 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, Contour HD 1080 and Sony HDR-AS30V Sports cams.

tpolakov wrote on 11/28/2021, 12:45 PM

@tpolakov

Hi

Thanks for the update.

This is beginning to sound like there may be an issue with the VPX initialisation file.

Try moving or deleting the video_pro_x.ini file located in C:\Users\Username\AppData\Roaming\MAGIX\Video_Pro_X13 then start VPX.

A new ini file will be created - however do note this will remove any customisation to folder paths, additional links you have created and the recently used files list.

John EB

Hi John,

thank you, but deleting the ini file was part of the instructions in this thread that I have already tried. It's worth mentioning that with the ini file removed and the issue happens, the ini file does not get created. In other words, the program hangs at quitting before it would be able to write the new ini file.

Thanks

Tomas

Main editing machine (Desktop): CPU: Ryzen 9 3900X, GPU: AMD RX 580 4GB, 48GB RAM, System drive: 512GB M2 SSD, several other SSD data drives, Windows 10 Pro

Secondary machine (Notebook): CPU: Intel i5 8350U, integrated Intel UHD 620 graphics, 16GB RAM, 256 GB M2 SSD, Windows 10 Enterprise

johnebaker wrote on 11/28/2021, 1:44 PM

@tpolakov

Hi

Thanks for the info, a couple of of longshots, which may be related, with older versions of MEP and VPX:

  1. In older versions of Movie Edit Pro, VPX's little brother with the same core features, one of the causes of hanging when trying to exit was the News subprogram not shutting down and causing the program to hang.

    Is the Hide news option in program settings System tab checked? If not try checking it and close down VPX - you will need to use your workaround to get this saved into the ini file.
     
  2. The Updater' program would not close correctly - in Task Manager, ending this task enabled the programs to shutdown.

    If this one works you can uninstall Magix Cloud if you do not use it to see if this gives a permanent fix.

John EB

VPX 13, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2022.

PC - running Windows 10 Professional 21H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom, 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, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Albert_B wrote on 11/29/2021, 9:02 AM

Hi, I've the same problem. I've followed your instruction and removed the .ini file, erased the cahe as mentionned in previous answers. But the problem is still there.

My PC is : lenovo Yoga 910-131KB with Intel I7-7500 2.7Ghz; Ram 16GB; SSD 2x500GB; Intel graphics card 620.

New inputs?

Albert_B wrote on 11/29/2021, 10:15 AM

I've also also to change the program setting for import/editing/exporting. Instead of my graphic card "intel 620" I put "CPU", the same issue to exit the program. That means nothing is related to the graphic card, am I right?

The only "place" to exit is to exit before you create a project, but that means useless....., no?

Thanks if some new ideas!

johnebaker wrote on 11/29/2021, 10:54 AM

@Albert_B

Hi

. . . . change the program setting for import/editing/exporting. Instead of my graphic card "intel 620" I put "CPU", the same issue to exit the program. That means nothing is related to the graphic card, am I right? . . . .

The test you applied is for a different issue some users experience with lower specification GPU card/chipsets.

Did you see Tom's @tpolakov workaround further up the topic here and test the options I posted immediately above your first post.

John EB

VPX 13, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2022.

PC - running Windows 10 Professional 21H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom, 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, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Albert_B wrote on 11/29/2021, 11:17 AM

It works !!!

Thanks John for your input and Thanks to @tpolakov for "the solution" with two films on the project and the first one empty !!!.

(Magix software programer can see now where is their problem and fix it)