Glitches in preview windows and rendered file

Vegas21_user wrote on 5/5/2024, 6:09 PM

My project is not working properly. After imported a file from camera I can see a lot of glitches on it. Here you can see glitches and also you can see that video file is working properly in Windows Media Player on the left:
Here is rendered file with a lot of glitches:  https://we.tl/t-NruVMUu5Kt

Why I still have a lot of troubles with Vegas 21?
The funniest thing is that I actually was working about video about Vegas 21 and I talked about its bugs. So, left that type of glitches in my rendered video fits perfectly to the topic.


Here is mediainfo:

Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (mp42/avc1/CAEP)
File size                                : 101 MiB
Duration                                 : 14 s 114 ms
Overall bit rate                         : 60.0 Mb/s
Frame rate                               : 59.940 FPS
Performer                                : SAVSKY.MEDIA
Encoded date                             : 2017-09-14 14:04:47 UTC
Tagged date                              : 2017-09-14 14:04:47 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=3, N=30
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 14 s 114 ms
Bit rate                                 : 59.6 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.480
Stream size                              : 100 MiB (99%)
Language                                 : English
Encoded date                             : 2017-09-14 14:04:47 UTC
Tagged date                              : 2017-09-14 14:04:47 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 14 s 101 ms
Bit rate mode                            : Constant
Bit rate                                 : 256 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 438 KiB (0%)
Language                                 : English
Encoded date                             : 2017-09-14 14:04:47 UTC
Tagged date                              : 2017-09-14 14:04:47 UTC
 

Comments

RogerS wrote on 5/5/2024, 11:19 PM

Try build 208 or check enable legacy AVC decoding in preferences file io.

Wolfgang S. wrote on 5/6/2024, 1:45 AM

Having an original test file from the footage would be more helpful than a rendered clip, which cannot be used to test this issue. Original footage should be utilized for that purpose.

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

Vegas21_user wrote on 6/9/2024, 9:18 PM

Try build 208 or check enable legacy AVC decoding in preferences file io.

Try build 208 or check enable legacy AVC decoding in preferences file io.

Okay, but what about this problem in the future?

I can't afford to have a non-working version of the program.

If the older build works, does it mean that I (as a legal Vegas user and BUYER) should not use the newer version that I am entitled to? I want this program to have no errors and work properly. Just like with other companies.

RogerS wrote on 6/9/2024, 9:22 PM

If you want the problem solved other users need to be able to replicate it so please provide an original file. I wouldn't assume the developers have tested the new decoder with the media you are using.

Personally I am using build 208 of 21 and plan to next update when 22 comes out as I'm sure it will fix the issues with 21.315.

Vegas21_user wrote on 10/6/2024, 6:55 PM

If you want the problem solved other users need to be able to replicate it so please provide an original file. I wouldn't assume the developers have tested the new decoder with the media you are using.

Personally I am using build 208 of 21 and plan to next update when 22 comes out as I'm sure it will fix the issues with 21.315.

Having an original test file from the footage would be more helpful than a rendered clip, which cannot be used to test this issue. Original footage should be utilized for that purpose.

Ok, here you are: Transfer will expire in next 7 days. https://we.tl/t-3KZgc9b1Zn

EricLNZ wrote on 10/6/2024, 8:15 PM

MVI_5530.MP4 plays okay in my VP21/315 at 59.94 fps using mxcompoundplug.dll.

RogerS wrote on 10/6/2024, 9:13 PM

Thanks very much for this. What is your GPU? With my laptop (RTX 4060 GPU), I tested it with VP 21.208 and VP 22.122 and didn't encounter glitches. I used the clip twice on the timeline with a fade out and fade in, stepped backwards, skipped around the timeline, etc. which can often trigger glitches.

My guess is that 21.208 never had this issue and it was resolved by 22.122. Consider the trial of 22 to test it for yourself.

Edit::with further testing- just a crossfade on the same track vs multiple tracks- I don't see glitches like above but do see green screens.

I'd stay on 21.208 until this is resolved.

 

Last changed by RogerS on 10/6/2024, 9:36 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 5070 (12GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250
VEGAS Pro 23.302

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

john_dennis wrote on 10/6/2024, 11:04 PM

@EricLNZ said: "MVI_5530.MP4 plays okay in my VP21/315 at 59.94 fps using mxcompoundplug.dll."

The clip worked fine on the machine in my signature, also. Windows Pro 11. I worked with the media about 30 minutes.