[Wayne Waag]

Using OBS is your problem. Right now there are similar complaints by those attempting to use OBS using a variety of their available codecs. Just read some of the threads. Sadly, I have yet to see a solution. I would look to find some screen recording software compatible with Vegas. I’ve used Mirillis Action without a problem, although I don’t record games. It records 1920 x 1200 (monitor size) at 60 fps without issue. It always surprises me that so many will spend big bucks on a PC, money on Vegas which is a high end editor and then use freeware for screen recording. Bottom line–look for a better way to do your recordings.

wwaag

[Wayne Waag]

You’ve provided info about your PC and render settings, but nothing about your source footage and project settings. Also what type of FX are you applying? I often record at 1080 60P using a Sony Handycam and renders, even with a number of FX such as levels, color-match and unsharp are close to .8 real-time with an old i7 3770K CPU and a weak Nvidia 650 video card. You need to provide detailed information.

wwaag

[Wayne Waag]

In my book at least, you have a very high-end system–I’m a bit envious. That should not be an issue. All along, it’s sounded to me like a codec issue. Does OBS support Intel Quick-Sync which I know doesn’t have an issue inside of Vegas? Mirilli’s Action supports QS plus its own avi which imports well into Vegas. May not make a difference, but given all the problems with OBS, it might be worth a try. I’ll have a look upon return to my editing system, hopefully this weekend sometime. In the interim, perhaps someone else might have a look.

wwaag

[Wayne Waag]

From what you describe, your problem is with the preview and not the rendered output. Moreover, I couldn’t find your PC specs. A 1080 60P project is pretty demanding to begin with, especially using high bit rate mp4 footage as your source material. Add your velocity envelopes to that and it is not surprising that your preview would be marginal unless you have a really high-end system. Have you played around with different preview quality settings? It may help or may not, but it’s worth a try.

The bottom line is that since your final render is good, your poor preview performance isn’t a show stopper, just an inconvenience. When I return to my editing system (probably this weekend), I’ll give it a try.

wwaag

[Wayne Waag]

I’m confused. This is your first mention (?) of velocity changes. Are you applying a velocity envelope? If so, are you speeding up or slowing? Have you disabled resampling? More importantly, is your problem ONLY with preview performance? Are your rendered files OK? You mention a 10 sec clip that plays OK except when you make velocity changes. You could always upload that to Dropbox or something and perhaps someone might have a look at your clip.

wwaag

[Wayne Waag]

If you’re looking for a codec that will smart-render in Vegas, you might try UT Video or Magic YUV. My preference is Magic YUV since it decodes nicely for decent playback.

wwaag

[Wayne Waag]

What happens to the second, lower video strip during the editing process if it is not at all visible due to the 100% opacity of the top video strip?

It should have no effect at all. One thing you could do, however, is to simply mute that video track. That seeking behavior that you describe where the frame number starts having a string of dots is clearly indicative that Vegas cannot properly decode your video file. I’ve experienced that with files having a variable frame rate and also files that were corrupted. If all else fails, re-render in Handbrake, although that is really not a good long term solution. Perhaps you could try a different recording codec if that is possible. On the Vegas Pro forum, someone was having problems with OBS Studio using the UT Video lossless video codec. Like I said earlier, you are not alone in having problems with OBS. Sorry I can’t provide a solution.

wwaag

[Wayne Waag]

I’ve seen quite a few recent threads complaining about OBS not playing nicely with Vegas. MediaInfo shows constant frame rate but I have seen that to be wrong as well. Try this. Open Vegas and then import one of your clips and when it asks if you want to set Project settings based on that clip, enter “yes”. Then open project properties (alt-enter) and check your frame rate to see if it is exactly 60 fps. If you see anything other than exactly 60,0, e.g. 60.012, then the clip has a variable frame rate. One thing you could do is to import that footage into Handbrake and then render to an MP4, making sure you choose constant frame rate. Handbrake can read such files without any problem. You would lose a bit of quality, but at least the resulting files would load into Vegas without issue and you wouldn’t lose those recordings.

One final thought. If you want to do a lot of recordings, find some “paid” software that is compatible with Vegas. I use Mirilli’s Action and it works well for screen recordings, although I don’t do game recordings. It records 60 fps without issue. I believe there is still a 30 day trial and it only costs about $30. I’m sure there are other commercial vendors. Good luck.

wwaag

[Wayne Waag]

What this means is that Vegas does not like your source media. This seems to be a common problem with game recordings–finding he right codec for Vegas. You need to provide detailed information on your source media (preferably a screenshot from MediaInfo). Vegas expects a constant frame rate recording and unfortunately much of the available recording software does variable frame rate recording. In any case, you need to provide more information about your recordings. Perhaps someone with experience with such recordings can be of help.

wwaag

[Wayne Waag]

LX-100 footage should be fine. Have you tried turning off GPU during render?

wwaag