Vegas Pro default location C:

Source Files C:\YouTube\MainStationOperation4\

Thanks for answering, as you can see, everything to default values, everything on one drive.

I cannot find a thing that looks wrong, but the bottleneck can be that you only use 1 drive.
I should at least make 2 extra partitions on that drive besides C:\ < one for sourcefiles and one as renderlocation.
I run and edit my GOPro HEVC 4K 50p files together with DJI Osmo AVC 4K 50p files on laptop and desktop from signature.
Laptop with one 2 TB HDD divided in partitions and one SSD with 3 partitions, one for C with only Windows 10 and the programs, one as rendering target and one for other online activities as Dropbox a.s.o.
On desktop I have besides SSD 5 other big drives partial on removable disc locations.
Always and everywhere my Documents (Windows) is replaced from C to a data location on another drive.

My normal house keeping is to have operating system and programme files on C drive and working files on D. For the purpose of this experiment I put everthing on C.

BUT

I think I may have discovered the problem.

In this (and many others I have made), I use the reverse condition on the clips to run the clip backwards. I have just tried rendering the pieces where the changeover from forward to reverse occurs and it consistenly fails.

Will try to render the video without the reverses to see what happens, if its a bug I'll report it to Vegas.

Will keep you informed, thanks again for your trouble.

Low memory could be associated with dynamic RAM preview, try setting that to 0.

Yeah even with the reverses removed, it still flipped out on Low Memory, although it did get further.

I'm now trying it with the advice from fr0sty, reducing the dynamic from 200Mb to zero. This is a ten minute video I'm trying to render and the predicted duration is over 4 hours. My head is in my hands......

Are you monitoring memory usage while rendering? If not, you're just shooting in the dark.

Use either task manager or resource monitor so that you can see what's happening in real time.

@Doug-Wilson

"Twin Xeon 6 core 3.5Ghz processors"

Have you tried CPU only?

Even as a diagnostic approach.

Its rendered it ok using RAM preview set to zero. It took over 6 hours. When I have the preview set to default (200Mb) the memory usage, from resource monitor is around 26Gb (36Gb free), with zero Mb its steady at 11Gb. I'm wondering what memory its running out of. Every time it fails there are lots free. I have twin 8 core 3.5GHz processors and have not tried CPU only. As a footnote, in V17 I had the RAM preview set to 16GB! never had a problem. Thanks to you all for your suggestions. Still feel no further forward, all this proceesing power and can't use it.

I have tried the CPU only method suggested by John Dennis, with the RAM preview set to 200Mb (default), went away very fast predicting 1:20 to task completion, memory usage 5%, CPU usage around 60%. Rendered 34% and stopped, unable to close application, reboot to bail out.

Tried increasing RAM preview set to 16Gb, my setting in V17, (and susequently 8Gb) both failed due to low memory.

Open to more suggestions, 6 hours to render a file that a similar one in V17 usually took around an hour is not good enough.

Open to more suggestions,

No suggestion to try out for you, but now I'm back from vacation and have a lot of time, I could try to handle and render your project on my hardware.
I think I only need the projectfile without content, because maybe I can fill your project with my own files, unless you used a lot I don't have on effects and filetypes.
You can send me (us) by PM or via this forum a link to download that veg file somewhere.

That's very kind of you j-v, someone else has just offered the same thing. I have another machine, a lesser spec, I was thinking of trying to run it that. I have this problems all along with V18, but only on rendering, everything else is superb. I have the Post version and have had V18, Effects and Image all running at the same time and the new version is really quick switching between the three. All other software I run on this machine runs fine, including having the three Vegas packages and running OBS at the same time. I'm trying another couple of things, got one running at the moment.

Running CPU render only, RAM preview 200 Mb (default) everything else in default

Changed resampling to 'Disabled' in this run

Memory usage started around 3Gb increasing as render progressed, failed at 16 Gb. Can't be sure but other failures around the 8GB mark.

If I increase the RAM preview to 8Gb or 16Gb it fails immediately on low memory.

Any thoughts?

