Lots of glitching frames after upgrading to Vegas Pro 21

Richard-Steele wrote on 10/24/2023, 2:28 PM

Hi guys,

I've been making videos using OBS Studio and Vegas Pro 20 for a while now without any issues. A few days ago I just upgraded to Vegas Pro 21 and using exactly the same settings I am now running into issues. The issue is many glitches within both the video preview and also the rendered video result however, the original files are totally fine. It seems to be Vegas 21 causing these glitches.

Video example of my issue, seen at 14seconds - https://streamable.com/3w1y2h

This same issue appears throughout whole video many times.

In OBS studio I am recording the video into MP4 format using video encoder NVIDIA NVENC H.264, rescaling my output from 1920x1080 up to 2560x1440, 60 FPS, CBR of 13,000 kbps, two passes, high quality, max b frames is 2, psycho visual tuning is enabled. I also tried NVIDIA NVENC HEVC but get the same issue.

In Vegas 21 Pro, I am using resolution 2560x1440 in project settings, disabled resample (in project settings and by right clicking video file), Best rendering quality, 60 FPS, pretty much everything else set to default.

I still have Vegas Pro 20 installed. Not sure if that affects anything?

The glitches show in the preview, every now and again a frame will just completely glitch out, almost like showing a different part of the video for 0.25 of a second before continuing.

For rendering settings I am using MAGIX AVC/AAC MP4, 2560x1440p, 60 FPS, 9,000,000 bit rate max and 9,000,000 bit rate max set to VBR, Preset is high quality, Encode mode is NV Encoder, video rendering quality set to max.

I have tried 32gb RAM running at 6000mhz, ASUS ROG STRIX 3090, AMD 7950x, all really high end stuff. Everything worked fine before, its just when i upgraded to 21 Pro that these issues began. Worth noting I did get Vegas Pro Post 21. Note the Post part, it installed a tonne of plugins - all the stuff that comes with that package. Could any of that be of any cause here?

Please someone help, I just paid a tonne of money for this upgrade from 20 pro to 21 post pro and now cannot make videos. Really will appreciate the assistance!

Thanks, Richard

Comments

RogerS wrote on 10/24/2023, 4:11 PM

Are preferences/ video and preferences file i/o the same between versions of VEGAS?

