Rendering freezing at frame before crossfades

D.Griffin wrote on 4/15/2022, 12:11 AM

Hello,

I'm going to copy paste a reddit thread I started on the r/VegasPro thread as it's not getting as much attention there as it would have here.

"After multiple weeks of failed renders since switching recording formats, I've finally upgraded to 19 just because Steam had such a good deal on the upgrade and I was wondering if the upgrade would fix the render issues. What I have figured out because of the 19 upgrade, is that it does not fix the issues but is easier to pinpoint them on. My freezes while rendering are happening the exact frame before crossfades. I'm so torn on why that would even be happening. I have had nothing but freezes no matter the types of files that I've inputted, the framerates I've chosen, the bitrate I'm rendering in, HVEC vs. AVC, it just freezes before crossfades ALWAYS. It gets so old. How can a company charge 250 dollars for this?

I'm using a 9700k, 3080ti with latest studio drivers, Windows 10, I upgraded from Vegas Movie Studio 17 Plat to Vegas 19 (I'm a dumbass for that) it's not pirated and of course I've googled the issue, I don't think anyone's first thing they do when a problem occurs is to open a reddit thread.

I have messed with all sorts of settings including: leaving settings default, turning off/on GPU accel, adjusting RAM preview from 0 to 30%, Trying non NVenc renders I'm out of ideas and so is the internet apparently." -end reddit rant

I'll attach three photos showing what is going on. One of them is rendering starting off smooth, the other is when it freezes (note the frame it freezes on), and then one of the project with me on the transition frame (it freezes the frame before the transition every time)

Comments

john_dennis wrote on 4/15/2022, 1:21 AM

Have you turned off the GL Transistion?

D.Griffin wrote on 4/15/2022, 2:33 AM

@john_dennis it does it regardless of the transitions. It does it at simple crossfades too. I tried trying differrent transitions (switching cross fades for other transitions including the GL Transitions and vice versa) at the points where it was freezing. (FINALLY got it to render almost 9 hours after the first attempt at rendering.) No matter what, it made me fidget the timeline events in order to get it to pass it.

Former user wrote on 4/15/2022, 3:23 AM

(FINALLY got it to render almost 9 hours after the first attempt at rendering.) No matter what, it made me fidget the timeline events in order to get it to pass it.

What is the media, is it nvenc(new) from OBS, what is the capture resolution?

You fixed by moving the transition point slightly until it worked?

If you have this problem again will you know immediately how to fix, or you fixed via pure chance and couldn't replicate the fix quickly?

It's a very common problem.

D.Griffin wrote on 4/20/2022, 8:10 PM

@Former user Yes I've used both Nvenc regular and Nvenc(new) on recordings. My capture and output resolution is 3840x1080 (one 1920 is my webcam, the other is my recording screen. No I can't replicate the fixes. It's move a transition 1-60 frames either way and hope it renders on the next attempt. If it's such a common problem why do they leave us with this? There's no way a product should still be taking people's money if there is glaring issues with it.

Sidenote: on a completely unrelated project I'm doing right now, I have created a video proxy and it is crashing all the time. I've crashed 4 times already and the project is less than a minute long. I've never had this issue since I've switched to creating proxies of my bigger files. I think it's finally time to say it but as good as Vegas is when it's working, it sucks most of the time. I'm not spending another dollar on this crap software and hope Adobe can fix my problems. At least if I have issues with them they have better technical support and it's not just me having to post every single issue on forum threads hoping someone else has encountered the issue and has the solutions.

john_dennis wrote on 4/20/2022, 10:42 PM

@D.Griffin

I'm going to spitball this one more time, then, I'm going to send you off to do the staff work necessary to fix your problem.

In Vegas 19-550, set the Options like the following screenshot, then look for red vertical lines on the timeline.

Work this https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/ and report everything in B and C back into this thread.

If you don't complete this staff work, you won't see my face again, and you likely won't get much meaningful help from others playing 20 Questions.

D.Griffin wrote on 4/20/2022, 11:31 PM

 

