Any suggestions on how I can get reach out to the Magix support team?

sa007 wrote on 11/10/2025, 5:15 AM

Since April of this year, I've been experiencing a very annoying bug which doesn't allow me to use my graphics card with the software (Vegas Pro 22). The only workable solution Magix provided for me was to not use my graphics card at all (I'm not kidding)

But when I pressed them for a more reasonable solution, they stopped responding to me.

A couple of months back I asked if it was possible to get a refund since their product wasn't fit for purpose and they're not willing to help. They instead had me try out Vegas Pro 23 instead. But when I experienced slight issues with that, their support stopped responding to me on that too.

I'm trying to give Magix every chance before I demand my money back (since their software hasn't been fit for use), but they've stopped responding to me. They won't help me address the bugs (they stopped responding to this). And they don't appear to want to give me my refund (stopped responding to this too).

Any suggestions on what I can do?

Comments

Dexcon wrote on 11/10/2025, 5:21 AM

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

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

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

sa007 wrote on 11/10/2025, 5:46 AM

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.

Dexcon wrote on 11/10/2025, 6:24 AM

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.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

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/10/2025, 7:21 AM

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.

sa007 wrote on 11/10/2025, 7:55 AM

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
 

sa007 wrote on 11/10/2025, 7:57 AM

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.

Wolfgang S. wrote on 11/10/2025, 8:11 AM

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?

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 11/10/2025, 8:16 AM

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.

sa007 wrote on 11/10/2025, 8:43 AM

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

sa007 wrote on 11/10/2025, 8:47 AM

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.

Wolfgang S. wrote on 11/10/2025, 9:06 AM

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.

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

Howard-Vigorita wrote on 11/10/2025, 9:18 AM

@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.

sa007 wrote on 11/10/2025, 9:26 AM

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.

 

sa007 wrote on 11/10/2025, 9:31 AM

@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.

Magix didn't advise against AMD specifically. They didn't mention AMD at all. They didn't confirm (or even suggest) there were compatibility issues with specific video boards

They just advised me to stop using the graphics card full stop - which, to me, is not reasonable at all.

And my main issue now is that they won't respond to me at all anymore - which is really bad after spending hundreds with them

andyrpsmith wrote on 11/11/2025, 12:40 PM

You can if you wish look at the GPU log file to see what Vegas finds when testing your GPU. I can tell you where to find it if you like?

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

sa007 wrote on 11/17/2025, 4:50 AM

You can if you wish look at the GPU log file to see what Vegas finds when testing your GPU. I can tell you where to find it if you like?

Hey Andy, sorry for the late reply.

That would be helpful, if you don't mind? As no-one from the Magix support team has recommended this. So it can't hurt trying

andyrpsmith wrote on 11/17/2025, 1:45 PM

Log file can be found here:

C:\Users\username\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log 

It can be opened by notepad, it is quite a long file but it shows Vegas running through GPU function test and gives an indication if it can use your GPU.

Here is mine: Note it says " Device is compatible" somewhere near the bottom

