Click on Audio Vegas Pro 23

Andrea-Berfio wrote on 3/6/2026, 4:59 AM

Good morning, I'm a longtime Vegas user and have never had any particular problems... the problems started with the purchase of version 23. I have a machine with a 32 GB Windows 11, a 5070 graphics card, a UMC 1820 sound card, a Ryzen 9 7900 processor, and 1 TB NVMe drives, one of which is dedicated to the OS only. Since I got Vegas Pro version 23, the audio in every project is full of clicks for no real reason... don't tell me that the audio clips must all be the same type because before I could mix flac, wav, and mp3 without any problems... it's not nice to say, but since Vegas moved from Sony to Magic, it's been constantly getting worse... Does this happen to you too? Thanks, Andrea

Comments

Dexcon wrote on 3/6/2026, 5:32 AM

... since Vegas moved from Sony to Magic, it's been constantly getting worse... Does this happen to you too?

First of all, the company's name is MAGIX not Magic.

Do I get audio clicks in Vegas Pro 23? No, not at all - not so far anyway.

 

Do you have Sound Forge Audio Studio installed on your system? if yes, there has previously been similar problems in Vegas Pro particularly with MP3 audio (though static not clicks) and the solution provided on the forum some 4 years ago was:

Hi! this sounds like another case of the magix low latency 2016 driver interference again...i would recommend uninstalling the magix low latency driver...here's how to do it:

press the Windows key + R on your computer keyboard, and type REGEDIT in the Open field:

Then navigate to:  HKEY_LOCAL_MACHINE > SOFTWARE > ASIO > Magix Low Latency 2016:

Now, simply right click the Magix Low Latency 2016 folder, and delete it.  

this should do the trick!

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

Andrea-Berfio wrote on 3/6/2026, 6:40 AM

Credo che anche se c'é un errore di tastiera da Magix a Magic non sia quello il problema ..., nel mentre mi sono trasferito su Da Vinci Resolve. Ma la mia riflessione relativa al consiglio è questa : Non ho mai installato SoundForge studio, il pc è stato formattato perché volevo creare una macchina completamente pulita e dedicarla solo alla produzione  ho installato Vegas 23 e i relativi moduli e plug a corredo tra cui sound forge 18 PRO e ACID PRO 11 inoltre ho anche Samplitude PRO 7 suite…ma se un programma Magix  può essere un problema per lo stesso Vegas , questo rafforza ulteriormente la mia sensazione, ovvero che si è sempre più andati vs un prodotto che non può essere inserito in produzioni aziendali ma solo prosumer . Ho fatto ulteriori ricerche e sembra che il motore di Vegas sia cambiato dalla 20 vs la 23   e questo potrebbe essere il vero problema. Intanto lavoro su altro sistema poi vedremo  al limite Magic(x) avrà perso un vecchio cliente .  Saluti   


I believe that even if there is a keyboard error from Magix to Magic that is not the problem ..., in the meantime I moved to Da Vinci Resolve. But my reflection on the advice is this: I have never installed SoundForge studio, the PC was formatted because I wanted to create a completely clean machine and dedicate it only to production. I installed Vegas 23 and the related modules and plug-ins including sound forge 18 PRO and ACID PRO 11. I also have Samplitude PRO 7 suite ... but if a Magix program can be a problem for Vegas itself, this further strengthens my feeling, that is, that we are increasingly going against a product that cannot be inserted into corporate productions but only prosumer. I did further research and it seems that the Vegas engine has changed from 20 to 23 and this could be the real problem. In the meantime I'm working on another system and then we'll see if Magic(x) will have lost an old customer. Regards