@john_dennis You don't have to be a ****. The only thing you had asked me was if I had turned off GL transitions to which I kindly responded to you. I wouldn't want help from you anyways if you are going to be that way. You aren't better than me or anyone else here. I've done everything people have suggested on this thread. This is the first time I'm seeing the suggestion you are offering. Don't be a ****.

walter-i. wrote on 4/21/2022, 3:05 AM

You aren't better than me or anyone else here.

Yeah, really? Click on @john_dennis avatar and see how many solutions he's offered and how many "thanks" he's received, and then compare it to some others.

If you really expect help, do what he advised, otherwise it will be really hard to offer you further help.

Work this https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/ and report everything in B and C back into this thread.

 

And please 🙏- spare us your vulgar expressions - we are a user to user forum here, and do this in our precious spare time.

Former user wrote on 4/21/2022, 4:17 AM

@walter-i. Despite the 'solutions he's offered and how many "thanks" he's received,' there's a lot in his reply that was unnecessary! Stop defending the regulars on here who think they can write what they want, 😒

RogerS wrote on 4/21/2022, 9:04 AM

FWIW, some of the needed information is shared in the Reddit thread.

Especially for newer/less active members, I think we can be more helpful and less jaded and demanding. We've dealt with inadequate information for the 100th time, but for members just joining here it's not as obvious what w need and I think they deserve our patience and understanding or it's best to leave the reply to others.

We've noticed a growing number of comments directed from one participant to another that can easily be interpreted as rude, hostile, aggressive, or otherwise undesirable. This community thrives because of the helpful interaction between it's members. We all get frustrated, angry, and short tempered now and then, but please keep in mind Community Rule #1, Respect the opinions and views of other members of the community.

https://www.vegascreativesoftware.info/us/forum/respecting-fellow-community-members--131115/

walter-i. wrote on 4/21/2022, 4:00 PM

@walter-i. Stop defending the regulars on here who think they can write what they want, 😒

@Former user
and the vulgar expressions, which were directed to @john_dennis and had to be deleted by vkmast, we want to generously overlook.......

Former user wrote on 4/21/2022, 4:08 PM

@walter-i. Yep I understand the unacceptance & removal of the 'vulgar expressions' in @D.Griffin reply but still not a single denunciation of the snide & unnecessary comments by @john_dennis that instigated D.Griffin's response , I call that 'defending the regulars' !!

D.Griffin wrote on 4/21/2022, 7:47 PM

You aren't better than me or anyone else here.

Yeah, really? Click on @john_dennis avatar and see how many solutions he's offered and how many "thanks" he's received, and then compare it to some others.

 

@walter-i. This doesn't make him better by any means. It just means he's been here longer. If anything he should be held to a higher standard of the community guidelines. He's also a grandfather according to his bio. I'm sure when his grandkids come to him for help, he'd tell them to do parts "B and C" or they'd never see his face again. I'm not saying I handled it right, but i was honestly appalled by that response. As a 26 year old looking to get into film editing both you and John are very off putting. The fact you justify that because he's done so much for the community is disgusting and wish you'd both take that energy elsewhere. Just because you are good at something doesn't mean you get to treat people like that, there's a reason Antonio Brown is a free agent in the NFL.

@Former user I completely agree, I've seen this on multiple threads that I've read before posting my own. There are a few toxic people that think it's okay to not helpfully inform people that they should be posting more information and say that "no one will help you" and hurtful things. Yes, I'm sure they've seen newbie posts like mine several hundred times, but how hard is it to say. "Hey I see you are newer to the community, if you are able to do parts B and C of this thread it will help our community get you answers much faster." Seems pretty simple to me, so thank you for acknowledging that responses like that are inexcusable.

@RogerS I think it's safe to say both parties were in the wrong and I'm glad that you acknowledged that. I've seen this on multiple threads while doing my research and then couldn't believe that someone posted one to me as well. Thank you.

 

D.Griffin wrote on 4/21/2022, 7:50 PM

As for B and C that were referred to earlier: this is the code from my video file if anyone is still willing to help.

