Problems with VEGAS Crashing w/ Video Recorded in OBS

Back to post

Comments

mark-y wrote on 4/2/2024, 10:28 PM

Jake, "keyint length" means the interval between keyframes, which are encoded from scratch and take longer to process than "b" or "p" frames, which are really just road signs. You can study this for yourself on the internet.

In Vegas, unless something has changed recently, a keyint of 300 frames is fine, but 301 frames will throw a little nag screen, something about "inefficient editing," which is a minor nuisance.

But since you are working with a hardware encoder, the keyint is displayed in seconds, not frames.

So, at 60 frames per second, a keyint of 5 seconds or less, should theoretically work. On my Intel QSV system, Auto (0) also works.

That's the math, you should test intervals of 1 to 5 seconds for yourself and let us know if it gives more improvement within Vegas. Inquiring minds want to know . . .

RogerS wrote on 4/2/2024, 10:31 PM

Set it to 1. (1 keyframe for 1 second of footage is what it means. 0 is auto and can be way too long like 250s).

For Preset and Tuning you might just try it on defaults at the moment and confirm that it even plays okay in VEGAS before experimenting further to optimize image quality. I wouldn't bother with multipass (but up to you).

JakeGetCake wrote on 4/5/2024, 6:27 AM

It appears that changing the keyint length to 1 has helped. I also changed my CQP number (not sure exactly what to call it) to 22. I’m not 100% sure if this did it because the footage I got was okayish so all I did was throw it into Vegas. I made sure to chroma key my face recording half and crop it to said location and same with gameplay before I started playing the preview and skipping around. It seemed to work much better, but I didn’t add any effects, music, or subtitles. I think it is fixed but if not, y’all will definitely find me here again. I would like to thank all of you for being so helpful when it comes to my issue.

RogerS wrote on 4/5/2024, 8:04 AM

Of course, we're here to help. CQP is okay quality- if there are detailed scenes with lots of motion consider a lower number if you notice artifacts.

I think at this point we have the media decoding in a good place.

No guarantees everything else will play back amazingly (esp. animated text, difficult Fx, etc.) but that's what highlighting part of the timeline and doing shift + b or shift + m are for.

Maybe mark this thread as solved (for now).

fr0sty wrote on 4/5/2024, 10:34 AM

I'll go ahead and tag this one as solved, if the issue pops up again, we'll un-solve it and get back to helping... if you don't mind, I'm going to edit the title to better reflect what the problem you are having is, so if other users are trying to find help with this same issue, they can search for it more easily. Let me know if you'd like that changed reversed, though, this is your thread and I don't want to give the impression that we are trying to "censor" your title at all.

Last changed by fr0sty on 4/5/2024, 10:35 AM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

mark-y wrote on 4/5/2024, 11:53 AM

Glad it's working better for you. Keep us posted.

 

Former user wrote on 4/5/2024, 5:11 PM

It appears that changing the keyint length to 1 has helped. I also changed my CQP number (not sure exactly what to call it) to 22. I’m not 100% sure if this did it because the footage I got was okayish so all I did was throw it into Vegas.

@JakeGetCake The CQP number is about efficiency only using the data it needs, with AVC it can still create very large files, but with HEVC and AV1 it works even better, I transferred over to AV1 a while ago, files half the size and in other editors it edits as smoothly as a knife through butter. Not seen a negative so far

@mark-y you keep saying Vegas edits just great at GOPs up to 300 even though you've seen countless cases where reducing the GOP to 30(in this case) or 60 fixes the problem. This is something you can try for yourself. transcode using handbrake with it's default template, then go back and transcode using production standard template. You want to stress your computer, so for me I'd test with 4K60, but if you haven't upgraded for a while use whatever it appropriate to stress your system.

Make a lot of cuts move sections around, add transitions and fades between the clips. If you have GPU decoding on you should notice a huge difference between smoothness of editing on playback. If you're a beta tester and that's what you're using now maybe you won't