Personally, I'm suss on how VP deals with VRAM.. indication is that: Preference 'Autocalc Video Memory - 64Bit' cannot be set to 'TRUE' even though default is 'TRUE'. Value is 'FALSE'. Even when you try to change by hand. Go figure..

I do not think that's because of it, but in the video I see that it's still the 4.5.5 of Neat Video. VP15 is mentioned in the release notes of 4.6. The current version is 4.7, I think.
Another attempt would be to set Dynamic RAM Preview to 0 because it can cause problems with GPU acceleration.

Strange that ther is no notification in VP 15 build 311 that there is a new version available.

daws? Don't you mean NLEs?

I was able to resolve my problem finally... When Nick suggested exporting the part of the project I was working on to a new project, I thought I was out of luck because I couldn't render anything. I was unaware that if you have more than one instance of Vegas open, you can copy any event from it to the new instance. so, I selected every clip in the highlight video at once, cut them to the clipboard, and pasted them into a new project. I had to redo all of my color grading and fx, and the first time Neat Video crashed saying that it was given invalid data, something about gamma. So, I restarted, enabled so4compoundplug.dll again (I had turned it off earlier for testing), and was able to get the render going. Everything went fine until the last 3 scenes, then the video started glitching up really bad, freezing, stuttering. etc. So, I dropped the project settings to 8 bit, and it rendered out properly that time.

 

So, in summary, to help anyone else who might come across a similar issue with this version:

VP15 v321 doesn't like long projects. Keep them short, or expect lots of crashes, low memory errors, neat video running out of GPU RAM, encodes not encoding at all, etc.

If you already have a long project that is crashing, Copy/Paste what you need into a new instance of Vegas to avoid encoding.

If using Neat Video, Rendering to 4K, and using a GTX970, it doesn't like 32bit projects, so switch it to 8 before rendering. This is what causes the glitching in the video, or black frames.

Make sure so4compoundplug.dll is ENABLED (that's a welcomed first!)

Now I have a beautifully rendered video, took about 40 minutes to complete (10 minutes long, some scenes with neat video applied), and a happy client who is no longer blowing up my phone.

Thanks for the suggestions and patience with my flood of posts. I wasn't sure if making a new thread would be what was preferred or not, since this problem was related to a bug introduced with this new version. Hopefully these posts save someone else this same headache.

 

Here's the video that resulted, if anyone cares to see it.

https://drive.google.com/open?id=13ypABDQdDF-Tre4kFaVpb9Maaw3FjCXb

Sorry Frosty

Sorry Frosty. Vegas actually started as a DAW. Yes NLE works today more so really. LOL.

Glad you got your video finally rendered. : )

Strange that ther is no notification in VP 15 build 311 that there is a new version available.

