[Wayne Waag]

Is your footage from an iPhone? If so, that is most likely your problem. Vegas expects a constant frame rate video and your iPhone by default records with a variable frame rate, which Vegas does not like. There is an app that you can purchase which enables to record at a constant frame rate plus set all kinds of other things. It costs about $10. It’s name is FilmicPro. I haven’t used it but it comes highly recommended.

wwaag

[Wayne Waag]

Debugmode Frameserver works fine in V13 on Windows 10. No guide needed. Just select the default template and render to the location of your choice with the file name of your choice. You should then be able to directly open that file in TMPGEnc Video Mastering Works., I’ve done this in Win 7, but have not tried it in Win 10, although I see no reason it shouldn’t work.

wwaag

[Wayne Waag]

Automation?? Not sure what you mean. In my post, I mentioned Animate not automate. Selecting the Animate button, the little clock-looking icon, in your effects window allows you to add keyframes at any point along the timeline and change the value of selected parameters–e.g. input level. In this manner you can change the values of parameters along the timeline and Vegas will automatically make those changes according to whatever type of keyframe you are using (e.g. linear, smooth, etc.).

wwaag

[Wayne Waag]

I’ve used the UT Video codec in the past without any problems. Just to make sure that it is installed properly, open any Vegas project and then open the Render dialog box, and select Video for Windows (.avi). Select any template, then customize and see if the UT Video codec shows up. You could even try a test render and then re-import it back into Vegas. My suspicion is that it’s a problem with OBS. I’ve never used it, but have seen many complaints when footage from OBS is imported into Vegas. Perhaps someone successfully using OBS in Vegas could offer some help. Good luck.

wwaag

[Wayne Waag]

I think you are looking for some type of autolevels capability. There was a filter written for Vegas by Mike Crash some years ago, but it only worked for 32 bit versions.

https://www.mikecrash.com/index.php?name=Downloads&d_op=viewdownload&cid=13

There are also filters available using Avisynth that may work. Having said that, the best is just to apply the Level FX filter in Vegas and then use Animate to change the white and black levels manually. It may be tedious, but the results may be better. How much, however, is pretty questionable since overblown highlights are virtually impossible to correct. Its always better to err in the direction of underexposure.

wwaag

[Wayne Waag]

Have you tried disabling your GPU?

Regarding format, here is a screenshot from the file properties box.

wwaag

[Wayne Waag]

I would presume it’s Sony Vegas Pro 13, but I don’t know for sure. Perhaps someone who has purchased the deal could comment.

wwaag

[Wayne Waag]

Good to know. Thanks for sharing.

wwaag

[Wayne Waag]

And just maybe it will permit email notifications whenever there is a reply–one nice thing about this forum and a shortcoming of the Sony Vegas forums.

wwaag

[Wayne Waag]

Everything works well on V13. I found V13 to be a lot more stable than V12 and some of its features and fixes are very useful to me. E.g. the built-in loudness logs and the fix for GoPro footage in the latest release. If you’re on V12, I’d recommend going for the offer. Like others have commented, the use of scripting in V14 will definitely be broken. We won’t know the real extent until the actual release. And for sure, it seems like the Frameserver will be lost since the developer has abandoned the project. But, V13 works well and the projects created are also backward compatible with V12. Who knows the compatibility issues with the new release. In any case, for the price, it seems a real bargain. Hope this helps.

wwaag