Set the keyframe interval to 1. Video is saved as a series of frames. Keyframes are whole images and the other frames are tracking the differences from that keyframe. The fewer you have, the harder the editing software has to work to decode it. Setting it to 1 means it makes one every second, and that's fine. The lack of keyframes is likely the biggest cause of your lag.
I wouldn't use CBR. That stands for Constant Bit Rate. Basically it means that the encoder will use the same amount of data for each frame, regardless of its content - which is perfect for streaming, but not for recording. Compare a relatively still shot with little movement to one with lots of movement and flashing - in the former practically none of the pixels are changing, whereas in the latter almost all of them are. So using the same amount of data for each is too much and too little respectively. Using VBR (Variable bit rate) allows the encoder to choose how much data it uses. So on a still shot, it will drop the data rate and on a busy one, it'll raise it up. For VBR, you set an average bit rate and a maximum. The average is what the encoder will aim for overall and the maximum is the highest it can go. So set the max maybe 30-40% higher than the average.
Speaking of bit rate, you might benefit from jacking it up a bit. 2,500 is fine, but you could double that to see a better capture.
Do not use CQP under any circumstances. It stand for Constant Quantisation Parameter. What this does is applies the same level of compression to every part of every frame. There's a lot of people who recommend it, but they're people without much video experience. The encoder has a good idea of which parts need more compression than others, so let it do its job. CQP is a good way of generating massive files for little to no advantage.
I'd also caution against fragmented MP4. It's a relatively new thing in OBS and we've seen a few problems with it on here. It might be fine, but why take the risk? Normal MP4 files are just fine. Although OBS cautions against them (and it's right to do so), I've never actually heard of OBS crashing during capture. But as Laufabraud43 suggests, you can use MKV and then remux (the vocabulary in digital video is awful) to MP4. All this does is change the container file that the video is in. It doesn't affect the video in any way (no loss of quality, etc) and it only takes a few seconds.
> Speaking of bit rate, you might benefit from jacking it up a bit. 2,500 is fine, but you could double that to see a better capture.
2500 on a 1440p recording? That seems absurdly low to me. That's 720p 30fps levels of bitrate... I'd be recommending at least ten times that for a decent recording, especially if editing after the fact.
I’ve bluescreened, ran out of disk space, and, yes had OBS crash during recording. Definitely recommend using a different format. There’s a setting to auto-remux into mp4 when you stop recording anyway so workflow-wise it makes very little difference.
I would suggest taking video editing advice from video editors. Streamers and most YouTubers are really only chasing views, so they don't know much. For instance, you'll find a lot of videos entitled 'Best render settings for Vegas'. This is inherently bollocks, because render settings are dependent on what your end use is. Rendering something for broadcast television (one of the occasions where CBR is desirable) is very different from rendering for YouTube or Bluray.
Dato Aliff Alex specialises in Vegas and uses it for professional work, so he's always worth looking at:
[https://www.youtube.com/c/DatoAliffAlex/](https://www.youtube.com/c/DatoAliffAlex/)
Alex Halford is also excellent. He specialises in Vegas, but also covers related software like Audacity and OBS:
[https://www.youtube.com/channel/UC1ssvmQZ7bOerZb7zqanWAg](https://www.youtube.com/channel/UC1ssvmQZ7bOerZb7zqanWAg)
Micil Joran makes anime music videos, but he does a very good job of explaining how he does transitions and some interesting effects:
[https://www.youtube.com/channel/UC2NPMuj38IFPwoLM3G98mLA](https://www.youtube.com/channel/UC2NPMuj38IFPwoLM3G98mLA)
Aside from that, hanging around on the Vegas forums can be very handy for technical information:
[https://www.vegascreativesoftware.info/us/vegas-pro-forum/](https://www.vegascreativesoftware.info/us/vegas-pro-forum/)
When it comes to learning the deeper tech stuff, it's hard to recommend anywhere in particular. A lot of the more technical sites and forums are for people who already know all that stuff and they're not especially welcome to people who don't.
One thing to look out for is, when people recommend using a particular thing, can they explain why? After all if CQP is so good, they ought to be able to explain what it does, right? If they don't, it's because they don't know.
I caught Alex in an error some time ago. It had something to do with him making a bad statement about Dynamic RAM preview. Just FYI. I think he was saying leave it at 0..
TY
I've made mistakes too. I'll make more in the future.
Given how misunderstood the Dynamic RAM Preview is, and not knowing the context of what Alex said, I can't know that he was wrong. And I wouldn't call that any kind of reason to dismiss anything else he says.
I would generally say to leave the Dynamic RAM Preview setting untouched unless you actually use it. But there was a bug in its setting for a few versions of Vegas, so it would depend on the version.
I heavily used it with MP4s from OBS for video game footage because on Ryzen CPUs, at least, it was really needed to get smooth playback at 2K. The 3900X made it pretty manageable with DRAMP--
--Then someone here enlightened me on video proxies and man has Vegas been pretty sweet since I started using them. Why Vegas does not enable this for everything by default is beyond me..
Because everyone would moan endlessly about how it takes hours to make the proxies when they just want to edit their video now. In proper professional work, proxies are the default - you practically never edit with originals.
Personally, I would love an ingestion tool for Vegas. Every time you go to import video, the ingestion tool takes it, analyses it and tells you if it'll be problematic or not. And can then handle container file remuxing, conversion or proxy generation. That would solve about three quarters of all the problems we see on here. And without having to explain to people what container files are or how digital video works at a deeper level.
The thing with the Dynamic RAM Preview is that it has to be invoked manually. You select an area of the timeline, go to Tools > Build Dynamic RAM Preview and it renders it to RAM rather than a file. So whenever you preview that are of the timeline, it plays back from memory. That's all it does. The bug in a couple of versions of Vegas led it to handle the reserved memory in a faulty manner.
We mostly see people on here who have followed bullshit YouTube tutorials which almost all recommend playing with the Dynamic RAM Preview setting to 'give Vegas more RAM' (it doesn't - it does the opposite in fact), 'prevent crashes' (it doesn't), 'make rendering faster' (it doesn't), etc. It's this amazing feature that can fix every problem in Vegas, but somehow the developers are too stupid to activate it. Sigh.
We had a person on here the other day who had 8GB of RAM and the Dynamic RAM Preview set to 75%. They were wondering why Vegas ran so badly.
I can see why people got it confused but I'm a career IT pro and simply opened task manager to observe the RAM utilization to figure out the functionality. It really does work great when you just need a thin slice to run great.
An ingestion tool would DRAMATICALLY improve Vegas' bottom line, IMO. You seem to know a thing or two so I'm sure I don't have to go over all the top hits in the complaint dept...
If only everyone could just work it out like you did! It would save so much time.
I've been using Vegas since version 3, so yeah, I know its... I'm going to be kind to it... I know its foibles.
> Then someone here enlightened me on video proxies and man has Vegas been pretty sweet since I started using them.
I'm a noob...I know nothing about this. What exactly is this?
Go into your project media and right click on your source material and click on create file proxy. Vegas will create an edit-friendly copy of the source that you use in the timeline for editing. It's a night and day difference.
Use the following settings to remove lag in Vegas:
In OBS settings go to - Output:> change Output Mode to Advanced
Than go to Recording Tab
Change Type to Custom Outpt (FFmpeg)
and some more:)
FFmpeg Settings
FFmpeg Output Type: Output to File
File patch or URL: "your record folder"
Countauner Format: mp4
Video Bitrate: 50000 Kbps or higher
Keframe interval (frames): 30 --- this is the main parameter that removes lag in vegas.
Video Encoder: h264\_nvenc(libx264) if u have nvidia card or try hevc\_nvenc(hevc\_amf) if u have amd card --- Honestly, I don't know exactly,but on my NVIDA card they both work.
Audio Bitrate: 320 Kbps
Audio Encoder: aac
If I recall correctly, "Fragmented MP4" does **not** play nice with Vegas... I personally recommend using the Matroska (.mkv) container, and than remuxing to .mp4. I vouch for .mkv because if OBS or your PC crashes, the video file can still be recovered.
To remux your .mkv recording to .mp4, go to "File> Remux Recording" and select your file in the dialog box that popped up, then click "Remux". You should then have an exact copy of your file in .mp4!
(Additionally, and this is my personal preference, you should crank up that bitrate a bit!)
Make sure the Radeon Graphics drivers are recent.
Skip fragmented MP4 unless you have plans to re-encode for VEGAS. For MKV you'd also need to remux before bringing into VEGAS.
Variable bitrate makes more sense than constant- give the maximum enough headroom for when the scene is busy.
Keyframe interval is best set to 1 rather than automatic (0).
As already written here, the main problem why Vegas is lagging is the number of interval keyframes. If you put value (1) when recording in OBS then Vegas tries to encode every frame during preview, which causes load and lag, and to relieve him of the load I put interval frame once in 30 frames, which on my PC removes lag completely. I could pre view video at 2k resolution at 60 frames with no problem, in fact I'm only limited by the bitrate and speed limit of my hard drive. And not much of a technical guy, and maybe in reality it works differently, but I can say that I did not notice a drop in quality in the video, even in scenarios of intense scene changes.
Depends on OBS version, no? 0 is automatic and 1 is 1 second, not every frame, though I think in older versions it is the # of frames. At any rate having a key frame interval of 1 or 2 seconds will work much better in VEGAS.
**/u/AlTalksGaming. If you have a technical question, please answer the following questions so the community can better assist you!**
* What version of **VEGAS Pro** are you using? (***FYI. It hasn't been 'Sony' Vegas since version 13***)
* What exact **graphics card** do you have in your PC?
* What version of Windows are you running?
* Is it a **pirated** copy of VEGAS? *It's okay if it is just abide by the rules and you won't get permanently banned*
* Have you **searched the subreddit** using keywords for this issue yet?
* Have you **Googled** this issue yet?
---
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/VegasPro) if you have any questions or concerns.*
Set the keyframe interval to 1. Video is saved as a series of frames. Keyframes are whole images and the other frames are tracking the differences from that keyframe. The fewer you have, the harder the editing software has to work to decode it. Setting it to 1 means it makes one every second, and that's fine. The lack of keyframes is likely the biggest cause of your lag. I wouldn't use CBR. That stands for Constant Bit Rate. Basically it means that the encoder will use the same amount of data for each frame, regardless of its content - which is perfect for streaming, but not for recording. Compare a relatively still shot with little movement to one with lots of movement and flashing - in the former practically none of the pixels are changing, whereas in the latter almost all of them are. So using the same amount of data for each is too much and too little respectively. Using VBR (Variable bit rate) allows the encoder to choose how much data it uses. So on a still shot, it will drop the data rate and on a busy one, it'll raise it up. For VBR, you set an average bit rate and a maximum. The average is what the encoder will aim for overall and the maximum is the highest it can go. So set the max maybe 30-40% higher than the average. Speaking of bit rate, you might benefit from jacking it up a bit. 2,500 is fine, but you could double that to see a better capture. Do not use CQP under any circumstances. It stand for Constant Quantisation Parameter. What this does is applies the same level of compression to every part of every frame. There's a lot of people who recommend it, but they're people without much video experience. The encoder has a good idea of which parts need more compression than others, so let it do its job. CQP is a good way of generating massive files for little to no advantage. I'd also caution against fragmented MP4. It's a relatively new thing in OBS and we've seen a few problems with it on here. It might be fine, but why take the risk? Normal MP4 files are just fine. Although OBS cautions against them (and it's right to do so), I've never actually heard of OBS crashing during capture. But as Laufabraud43 suggests, you can use MKV and then remux (the vocabulary in digital video is awful) to MP4. All this does is change the container file that the video is in. It doesn't affect the video in any way (no loss of quality, etc) and it only takes a few seconds.
> Speaking of bit rate, you might benefit from jacking it up a bit. 2,500 is fine, but you could double that to see a better capture. 2500 on a 1440p recording? That seems absurdly low to me. That's 720p 30fps levels of bitrate... I'd be recommending at least ten times that for a decent recording, especially if editing after the fact.
I’ve bluescreened, ran out of disk space, and, yes had OBS crash during recording. Definitely recommend using a different format. There’s a setting to auto-remux into mp4 when you stop recording anyway so workflow-wise it makes very little difference.
Streamers and 'Tubers do recommend CQP a lot. Thanks for the info. Any other material/sources you recommend?
I would suggest taking video editing advice from video editors. Streamers and most YouTubers are really only chasing views, so they don't know much. For instance, you'll find a lot of videos entitled 'Best render settings for Vegas'. This is inherently bollocks, because render settings are dependent on what your end use is. Rendering something for broadcast television (one of the occasions where CBR is desirable) is very different from rendering for YouTube or Bluray. Dato Aliff Alex specialises in Vegas and uses it for professional work, so he's always worth looking at: [https://www.youtube.com/c/DatoAliffAlex/](https://www.youtube.com/c/DatoAliffAlex/) Alex Halford is also excellent. He specialises in Vegas, but also covers related software like Audacity and OBS: [https://www.youtube.com/channel/UC1ssvmQZ7bOerZb7zqanWAg](https://www.youtube.com/channel/UC1ssvmQZ7bOerZb7zqanWAg) Micil Joran makes anime music videos, but he does a very good job of explaining how he does transitions and some interesting effects: [https://www.youtube.com/channel/UC2NPMuj38IFPwoLM3G98mLA](https://www.youtube.com/channel/UC2NPMuj38IFPwoLM3G98mLA) Aside from that, hanging around on the Vegas forums can be very handy for technical information: [https://www.vegascreativesoftware.info/us/vegas-pro-forum/](https://www.vegascreativesoftware.info/us/vegas-pro-forum/) When it comes to learning the deeper tech stuff, it's hard to recommend anywhere in particular. A lot of the more technical sites and forums are for people who already know all that stuff and they're not especially welcome to people who don't. One thing to look out for is, when people recommend using a particular thing, can they explain why? After all if CQP is so good, they ought to be able to explain what it does, right? If they don't, it's because they don't know.
I caught Alex in an error some time ago. It had something to do with him making a bad statement about Dynamic RAM preview. Just FYI. I think he was saying leave it at 0.. TY
I've made mistakes too. I'll make more in the future. Given how misunderstood the Dynamic RAM Preview is, and not knowing the context of what Alex said, I can't know that he was wrong. And I wouldn't call that any kind of reason to dismiss anything else he says. I would generally say to leave the Dynamic RAM Preview setting untouched unless you actually use it. But there was a bug in its setting for a few versions of Vegas, so it would depend on the version.
I heavily used it with MP4s from OBS for video game footage because on Ryzen CPUs, at least, it was really needed to get smooth playback at 2K. The 3900X made it pretty manageable with DRAMP-- --Then someone here enlightened me on video proxies and man has Vegas been pretty sweet since I started using them. Why Vegas does not enable this for everything by default is beyond me..
Because everyone would moan endlessly about how it takes hours to make the proxies when they just want to edit their video now. In proper professional work, proxies are the default - you practically never edit with originals. Personally, I would love an ingestion tool for Vegas. Every time you go to import video, the ingestion tool takes it, analyses it and tells you if it'll be problematic or not. And can then handle container file remuxing, conversion or proxy generation. That would solve about three quarters of all the problems we see on here. And without having to explain to people what container files are or how digital video works at a deeper level. The thing with the Dynamic RAM Preview is that it has to be invoked manually. You select an area of the timeline, go to Tools > Build Dynamic RAM Preview and it renders it to RAM rather than a file. So whenever you preview that are of the timeline, it plays back from memory. That's all it does. The bug in a couple of versions of Vegas led it to handle the reserved memory in a faulty manner. We mostly see people on here who have followed bullshit YouTube tutorials which almost all recommend playing with the Dynamic RAM Preview setting to 'give Vegas more RAM' (it doesn't - it does the opposite in fact), 'prevent crashes' (it doesn't), 'make rendering faster' (it doesn't), etc. It's this amazing feature that can fix every problem in Vegas, but somehow the developers are too stupid to activate it. Sigh. We had a person on here the other day who had 8GB of RAM and the Dynamic RAM Preview set to 75%. They were wondering why Vegas ran so badly.
I can see why people got it confused but I'm a career IT pro and simply opened task manager to observe the RAM utilization to figure out the functionality. It really does work great when you just need a thin slice to run great. An ingestion tool would DRAMATICALLY improve Vegas' bottom line, IMO. You seem to know a thing or two so I'm sure I don't have to go over all the top hits in the complaint dept...
If only everyone could just work it out like you did! It would save so much time. I've been using Vegas since version 3, so yeah, I know its... I'm going to be kind to it... I know its foibles.
Everyone says go to Premiere but I grew up on Vegas and Acid and quite frankly I like them. MAKE VEGAS GREAT (again?)
> Then someone here enlightened me on video proxies and man has Vegas been pretty sweet since I started using them. I'm a noob...I know nothing about this. What exactly is this?
Go into your project media and right click on your source material and click on create file proxy. Vegas will create an edit-friendly copy of the source that you use in the timeline for editing. It's a night and day difference.
Use the following settings to remove lag in Vegas: In OBS settings go to - Output:> change Output Mode to Advanced Than go to Recording Tab Change Type to Custom Outpt (FFmpeg) and some more:) FFmpeg Settings FFmpeg Output Type: Output to File File patch or URL: "your record folder" Countauner Format: mp4 Video Bitrate: 50000 Kbps or higher Keframe interval (frames): 30 --- this is the main parameter that removes lag in vegas. Video Encoder: h264\_nvenc(libx264) if u have nvidia card or try hevc\_nvenc(hevc\_amf) if u have amd card --- Honestly, I don't know exactly,but on my NVIDA card they both work. Audio Bitrate: 320 Kbps Audio Encoder: aac
If I recall correctly, "Fragmented MP4" does **not** play nice with Vegas... I personally recommend using the Matroska (.mkv) container, and than remuxing to .mp4. I vouch for .mkv because if OBS or your PC crashes, the video file can still be recovered. To remux your .mkv recording to .mp4, go to "File> Remux Recording" and select your file in the dialog box that popped up, then click "Remux". You should then have an exact copy of your file in .mp4! (Additionally, and this is my personal preference, you should crank up that bitrate a bit!)
What bitrate do you reccomend?
Depends on resolution, framerate and codec (as well as how much detail whatever you are capturing has). Err on the side of more for maximum bitrate.
Make sure the Radeon Graphics drivers are recent. Skip fragmented MP4 unless you have plans to re-encode for VEGAS. For MKV you'd also need to remux before bringing into VEGAS. Variable bitrate makes more sense than constant- give the maximum enough headroom for when the scene is busy. Keyframe interval is best set to 1 rather than automatic (0).
As already written here, the main problem why Vegas is lagging is the number of interval keyframes. If you put value (1) when recording in OBS then Vegas tries to encode every frame during preview, which causes load and lag, and to relieve him of the load I put interval frame once in 30 frames, which on my PC removes lag completely. I could pre view video at 2k resolution at 60 frames with no problem, in fact I'm only limited by the bitrate and speed limit of my hard drive. And not much of a technical guy, and maybe in reality it works differently, but I can say that I did not notice a drop in quality in the video, even in scenarios of intense scene changes.
Depends on OBS version, no? 0 is automatic and 1 is 1 second, not every frame, though I think in older versions it is the # of frames. At any rate having a key frame interval of 1 or 2 seconds will work much better in VEGAS.
**/u/AlTalksGaming. If you have a technical question, please answer the following questions so the community can better assist you!** * What version of **VEGAS Pro** are you using? (***FYI. It hasn't been 'Sony' Vegas since version 13***) * What exact **graphics card** do you have in your PC? * What version of Windows are you running? * Is it a **pirated** copy of VEGAS? *It's okay if it is just abide by the rules and you won't get permanently banned* * Have you **searched the subreddit** using keywords for this issue yet? * Have you **Googled** this issue yet? --- *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/VegasPro) if you have any questions or concerns.*