Super Loud Blip Sound on Clip Start/End on occasion

Comments

Yelandkeil wrote on 8/17/2023, 7:24 PM

Very random and inconstant, V21B108.
Last second you see and hear it, go zooming and it's vanished.

But it doesn't happen with clips from my cameras.

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO 512GB>sys + 2TB>data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT + AdrenalinEdition 23.7.2
Samsung 2xLU28R55 10bit4k60Hz 300CD/m²HDR10 ->2xDPorts
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

GH5sHLG_4k30p: AWB, Exposure=M, Shutter50, ISO320
ProtuneFlat_2.7k60pLinear: WB5500K, Auto-Shutter, EV-Comp-1.0, ISO400

Windows11Pro 22H2-22621.2361
Direct3DAPI 12.2, OpenCL®Driver 31.0.21023.2010

Vegaspro21 + Handbrake/XMediaRecode + DVDArchi7 
Acidpro10 + SoundForgepro14.0.065 + SpectraLayerspro7 

K-LitecodecPack17.7.3 (MPC Video Renderer for HDR10-Videoplayback) 

Jody-Nasworthy wrote on 8/18/2023, 8:14 AM

I have posted several times about this issue as well.

Jessariah67 wrote on 8/21/2023, 8:29 AM

Ditto. Ditto. Ditto. I also have sonic clicks at the beginning of audio edits - even with fading in (have to try to crossfade to solve). And there's also that thing where it will stop playing back the first part of certain clips at times (though it renders fine).

Jessariah67 wrote on 8/21/2023, 9:45 AM

Go in and fade that out before the end of the clip - turn off everything on the track. Rerender. The artifact is still there.

Cross faded with an empty audio event. Rerender. Still there.

Faded the end into a -40dB 1K tone for a good half second. Rerender. Original artifact is still there.

shovel wrote on 8/21/2023, 11:58 AM

Go in and fade that out before the end of the clip - turn off everything on the track. Rerender. The artifact is still there.

Cross faded with an empty audio event. Rerender. Still there.

Faded the end into a -40dB 1K tone for a good half second. Rerender. Original artifact is still there.

Yea. Vegas is not in a good reliable working state. I won't be using it for anything more than simple quick video edits because of this (sadly). I do a lot of action animation work which requires a LOT of sound fx. I'm not about to commit to a huge project in this software when it means possibly having to fix hundreds of files on the timelines due to this ongoing bug.

It needs to be fixed asap or its the final nail on the coffin. I would have moved on way earlier, but its better to reach out first and see if they will fix things (same for any software). But two versions later, here we are still.
Mainly because this was a lot of money and I don't want to accept it was a poor investment.

cyro wrote on 8/29/2023, 9:07 PM

Argh, I ran into this bug today when I had to re-render around 10 old projects in a different resolution. Every single f'ing time Vegas 20 would add loud audio spikes to the output files or mess up audio completely. So insanely frustrating. I get that Magix is focusing on cool new features to sell more product and broaden the user base but come on, fix these ancient infuriating bugs!

My workaround was to export the projects and then re-render them on a colleague's Mac, not my preference at all. But trimming the noises from the ends of clips wasn't a reliable workaround with V20 on a PC.

Please help: is there a reliable workaround that works with V20?

rraud wrote on 8/30/2023, 9:39 AM

is there a reliable workaround that works with V20?

Render the audio separately on working version of VP or other DAW and mux in the good audio. A work-a-round at best....reliable, but not as easy as a single A/V render.

Which brings up the question, does the noise happen when rendering the project as audio only in VP-20. If that is the case, it would be faster to render and mux in the sound to the existing video.

cyro wrote on 8/30/2023, 1:50 PM

is there a reliable workaround that works with V20?

Render the audio separately on working version of VP or other DAW and mux in the good audio. A work-a-round at best....reliable, but not as easy as a single A/V render.

Which brings up the question, does the noise happen when rendering the project as audio only in VP-20. If that is the case, it would be faster to render and mux in the sound to the existing video.

Yes, unfortunately VP20 still messes up when rendering Audio only.

The attached picture shows the two original audio tracks above and the re-imported rendered audio track below. 100% repro across a good 20-something projects now. Sources are clean and render fine in Premiere. I think I'll open a ticket with Magix, whatever good that may do.

john_dennis wrote on 8/30/2023, 7:33 PM

@cyro @shovel @Jessariah67 @Jody-Nasworthy @shovel @rraud @VEGASDerek

In Options / Preferences / File I/O tick "Enable legacy AVC decoding".

If you can live with compoundplug.dll doing the decoding of AVC-AAC in an mp4 wrapper, your audio problems will be gone for first generation renders. If you already have generation 2 through n renders that you might have to add back to a Vegas timeline, you're screwed and will have to resort to truncating the audio for each event before rendering again. If your video source requires the newer S04compoundplug.dll, then you're screwed until Magix fixes the audio decoding in that plugin.

Video at 5.

Edit: As promised Video at 5... err 6.

Last changed by john_dennis on 8/30/2023, 8:15 PM, changed a total of 1 times.

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel

cyro wrote on 8/30/2023, 10:07 PM

If you can live with compoundplug.dll doing the decoding of AVC-AAC in an mp4 wrapper, your audio problems will be gone for first generation renders. If you already have generation 2 through n renders that you might have to add back to a Vegas timeline, you're screwed and will have to resort to truncating the audio for each event before rendering again. If your video source requires the newer S04compoundplug.dll, then you're screwed until Magix fixes the audio decoding in that plugin.

Well, that works for 3/4 of my scenarios - THANK YOU John!
Let's hope Magix will fix this soon, especially since it seems to be 100% reproducible etc.