INFO 2025-11-17 14:13:55 *** Start of GPU-accelerated video processing log ***
INFO 2025-11-17 14:13:55 VEGAS Pro 22.0
INFO 2025-11-17 14:13:55 Version 22.0 (Build 250)
INFO 2025-11-17 14:13:55 
INFO 2025-11-17 14:13:55 [system device log] **************************************************************************************
INFO 2025-11-17 14:13:55 [system device log] 
INFO 2025-11-17 14:13:55 [system device log] -- NVIDIA GeForce RTX 4080 SUPER --
INFO 2025-11-17 14:13:55 [system device log] MX ID: 0x12494
INFO 2025-11-17 14:13:55 [system device log] DXGI description: NVIDIA GeForce RTX 4080 SUPER
INFO 2025-11-17 14:13:55 [system device log] LUID: 0x0:0x12494
INFO 2025-11-17 14:13:55 [system device log] Vendor: 0x10de
INFO 2025-11-17 14:13:55 [system device log] ID/SubSys/Rev: 0x2702, 0xf30510b0, 0xa1
INFO 2025-11-17 14:13:55 [system device log] Memory: 15.671 / 0 / 47.846 GB (video/system/shared)
INFO 2025-11-17 14:13:55 [system device log] Flags: 0
INFO 2025-11-17 14:13:55 [system device log] 
INFO 2025-11-17 14:13:55 [system device log] 
INFO 2025-11-17 14:13:55 [system device log] -- Microsoft WARP device --
INFO 2025-11-17 14:13:55 [system device log] MX ID: 0x1357d
INFO 2025-11-17 14:13:55 [system device log] DXGI description: Microsoft Basic Render Driver
INFO 2025-11-17 14:13:55 [system device log] LUID: 0x0:0x1357d
INFO 2025-11-17 14:13:55 [system device log] Vendor: 0x1414
INFO 2025-11-17 14:13:55 [system device log] ID/SubSys/Rev: 0x8c, 0x0, 0x0
INFO 2025-11-17 14:13:55 [system device log] Memory: 0 / 0 / 47.846 GB (video/system/shared)
INFO 2025-11-17 14:13:55 [system device log] Flags: 2
INFO 2025-11-17 14:13:55 [system device log] 
INFO 2025-11-17 14:13:55 [system device log] **************************************************************************************
INFO 2025-11-17 14:13:55 OpenGL_Initialize
INFO 2025-11-17 14:13:55 GLC: 0000000000010000
INFO 2025-11-17 14:13:55 GL 10-bit Available: FALSE
INFO 2025-11-17 14:13:55 GL 10-bit Pixel Format Index: 0
INFO 2025-11-17 14:13:55 GL_VENDOR: NVIDIA Corporation
INFO 2025-11-17 14:13:55 GL_RENDERER: NVIDIA GeForce RTX 4080 SUPER/PCIe/SSE2
INFO 2025-11-17 14:13:55 GL_VERSION: 4.6.0 NVIDIA 581.57
INFO 2025-11-17 14:13:55 GLEW Init OK
INFO 2025-11-17 14:13:55 
INFO 2025-11-17 14:13:55 OpenCL_Initialize
INFO 2025-11-17 14:13:55 Platforms: 1
INFO 2025-11-17 14:13:55 Platform: 0
INFO 2025-11-17 14:13:55   Vendor:     NVIDIA Corporation
INFO 2025-11-17 14:13:55   Name:       NVIDIA CUDA
INFO 2025-11-17 14:13:55   Version:    OpenCL 3.0 CUDA 13.0.97
INFO 2025-11-17 14:13:55   Profile:    FULL_PROFILE
INFO 2025-11-17 14:13:55   Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-11-17 14:13:55 
INFO 2025-11-17 14:13:55 [system device log] initializing MxGpuDevice...
INFO 2025-11-17 14:13:55 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-11-17 14:13:55 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] create DX11 device. HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] setting private data - . HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-11-17 14:13:55 [system device log] .. end initializing MxGpuDevice
INFO 2025-11-17 14:13:55 [system device log] initializing MxGpuDevice...
INFO 2025-11-17 14:13:55 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-11-17 14:13:55 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] create DX11 device. HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] setting private data - . HRESULT=0
INFO 2025-11-17 14:13:55 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: isSoftware 1

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-11-17 14:13:55 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-11-17 14:13:55 [system device log] .. end initializing MxGpuDevice
INFO 2025-11-17 14:13:55   Devices: 1
INFO 2025-11-17 14:13:55   Device: 0
INFO 2025-11-17 14:13:55     Type:            GPU
INFO 2025-11-17 14:13:55     Vendor:          NVIDIA Corporation
INFO 2025-11-17 14:13:55     Name:            NVIDIA GeForce RTX 4080 SUPER
INFO 2025-11-17 14:13:55     Profile:         FULL_PROFILE
INFO 2025-11-17 14:13:55     Version:         OpenCL 3.0 CUDA
INFO 2025-11-17 14:13:55     C version:       OpenCL C 1.2 
INFO 2025-11-17 14:13:55     Extensions:      cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-11-17 14:13:55     Driver version:  581.57
INFO 2025-11-17 14:13:55     Available:       Yes
INFO 2025-11-17 14:13:55     Compiler:        Yes
INFO 2025-11-17 14:13:55     Image support:   Yes
INFO 2025-11-17 14:13:55     Unified memory:  No
INFO 2025-11-17 14:13:55     Vendor ID:       4318
INFO 2025-11-17 14:13:55     Compute units:   80
INFO 2025-11-17 14:13:55     Work dimensions: 3
INFO 2025-11-17 14:13:55     Clock Frequency: 2580
INFO 2025-11-17 14:13:55     Image reads:     256
INFO 2025-11-17 14:13:55     Image writes:    32
INFO 2025-11-17 14:13:55     Samplers:        32
INFO 2025-11-17 14:13:55     Workgroup size:  1024
INFO 2025-11-17 14:13:55     Image width:     32768
INFO 2025-11-17 14:13:55     Image height:    32768
INFO 2025-11-17 14:13:55     Parameter size:  32764
INFO 2025-11-17 14:13:55     Maximum alloc:   4292739072
INFO 2025-11-17 14:13:55     Memory size:     17170956288
INFO 2025-11-17 14:13:55     Local memory:    49152
INFO 2025-11-17 14:13:55     Work item sizes: 1024, 1024, 64
INFO 2025-11-17 14:13:55     Out of order Q:  Yes
INFO 2025-11-17 14:13:55     Profiling Q:     Yes
INFO 2025-11-17 14:13:55     NV compute (maj):8
INFO 2025-11-17 14:13:55     NV compute (min):9
INFO 2025-11-17 14:13:55     NV warp size:    32
INFO 2025-11-17 14:13:55     NV overlap:      Yes
INFO 2025-11-17 14:13:55     NV integ. mem:   No
INFO 2025-11-17 14:13:55 Device is compatible.
INFO 2025-11-17 14:13:55 This is the selected device.
INFO 2025-11-17 14:13:55 
INFO 2025-11-17 14:13:56 Attempting to create CL<->DX11 interop context on device 'NVIDIA GeForce RTX 4080 SUPER'
INFO 2025-11-17 14:13:56 CL<->DX11 context: 000000000FEEC2D0
INFO 2025-11-17 14:13:56 Command queue: 000000000FDFC540
INFO 2025-11-17 14:13:56 Buffer write mapping flags: 0x4
INFO 2025-11-17 14:13:56 2DWGO: 16x16
INFO 2025-11-17 14:13:56 HWBL: 1
INFO 2025-11-17 14:13:56 OCL compile, bin: 91426185, kernels: kddb9a9580 kddb9a9581 kddb9a9582 
INFO 2025-11-17 14:13:56 CPWB successful
INFO 2025-11-17 14:13:56 BP successful
INFO 2025-11-17 14:13:56 OCL compile, bin: 8a7f119a, kernels: k4fce1a180 k4fce1a181 k4fce1a182 k4fce1a183 k4fce1a184 
INFO 2025-11-17 14:13:56 CPWB successful
INFO 2025-11-17 14:13:56 BP successful
INFO 2025-11-17 14:13:56 OCL compile, bin: 6311d26d, kernels: k13650b260 k13650b261 k13650b262 k13650b263 
INFO 2025-11-17 14:13:56 CPWB successful
INFO 2025-11-17 14:13:56 BP successful
INFO 2025-11-17 14:13:56 OCL compile, bin: b5443ede, kernels: kf2c0fea20 kf2c0fea21 kf2c0fea22 kf2c0fea23 kf2c0fea24 kf2c0fea25 kf2c0fea26 kf2c0fea27 kf2c0fea28 kf2c0fea29 kf2c0fea210 kf2c0fea211 kf2c0fea212 kf2c0fea213 kf2c0fea214 kf2c0fea215 kf2c0fea216 
INFO 2025-11-17 14:13:56 CPWB successful
INFO 2025-11-17 14:13:56 BP successful
INFO 2025-11-17 14:13:56 OCL compile, bin: f9312813, kernels: k201db7240 k201db7241 k201db7242 k201db7243 k201db7244 k201db7245 k201db7246 k201db7247 k201db7248 k201db7249 k201db72410 k201db72411 k201db72412 k201db72413 k201db72414 k201db72415 k201db72416 k201db72417 k201db72418 k201db72419 k201db72420 k201db72421 k201db72422 k201db72423 k201db72424 k201db72425 k201db72426 k201db72427 k201db72428 k201db72429 k201db72430 k201db72431 k201db72432 k201db72433 k201db72434 k201db72435 k201db72436 k201db72437 k201db72438 k201db72439 k201db72440 k201db72441 k201db72442 k201db72443 k201db72444 k201db72445 k201db72446 k201db72447 k201db72448 k201db72449 k201db72450 k201db72451 k201db72452 k201db72453 k201db72454 
INFO 2025-11-17 14:13:56 CPWB successful
INFO 2025-11-17 14:13:56 BP successful
INFO 2025-11-17 14:14:01 Readback profiling: [15, 32], selected 0
INFO 2025-11-17 14:14:01 DX12_HDR_Initialize
INFO 2025-11-17 14:14:01 DX12 HDR Available: FALSE
INFO 2025-11-17 14:14:01 
INFO 2025-11-17 14:14:13 OCL compile, bin: d29e8d1d, kernels: k556c32f70 
INFO 2025-11-17 14:14:13 CPWB successful
INFO 2025-11-17 14:14:13 BP successful
INFO 2025-11-17 14:15:44 OpenCL_Shutdown
INFO 2025-11-17 14:15:44 OpenGL_Shutdown
INFO 2025-11-17 14:15:44 
INFO 2025-11-17 14:15:44 *** End of GPU-accelerated video processing log ***
 

Last changed by andyrpsmith on 11/17/2025, 1:56 PM, changed a total of 2 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

sa007 wrote on 11/25/2025, 1:45 AM

Hey @andyrpsmith. I've just tried the above, and it says my GPU is compatible. Thanks for the suggestion

EricLNZ wrote on 11/25/2025, 3:53 AM

@sa007 Of interest - have you been dealing with the MAGIX Support team or VEGAS Support?