Lots of glitching frames after upgrading to Vegas Pro 21

Comments

Jeffrey-Stachowiak wrote on 5/21/2024, 3:37 PM

An extra step, to me anyways, is not a solution.

Wolfgang S. wrote on 5/21/2024, 4:00 PM

I started having the same glitchy issues after updating v21to build 300 a while back. I was able to get around it by using Adobe Media Encoder to convert all my files to Apple Pro Res.
 

So the conversion ti ProRes has helped? I remember, GoPro had also aquired Cineform long time ago. Hmmm

 

Now, after updating to build 314 yesterday the problem hasn't shown up.

So with b 314 you do not see that anymore? Is that a solution then?

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

RogerS wrote on 5/21/2024, 7:46 PM

PiP is the Fx you mentioned. You see this error with no PiP Fx applied?

So I was having the same issue I think. Glitching and a Picture in Picture flashing both especially on transitions

Or did you just mean pan/crop to create a picture in picture like effect? Anyway not replicating it on my laptop. I can try with my desktop later.

I do not use PiP, I mentioned it because one of the glitch renderings there appeared to be a PiP in the lower right corner of the frame flashed like a PiP. Also FYI, In Preferences in File I/O "Enable legacy AVC decoding" is Checked and "Enable experimental HEVC decoding" is Unchecked.

While having nothing to do with this HEVC media I suggest unchecking the legacy AVC decoding- it's the old so4compound one which has various bugs and will be going away.

You could try enabling experimental HEVC (also the same to be phased out decoder) and see if there is any difference with this media.

For my own test conditions, preferences video has my GTX1050 enabled, dynamic ram preview is on defaults, file io has legacy AVC and experimental HEVC unchecked. Latest NVIDIA studio driver. Project is in 8-bit full mode. I rendered using a template with NVENC at the same framerate and resolution as the project. No glitches.

I'll try with my 2080 Super soon.

Jeffrey-Stachowiak wrote on 5/21/2024, 8:02 PM

I started having the same glitchy issues after updating v21to build 300 a while back. I was able to get around it by using Adobe Media Encoder to convert all my files to Apple Pro Res. Now, after updating to build 314 yesterday the problem hasn't shown up.

So you're saying since upgrading to 314 you don't have to convert your videos? What graphic card do you have?

RogerS wrote on 5/21/2024, 8:24 PM

With my RTX 2080 Super and VP 21.314 I just did a NVENC render (UHD 60fps) and here's the result. I don't see glitches.

Wolfgang S. wrote on 5/22/2024, 1:21 AM

I also have an Nvidia 3080 Ti in my laptop and I don't notice any glitches; the rendering results are quite similar whether I use the Nvidia GPU or not, especially after the latest update.

What confounds me is the subpar quality of the original footage. I understand that encoding a water surface is challenging because of the constant movement, yet there is noticeable blocking in both the original and the rendered footage.

Perhaps we're missing something that you're seeing?

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Jeffrey-Stachowiak wrote on 5/29/2024, 4:26 PM

I updated Vegas as of last update, and the last video I processed worked great with Nvidia on. So for now its fixed. BTW I leave Legacy AVC decoding checked because it fixes the choppy monitor playback when editing. With it unchecked the monitor playback while editing is slow and choppy.

Jeffrey-Stachowiak wrote on 6/24/2024, 7:54 AM

Latest update on Glitching - I've rendered a few videos with no problems however yesterday got the glitching again. During a Specific Title screen. I went and changed the Titles to Legacy Titles instead of the new Vegas Titles and the glitching did not appear.

RogerS wrote on 6/24/2024, 8:36 AM

@Jeffrey-Stachowiak Could you make a super simple project and media available with the title part that shows glitching? I'd like to test it with my two NVIDIA systems and help get this fixed.

It's interesting you need to use the old decoder with your NVIDIA for performance reasons. Could you share MediaInfo for the media you are using (or a sample again)? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Martin-Visser wrote on 6/29/2024, 4:46 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.

I beg to differ. I removed vegas 21 and reinstalled it on administrator profile, as instructed by support. After that all my settings were lost in vegas 20! It was completely back to state after installation. So I think there is really a problem with interaction between 21 and 20.

I am completely not happy with 21:

I could not preview hdv files, vegas 21 crashed with red preview screen after a while and render had same problem after several minutes. Underlaying problem: memory low. 64GB and only 16 in use! Also the fps of 21 was in preview lower then for 20 (for hdv and 4k files). Also advertisement was the fastest version ever. It practice is much slower then 20. My pc can preview 4k files in best (full) setting with color corrections on clips without a problem. Transitions not but the clips themselves work in full setting for 20. In 21 I had to lower to best (half) to get the same results. For HDV the same results.

I have tried all possible settings and no solution for version 300 and new versions 314/315. It does not work.

I have removed it and asked and got my money back and gone back to 20.

Before I removed 21 I opened 20 and 21 simultaneous and copied everything from the projects in 21 to 20. After that I copied and pasted in vegas 20 my event attributes from the adjustment events to the clips themselves. Yes, event attributes can be copied from 21 to 20. They don't work in 20 but it is possible to copy the events from them. Cost less time then do it all over again.

I only can hope 22 will be better. But this time I will test it first before buying!

 

pats2265 wrote on 11/18/2024, 9:38 PM

