VEGAS Pro 14 Update 3 (build 201)

Comments

set wrote on 12/15/2016, 5:02 AM

This is it: I'm unable to reproduce the issue... I'm in the middle of project right now. For saving, I usually Ctrl-S to save and File>Save-as. I was just taking a nap and got back, rerun VP14.201 and I can open the project as usual...

Fiola wrote on 12/15/2016, 5:10 AM

This is it: I'm unable to reproduce the issue... I'm in the middle of project right now. For saving, I usually Ctrl-S to save and File>Save-as. I was just taking a nap and got back, rerun VP14.201 and I can open the project as usual...


This is same for me most of the time. But then ... from time to time. When got back, and rerun VP14.201 - some project I can't no longer open. :) Until I rename the folder. That's only thing that is really obvious - what changes the renaming the folder, that it start working somehow? :D

Paul-Fierlinger wrote on 12/15/2016, 5:32 AM

What if you tried simlpifying the renaming process by creating just two versions. It is something I do routinely. One is called Movie and the other is called Movie safety. I keep going Save As periodically between just the two.

set wrote on 12/15/2016, 5:39 AM

Fiola, Tell me, how old is your recent OS?

> Compared with mine, my PC was a reinstalled Win7 in Nov 2014 - moving to SSD system, and upgrade to Win10 in April 2016 - then in August 2016 - changed my video card from Radeon 5750 to Radeon RX470. Had system-restore only once in Sept 2016.

 

Also, may I know, what applications do you install in your PC?

> Compared with mine, Instead of editing, I also do 'General Computing' in this PC, so I have browsers (Mozilla, Chrome, Opera) installed and have WPS office (I don't use MS office) - old Photoshop, DaVinci Resolve, Natron open-source compositing, Nuke non-commercial compositing app (but never had a chance to be able to seriously learn it). Had few-beta testing application but all of them ended nicely. Didn't install any codec pack here, only install additional AVID codec.

Have Steam installed as well in Nov. 2016, but only have Cities Skylines game (as I am a fan of Simcity and similar one - got that during Black Friday😁). However, the system is still good here...

Of course, looking at Steam / Win10's store - there are numerous free application I love to try / play 😜 like I did in my Android gadget - but I don't want to do that to prevent any issues because of these!

DeTomasi wrote on 12/29/2016, 6:33 PM

When will build 201 be pushed to the Steam version of Vegas Pro 14? I tried updating manually, but that obviously didn't work out too well applying the retail update to the Steam version.

Edit: Nevermind, I actually just pulled it off. I was able to install build 201 over the Steam version by applying the update to: C:\Program Files (x86)\Steam\steamapps\common\Vegas Pro 14.0\Vegas Pro 14.0

I originally tried installing it to just C:\Program Files (x86)\Steam\steamapps\common\Vegas Pro 14.0

Hitfilm Pro 2017 Integration seems to work just fine now!

How do you make it work? For me does not work, got an error.

Did you make 211 work!

roland-graf wrote on 3/9/2017, 2:06 AM

since 201 V 14 freezes every time i open a .mov file: i can load it. looks good. play: no reaction. any hint? (win 7)

roland-graf wrote on 3/9/2017, 2:52 AM

since 201 V 14 freezes every time i open a .mov file: i can load it. looks good. play: no reaction. any hint? (win 7)

sorry it was 211 not 201 :-) a quick solution was to start V14 with CTRL-SHIFT. resetting everything helped.

https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

wsd wrote on 3/23/2017, 5:34 AM

Stability is "half"-fine. I am no longer struggeling with unexpected crashes and stuff like that. Even more so, it is unlikely I encouter a crash during editing.

One persistent crashing instance still isn't resolved. If I want to render a project, it crashes after I press the render button. I can counter this by selection all the clips in the bins and deleting them all, apart from the clips that are in use on the timeline. Then, save it to a different project name, close vegas, reopen vegas with the new project - and then it works. It is annoying to have to do so every time you want to render a small portion, but it is the only way that it works reliably.

I've had this issues since VP13, I think. It is still exactly the same. I don't know if anyone encountered the same thing, but it is a bit tedious, as you can imagine.