Rendering gets stuck at x%

walter-i. wrote on 1/3/2021, 2:56 AM

If it gets stuck in the same spot over and over again, that is the flaw to look for. Try to swap or re-integrate the file.

If the project is not too complicated, you can also mark the entire project and insert it into a second instance of Vegas Pro that is open at the same time.

___ wrote on 1/3/2021, 5:43 PM

If it gets stuck in the same spot over and over again, that is the flaw to look for. Try to swap or re-integrate the file.

If the project is not too complicated, you can also mark the entire project and insert it into a second instance of Vegas Pro that is open at the same time.

ah alright. What codecs are the most compatible with Vegas Pro 18?

RogerS wrote on 1/3/2021, 8:39 PM

Can you start with what file types you are currently using? OBS is totally different than variable frame rate HEVC from a phone vs regular AVC from a camera.

___ wrote on 1/3/2021, 9:54 PM

Can you start with what file types you are currently using? OBS is totally different than variable frame rate HEVC from a phone vs regular AVC from a camera.

Here (mp4):

some of them were ran using ffmpeg under this command (the data shown here isn't from ffmpeg I believe): ffmpeg -i input.mp4 output.mp4

Format: MPEG-4
Format profile: Base Media / Version 2
Codec ID: mp42 (mp42/isom)
File size: 777 MiB
Duration: 25 min 53 s
Overall bit rate mode: Variable
Overall bit rate: 4 195 kb/s
Encoded date: UTC 2020-11-01 00:19:48
Tagged date: UTC 2020-11-01 00:19:48

Video
ID: 2
Format: AVC
Format/Info: Advanced Video Codec
Format profile: High@L4.2
Format settings: CABAC / 3 Ref Frames
Format settings, CABAC: Yes
Format settings, Reference frames: 3 frames
Format settings, GOP: M=4, N=15
Codec ID: avc1
Codec ID/Info: Advanced Video Coding
Duration: 25 min 53 s
Bit rate mode: Variable
Bit rate: 3 995 kb/s
Maximum bit rate: 6 000 kb/s
Width: 1 920 pixels
Height: 1 080 pixels
Display aspect ratio: 16:9
Frame rate mode: Constant
Frame rate: 60.000 FPS
Standard: NTSC
Color space: YUV
Chroma subsampling: 4:2:0
Bit depth: 8 bits
Scan type: Progressive
Bits/(Pixel*Frame): 0.032
Stream size: 740 MiB (95%)
Language: English
Encoded date: UTC 2020-11-01 00:19:48
Tagged date: UTC 2020-11-01 00:19:48
Color range: Limited
Color primaries: BT.709
Transfer characteristics: BT.709
Matrix coefficients: BT.709
Codec configuration box: avcC

RogerS wrote on 1/4/2021, 12:01 AM

This looks like standard AVC, so likely not an issue as far as I can tell (which is good). Can you just delete the clip at the point where the render gets stuck from the project and then re-add it and try to render again?

Other generic advice includes setting dynamic ram preview to 0MB before rendering, and updating video card drivers to Studio or Pro/Enterprise, and if that fails, disabling GPU preview acceleration, and finally resetting Vegas (control-shift on startup).

NickHope wrote on 1/4/2021, 12:08 AM

Rendering troubleshooting tips here: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

___ wrote on 1/4/2021, 1:03 AM

This looks like standard AVC, so likely not an issue as far as I can tell (which is good). Can you just delete the clip at the point where the render gets stuck from the project and then re-add it and try to render again?

Other generic advice includes setting dynamic ram preview to 0MB before rendering, and updating video card drivers to Studio or Pro/Enterprise, and if that fails, disabling GPU preview acceleration, and finally resetting Vegas (control-shift on startup).

Rendering troubleshooting tips here: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

I've tried all of these already, and I still get the same issue. It's really annoying to deal with (including the fact that it happens with 90% of all of my other projects).

RogerS wrote on 1/4/2021, 2:07 AM

Is there a 3rd party plug-in you are using and could try disabling to see if you can render? You are rendering to a format like MagixAVC at a resolution that is an even number of pixels?

Another workaround is to render through Voukoder (which is what I use for quality and speed, not because of errors).

Otherwise I don't have ideas and you have an unusual situation and should try Magix support.

___ wrote on 1/4/2021, 9:37 AM

Surprisingly, I use Voukoder to render stuff. Also no I didn't use any 3rd party plugins.

RogerS wrote on 1/4/2021, 10:09 AM

Could you screenshot your exact Voukoder render settings? There are a few things it can't do in Vegas (maybe check out 7rc1 which fixes a recent issue).

___ wrote on 1/4/2021, 11:46 AM

crf=17.000 opencl=1 preset=medium rc=crf x264-params=qpmax=24:aq-mode=2:aq-strength=0.700:rc-lookahead=180:keyint=360:min-keyint=1:bframes=14:b-adapt=2:ref=3:deblock=0:direct=auto:me=esa:merange=52:subme=10:trellis=2:no-fast-pskip=1:no-psy=1

b=192000 profile=aac_low

j-v wrote on 1/4/2021, 12:14 PM

For the use in Vegas your Voukoder settings are totally wrong, but first I like to know which program you are using and buildnumber of it.
What is the hardware on which you use the program?

___ wrote on 1/4/2021, 2:42 PM

Version: 18.373

Specs (bottlenecked):

Processor: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz, 3601 Mhz, 8 Core(s), 8 Logical Processors
RAM: 16 GB
GPU: NVIDIA GeForce GTX 760, 2 GB
Motherboard: ASRock Z390 Phantom Gaming 4S/ac
Display: VG248DELL P2213 @144 (1920 x 1080)
Operating System: Windows 10 Pro x64 (1909 build 18363)
Installed on: 20.2.10
OS build: 18363.657
Manufacturer: Micro Electronics, Inc.

j-v wrote on 1/4/2021, 3:11 PM

Then you must change nothing in Voukoder using this rendertemplate, no customize, no change

___ wrote on 1/4/2021, 4:56 PM

I just tried that, and it's still getting stuck.

RogerS wrote on 1/4/2021, 6:34 PM

Is only having 2GB of video ram causing problems? 4 is minimum for 18.

___ wrote on 1/4/2021, 7:04 PM

Is only having 2GB of video ram causing problems? 4 is minimum for 18.

Well this is the only issue I have. I don't seem to be having any other issues.

RogerS wrote on 1/4/2021, 9:03 PM

Maybe just try turning off everything GPU-related to troubleshoot.

In preferences, turn preview acceleration off, in file i/o set hardware decoding to off, don't use a NVENC render template (your x.264 should be fine). If it still fails then disable the GPU in device manager temporarily and see if that helps.

___ wrote on 1/4/2021, 10:42 PM

Maybe just try turning off everything GPU-related to troubleshoot.

In preferences, turn preview acceleration off, in file i/o set hardware decoding to off, don't use a NVENC render template (your x.264 should be fine). If it still fails then disable the GPU in device manager temporarily and see if that helps.

ok somehow that made it 10x worse. Instead of the same project getting stuck at 104 frames, now it gets stuck at frame 4. and when I go ahead and disable my GPU via device manager, it gets stuck at frame 3. My cpu can't possibly be worse than my GPU since its a i7 9700k.

In addition to disabling my gpu, vegas gets stuck a lot when I boot it up, so I have to force close it through task manager which doesn't make it any better. I really wish vegas wasn't this horrible at performing even when you actually buy the program.

What's really strange is that this project doesn't use any OFXs. I just did a render today that used 7 ofxs, and it completed the render without any problems. I don't understand why it has to happen to all of my other projects.

RogerS wrote on 1/5/2021, 12:52 AM

When you disabled the GPU, you disabled the NVIDIA and not the Intel one, right? You should have had both in device manager.

Yes, your perfectly good CPU should work fine with Vegas. My i7 does.

For Voukoder to have multiple reference frames work right you need the latest beta:
https://github.com/Vouk/voukoder/releases/tag/7.1rc1
However this will also mean no Voukoder support for your kepler-generation NVIDIA card if you ever use it.

Did you do the full reset of Vegas already (control-shift on startup)?

Something is very unusual here- you should file an official support request, too. Screenshots of the render errors would be great to include.

___ wrote on 1/5/2021, 9:59 AM

When you disabled the GPU, you disabled the NVIDIA and not the Intel one, right? You should have had both in device manager:

Yeah I did disable the MVIDIA one.
For Voukoder to have multiple reference frames work right you need the latest beta:
https://github.com/Vouk/voukoder/releases/tag/7.1rc1
However this will also mean no Voukoder support for your kepler-generation NVIDIA card if you ever use it.

I went ahead and ran the installation, opened up vegas and rendered as usual. Same issue.

Did you do the full reset of Vegas already (control-shift on startup)?

Yeah I did. Same Issue.

Something is very unusual here- you should file an official support request, too. Screenshots of the render errors would be great to include.

The issue with this is that there is no error. The render gets stuck.

j-v wrote on 1/5/2021, 10:13 AM

@___
How is the location to where you tried to render formatted?

___ wrote on 1/5/2021, 2:00 PM

what do u mean exactly?

j-v wrote on 1/5/2021, 2:42 PM

Go to My Computer and right click on the location you are rendering to and tell us what's there stated or show this picture