VMS 17 crashes when I try to open an VMS 16 project.

Jack-Riser wrote on 5/9/2020, 9:54 PM

I can not open my VMS 16 projects. They crash instantly. The example project at startup runs fine. I can open my VMS 16 project with VMS 16. What is going on?

Comments

Former user wrote on 5/9/2020, 10:03 PM

Probably a plug in that is not supported in 17. (exclusive to 16)?

 

Jack-Riser wrote on 5/10/2020, 9:19 AM

Thanks for your reply!

One of the projects from 16 is a short video from my phone I loaded just to trim the video. I saved it as a project for future use and renderered the shortened video. Nothing else was done to the video. Are you suggesting that all of my projects made with VMS supplied plugins can't be loaded?? I would hope that Magix wouldn't sell a product that would not allow previous projects to load without telling customers or providing some kind of conversion utility, right....

j-v wrote on 5/10/2020, 11:18 AM

Can you make new projects in VMS 17 and start them afterwards again in VMS ?
What are the specs of your hardware?
As a workaround in this case you can open the project in 16 and copy the contents to 17

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
522.22 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 522.22 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Jack-Riser wrote on 5/10/2020, 7:12 PM

I find that I can't make new projects. VMS crashes when I try to add a video clip. I tried copy and paste, but I get the same results. Instant crash!

I am running win 10 on an i5 machine. Never, never had problems like this. VMS has always been good to me.

Really frustrating. Am I the only one?

Jack-Riser wrote on 5/10/2020, 7:14 PM

I am trying a re-install tonight.,....

Tried the re-install. No improvement ....

VMS crashes whenever I try to add media, however, I can add the welcome project at startup. If I try to add anything to the welcome video --- VMS crashes ----. ?!!XX@#$%^

KenB wrote on 5/11/2020, 3:40 AM

Is it possible you had disabled the SO4 Compound plugin in VMS16?

Ken.

Vegas Pro 18.0 (Build 284)
OS: Windows 10 Pro 2004
CPU: Intel Core (4th gen) i7-4790 @ 3.60GHz (HD Graphics 4600 - driver 15.40.46.5144)
Memory: 32GB DDR3
GPU: NVIDIA GTX 1660 SUPER - driver 452.06
Monitor: 1920x1080x32

Jack-Riser wrote on 5/11/2020, 9:17 AM

Thanks for the super feedback. I have a lot to try to solve this.

In the meantime I loaded VMS 17 on my i7 laptop which I don't normally use for VMS. On the i7 laptop, VMS 17 loads my VMS 16 projects as expected. One project gave me a warning that VMS 17 doesn't contain a plugin found in the project, but it loaded anyway and I was able to continue normally.

At this point, I believe my problem is related to my i5 and I need to do some diagnostics on that system before I continue here. I'll post a followup after I finish checking out my system.

Thanks.

VEGASDerek wrote on 5/11/2020, 10:22 AM

It is possible that this is a driver issue. VMS 17 has much more extensive GPU handling but it may be more susceptible to having issues with GPU drivers. If updating your drivers doesn't work another thing to try is to turn off the GPU decoding in the File I/O tab in preferences.

Jack-Riser wrote on 5/11/2020, 11:48 AM

I think my problem has been solved. I opened Option>Preferences>File I/O in VMS 17 and unchecked the first checkbox "Enable Hardware Decoding for supported formats". VMS 17 now works as expected. No more crashes when loading my VMS 16 projects.

FYI. This option "File I/O" did not exist as a tab in the VMS 16 in Prefences as far as I can see. It seems to be new ?? (I checked VMS 16 for this option but didn't see it.) The option "Enable Hardware Decoding for supported formats" in the File I/O tab is checked by default. Again, unchecking this solved my problem.

Thanks for all the great feedback from the group which led me to solving my problem.

You are all awesome... Stay Safe!

j-v wrote on 5/11/2020, 11:58 AM

@Jack-Riser
Which GPU was choosen at the bottom of that File I/O tab?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
522.22 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 522.22 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Jack-Riser wrote on 5/11/2020, 12:46 PM

By default the Intel QSV is selected. I did not change that.

Also that seems to be the only selection that causes the crashes. I have only Intel HD Graphics. If the "Enable Hardware Decoding..." box is checked, the Intel QSV is the only selection of the three that cause my crashes. I tried the others with the box checked with no problem.

VEGASDerek wrote on 5/11/2020, 12:59 PM

I suspect the Intel GPU driver is out of date if this is causing the problem.

Jack-Riser wrote on 5/11/2020, 1:15 PM

Thank you. I will check on it and report back my findings.

Jack-Riser wrote on 5/11/2020, 1:44 PM

Sorry to say that this driver upgrade did not fix this issue. I updated the driver from a 2015 version to a 2020 version from Intel's website. The program crashes with the new driver just as before when the "Enable Hardware...." box is checked. The driver I updated is the Intel HD Graphics 2500 driver.

VEGASDerek wrote on 5/11/2020, 5:33 PM

That GPU is below system requirements. You will need to continue to run with the GPU decoding set to off.

Jack-Riser wrote on 5/11/2020, 7:01 PM

Thank you VEGASDerek! I think it may be time for an upgrade...

EricLNZ wrote on 5/11/2020, 11:13 PM

With VMS17 Plat there seems to be six places where you can set Graphic related options. VMS is getting even more "technical" for us consumer level folk 😀

  1. Preferences-General. Enable QSV Encoding and Decoding,
  2. Preferences-General. OpenCL/GL Interop for Intel GPU (may not appear if you don't have Intel?)
  3. Preferences-Video. GPU acceleration of video processing
  4. Preferences-File I/O. Enable Hardware Decoding....
  5. Preferences-File I/O. Enable Legacy HEVC.....
  6. Preferences-Deprecated Features. Allow legacy GPU rendering.

 

KenB wrote on 5/12/2020, 2:55 AM

And don't forget the Internal options (hold Shift when selecting Preferences):

  1. Enable Hardware decoding for So4 Compound Reader
  2. Enable YUV To RGB conversion using OpenCL for NVIDIA

Ken.

Vegas Pro 18.0 (Build 284)
OS: Windows 10 Pro 2004
CPU: Intel Core (4th gen) i7-4790 @ 3.60GHz (HD Graphics 4600 - driver 15.40.46.5144)
Memory: 32GB DDR3
GPU: NVIDIA GTX 1660 SUPER - driver 452.06
Monitor: 1920x1080x32

Jack-Riser wrote on 5/12/2020, 6:28 AM

Thanks for these "option" tips. I have been using vms since v15 and now I am feeling like a newbie. Great community. Thank you.