(Yet Another) VegasPro 18 Render Crash/Hang Post

sakendrick wrote on 10/12/2020, 9:25 AM

If you been following my posts - I'm in a world of hurt... just upgraded from MSP to VP18 this weekend and spending more time troubleshooting than being productive. The latest issue is rendering hanging or sometimes the app just shutting down as soon as I go to Render As - no errors, nothing.

I've tried almost everything listed here: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/ and all the suggestions from Scrapyard films (on youtube)

There's lots of conflicting information when you google

- use acceleration, don't use acceleration

- set your ram to super high, set it zero

I've tried different file formats for rendering. I've deleted my app temp folder.

The most common issue is it gets stuck at 29%... I've investigated the file around 29% through it's timeline and nothing peculiar there. The weird thing is it has gotten stuck at 29% when I render the whole project (4 minute video) and when I render just a small part of the project.

The file content is mostly multiple videos (in tiles on the screen, sometimes up to 8), and track motion on various tracks, but not for the full 4 minutes, only in parts. There are no fx on the video, haven't even got to coloring yet. But all that said - I have a much simpler version with no track motion that renders fine in MSP 17 but won't render in Vegas.

I'm desperate for help - this is my last day to work on this project. Any suggestions welcome.

Comments

set wrote on 10/12/2020, 9:33 AM

😓...

I also gone confused reading your posts... but also difficult to suggest any...

Correct about setting the Dynamic RAM to 0. I also did this.

Anyway, by reading your latest post here, if you still able to do rendering, try render part by part to Magix intermediate format.

j-v wrote on 10/12/2020, 9:38 AM

Do a full reset of the program and let it stay that way and for sure no changes in Preferences Video and Pref FileI/O. The only thing maybe needed is Help/Check for Driver Update

RogerS wrote on 10/12/2020, 9:51 AM

I'd start with J-V's advice, update all drivers and reset the computer.

Still have issues? Standard render freeze advice is to disable GPU preview acceleration and set dynamic ram preview to 0 MB. I've never seen credible advise to set the ram high.

What render format are you using? Try Magix AVC in a non-GPU mode (not QSV, NVENC).

Good luck.

sakendrick wrote on 10/12/2020, 10:01 AM

Thanks all... will try resetting and starting over.

I'm using Magix AVC - I've tried every variant of QSV, NVENC, and not. In MSP, this project renders fine, and quick, and my best settings in MSP seem to be (after lots of trial and error, and hangs) QSV with the Intel acceleration on, RAM at 1000. But I've been trying 0 RAM and no acceleration with VP.

And while the project and associated files render perfectly fine in MSP, VP does seem to have a problem with a couple of my clips - see post here: https://www.vegascreativesoftware.info/us/forum/missing-file-error-when-it-s-not-enable-legacy-avc-decoding--124499/. When I delete these and enable the file i/o settings, I have better luck. I'm trying to see if rerendering those two clips via handbrake help any, but that's certainly not the only issue.

I'm also up for rendering in sections but afraid of losing quality, but I will definitely try it if I can get the sections to render. After these are rendered, do you reimport into a new project and render from Vegas, or do you just stitch together with something like ffmpeg?

JN- wrote on 10/12/2020, 10:43 AM

@sakendrick Just render out the suspect files one at a time to an intermediate like Magix 422 HQ. Then place it in the same location as the original files location, with the same name, having previously changed the name of the original file, by say adding a hyphen to the end of it.

When VP prompts, missing file, navigate to the Intermediate.

sakendrick wrote on 10/12/2020, 11:59 AM

So it appears those two files where causing my issues... I rerendered with handbrake and replaced and I seem to be able to get through a render now without resetting anything yet. I will try again with Magiz 422 HQ as I inadvertently adjusted the resolution when I used HB...

fr0sty wrote on 10/12/2020, 12:46 PM

To make sure you get max stability,

1. Make sure your system meets the min. requirements to run VEGAS

2. Make sure you run the driver update utility in the help menu of VEGAS to make sure you have the driver it wants you to have.

3. Make sure you are not using the legacy decoders unless you are forced to.

sakendrick wrote on 10/12/2020, 3:03 PM

I spoke too soon - I think... so I replaced those files with some rerendered out of handbrake and it rendered. I then rerendered the files at Magix HQ Intermediate, integrated back in, and tried to render just a portion of the video (about 1:30 worth) and it hung again right at 29 %. I don't know if it's those files again or not.

@fr0sty I exceed minimum system requirements, I'll double check driver utility, but can you explain what legacy decoders are and how to "not use them" or determine if I can not use them?

