Unexplainable Render freeze in Vegas Pro 18

Micky-1111 wrote on 6/7/2021, 9:38 AM

Firstly my rig:
Windows 10 Pro
CPU: AMD Ryzen 7 2700X Eight-Core Processor
GPU: Nvidia GTX 1080ti
32GB of RAM
1 500GB SSD / 1 2TB HD
Vegas Build: 527

I've been an avid user of Vegas for years now...dating back to Vegas 11. I've tried just about every trick in the book related to solving render issues. CPU/GPU rendering, multi core disabling, reinstalling, etc. I was on Vegas 17 prior and upgraded to 18 but the problem still occurs. I had 16 GB of RAM and just added an extra 16 to now equate to 32GB - the render still randomly freezes anywhere from 79% up to my longest render being 91%.

The only connection to my crashes is not so much troublesome footage, because I'm able to render half (and put the two together) without any issues - it's only when trying to render the full 13 minute video. I got a Sony a6400 camera about a year ago and from the jump when I was handling 4k footage from it, I've always had some trouble editing it. The upgrade to Vegas 18 has helped smooth the editing process but it did not solve this rendering freeze.

This is the only connection because at a point I switched from editing the direct footage, and began using an adapter to stream the camera onto my PC, then use a PC program to record the camera - this removed all issues from rendering but I did not like the quality loss I was receiving. The same goes for having to render the project in half, then put them back together as a whole - I really am trying to avoid the quality loss. Plus, the way my render is moving both quick and smooth, then randomly near the end craps out, is frustrating to see. It feels like there is a a small bug causing this and I am desperate to solve it so I can finally have a smooth experience and not spend days on rendering...I'm slowly being driven to insanity :).

Any help or guidance on this would be greatly appreciated. Is there a format I can render half of the project to that would minimize the quality loss from a double render? This is the 2nd project I've spent 2+ FULL days simply trying to get a successful render. The first time was out of sheer luck that it decided to not freeze after a 3 day attempt (my memorial day weekend was robbed!).

Thanks in advance.

Comments

Former user wrote on 6/7/2021, 9:39 AM

Possibly a heat problem in your computer?

j-v wrote on 6/7/2021, 10:00 AM

- We need the MediaInfo of your sources
- Show us a screenshot of the interface with your project loaded
- Show us a screenshot of Options/Preference/Video
- Show us a screenshot Options/Preference/File I/O
- Show us a screenshot of Help/Check for driver Updates loaded.

Micky-1111 wrote on 6/7/2021, 11:08 AM

- We need the MediaInfo of your sources
- Show us a screenshot of the interface with your project loaded
- Show us a screenshot of Options/Preference/Video
- Show us a screenshot Options/Preference/File I/O
- Show us a screenshot of Help/Check for driver Updates loaded.

Media Info of sources (2 types - 1. gameplay recording / 2. sony a6400 footage [4k])
1.

The project

File I/O:

Drivers up to date (I switched from NVIDIA Game drivers to Studio drivers):

Preferences:

My error message from Vegas is always around so4compound plugin...and I noticed through the gathering of these screenshots that both types of my recordings are AVC format, which the so4 plugin relates to. I'm going to test disabling that plugin and seeing if it resolves the issue...

Micky-1111 wrote on 6/7/2021, 12:11 PM

Possibly a heat problem in your computer?

After watching my temps when doing a render I don't think this is the case? My temperatures look normal/stable when rendering. I'm unsure if there's a more efficient way to monitor this but with my AMD CPU is set at 85C. That's usually what I'm at when gaming as well.

j-v wrote on 6/7/2021, 12:26 PM

I ee nothing wrong in your settings on the moment but you did not give the Media Info of the program MediaINfo

Micky-1111 wrote on 6/7/2021, 1:37 PM

I ee nothing wrong in your settings on the moment but you did not give the Media Info of the program MediaINfo

I'm not sure what you're referring to. If you could explain a bit more I can get the info for you.

As an update -
I cleared my cache for Vegas 18 and the render got all the way to 100%...before it hung and never completed successfully.

In trying to disable the so4 compound plugin I noticed the settings have changed in Vegas 18 and it's as if I'm unable to disable it from the UI.

My assumption is that Hardware Decoder for So4 Compound Reader is the equivalent of what this post is describing to disable, but you can clearly tell Vegas 18 has drastically changed with how to go about this process. Another assumption is that 1 = true and 0 = false (following the basics) but when I set the hardware decoder setting to 0, I check and see my XAVC-S (4k Sony a6400 footage) is still leveraging so4compound. I think through this change I was able to force the gameplay footage to resort to the base compound plugin, but the a6400 footage is still leveraging it.

I truly think my problem lies with this so4compound so if anyone can help me disable this - that'd be great. All tutorials I've found online are for Vegas 17 and below.

j-v wrote on 6/7/2021, 2:15 PM

Text in blue means here on this user forum a link to something else.
Did you already try to render with voukoder?

Micky-1111 wrote on 6/7/2021, 4:18 PM

Text in blue means here on this user forum a link to something else.
Did you already try to render with voukoder?

Just tried Voukoder to no success.
Got to 85% before it crashed/froze.

The link I sent was to another post on this website, it's in relation to the so4compound plugin.

Micky-1111 wrote on 6/7/2021, 4:59 PM

I know I need to step away from the computer but its feels like I'm truly going insane. The unexplainable freezes in random locations when I'm 5 minutes away from a completed render is getting more and more mind boggling. Nothing I do is helping and it's all because of good quality footage.

I usually solve my program issues after a few days but as it is I'm not seeing any light at the end of this tunnel.

RogerS wrote on 6/7/2021, 8:50 PM

Disabling so4compound can be done by checking legacyAVC under file i/o.

RogerS wrote on 6/7/2021, 8:52 PM

The issue is something with the gameplay recording but you didn't give us MediaInfo using the program by the same name. I'd transcode it before bringing into Vegas.

I use a6500 and a6600 XAVCS clips without issues.

Micky-1111 wrote on 6/7/2021, 9:14 PM

The issue is something with the gameplay recording but you didn't give us MediaInfo using the program by the same name. I'd transcode it before bringing into Vegas.

I use a6500 and a6600 XAVCS clips without issues.

I find that hard to believe only because when my gameplay recordings are problematic it's pretty binary - it causes a consistent issue. This time. there's a section it consistently fails, but sometimes the gameplay is on the screen, other times the camera footage is...could the gameplay be the culprit in this situation?

I have multiple files of footage but they are basically all the same, just different length.

Gameplay:

a6400:

Also, do you create a proxy for your clips? That should benefit me vs harm but I thought I'd ask to see if there's differences there.

RogerS wrote on 6/7/2021, 10:09 PM

For MediaInfo, please switch to text view ("View" > "Text") and you can copy and paste all the text.

I don't create proxies (normally) but it shouldn't impact rendering either way as the render is made from the source file.

I'd put preferences including so4 back to default for testing purposes.

If you want to just make a dummy project, put all your a6400 clips on it and render to whatever your normally use (MagixAVC 29.9fps?) and you should be able to see if there's any problem. There shouldn't be. My guess is it's how the gameplay footage was recorded.

For a second test, just take some of the gameplay footage and see if you can render it as Apple ProRes 422 (it may not work). Stick it back on the timeline with the a6400 footage and render again. If both steps work, that's a workaround.