Can't change project properties to saved template?

NCARalph wrote on 6/16/2019, 2:13 PM

Vegas Pro 16.0 Build 424 seems to no longer support changing project properties to a custom defined template. It will allow me to change to one of the built in templates, for example "4K 16:9 24p (4096x2304, 23.976 fps)", however, if I try to change to my custom template with 1080x1920 29.970 progressive, nothing changes in the properties box except the name. The Apply button is grayed out as well.

If I change to another built in template, e.g. "HDV 1080-60i (1440x1080, 29.970 fps)", then it works, the template's settings are put into the box and can be applied.

If I save the settings from a built in template to a custom template with no changes, I get a warning that I'm duplicating a built in template. However when I attempt to use it, it behaves the same as with other custom templates, it's not used and Apply is grayed out.

Setting the fields in the property box works, they just can't be saved and reused.

This seems like a huge regression if true. Any thoughts?

Comments

j-v wrote on 6/16/2019, 2:50 PM

Here no problem, try a reset of the program through Ctrl-Shift-DoubleClick Pic>>>>all

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
551.61 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 551.61 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)

 

NCARalph wrote on 6/16/2019, 3:00 PM

I tried that, no changes. I also completely uninstalled it, cleaned the registry, reinstalled 361 which works perfectly, uninstalled that and installed a new download of 424 and it fails as described above.

Last changed by NCARalph on 6/16/2019, 3:01 PM, changed a total of 1 times.

Windows 10 Pro 64, i7 6700K @4GHz (with Intel Graphics 530) , 32 GB, AMD Radeon VII, Samsung 1TB NVME, 9TB storage spaces RAID, 3 monitors running off the Radeon

j-v wrote on 6/16/2019, 3:52 PM

No idea for other possibilities. I can only show you how it work with me on build 424 with Windows 10 home new version 1903 since yesterday.
Look

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
551.61 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 551.61 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)

 

NCARalph wrote on 6/16/2019, 5:44 PM

I believe you, but that's definitely not what my system does.

NCARalph wrote on 6/16/2019, 5:58 PM

This sounds like a previously reported problem with custom project templates. I have no idea what's different with our setups from the ones that work though.

https://www.vegascreativesoftware.info/us/forum/custom-project-settings-preset-not-holding--115945/

NCARalph wrote on 6/16/2019, 6:28 PM

I seem to have fixed this.

I have no idea what caused the problem, but this is what I did to fix it:

  • Uninstall Vega Pro
  • Clean the registry with CCleaner - I'm doubtful this is necessary.
  • Open the Registry Editor and save the current registry setup for safety
  • Delete the entire subtree:
    Computer\HKEY_CURRENT_USER\Software\Sony Creative Software\Vegas Pro\16.0
  • Reinstall Vegas Pro

Of course, this loses all your customizations, but I was able then to recreate my custom templates, save them and reuse them. Apparently something got corrupted in the Vegas Pro 16 registry entries.

 

Grazie wrote on 6/17/2019, 12:15 AM

I seem to have fixed this. .....Apparently something got corrupted in the Vegas Pro 16 registry entries.

@NCARalph - That’s some great analysis and then your remedy. I’m in awe of you and others who’ve got the knowledge to do this type of Registry editing. Is it possible that the VP installation file doesn’t freshen up our Registries to make a newly made bed ready for the VP installation? If this is the case then maybe this could be at the bottom of other issues. For me that’s that Vegas.exe remaining in Task Manager after closure.