I'm having the same issue and just found this thread (Glitching during transitions for me).
I've used Vegas since Vegas Pro 8.0 and never seen this kind of problem.

I noticed it when I took a video that was created from Vegas Pro 20 and did some minor edits in Vegas Pro 21. When I rendered using Vegas 21, the glitches were observed. I re-rendered using Vegas Pro 20 and no artifacts (glitches) were observed.

I should add that iPhone 14 Pro video downloaded from iCloud at 1280x720 did not encounter the glitching that occurred with other video files I worked with. In all cases, I was using MP4 files as the source files.

I'm not interested spending time testing this since I have a version that works and don't really need to use Vegas 21 but want to continue supporting Vegas/Magix.

RogerS wrote on 11/18/2024, 9:55 PM

@pats2265 I'd use build 208 of 21 as it doesn't have glitches in my testing and is basically 20 with bugfixes. Uninstall 315 and download 208 from here: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

pats2265 wrote on 11/18/2024, 10:34 PM

@pats2265 I'd use build 208 of 21 as it doesn't have glitches in my testing and is basically 20 with bugfixes. Uninstall 315 and download 208 from here: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

Thanks. I'm giving that a try.

A note of disappointment: When I tried to re-render a video that had glitches Vegas 21 (Build 208) could not open and use the *.VEG file created with Vegas 21 (Build 315). This IMO is a bug as a change in build shouldn't be requiring new file formats or changing existing Vegas 21 file formats.

 

RogerS wrote on 11/18/2024, 10:46 PM

The changes to VEGAS Pro after build 208 were so massive they incremented the project version. It's not a bug and was in the release notes.

As a workaround you could copy a 315 timeline to 20.411, save it and open it in 208.

pats2265 wrote on 11/19/2024, 8:15 AM

The changes to VEGAS Pro after build 208 were so massive they incremented the project version. It's not a bug and was in the release notes.

I'm a software developer (30+) years. You can defend it if you want (call it a feature), but IMO it is bad form to change the format in a major release, as is indicated when the realized they needed to change the project version.

As a workaround you could copy a 315 timeline to 20.411, save it and open it in 208.

I no longer have the *.VEG v20 to go back to... In general, when there is a major version change, I save the previous *.VEG file with the version number (PROJ-v20.veg), but in this case I didn't because the edit/tweak was so small.

So moving forward... (and thank you for all of your help/responses)...

I deleted version 315 and so I'm not sure if two versions of Vegas 21 can co-exist (208 and 315). My thought is to re-install Vegas 21 (Build 315) so I can open it and copy the events to Vegas 20.

Also, does version 22 also fix it, and I would expect that Vegas 22 would open my current Vegas 21 (Build 315) *.VEG file to support the changes I've made.

As I've said, I'm a major fan of Vegas and want the product to succeed and would 100% likely upgrade to it at some point. I'd like to believe that what happened was a one off. The early days of Vegas (before Magix acquired Vegas) had it's issues too!

RogerS wrote on 11/19/2024, 8:36 AM

I didn't defend anything and this change got quite a lot of criticism at the time as build 300 had major bugs and users couldn't return to 208 with their projects.

Many decoding issues with 21.300+ have been fixed by now and a lingering large issue with green frames during transitions will be addressed in an upcoming patch to 22 according to a recent post by a developer. My advice would be to wait and trial that patch and see if it works for you.

You can reinstall 20 at any time and 20 and 21 can coexist on the same machine. That should let you copy over your current project as I recommended.

I also want VEGAS to succeed.

pats2265 wrote on 11/19/2024, 9:32 PM

I didn't defend anything ....

My apologies, I read more into this than I should have.

pats2265 wrote on 11/20/2024, 8:33 PM

So I've got another video that was ONLY edited in Vegas 21 (Build 315) and want to copy it to Vegas 20 (Build 411). The copy of the events worked, but the Markers are not being copied.

I did a search and found this

https://creativecow.net/forums/thread/copying-markers-between-projects/

which says:

there is a way to do this.
In Edit Details in the first project, select Markers in the Show column.
Click the blank space under the word Show (above the #1 and to the left left of Position) to highlight everything.
Do a Ctrl+C to copy.
Start a new instance of Vegas, open Edit Details, click that same box and paste by doing Ctrl+V.
I just tried this on an empty project and, to my surprise, it worked

So I'm trying to find the Edit Details dialog or how that works. I'll keep looking.

I think I found it... See https://video.stackexchange.com/questions/24138/how-to-copy-markers-and-regions-between-projects-in-vegas-pro

which says View | Window | Edit Details

I switched to the Marker's list, and selected all of the rows of Markers and press Ctrl+C to copy them.

I opened a 2nd copy of Vegas Pro 20 (Build 411) and opened the View | Window | Edit Details dialog and navigated to the Markers list and clicked on a row and pasted (Ctrl+V) and viola, it worked!

All my markers copied to the other project.

I'm tempted to delete this since it is no longer a question but it might help others who need to do this so I'll leave it unless folks say I should delete it.

Dexcon wrote on 11/20/2024, 8:39 PM

@pats2265  ... Edit Details can be found under the View/Window menu:

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

RogerS wrote on 11/20/2024, 8:55 PM

I think keep it as others may benefit, you never know what someone will search for and find this post in the future.