@BONLEV No problem here opening and playing that mxf clip on my 11900k/6900xt desktop machine with Amd selected for both video and decoding. I 1st tested with vp22b169 before updating to b250. Amd driver v24.12.2. Fwiw, also fine selecting Nvidia 4090 or Intel a380 decoders.

@BONLEV No problem here opening and playing that mxf clip on my 11900k/6900xt desktop machine with Amd selected for both video and decoding. I 1st tested with vp22b169 before updating to b250. Amd driver v24.12.2. Fwiw, also fine selecting Nvidia 4090 or Intel a380 decoders.

thx for testing! It's strange I still have those glitches. I will test some further when I have more time.

A little late to the party. vacations....

Downloaded the clip and it played back fine (50fps Best>Half) in VP22 B250 with AMD driver 25.6.1

@BONLEV Is there another factor at play like an effect applied that could be triggering the glitch, or is just the uncut file on the timeline showing this distortion?

@BONLEV Is there another factor at play like an effect applied that could be triggering the glitch, or is just the uncut file on the timeline showing this distortion?

I waited for this answer when I had filmed a new "fresh" project.

I filmed a school performance this weekend and even without any effects applied I saw glitches in the timelime of VP22. Now I copied this to VP21 and see how this goes. I just started the project. I checked the original footage outside of vegas where I saw the glitch but the original footage played fine in VLC media player and catalyst browse. So no corrupted SDXC cards so far. Within a few days this will be edited so I can give a update.

Thanks for the update. 21.208 should be glitch free (I hope!)

If you have another file I'm sure we can all help test it. I doubt it's a card issue but rather an issue with GPU decoding in VEGAS.

Thanks for the update. 21.208 should be glitch free (I hope!)

If you have another file I'm sure we can all help test it. I doubt it's a card issue but rather an issue with GPU decoding in VEGAS.

I keep in mind to test 21.208 when I have more time to edit. I now have deadlines for the projects to make. So you think in my latest version of VP22 the GPU is glitching?

I think there are still some issues with how the new decoder in VEGAS handles media and uses the GPU.

I think there are still some issues with how the new decoder in VEGAS handles media and uses the GPU.

21.208 is refering to vegas pro 21? I have 21.0.0.208 which has no render glitches but freezes a lot while editing. There is no stable version in VP22? There I have almost no freezes while editing but the render glitch...

21.208 means build 208 of VEGAS Pro 21.

The most stable build of 22 is 250 but if you have render glitches that doesn't help you.

I am also also using Vegas 22 with an AMD card and I tend to see that while editing (and thus previewing using AMD acceleration) and with rendering that Vegas requires a ever growing amount of "Commited" memory. You can see this in the Task Manager and then under the Memory tab...

I found that in the end on my system I had my Virtual memory limited to only 2Gb of Page file. With that vegas 22 would crash randomly with either black screen or a plain windows crash or with luck (and the setting for it enabled ) a reporting tool of Vegas.
So what I did is increase the Page file on my fastest NVME disk from 2Gb to 32Gb which makes Vegas 22 a lot more usable, but it will still crash once the page file is full.

You can check your 'page file'/'virtual memory' settings in windows 11 via a search on 'view advance system settings'. In the Systems Properties window you click on the 'Advanced'-tab then click on Setting of the Performance section.
In that window (Performance Options) you click the Change button under the Advanced tab.

On my system it was custom set to 2Gb (probably something I did years ago on my Windows 10 install).
Nevertheless I have not tried 'System managed size' yet, but for me this worked to edit fairly okay on 40Gb of 4K of mp4 footage into a 2 hour video. For rendering I needed to increase the page file from 16Gb to 32Gb.

Another thing that helped me to use Vegas 22 with more stability is using the 'Enable legacy AVC decoding' under Options -> Preferences -> File I/O
With that option a lot less memory is used.. but rendering is also slower. And TBH we should be using the new stuff, but if it doesn't work well with AMD we might need to.

My two cents, hope it helps

I am also also using Vegas 22 with an AMD card and I tend to see that while editing (and thus previewing using AMD acceleration) and with rendering that Vegas requires a ever growing amount of "Commited" memory. You can see this in the Task Manager and then under the Memory tab...

I found that in the end on my system I had my Virtual memory limited to only 2Gb of Page file. With that vegas 22 would crash randomly with either black screen or a plain windows crash or with luck (and the setting for it enabled ) a reporting tool of Vegas.
So what I did is increase the Page file on my fastest NVME disk from 2Gb to 32Gb which makes Vegas 22 a lot more usable, but it will still crash once the page file is full.