Does rendering to MagixAVC with Mainconcept show the same issues?
What about temporarily setting dynamic ram preview to 0MB. Does that help (shouldn't be needed with 21 but worth a try).
Another potential fix is disabling GPU in preferences/ video (re-enable to edit again).

While probably not related, for OBS it's best to set the keyframe interval to 1 for better performance. For the render try the default NVIDIA template vs max and set a higher maximum bitrate than average to take advantage of variable bitrate.

Robert Johnston wrote on 10/24/2023, 5:02 PM

@Richard-Steele  If not already, try setting in File I/O preferences Enable Legacy AVC Decoding. That one really helped me. The Hardware Decoder to Use is set to Auto.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro

Howard-Vigorita wrote on 10/24/2023, 5:12 PM

@Richard-Steele Do your old projects do that when pulled into vp21 and re-rendered? If it's just new projects created with vp21, it's probably a default preference you changed in vp20 and forgot about. I'd suspect the loop switch which is checked by default for new clips. If it's checked and the clip gets lengthened, the beginning frames get repeated at the end. If that's it, the default can be changed in Preferences/Editing.

mark-y wrote on 10/26/2023, 5:49 AM

 CBR of 13,000 kbps, two passes,

Doesn't quite sound right.

Try VBR, two passes, maybe higher ABR than 13,000Kbps.

Lnrdgo wrote on 1/7/2024, 4:54 PM

None of the above is helpful. MAGIX: Fix the version 21 issues. We are paying a lot of money for a product that is not working. This is the first time I have seen this problem in any of the versions. And it really sucks that a project that I have been working on for two weeks is not backwards compatible to ver 20. Frustrating as heck!!!

EricLNZ wrote on 1/7/2024, 7:07 PM

@Lnrdgo Is your problem exactly the same as that experienced by Richard-Steele, the original poster?

Richard hasn't posted back since his 25 October 2023 post so we don't know if he resolved his problem.

Lnrdgo wrote on 1/7/2024, 11:59 PM

Basically yes. Glitch city. I’ll render the clip out, video blacks out comes back blacks out. Also, I just discovered that my FX’s are not working half the time or don’t manifest in the render. This sucks. Heading back to version 20. As Richard said, just paid a lot of money for the upgrade. I’ll add ‘tis a piece of crap.

pierre-k wrote on 1/9/2024, 4:23 PM

You are probably another one of us who has a problem with setting the number of threads in Vegas. In the video folder, set the number of fibers to 1 and the flickering problem will disappear. Set the dynamic memory as you want, but not to zero! Vegas is slow after that.

Former user wrote on 1/9/2024, 5:33 PM

In the video folder, set the number of fibers to 1 and the flickering problem will disappear.

@pierre-k What's the negative to doing that?

RogerS wrote on 1/9/2024, 7:19 PM

In theory I think that would reduce performance but in practice may trade one bottleneck for another and not have a big impact.

Hopefully video engine improvements address all of these issues.

Former user wrote on 1/9/2024, 7:23 PM

@RogerS With sample project benchmark, I get 19.40fps with what I think is default threads (32), but with 1 thread I get 19.66fps encoding to 4K. There's got to be a downside though otherwise Vegas would default to 1 thread.

Lnrdgo wrote on 1/21/2024, 2:12 PM

Okay, I'm having the same issue as I posted above, and it seems to have started when I installed Version 21. I have attached a Vimeo link showing what is happening to my renders. It seems to happen when I copy and paste camera 2 into the time line. I first noticed this when I installed 21. I'm not too geeky when it comes to the various RAM and rendering threads but I tried various settings and nothing worked. So I uninstalled 21, and tried in ver 20. Same problem. Then I went back to 19. Same problem. I've tried every imaginable fix I can think of...turning off the wifi and anti virus software, stopping as many extra background applications as I can. Still having the same issues. The attached is back in version 20. The only thing I can think of is that something was left in the registry from ver 21 even after I uninstalled the version, or something in the latest NewBlue that came with ver 21 is causing this issue?? Regardless, this sucks. I'm sure there will be various comments on how to tweak this setting or that setting. But the issue is: Version 21 is unstable and is causing huge problems. One shouldn't have to spend half the time editing trying to figure out what the heck is bugging this version and causing other previous versions to bug out. BTW, not once did this happen pre instillation of 21. HELP!!!!

Here's the vimeo link: https://vimeo.com/904979933?share=copy

Please, someone help!!

Lnrdgo wrote on 1/21/2024, 2:40 PM

P.S. I forgot to mention that my video event FX's are not holding when the render is done. I basically use two simple FX events: Brightness and Contrast, and Video Tuneup Plus. When the render is complete, the FX's will work for about the first minute or so. After that, the don't hold in the video. Again, same issue in versions 19 and 20. AND again; this did not happen pre version 21. In the following link, you'll notice that the subjects face has a darker more realistic skin tone. At 1:20 or so, it goes back to the lighter color of how we originally shot it. Same thing with the added broll (completely random): https://vimeo.com/903928624?share=copy

Please fix these issues MAGIX!!! Please! This can't just be happening on my machine.

Adis-a wrote on 1/21/2024, 3:11 PM

@Lnrdgo Try disabling GPU acceleration of video processing?

Richard-Steele wrote on 1/21/2024, 3:33 PM

@Richard-Steele  If not already, try setting in File I/O preferences Enable Legacy AVC Decoding. That one really helped me. The Hardware Decoder to Use is set to Auto.

Hi guys,

It was this that fixed things for me in the end.

Why is Vegas so fiddly?

Why can't it come with some hot tips of quick fixes? I have a top end PC and I have to flick like 4-5 settings every time after fresh install? shouldnt this only be the case if I had an ancient pc?

 

Thanks

Lnrdgo wrote on 1/21/2024, 3:56 PM

Thanks gang! I'll give these changes a go and get back on this. Working on a big project and cranking out a short about every three or four days so its good timing to try and figure this out. I do know I've gone back and forth with enabling/disabling the GPU accelerator.

Lnrdgo wrote on 2/2/2024, 12:37 PM

Nearly one month later, still working on the same project, still having the same problems. The video Event FX's don't hold when rendering, the unstable video becomes shaky and unstable, or the broll or second camera disappears completely during render. This now happens in all of the versions I have on my machine...19, 20, 21. The problems did not occur pre Version 21 installation. I cannot imagine I'm the only one having this issue. Thankfully, I don't have a major project going into a festival or on a big screen presentation, or I would be completely screwed.

Does MAGIX know about these issues? Is there anyone on this thread who is a developer for MAGIX? Again, I have tried every combination of settings within the program and on my PC. So. Short of reinventing the wheel, and starting all over again with a new and more stable editing platform, I honestly don't know what else to do. One thing for sure. MAGIX should be giving this piece of sh&$ away for free. It's a total ripoff in this state.

Does anyone have connections to the MAGIX developers and could possibly start communicating with them? Thanks for any help you can offer.

fr0sty wrote on 2/2/2024, 12:56 PM

You say the issues weren't present in previous versions, but are now... that shows it could be an influence outside of VEGAS that could be causing these issues. Driver issues, windows updates, etc. can be culprits. Software doesn't just stop working on its own when it worked fine before, and VEGAS 21 has no ability to affect the installations of previous versions.

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)