Reason for stopping is a fault in one or more effects, but we can't see which one.
Give the same error report with both options selected and so that we can read which is the fault module(s?).

Can't get the rest, already sent to Vegas

This is the timeline,

Top track copy of second track, all masks no effects

Second track Two effects used Chroma Key Pro (NewBlue, checked latest version) and Bezier Masking

Third track No effects

Fourth track No effects

To seasoned VEGAS users:

I was racking my brain over this problem after reading the entire conversation

At first, I was thinking something along the lines of insufficient virtual memory (a harddrive configuration) but if I remember correctly - Windows itself should prompt an error regarding this if that was the case. Might be worth exploring.

What I'm looking at right now is that @Doug-Wilson has a multitude of VEGAS versions on his machine, assuming all are connected with the plugin suites he has installed.

I know that after sometime, OFX folder tends to get messy and sometimes require to be deleted entirely and installing everything from scratch. Could that be the problem?

 

Indeed  @Mohammed_Anis, that's why I wished to know what was in that error report concerning the fault module.
If it was indeed NewBlue or Bezier Mask (maybe both?) it should be worthy to see how the render went without one of both.

Right, we maybe are getting to the root of the problem here. I only have two versions of Vegas on this machine v17 and v18. Over the last few weeks I have rendered some training videos, each over 30 minutes long without a problem. they were outputed from OBS Studio, there was no NewBlue effects in any of them. I wiil remove V17 and NewBlue and re-install NewBlue. Will let you know guys. Thanks again.

Right, we maybe are getting to the root of the problem here. I only have two versions of Vegas on this machine v17 and v18. Over the last few weeks I have rendered some training videos, each over 30 minutes long without a problem. they were outputed from OBS Studio, there was no NewBlue effects in any of them. I wiil remove V17 and NewBlue and re-install NewBlue. Will let you know guys. Thanks again.

Actually, if what I'm saying is on the money - I believe the solution needs to be a bit more radical then that.

@j-v Correct me, please.

What I would do is first completely wipe out VEGAS. Entirely. Gone. Then, I would find the OFX folder and rename it to OFX.old

Now finding OFX folder is something I'm having trouble remembering but once you do that, you install VEGAS PRO and attempt the render.

If the render goes through, get rid of OFX.old and install your plugins.

 

Removed V17 and NewBlue effects, re-Installed New Blue (same latest version from NewBlue site).

Disabled Chroma Key Pro from all clips, left Bezier Enabled. Rendered using Processor only. Rendered ok in 1 1/2 hours

As above, rendered with a NVidia profile I used all the time in v17, failed after a few minutes 'Low memory'

Looks like NewBlue isn't the problem.

Getting late now will try your suggestion tomorrow Mohammed.

@j-v Correct me, please.

Not a correction, but as addition maybe is it better to reset VPro 18.
And make no changes in the Vegas setting if the drivers are all the newest, VPro 18 will find automatically what are the best settings.
Renaming the different Effects and trying which one it is is also a better methode than deleting all and reïnstalling.

I refer back to this comment

j-v wrote on 9/2/2020, 4:04 PM

Indeed  @Mohammed_Anis, that's why I wished to know what was in that error report concerning the fault module.
If it was indeed NewBlue or Bezier Mask (maybe both?) it should be worthy to see how the render went without one of both.

-------------------------------------

Before I start deleting or changing this control programme, I decided to complete the process j-v suggested (above).

I've already disabled Chroma Key Pro from all clips, left Bezier Enabled (results above), so this morning I reversed the process enabled Chroma Key Pro from all clips, disabled bezier

Ran this three times, processor only, rendered perfectly each time just under an hour.

Ran using standard NVidia profile failed differently, missed out top three tracks and only rendered 4th after a few minutes. Tried again rendered black screen after about 30%

Disabled both effects, rendered Processor only and standard NVidia profile, both rendered perfectly.

I'm not sure what conclusion to come to here, maybe you guys may have some thoughts.

My suspicions fall on the Bezier Masking, its the only component here that's been changed. (tracking removed since last version).