Please advise the specifications of your computer as well as, especially, the computer's graphics card (GPU).

Thanks Dexcon

Processor - AMD Ryzen 9 7900X 12-Core Processor (4.70 GHz)
Installed RAM - 64.0 GB (63.1 GB usable)
System type - 64-bit operating system, x64-based processor
Graphics card - AMD Radeon RX 7600 XT

In case you were wondering, the bugs have been the following:

1. Videos clips being edited often become scrambled/pixelated
2. Video clips sometimes sometimes jump to another part of the video. For example, say if in a 20 minute video I'm trying to use a segment from 16:22 - 16:32, it would instead randomly pull in scene parts from 17:21.

Number 2 has become less of an issue, but number 1 persists.

My main issue now however isn't just the software itself. It's the support team. I'd prefer to continue communicating with the tickets I've raised because that has an entire history of my problems. But they've stopped responding to me on those entirely.

Thank you for the computer information.

Another issue could relate to what video media that you are using on the timeline. Could you please upload to the forum a detailed MediaInfo report (a free app) of the media that you are using on the timeline as well as the source of that media.

Hopefully, others on the forum will then be able to provide an opinion.

Also, which build of Vegas Pro 22 are you using?

In the meantime, an option would be to return Vegas Pro 22 back to its default (factory) settings via the process outlined in https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/. This can often fix some issues.

The problem is perhaps that while they can document and pass on bugs, there's nothing to advise you beyond workarounds like disabling the GPU until the bug is fixed.

Thank you for the computer information.

Another issue could relate to what video media that you are using on the timeline. Could you please upload to the forum a detailed MediaInfo report (a free app) of the media that you are using on the timeline as well as the source of that media.

Hopefully, others on the forum will then be able to provide an opinion.

Also, which build of Vegas Pro 22 are you using?

In the meantime, an option would be to return Vegas Pro 22 back to its default (factory) settings via the process outlined in https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/. This can often fix some issues.

Thank you. I've tried returning into default before but the problem still persists. As well as using different builds.

BUILD: Version 22.0 (Build 250)

SOURCE OF MEDIA: I mainly edit video I obtain from YouTube (using a YouTube downloader such as Tube Digger)

MEDIA REPORT: please see below:

Format: MPEG-4
Format profile: Base Media
Codec ID: isom (isom/iso2/avc1/mp41)
File size: 245 MiB
Duration: 11 min 39 s
Overall bit rate : 2 942 kb/s
Frame rate : 25.000 FPS
Writing application : Lavf58.45.100

Video
ID : 1
Format  : AVC
Format/Info  : Advanced Video Codec
Format profile: High@L4
Format settings: CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames: 3 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 11 min 39 s
Bit rate: 2 808 kb/s
Width: 1 920 pixels
Height: 1 080 pixels
Display aspect ratio: 16:9
Frame rate mode: Constant
Frame rate: 25.000 FPS
Color space: YUV
Chroma subsampling: 4:2:0
Bit depth : 8 bits
Scan type: Progressive
Bits/(Pixel*Frame)   : 0.054
Stream size : 234 MiB (95%)
Title  : ISO Media file produced by Google Inc.
Writing library  : x264 core 155 r2901 7d0ff22
Color range   : Limited
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   : 11 min 39 s
Bit rate mode : Constant
Bit rate : 128 kb/s
Channel(s) : 2 channels
Channel layout   : L R
Sampling rate   : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size  : 10.7 MiB (4%)
Title  : ISO Media file produced by Google Inc.
Language     : English
Default   : Yes
Alternate group : 1
 

The problem is perhaps that while they can document and pass on bugs, there's nothing to advise you beyond workarounds like disabling the GPU until the bug is fixed.

I see.

Is it possible that they have no intentions of fixing the bug at all?

Like, if they don't have a current fix, I understand. But can they let me know if they have any intentions at all to fix it? I'd rather be told that, and then I can push for a refund. But instead I've been ignored altogether.

While nobody here from side of the users or the moderators can answer really if they will come up with a fix, I tend to expect that we will not see a fix for VP22 any more.

Have you tested if that happens with VP23?

It's probably too late to get a refund for 22 as it's not even sold currently.

I would assume it will be fixed in 23 or later but as Wolfgang said we don't have insights into that and the development team doesn't say much about fixes in advance.

While nobody here from side of the users or the moderators can answer really if they will come up with a fix, I tend to expect that we will not see a fix for VP22 any more.

Have you tested if that happens with VP23?

Instead of giving me a refund, they suggested I try VP23.

VP23 was slightly more stable, but they wanted me to try a few more things with it. Whilst trying those and asking what their resolution would be, they stopped responding to me altogether and I can't get through to their support anymore. It's incredibly frustrating

It's probably too late to get a refund for 22 as it's not even sold currently.

I would assume it will be fixed in 23 or later but as Wolfgang said we don't have insights into that and the development team doesn't say much about fixes in advance.

I hope I'm eligible for a refund, because their software isn't working as intended. Their only fix is for it to be used without a graphics card - which, in my opinion, is absurd. A video editing software that can't be used with a graphics card, is no use to anyone

I'm at my wit's end now, because if they won't fix the issue (which is preventing me from using the software) and they won't respond to any of my queries, I genuinely don't know what to do. I'm spent hundreds on a software that I can't use properly.

Have you tried VP23? If not, also fine for me. But since we do not have your footage, nobody can test that. And for high compressed YouTube footage it is hard to say anything. You could try to convert the footage to another codec, up to yo too. But users are not in the position to give you a refund - sorry to say so.

@sa007 If official Magix support advises against using newer Amd video boards, you should advise Amd support so they can at least spread the word. Fwiw, I've been having so much better luck with newer Nvidia boards, starting with vp21 b300, that I've pulled my 6900xt in favor of a 4090 & 5080, especially with vp23.

Have you tried VP23? If not, also fine for me. But since we do not have your footage, nobody can test that. And for high compressed YouTube footage it is hard to say anything. You could try to convert the footage to another codec, up to yo too. But users are not in the position to give you a refund - sorry to say so.

Oh, just to be clear, I wasn't looking for users to give me a refund

I was looking for suggestions on how best to reach the Magix support team - so they could give me the refund

And yes, I tried VP23 - which worked slightly better (though not without some faults). But on the issues with that, they stopped helping me.