+1
You are not alone :-(((

Same here. I didn't know of an update until I came to the forum....

Setting Dynamic RAM Preview to 0, this is (was) something I always did first with my previous PC (the one with 4790K and Nividea Titan maxwell). You do not want to know how many times this saved my ass on that setup. It solved crashes, stuttering in final render, weird frame drops. With my new PC I have not done much working/ rendering yet, so I cannot say it still needs to be put to 0. My new system HW deviates a lot from the previous and so does the Nvidea architecture (pascal now).

Regarding the memory issues mentioned in some of the previous postings, when I installed my new system, I also increased my virtual memory significantly (set to 197000 MB), as I read somewhere you need about 3x the amount of real memory for Vegas to be on the safe side....

And I probably do not need to mention this, but UI slow issue is solved with me as well.

What I noticed reinstalling 14 and 15, is how much zippier the 14 interface felt. SNAP! It was there. 15 is better now, but still draggy compared to 14 on the same computer. Then, there is another NLE that I resolve to start learning and its interface feels very solid.

Still having the frame stutter on xavc-s footage here right before a cut on the timeline. Almost like a freeze frame then jumps to next clip. If I loop it, it is random. Hope this gets a look at. Let me know if I ca be of any help.

Still having the frame stutter on xavc-s footage here right before a cut on the timeline. Almost like a freeze frame then jumps to next clip. If I loop it, it is random. Hope this gets a look at. Let me know if I ca be of any help.

My experience with (Sony) xavc-s in the trimmer window; frequently using frame forward, frame back and play almost all the time resulted in the program freezing up and having to force the program to close and restart, unworkable...

Is it just me, or are others having this issue too?...

@Happy I haven't even tried the trimmer window yet. Yikes!! It is indeed sony A7S footage XAVC-S. ARGH.

..I was unaware that if you have more than one instance of Vegas open, you can copy any event from it to the new instance. so, I selected every clip in the highlight video at once, cut them to the clipboard, and pasted them into a new project. I had to redo all of my color grading and fx...

Why not do it the other way round? Just copy the project, delete the unwanted stuff, do a "Remove All Unused Media From Project", then save. Then when you've got your intermediates (XAVC-I, MagicYUV or whatever) from the smaller projects, recompile them together in a new project.

I thought about this, however when I removed the rehearsal dinner footage from the project earlier to try to reduce memory usage to see if it would help, every time I would open the project afterwards it would still give the error that the media was missing from the project, I'd have to tell it to ignore all missing clips and open the project anyway, so I was not sure if it was actually removing the media completely from project memory or not, and I wanted to be sure of it. I was deleting the media from both the timeline and project media, btw.

It is wrong to jump to the conclusion that GPU acceleration should be disabled in Neatvideo4 generally. Because if that would be required really, Neatvideo would not work here in my setting, with two different GPUs enabled for GPU acceleration within Neatvideo.

It must be something different that makes the troubles (other footage, other GPUs, other drivers...).

That isn't what I ended up having to do. I was able to leave all GPU acceleration on in the end, but not while using a timeline that spanned more than 2 hours with 150gb worth of media in it, and not while in 32 bit format even in a shortened project. As long as I'm rendering 8 bit and the project isn't too long, everything with the GPU works perfectly as it should. GPU utilization hangs out around 50% during render, and about 3.5 of my 4gb of VRAM. It rendered at about 10fps for a 4K AVC render with LUTS, curves, color correction, and level adjustments applied on the various tracks and master fx bus. Once it hit the Neat Video scenes, that dropped to about 2fps, but 4K noise reduction (on max quality settings) can take some serious time, so that isn't that bad.

@Happy @david-ruby If you're having trouble with XAVC-S then try disabling so4compoundplug, if you haven't already.

It is wrong to jump to the conclusion that GPU acceleration should be disabled in Neatvideo4 generally. Because if that would be required really, Neatvideo would not work here in my setting, with two different GPUs enabled for GPU acceleration within Neatvideo.

It must be something different that makes the troubles (other footage, other GPUs, other drivers...).

You stated above that you had to disable GPU Support - but that is not the general issue. Otherwise it would not work at all.

That isn't what I ended up having to do. I was able to leave all GPU acceleration on in the end, but not while using a timeline that spanned more than 2 hours with 150gb worth of media in it, and not while in 32 bit format even in a shortened project.

I think that development team will not have such a huge Project. So it will be hard to repro if the issue takes place with a Project sice of 2 hours/x Events in the timeline only. How many Clips do you have in the project?

As long as I'm rendering 8 bit and the project isn't too long, everything with the GPU works perfectly as it should. GPU utilization hangs out around 50% during render, and about 3.5 of my 4gb of VRAM. It rendered at about 10fps for a 4K AVC render with LUTS, curves, color correction, and level adjustments applied on the various tracks and master fx bus.

At least with some shorter test projects it works here with 32bit too. Hard to say where the system Limits are, both for 8bit and 32bit project settings.

What happens with both the GPU but also the CPU utilization if you take the long project? Do you run in the 100% utilization in case of the long project?

Once it hit the Neat Video scenes, that dropped to about 2fps, but 4K noise reduction (on max quality settings) can take some serious time, so that isn't that bad.

The low fps number during rendering with Neat4 is normal and not the issue very likely. Denoising takes a lot of calculation power on my system too.

It has already been reported that the RAM requirements of VEGAS are sometimes very high. As a reason I have diagnosed here the creation of the Thumbnails in the Explorer. Coincidentally, I just opened a directory with 1500 time-lapse JPGs. If the thumbnails are created in the background, this will bring about 3.5Gb! additional memory usage. If I then switch to other directories, the memory usage increases even further. The memory is released only when closing again, it seems. If you do not switch to an empty directory before closing VEGAS, this will happen again the next time you start the program.

I am still missing

h265 4k nvenc....

There is no such template. Or is it not implemented yet?

If not, when it can be expected?

@Happy @david-ruby If you're having trouble with XAVC-S then try disabling so4compoundplug, if you haven't already.

@NickHope Yep done that a while back off and on. No relief here.

@Happy @david-ruby If you're having trouble with XAVC-S then try disabling so4compoundplug, if you haven't already.

@NickHope Yep done that a while back off and on. No relief here.

@NickHope  so4compoundplug disabled made no difference..

I do also see the flashing that happens under preview window where the play button is.

Going to add my computer info here as well.:

Intel core 17-3930k cpu 3.20 ghz 4.20 ghz 6 core, 12 logical processors

ram: 32 gb

windows 10 64 bit latest

c drive

e drive raid 0

f drive raid 0

nvidia geforce gtx 670

Sony A7S XaVC-S footage. AVC or mpeg4 as Premiere Pro calls it.