General
Complete name                            : D:\Videos\Phasmo\2022-04-11 21-20-19.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 2.96 GiB
Duration                                 : 55 min 43 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 7 597 kb/s
Writing application                      : Lavf58.76.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 55 min 43 s
Bit rate mode                            : Variable
Bit rate                                 : 7 324 kb/s
Maximum bit rate                         : 11.0 Mb/s
Width                                    : 3 840 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 3.556
Frame rate mode                          : Constant
Frame rate                               : 60.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.029
Stream size                              : 2.85 GiB (96%)
Color range                              : Limited
Color primaries                          : BT.601 NTSC
Transfer characteristics                 : BT.601
Matrix coefficients                      : BT.601
Codec configuration box                  : avcC

Audio #1
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 55 min 43 s
Bit rate mode                            : Constant
Bit rate                                 : 160 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 63.5 MiB (2%)
Title                                    : adv_aac0
Default                                  : Yes
Alternate group                          : 1

Audio #2
ID                                       : 3
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 55 min 43 s
Bit rate mode                            : Variable
Bit rate                                 : 99.3 kb/s
Maximum bit rate                         : 160 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 39.6 MiB (1%)
Title                                    : adv_aac1
Default                                  : No
Alternate group                          : 1
 

 

D.Griffin wrote on 4/21/2022, 7:51 PM

And here is my Vegas Properties:

General
  Name: 2022-04-11 21-20-19.mp4
  Folder: D:\Videos\Phasmo
  Type: AVC
  Size: 3.10 GB (3,175,174,172 bytes)
  Created: Monday, April 11, 2022, 9:20:19 PM
  Modified: Monday, April 11, 2022, 10:16:03 PM
  Accessed: Thursday, April 21, 2022, 5:49:03 PM
  Attributes: Archive

Streams
  Video: 00:55:43.533, 60.000 fps progressive, 3840x1080x32, AVC
  Audio 1: 00:55:43.463, 44,100 Hz, Stereo, AAC
  Audio 2: 00:55:43.463, 44,100 Hz, Stereo, AAC

Summary
  [TCFM]: 7

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: D:\Program Files\Steam\steamapps\common\VEGAS Pro 19.0\Vegas Pro 19.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.

 

D.Griffin wrote on 4/21/2022, 7:54 PM

Also sidenote: When working on a standard 1920x1080 recording from the past last night, I had 0 problems with rendering. It did still however have the freezing and crashing problems when trying to preview on Best (Full). With my hardware listed in the OP I wouldn't think this would still be an issue. It makes me think it's an issue with the resolutions of my recordings. Switching to CBR instead of VBR recordings has seemed to have no effect.

john_dennis wrote on 4/21/2022, 9:06 PM

@D.Griffin said:

"My capture and output resolution is 3840x1080 (one 1920 is my webcam, the other is my recording screen."

You posted a Mediainfo report for a 3840x1080 capture. Do you have a 1920x1080 file from your web cam that you are combining with your 3840x1080 capture?

Continue to post C8, your Vegas Pro Project Properties. it should look like this with different values:

... as well as your C9, your Vegas Pro Render Settings.

D.Griffin wrote on 4/22/2022, 3:08 AM

@john_dennis I've attached a bunch of pictures to this one that should clear up the rest. Both of the individual devices, a screen capture and my video capture device are put into Streamlabs OBS and recorded as one 3840x1080 (picture attached)  

 

I've messed with GPU acceleration both on and off. Both still freeze at transitions so I've kept it on due to it being faster. I've also tried rendering with HVEC using the same settings as I am with AVC and still the same results.

I'm on Vegas 19 Build 550, with Windows 10 Home v. 21H1, planning on uploading my videos to YouTube.

This final picture is an example of what I'm doing while editing. Track 2 is my webcam Chroma Keyed (poor lighting on green screen but still works) and track 3 is showing the game screen as seen in the Video Event FX window that's open. I did get this project to render after hours of wiggling the timeline around to get it to finally like it. Audio 5 is Default CPU audio and Audio 6 is My Yeti X Microphone. Since moving on to other projects with the same settings, I'm still getting freezes the frame before a transition starts. I hope all of this information is helpful.

Former user wrote on 4/22/2022, 6:27 AM

 