I was soo. close :(

sakendrick wrote on 10/12/2020, 4:30 PM

There were driver updates recommended, although unsure if they were different then what was installed (see explanation below). I downloaded both the Nvidia and intel drivers. installed. Ran into a bunch of problems with my system hanging on "restarting" or shutting down. But regardless the drivers are installed (checking version numbers in control panel). The weird thing is when I ask Vegas to check drivers again it keeps giving the same message. I also reset Vegas to defaults (just through preferences not through the ctrl shift launch).

All that said - on first attempt to render a section, it now seems stuck at 78%.. just hanging.

Now trying hardware acceleration off...

set wrote on 10/12/2020, 4:39 PM

... can you explain what legacy decoders are and how to "not use them" or determine if I can not use them?

It's for compatibility and stability purposes, so it uses the previous decoders that was used on previous version of VP.

Something that make it unstable in your PC, but haven't know what is it.

But regardless the drivers are installed (checking version numbers in control panel). The weird thing is when I ask Vegas to check drivers again it keeps giving the same message.

As long as the drivers are up to date as recommended by the Driver update section, it should be ok. Is the driver update process goes smooth overall?

Now trying hardware acceleration off...

ok...

sakendrick wrote on 10/12/2020, 4:42 PM

so no acceleration and 0 RAM hangs at 15% for just a section... getting worse

set wrote on 10/12/2020, 4:54 PM

Is this your PC spec?

Windows 10
64-bit
Dell Precision 5530
Intel i7-8850HCPU @ 2.60GHz, 2592 Mhz, 6 Cores, 12 Logical Processors
32 GB RAM
288 GB free on solid state drive

https://www.vegascreativesoftware.info/us/forum/v-17-crashing-when-i-try-to-open-v-14-files--121929/#ca759620

set wrote on 10/12/2020, 4:56 PM

Ok, just notice your another post: https://www.vegascreativesoftware.info/us/forum/missing-file-error-when-it-s-not-enable-legacy-avc-decoding--124499/

So, you are working with iPhone shot material of the whole project?

sakendrick wrote on 10/12/2020, 5:04 PM

yes, that's my PC specs, and no it's not all iphone. There are multiple iphone clips and some other. Those two clips mentioned above, I rerendered and now no longer get the error message, but I'm still suspect they could be contributing.

sakendrick wrote on 10/12/2020, 5:23 PM

an almost successful partial render... I got to 100%, unfortunately there's some weird flickering and artifacts in parts of it. But here's what I did- after no luck resetting and using default features I went back to the following

- In Internal settings disabled to OpenCL features

- Enabled Legacy AVC and HEVC decoding, my understanding is this shuts off the SO4 engine or whatever and this seemed to help with those iphone files

- Had Hardware Decoder set to off, although I didn't try this on NVIDIA

- Had NVIDIA hardware acceleration, and used the related Magix AVC/AAC HD 1080P 29.97 NVENC render option

- I also had 1000 for ram preview but I shut my preview window off

So at least I'm back to rendering, but

- haven't tried full file

- need to figure out why I'm getting weird flashes in some... maybe that's the acceleration in the format (?)

set wrote on 10/12/2020, 5:30 PM

"flickering and artifact"

is it the 'black' / 'blank' frame?

sakendrick wrote on 10/12/2020, 5:39 PM

Not sure what you mean but, yes there's black flickering that is sometime occurring over the full vide but really noticeable on my white background pieces.

JN- wrote on 10/12/2020, 5:43 PM

@sakendrick Have you converted your VFR phone clips to CFR? In this thread Richard saw “jitter” when using phone footage.

sakendrick wrote on 10/12/2020, 6:01 PM

It's not in the clips, it's the full screen (i.e. I have multiple clips on the screen at once and it's actually the border which is just a solid color background clip). I've also rendered parts of this other times and this is the very first time I'm seeing this flickering. So must have to do with either the render settings or updated drivers.

set wrote on 10/12/2020, 6:03 PM

so...flickering occurred on the rendered part?

sakendrick wrote on 10/12/2020, 6:13 PM

yes... for the first time since I updated drivers.

set wrote on 10/12/2020, 6:13 PM

I wonder what are the other sources besides that iPhone XS? is it also other phone?

So far my experience is, VEGAS Pro having trouble when working with iPhone or Android's recorded media that has VFR (Variable Frame Rate) besides of CFR.

I have this flicker issue as well when I receive the media (for online choir project so I only got the media from 'their submissions') - when previewing by the Video preview itself, will not noticing any blank frames, but once rendered - appear. My overall workflow for this online choir is to convert every submission to Magix Intermediate format to ensure the stability as I will combine 100 video in one sequence later (project still on going).

RogerS wrote on 10/12/2020, 6:21 PM

I had flashes when ram preview wasn't set to zero. You tried that? I think you are changing too many settings at once.

sakendrick wrote on 10/12/2020, 6:58 PM

Just trying now - I first tried switching from NVIDIA to INTEL hardware acceleration and using that render profile. It got to somewhere around 60% and failed gracefully saying a codec error, but gave me a viewable file. I think (will have to double check) the flickering was gone. So now I set RAM to 0, and turned off hardware acceleration, using the the basic 1080 profile. Going slow, currently at 50%

One thing regarding the source of videos... I have developed three music videos with the same devices as sources using MSP 17. (example: ). There is one difference which is this time I had the band send me 4K vids... however, before I upgraded to Vegas Pro this weekend, it was working fine and fast in MSP. Had I known none of the features I was upgrading for would help/work, I would have stayed with MSP 17 (and be done by now and $200 richer). Unfortunately I did a bunch of work in SV so I can't go back w/o restarting. sorry.. just venting some. Appreciate the ongoing support.