That's not true. Highly compressed captures, especially with long GOPs seem to hit some kind of cache limits in VEGAS and struggle with performance and stability especially with GPU decoding. Converting them to lightly compressed ProRes or standard AVC can solve it.

There still may be other issues with VEGAS and stability but starting with good media is a basic precondition for having a successful edit [and advising someone not to avoid media with obvious problems isn't helpful for anyone.]

1 means create a keyframe after every second of footage. In this case that's 120 frames which is a lot.
I'd do 1 instead of blindly copying other people using different editing software. 2 would be 240 frames.
(0 is automatic so even greater number of frames).

For re-encodes I already explained this.

For troublesome types of footage I use the free ShutterEncoder to convert it using h264 or ProRes and then replace it in VEGAS. You can batch convert many files at once if you want.

Or re-render through VEGAS (don't really recommend as you are having problems with VEGAS and these files):

You can also try a workaround using VEGAS. Make a new project with only the screencapture. Render the file as Apple ProRes422 or MagixAVC with mainconcept.

By "replace it in Vegas" do you mean render back to mp4?

1 means create a keyframe after every second of footage. In this case that's 120 frames which is a lot.
I'd do 1 instead of blindly copying other people using different editing software. 2 would be 240 frames.
(0 is automatic so even greater number of frames).

For re-encodes I already explained this.

For troublesome types of footage I use the free ShutterEncoder to convert it using h264 or ProRes and then replace it in VEGAS. You can batch convert many files at once if you want.

Or re-render through VEGAS (don't really recommend as you are having problems with VEGAS and these files):

You can also try a workaround using VEGAS. Make a new project with only the screencapture. Render the file as Apple ProRes422 or MagixAVC with mainconcept.

Okay, I will try this for my next video and see if it works. I'll let you know how it goes but I wanted to say thank you so much for helping me thus far and making things clear and easy to understand as well as doing so swiftly. Thank God for such a helpful forums page. Means a lot, God bless you all. Bruh moment for sure.

So far so good. I made one YouTube short after changing the keyframe interval to 1 but usually shorts don't cause any trouble since I can make them so fast and don't have to be in the program (VEGAS Pro) for so long. It usually occurs on my full-length videos so that will be the true test. I'll let you know what happens.

I've also seen this though it seems connected to the media I'm using. Screen captures cause the most problems.

Can you share MediaInfo for the main types of media you use? Here's how to share it: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

For troublesome types of footage I use the free ShutterEncoder to convert it using h264 of ProRes and then replace it in VEGAS. You can batch convert many files at once if you want.

Some discussion of optimizing OBS settings in the comments here.

I downloaded ShutterEncoder but I don't understand what you mean by "using h264 of ProRes and then replacing it in VEGAS." Do you have a tutorial or directions or something on how to do precisely that?

@r_ad Hi,

an MP4 is a container, a container is a bit like folder on your PC, within that container is the information of your video+audio, when you shared the MediaInfo you were sharing the information that is in that container, h264 is AVC (Video - Format on your MediaInfo - AVC), this is how the video information is compressed/shrunk to a manageable size, h265 is HEVC which is the same sort of thing to AVC but a more modern version designed to handle the bigger files of 4k, 6k 8k video etc,, , ProRes is another type of video compression format , there's other types of video container .MOV, AVI... & different types of compression format.

You would prob be better off Googling Video File Formats, Codecs and Containers, there's a lot of reading that I don't understand & the people on here can't really write it all here in simple comments, there's a bit too much, where do you start,

PS.

replacing it in VEGAS."

If you have a project that is underway you can 'Replace' footage on the timeline by right clicking on the footage in Project Media - Replace. So basically if you have poor variable footage on your timeline that isn't playing very well but you don't want to have to rebuild your project you can swap it out for the more stable converted video file

@r_ad Hi,

an MP4 is a container, a container is a bit like folder on your PC, within that container is the information of your video+audio, when you shared the MediaInfo you were sharing the information that is in that container, h264 is AVC (Video - Format on your MediaInfo - AVC), this is how the video information is compressed/shrunk to a manageable size, h265 is HEVC which is the same sort of thing to AVC but a more modern version designed to handle the bigger files of 4k, 6k 8k video etc,, , ProRes is another type of video compression format , there's other types of video container .MOV, AVI... & different types of compression format.

You would prob be better off Googling Video File Formats, Codecs and Containers, there's a lot of reading that I don't understand & the people on here can't really write it all here in simple comments, there's a bit too much, where do you start,

Thank you for the explanation! I just need to figure out what @RogerS meant as in the file type I should convert the mp4 obs screen recording to before I edit it in VEGAS Pro and also what I should render it to. And of course how to do it.

h264 of ProRes

@r_ad Hi, there's a spelling mistake in @RogerS's comment, I think it's supposed to read 'h264 or ProRes',

Thank you for the explanation! I just need to figure out what @RogerS meant as in the file type I should convert the mp4 obs screen recording to before I edit it in VEGAS Pro and also what I should render it to. And of course how to do it.

I'm sorry but I pretty much just told you that you'll have to do a little bit of research & a lot of what he wrote will become clearer.

h264 of ProRes

@r_ad Hi, there's a spelling mistake in @RogerS's comment, I think it's supposed to read 'h264 or ProRes',

Thank you for the explanation! I just need to figure out what @RogerS meant as in the file type I should convert the mp4 obs screen recording to before I edit it in VEGAS Pro and also what I should render it to. And of course how to do it.

I'm sorry but I pretty much just told you that you'll have to do a little bit of research & a lot of what he wrote will become clearer.

No, I understand that, and thank you. But I'm asking @RogerS for clearer instructions on what he suggested I do within the programs, not necessarily about the actual file types. I'm talking mainly about his actual method of using Shutter Encoder. Thank you for your help though with the "replacing" part within VEGAS Pro.

Sorry about the spelling mistake there.

Okay so for ShutterEncoder here's a quick guide.

First go to browse and select a file to start with. If you want to understand what is in it right-click on it and click "file information". This is the "MediaInfo" referenced before. It will tell you important things like if it's variable framerate or not, which codec it's using, bitrate, etc.

Next go to choose function and then if disk space isn't an issue editing codec, Apple ProRes. 422 should be sufficient. There aren't really other settings that need to be changed.

If it is an issue (it's a long recording), I use output codec h.264 with the arrow right of it selecting .mp4. For "image" on the upper right keep it at the same resolution "source". For bitrate if the original is also h.264 look at the bitrate of of the original and exceed it. Otherwise try CQ and start with a value of say 20 ("23" is default, lower is better quality with higher peak bitrates). Under advanced features check "set GOP to" and enter your target framerate here (30, 60, etc.). Click "start function" and look at the resulting file. If on your scenes with the most detail there is no visible quality loss then that CQ is a fine setting. You can set a lower number for higher quality (say down to 17).

Repalce the media in VEGAS (right-click in the media bin) and see if that looks okay and performs acceptably in VEGAS for you.

If others have your own approach or tips for ShutterEncoder feel free to share them!

Simple ZV-E10 H264 mp4, original files, dropped a few to the timeline and
like to seek to the next event on the timeline. Bumm! Vegas19b651 doesn't respond.

Force close the app, reopen project, and can work for another 5-10 minutes..

Whats going on here? Is there a 3rd party app which monitor Vegas behavior?
Memory handling error, dll error, decoding error? My system is very stable.
I can donate somebody if solve my issue.

@relaxvideo Can you make the original video available for download (google drive, dropbox, etc.)?

Windows has an "event viewer" which may yield clues.

You can also right-click on an application in task manager and "create dump file" and send that to VEGAS support.

Yes, here are a few, only for testing stability:
https://drive.google.com/drive/folders/1QUTREGOUY5zTLCRmpATQiFzKdvZdhEmq?usp=sharing

Thanks. Can you give any hints about the best way to trigger crashes? Are multiple clips overlayed? Any Fx, etc?

On my desktop (RTX 2080 Super with Intel UHD 770 doing decoding), I chopped up these files, overlapped them and then played them back for 10 minutes in a loop while watching another video. Then I skipped the playhead around the timeline for a few minutes while increasing and decreasing playback speed (press l multiple times). I wasn't able to crash it. I'll try on my laptop later.

Sorry about the spelling mistake there.

Okay so for ShutterEncoder here's a quick guide.

First go to browse and select a file to start with. If you want to understand what is in it right-click on it and click "file information". This is the "MediaInfo" referenced before. It will tell you important things like if it's variable framerate or not, which codec it's using, bitrate, etc.

Next go to choose function and then if disk space isn't an issue editing codec, Apple ProRes. 422 should be sufficient. There aren't really other settings that need to be changed.

If it is an issue (it's a long recording), I use output codec h.264 with the arrow right of it selecting .mp4. For "image" on the upper right keep it at the same resolution "source". For bitrate if the original is also h.264 look at the bitrate of of the original and exceed it. Otherwise try CQ and start with a value of say 20 ("23" is default, lower is better quality with higher peak bitrates). Under advanced features check "set GOP to" and enter your target framerate here (30, 60, etc.). Click "start function" and look at the resulting file. If on your scenes with the most detail there is no visible quality loss then that CQ is a fine setting. You can set a lower number for higher quality (say down to 17).

Repalce the media in VEGAS (right-click in the media bin) and see if that looks okay and performs acceptably in VEGAS for you.

If others have your own approach or tips for ShutterEncoder feel free to share them!

 

@RogerS u are an amazing person

I'll let you know if it works

Hey, @RogerS what do you think I should set my keyframe interval to for a 240 FPS video in OBS? Since you said 1 second for 120 FPS I thought 240 FPS might change something.

I think 1s is still okay. 240fps is going beyond normal video editing and may not play back well. I don't think you can render more than 120fps in VEGAS and sites like YouTube are capped at 60fps playback (The only time I've used that is for 10x slowmotion.)

I think 1s is still okay. 240fps is going beyond normal video editing and may not play back well. I don't think you can render more than 120fps in VEGAS and sites like YouTube are capped at 60fps playback (The only time I've used that is for 10x slowmotion.)

I see what you mean. It's a classic rendering trick in at least the competitive Minecraft content communities. You record at a high FPS such as 240 as well as enable smart resampling/any sort of frame blending setting or tool (seeing as you can replicate the same thing in Premiere Pro). Then when you go to render, you render the video to 60 FPS which causes all the extra frames to blend giving a motion blur type of effect. It's really gnarly.

I'm aware of the technique, VEGAS just wasn't made for it.

What about going into Shutter Encoder in the advanced section and setting the type of blending there? Then output 60fps and Vegas should work well with the files.

I'm aware of the technique, VEGAS just wasn't made for it.

What about going into Shutter Encoder in the advanced section and setting the type of blending there? Then output 60fps and Vegas should work well with the files.

Oh, my bad, I thought you were asking how it worked. That's a really good idea, it will probably make my editing process a lot smoother and also give me shorter render times. Thank you! I have been trying your h.264 strategy so far and it seems to be working pretty well but I'm going to continue testing it before I assume it's completely working. God bless you, man. And, of course, everyone else who's helping. :-) <3

Hey, side question:

Does anyone how to stop text from just being on 1 line? Like I want to create text like this:

What's good, Youtube?
Welcome back to another video!

But it always shows up like this:

What's good, YouTube?Welcome back to another video!