This final picture is an example of what I'm doing while editing. Track 2 is my webcam Chroma Keyed (poor lighting on green screen but still works) and track 3 is showing the game screen as seen in the Video Event FX window that's open.

@D.Griffin Hi, i'm not sure i understand this pic, if greenscreen you is on track 2 & the game is on track 3, why do both appear in the FX window with Game Screen dotted selection?, I've just woke up so maybe i'm missing something 🥱

PS just read the comment again 'put into Streamlabs OBS and recorded as one 3840x1080', i get it now 👍

I would cut that 3840x1080 in half into two 1920x1080 render those two sides, you & then the game as separate 1920x1080 clips, then reimport them to make the final project,

Former user wrote on 4/22/2022, 6:39 AM

@D.Griffin Also can you go to your icon at the top, click it - My Profile, & fill in your Signature with your Vegas version, Windows version & system specs, CPU, GPU, RAM etc. this will then show at the bottom of the comments & will help 👍 (see mine & others at the bottom of the comments)

john_dennis wrote on 4/22/2022, 8:01 AM

@D.Griffin

If you set a one minute loop region around the transition, does the render fail if you render one minute?

When you render to your usual render template?

If your render to Video for Windows using a customized template?

Example:

Report on the results of this test:

https://www.vegascreativesoftware.info/us/forum/rendering-freezing-at-frame-before-crossfades--134997/#ca843073

john_dennis wrote on 4/22/2022, 9:38 AM

@Former user said "I would cut that 3840x1080 in half into two 1920x1080 render those two sides, you & then the game as separate 1920x1080 clips, then reimport them to make the final project,"

@D.Griffin If you render the "talking head" green screen video to a separate file, use Pro Res XQ. It can have a transparent alpha channel. You need a lot of disk space.

D.Griffin wrote on 4/22/2022, 5:38 PM

@Former user That is genius! Such a simple fix that I'm assuming would work! I'm not sure why I never thought of that or been able to find other people suggesting that when I look up 3840x1080 issues. I'm heading out for work right now but will update my profile tonight, I'd never realized that was a thing.

@john_dennis I've done a little research on Alpha Channels and will continue to do so tonight when I get home, I may be wrong here but what you are saying that using a transparent alpha channel of me in front of the green screen will have better results than an AVC render with a Chroma Keyer? Also I will take your suggestion of one minute looping tonight when I get home. I currently have no 3840x1080 projects with failing renders going right now, but will start another one tonight.

Former user wrote on 4/22/2022, 5:58 PM

@D.Griffin We'll see if it fixes the issue but at least it's one thing you can discount because it'll/they'll just be regular files, I don't think adding chromakey to that 3840x1080 file + chromakey & only selecting half was a good thing.

I think what he is suggesting with Alpha channel is after you have done the chromakey & removed the green, then render out using Pro Res XQ, re-import that file with the transparent background to replace the green screen one, when it comes to render the final project a file with an alpha/transparent background will be easier on Vegas to render than a file with chromakey added. It's often better to break down a project & render out sections with fx's or crops because any fx you add complicates the render process, the same goes for like cutting your 3840x1080 in two halves of 1920x1080, Then put those rendered pieces together for a final project & render, all Vegas has to do is piece them together, Doing it this way also alerts you easily to any problems & therefore you can diagnose n fix them easier, it might take a bit longer in the end but you're more likely to get the result you want without the hassle of crashes or extremely long renders with poor results n hrs of trying to work out WTF! 🤦‍♂️😂🤯😂 👍

Your timeline would look more like this with the grey cheque of alpha (you might be able to just do the greenscreen chroma thing tho if cropping your 3840x1080 file in half fixes the issue 🤷‍♂️🤸‍♂️)

john_dennis wrote on 4/22/2022, 6:34 PM

@D.Griffin

Capture five minutes of mic check with some gaming to share on Google drive, One Drive, etc. and we will use the file to optimize workflow.

It seems to me that combining the screens into one file significantly increases the back-end processing over a "multi-camera" like capture where you have to sync two files. Theoretically, there's no clock drift, though.