You can check your 'page file'/'virtual memory' settings in windows 11 via a search on 'view advance system settings'. In the Systems Properties window you click on the 'Advanced'-tab then click on Setting of the Performance section.
In that window (Performance Options) you click the Change button under the Advanced tab.

On my system it was custom set to 2Gb (probably something I did years ago on my Windows 10 install).
Nevertheless I have not tried 'System managed size' yet, but for me this worked to edit fairly okay on 40Gb of 4K of mp4 footage into a 2 hour video. For rendering I needed to increase the page file from 16Gb to 32Gb.

Another thing that helped me to use Vegas 22 with more stability is using the 'Enable legacy AVC decoding' under Options -> Preferences -> File I/O
With that option a lot less memory is used.. but rendering is also slower. And TBH we should be using the new stuff, but if it doesn't work well with AMD we might need to.

My two cents, hope it helps

thank you for the long response and help already! I didn't find The virtual memory already and I'm a bit scared to change those settings. Because I don't have that problem with VP21 I will leave it at this moment.

I just started a new project and while scrubbing through the footage I saw glitches. In this case it was the sony FX6 mxf footage. When I changed the hardware decoder to use to off and restarted vegas the glitches seemed dissappeared. It was on auto (amd radeon rx 7800 xt)

I did this several times and I think this is the issue. So I scrubbed again to the footage and with off I couldn't find directly a glitch. With auto hardware decoder the glitches were back.

curious....how long was that clip?

curious....how long was that clip?

9 seconds. The glitch is not in the original clip. Just checked it in catalyst browse

Would you mine sharing?

I still having glitches with my rendering. I checked my usb flash drive and saw a glitch in the footage. I first thought it was a bad flash drive but it was also in the rendered file on my PC . I rendered without the GPU (= very slow) but the glitch was gone. Only color correction was applied on the timeline. I'm now on VP23 and AMD 25.12.1. So which version of the driver I have to check to avoid this issue? I think if I have to check every previous version it will take forever, isn't it?

@BONLEV It would be good if you are able to convert your .mfx files first before dropping them in Vegas, since no matter what you try they are causing you issues.

Personally, i always use Shuttle Encoder to convert files to H.264 etc. that are problematic to edit directly on the Vegas timeline.

@BONLEV It would be good if you are able to convert your .mfx files first before dropping them in Vegas, since no matter what you try they are causing you issues.

Personally, i always use Shuttle Encoder to convert files to H.264 etc. that are problematic to edit directly on the Vegas timeline.

thx for the tip Steve but actually I convert my mxf files already with handbrake before I put them in vegas 23. (since I had those glitches from my FX6)

Without encoding there are glitches in the preview window but not now anymore when converted first with handbrake.

Now the glitches become visable when I rendered with my AMD GPU. So I guess my amd graphics driver version conflicts with my VP23.

Still having glitches with VP23 build 302. With my graphic card RX7800XT i had glitches in build 26.1.1 (latest one). I went back to build 24.12.1 -> same problem and build 25.10.2 also same problem. I disabled my GPU in vegas. It's now a bit better but still having those glitches. When playing the footage it jumps back randomly.

It's not in the original footage! It's also in footage converted with handbrake but the problem is only in vegas.

My project is very long (40 hours) and at this moment still about 18 hours. I'm still selecting the footage for a aftermovie. (this will be reduces to about 3 hours I guess) I know in the past this was a bug in vegas when having a very long project.

I could try to go with an older build of vegas pro 23 but then I probably can't open this project anymore?

My project is very long (40 hours) and at this moment still about 18 hours. I'm still selecting the footage for a aftermovie. (this will be reduces to about 3 hours I guess) I know in the past this was a bug in vegas when having a very long project.

Never too old to learn, may I ask what you're editing and how does a 40 HOUR Vegas timeline look like and how do you not get lost? Ever thought about editing subprojects.

My project is very long (40 hours) and at this moment still about 18 hours. I'm still selecting the footage for a aftermovie. (this will be reduces to about 3 hours I guess) I know in the past this was a bug in vegas when having a very long project.

Never too old to learn, may I ask what you're editing and how does a 40 HOUR Vegas timeline look like and how do you not get lost? Ever thought about editing subprojects.

it's the yearly carnaval (carnival) I'm editing. First I throw all the footage on the timeline and then I select the clips I may use for the aftermovie. I'm not getting lost because I put markers in the timeline. In the meanwhile i putted back GPU back on in vegas. It seems that the glitching is only in the footage I converted with handbrake (but not glitching in VLC media player)

Just tested a handbrake clip in VP 22 and there are no glitches. So the problem is in VP23. It's easier for me that I see all the footage in 1 timeline with the orange flags (markers)