Question regarding switch from Vegas 17 back to Vegas 16

daniel-t2081 wrote on 8/10/2019, 6:48 PM

I purchased Vegas 17 but there has been a host of issues with crashing, unable to open my projects, etc. I have been working on a very big documentary for 6 months and it is extremely crucial that I can finish this film. I need to go back from Vegas 17 to Vegas 16.

Can I uninstall VP 17 and open my project in VP16? I haven't saved any changes in my project with VP17, by the way. And just in case, I backed up all my files, clips, all Vegas 16 files, etc, to an external hard drive.

 

Thank you.

 

Comments

fr0sty wrote on 8/10/2019, 6:50 PM

No. Your best bet is going to be to tell us about what is happening when it crashes, your hardware configuration, your GPU driver version, and that will get us started. We may need to ask you to download a program called mediainfo that gives us details about the media you are using. Chances are, the issues causing your crashes have already been resolved here previously, so once we find out what you're working with, we can likely recommend a quick fix or at least a workaround to get your project out the door.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

fr0sty wrote on 8/10/2019, 6:53 PM

I can give you 2 pointers that you can try right off hand that usually help:

1. for render issues, or crashing, sometimes updating the GPU drivers helps. if you are using nvidia, make sure to use the studio driver, not game.

2. For slow performance/hangs when editing complex projects, or if a project takes forever and hangs/crashes while loading, try to disable timeline thumbnails in preferences. See if that speeds performance back up. Many users have found this helped resolve those issues.

 

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

daniel-t2081 wrote on 8/10/2019, 6:59 PM

No. Your best bet is going to be to tell us about what is happening when it crashes, your hardware configuration, your GPU driver version, and that will get us started. We may need to ask you to download a program called mediainfo that gives us details about the media you are using. Chances are, the issues causing your crashes have already been resolved here previously, so once we find out what you're working with, we can likely recommend a quick fix or at least a workaround to get your project out the door.


Motherboard: Asus rog strix x470-f gaming

Drive: Wd Blue 4tb

Video card: Zotac rtx 2080ti amp

Drive: Samsung 870 evo 2tb nvme ssd

Processor: Ryzen 7 2700x

RAM: Corsair Vengeance RGB 64BG 4x16 3200mhz

 

 

fr0sty wrote on 8/10/2019, 7:01 PM

Make sure you have the latest studio driver from Nvidia installed, and try disabling thumbs on the timeline in preferences, see if that helps any.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

daniel-t2081 wrote on 8/10/2019, 7:08 PM

I have the Zotac rtx 2080ti amp video card. Is that still NVIDIA?

rraud wrote on 8/10/2019, 7:33 PM

You should not have to uninstall VP-17 to use VP-16. If clicking a <.veg> file opens 17 by default, that can be easily changed.

Uninstalling VP-17 could be a little risky if you have a project in the works. I have had instances where a Vegas uninstall also uninstalled some 'shared' plug-ins I needed. Was not a major catastrophe but time-consuming and stressful with a deadline looming

fr0sty wrote on 8/10/2019, 9:05 PM

Yes, that is an Nvidia Card.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

john_dennis wrote on 8/10/2019, 9:09 PM

"I have been working on a very big documentary for 6 months and it is extremely crucial that I can finish this film."

My mind is completely boggled every time I read such a thing. Didn't you back up your stuff, including your boot image, before you installed an application that was in general availability for just a few days?

AOMEI Backupper (Free)

In case you want to buy something...

No, no. You can thank me later.

fr0sty wrote on 8/10/2019, 11:03 PM

In this case, the OP started a project in VP 17, which means it cannot be opened in earlier versions, so a backup wouldn't help for them here. We've just gotta isolate the issue, plenty of other folks have had similar problems we've solved.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

alfred-w wrote on 8/11/2019, 9:50 AM

 I haven't saved any changes in my project with VP17, by the way. And just in case, I backed up all my files, clips, all Vegas 16 files, etc, to an external hard drive.

Apparently some of the previous posters didn't notice the quoted statement.

As indicated by a previous poster there is no need to uninstall VP 17.

If you haven't done any saves in VP 17 you might be able to open the existing project file in VP 16. If not you should be able to perform any of the following alternatives, any one of which will get you back to where you were when you created the most recent backup:

1) Open VP 16; use it to open the .veg file on the backup drive; VP 16 will probably open utilizing the clips at their original location on the internal drive. But if not a dialogue box will appear in which you can point it to the location of the clips, on either drive as you choose. You can then do a "save as" to save the .veg file to the internal drive.

2) Copy the .veg file from the external drive to a new folder on the internal drive. Open VP 16; use it to open that .veg file; VP 16 will probably open utilizing the clips at their original location on the internal drive. But if not a dialogue box will appear in which you can point it to the location of the clips, on either drive as you choose.

3) Copy the entire set of backups to a new folder on the internal drive. Open VP 16; use it to open the .veg file in that new folder; VP 16 will probably open utilizing the clips at their original location on the internal drive. If you wish you can change the location of the clips that are utilized by right-clicking on each of them in the project media tab, and choosing "replace."

Good luck. Regards,

-- Al

Last changed by alfred-w on 8/11/2019, 10:04 AM, changed a total of 2 times.

Computer: Corsair 760T case (black); MSI MEG 390 ACE motherboard; Intel Core i9-9900K cpu; Noctua NH-D15S cpu cooler; G.SKILL Trident Z Royal 32GB (2 x 16GB) DDR4-4000 memory; MSI GeForce RTX 2060 graphics card; Samsung 970 PRO M.2 2280 512 GB SSD ("C" drive); Samsung 860 EVO 1 TB SSD (video drive); WD Black 4 TB HDD (internal backup & storage drive); LaCie "Porsche Design" 4 TB HDD (external backup & storage drive); 2 x Asus DRW-24B3ST DVD drives; Vantec UGT-FW200 firewire card; EVGA SuperNOVA 850 G+ power supply; Windows 10 Pro x64.

Cameras: 3 x Panasonic AG-UX180

Sound Recorder: Sound Devices MixPre-6

Editing: Vegas Pro 15 & 16; Sound Forge Pro 12