VP17 Build 353 Unusable - Reinstalled B321. Back working . . . so far

Grazie wrote on 11/23/2019, 3:41 AM

So, since B353 I've had nothing but trouble. I've spent much time in chasing down the reason/cause but this morning have resorted to the semi-Nuclear approach.

1/- I did a System Restored prior to a the latest WU. Always a clue.

2/- Re-Installed my nVid Driver and started to load VP17.

3/- Fired-up VP17 and got the invitation to there being a NEW VP17 . . . I politley declined. I'm now running VP17 B321. This MUST have been my Sys Restore that jiggered that? Yes?

The results have been, so far, that using a previous crash test Dummy combo of Neat Video+HOS Render as New Take, this has now worked well. Also, VP17 B321 loads faster and SAVEs faster than B353.

I'll see how far along I get. But, having worked nicely with B321 previously, I have no reason to think it wont continue to.

@VEGASDerek & Eric, I really hope this helps you guys to make some changes for the better. I installed B353 as it had performance improvements, well not for me. Please view my Sig for the competency of my PC.

Comments

j-v wrote on 11/23/2019, 4:11 AM

Did you see it on both PC's?
I saw the same problems, but it was a Windows 10 update, I restored with a system copy and set the automatic updates to stop for 5 weeks. Build 353 goes now excellent with me (hobbyist)

AlesCZ wrote on 11/23/2019, 9:10 AM

I also have performance issues since the new version. I don't know if this is related to the latest system update. But it would be good to find a solution or make a quick patch.

fr0sty wrote on 11/23/2019, 10:03 AM

Everything works fine for me in the new update.

Grazie wrote on 11/23/2019, 10:07 AM

I also have performance issues since the new version.

@AlesCZ - I’m working up a theory. 😉. Tell me, do you have an external Scrubbing Device?

Grazie wrote on 11/23/2019, 10:08 AM

@fr0sty - Good!

AlesCZ wrote on 11/23/2019, 12:05 PM

I also have performance issues since the new version.

@AlesCZ - I’m working up a theory. 😉. Tell me, do you have an external Scrubbing Device?

I do not have :) Clean "new" system

Steve_Rhoden wrote on 11/23/2019, 12:21 PM

Build 353 is great. Some hidden update somewhere or something had thrown a wrench in your

usually smooth workflow Grazie....

Grazie wrote on 11/23/2019, 12:36 PM

And I think I’ve discovered that “wrench”. When I’ve finally nailed it I’ll make it Public. Good to see you here again Steve. It’s been far too long.

AlesCZ wrote on 11/23/2019, 1:09 PM

The whole thing is much worse. Vegas 17 353 crashes all the time, causing random black frames, NOT usable for work. I had to turn off GPU support to complete the project.
It's a disaster.

fifonik wrote on 11/23/2019, 3:04 PM

I'm sorry to hear that yo do have issues. VP is complicated program and heavily depend on you hardware/drivers and installed plugins or used media.

I bought VP17 recently, but already finished 4 small projects (3 - 15 minutes each, GPU enabled in preferences, rendering CPU only, updated to build 353 ASAP). No crashes at all on my system and everything definitely not slower than in VP15. (well, technically VP crashed once: when I clicked at old NewBlue Titler Pro 1.0 in Media Generators accidently. I should have uninstall it very long time ago). I have only used the following plugins in these projects: AAV Color Lab, Curves, Levels, White Balance, Sharpen, Color Corrector, NeatVideo v5, Mercalli v4.

UPDATE: Typo "VP15" changed to "VP17"

j-v wrote on 11/23/2019, 3:11 PM

I bought VP15 recently,

Update build 353???? I thought there the last update was 416.😉

vkmast wrote on 11/23/2019, 3:17 PM

Must be a typo re VP 15, probably means VP 17.

j-v wrote on 11/23/2019, 3:23 PM

😉

Robert-Rigg wrote on 11/23/2019, 3:33 PM

After downloading B353, picture in picture and Bezier Masking do not work. They worked great before B535 download.

Grazie wrote on 11/23/2019, 4:36 PM

@Robert-Rigg - Typo?

BruceUSA wrote on 11/23/2019, 5:43 PM

Before build 321 I got 2-3 crash in editing per project. Mostly freeze when I try to click here and there. But acceptable to work to finished the project. Build 321 is the best one. Edited and finished multicam project that is 1hrs 30minutes long. editing and rendering without a single crash. Happily to stay with 321 for now. Until Magix do major update relate to the support of AMD Decode.

AlesCZ wrote on 11/24/2019, 5:26 AM

I use the same hardware from VP15. Unfortunately, the latest version is the worst for me.

Paul-Fierlinger wrote on 11/24/2019, 10:25 AM

Once again I can't close one project to open another one without having Vegas crash, only this time it happens a few minutes into working on the #2 project when this happens and it happens every time. These days when I want to switch between two projects I always have to first close Vegas altogether and then reopen.

Grazie wrote on 11/25/2019, 3:29 AM

I've got reproducible GOOD results. B353 working great.

So not WU, nor INTERNET trolls, nor Wrenches in my System and definitely NOT my MONSTA! PC. - I'm just too fast for B353 to keep up with me. Oh, BTW, I have a mass of Plugs n Stuff, plus a PreSonus Control Surface with Faders zipping UP and DOWN.

BTW2 - Wasn't B353 a "performance" Update? What was improved?

fr0sty wrote on 11/25/2019, 11:26 AM

Lots of things. There's a list in the release thread's original post.

Grazie wrote on 11/25/2019, 11:41 AM

Lots of things. There's a list in the release thread's original post.

@fr0sty - Thanks! I’ll reread the list and note the performance improvements.