-
Audioon 8/30/2023
Super Loud Blip Sound on Clip Start/End on occasion
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.
-
Audioon 8/30/2023
Super Loud Blip Sound on Clip Start/End on occasion
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.
-
Audioon 8/29/2023
Super Loud Blip Sound on Clip Start/End on occasion
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?
-
Videoon 9/23/2020
Vegas Pro 18 Trial - Driver Update is blank
Which AMD card are you using @cyro? Frank has the Vega 64 8GB. AMD Fury-X (R9)
-
Videoon 9/22/2020
Split + Delete (While Playing) Causing Huge Hangs
Just FYI - This issue is still happening in the latest Build 334, 100% repro after the update.
-
Videoon 9/22/2020
Vegas Pro 16: Does it work better on a Ryzen or Intel CPU
If you are primarily concerned about rendering speed: If your encoder utilizes quicksync then go with Intel, otherwise go with Ryzen. And in general go for a laptop with the most powerful GPU that you can afford.If you are primarily concerned about editing speed and snappiness: Vegas scales really well with multiple scores so you'll see much snappier response etc. with more cores (all other things being equal), go with Ryzen.
-
Videoon 9/22/2020
VP18 Update 334 released
Build 334 "AMD drive update" still doesn't work with my AMD Fury-X GPU - the build notes claim 334 implemented AMD but it's not working for me - how are others doing?
-
Videoon 9/22/2020
Vegas Pro 18 Trial - Driver Update is blank
The driver update is only supporting NVIDIA and Intel. AMD is coming very soon. ;) Build 334 claims "AMD support for Driver Update dialog" but I still get a blank dialog with no action.Are you sure this got fixed/implemented in 334?
-
Videoon 8/22/2020
VP18 Driver Update - does it actually do anything?
Thanks vkmast! @Magix Frustrating experience, we're talking 1 min of extra development time to write a single line of text ("this isn't supported yet for AMS") versus users wasting their time looking for answers on support forums :(
-
Videoon 8/22/2020
Vegas Pro 18 Trial - Driver Update is blank
Ditto: it would be super helpful to at least show a message instead of just a blank screen.Frustrating experience, we're talking 1 min of extra development time to write a single line of text versus users wasting their time looking for answers on support forums :(
-
Videoon 8/22/2020
startet nicht mehr
Versuche die ueblichen Methoden: video driver rollback und/oder VP18 Neuinstallation :(
-
Videoon 8/22/2020
Building Proxies in VP18 takes forever
I let that run over night, some progress but proxies are still not done. I guess this is one of those Vegas things that just don't work unless you use the HOS tools or just disable the proxies (which works pretty well on fast machines), sigh.
-
Videoon 8/22/2020
Building Proxies in VP18 takes forever
Yeah, it looks like on my 12-core box it uses <10% CPU and no GPU and runs for hours to do the proxies. Not worth it, the machine is plenty fast (or better: the NVMe and GPU have so much bandwidth) working with >4K footage is not a problem. I'll just disable this.Thanks for your replies everybody, very helpful!
-
Videoon 8/16/2020
Split + Delete (While Playing) Causing Huge Hangs
Just wanted to say: THANKS Phil_P. I recently ran into the same issue in VP18 and VP17 and it is definitely impacting my workflow and project times while cleaning up audio (de-umming etc.). Thanks for staying on this and getting it through the initial layer of indifference/non-prioritization, let's hope this gets fixed soon!
-
Audioon 8/16/2020
Consistent crashes of VP18 (repro) with playing and S-cuts
Well... never mind, seems like this is an old favorite :(https://www.vegascreativesoftware.info/us/forum/split-delete-while-playing-causing-huge-hangs--122520 Damn, seriously, this has been going on for years and is still not fixed? ouch :(
-
Videoon 9/30/2016
Mercalli persistent "Analyze" behavior even when removed from FX chain
Also check Video Output FX and Media FX Duh, that was it... feeling a bit sheepish now, bah bah :) Thanks altarvic!
-
Videoon 9/30/2016
Mercalli persistent "Analyze" behavior even when removed from FX chain
Yes, Vegas Pro 14, haven't found a good repro scenario yet. Even deleting and adding the video track back in doesnt fix the issue - I would hate having to abandon the whole project :(
cyro
Offline, Last login 8/30/2023, Member since 9/30/2016