RogerS wrote on 2/2/2024, 9:15 PM

Nearly one month later, still working on the same project, still having the same problems. The video Event FX's don't hold when rendering, the unstable video becomes shaky and unstable, or the broll or second camera disappears completely during render. This now happens in all of the versions I have on my machine...19, 20, 21. The problems did not occur pre Version 21 installation. I cannot imagine I'm the only one having this issue. Thankfully, I don't have a major project going into a festival or on a big screen presentation, or I would be completely screwed.

Does MAGIX know about these issues? Is there anyone on this thread who is a developer for MAGIX? Again, I have tried every combination of settings within the program and on my PC. So. Short of reinventing the wheel, and starting all over again with a new and more stable editing platform, I honestly don't know what else to do. One thing for sure. MAGIX should be giving this piece of sh&$ away for free. It's a total ripoff in this state.

Does anyone have connections to the MAGIX developers and could possibly start communicating with them? Thanks for any help you can offer.

It's the source video that VEGAS doesn't like and that holds from 19-21 as they're all variations of the same program. Since this isn't your thread I don't see info about your system but is it an NVIDIA GPU by any chance?

Try re-encoding the source and then replace it within VEGAS "swap video files" and see if your problem disappears. I use ShutterEncoder with output codec h264 or editing codec ProRes.

Lnrdgo wrote on 2/6/2024, 4:21 PM

But why have to go through all of this re-encoding etc. I'm a video editor, not a programmer. fr0sty, I beg to differ. If version 21 has set something up in the registry, then it will affect earlier versions. I simply want version 21 to work. And it doesn't a lot of the time. And crashes. I did include info about my system. See above. Instead of having this discussion, is anyone on this thread a developer of Vegas Pro? Can't someone look into the problem instead of excuses for a dysfunctional program? I'm not trying to be a jerk here. I'm just saying that something is definitely wrong with version 21 and I am frustrated. In a big way.

RogerS wrote on 2/6/2024, 6:16 PM

If you want support, file a support request. We are fellow users.

mark-y wrote on 2/6/2024, 6:19 PM

If version 21 has set something up in the registry, then it will affect earlier versions.

No, that does not happen. Each installation is autonomous.

Jeffrey-Stachowiak wrote on 5/19/2024, 8:38 PM

So I was having the same issue I think. Glitching and a Picture in Picture flashing both especially on transitions. I tried turning on and off several things and I found that the Optimal - NVidia GeForce STX2060 was the culprit. Turned that OFF on the Video tab of Preferences and the glitches are gone. NVidia RTX2060 has latest driver, and Vegas 21 Build 314. The rendering speed is noticeably slower now.