VP18 Update 334 released

Comments

andyrpsmith wrote on 9/22/2020, 10:48 AM

@andyrpsmith: Thank you for the update - under normal circumstances, you should not really need to modify that internal preference. As you mentioned that you still do not see the XML file, I have sent you a private message with some other instructions - could you please try those, and see if it helps?

Many thanks for the PM message, the file is still not created. PM replied to. Many thanks Andy

 

(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

Howard-Vigorita wrote on 9/22/2020, 4:32 PM
...I still get a hang on my 9900k system if I set decode with amd and render qsv to an fhd frame with the 4k hvec version of Red Car.

Fixed it my updating my amd radeon vii driver from enterprise q3 to adrenalin 20.9.1. The release notes make specific reference to correcting an hevc decoding issue.

jeffagwm wrote on 9/22/2020, 5:40 PM

I just updated to build 334. Now my when I try to load any Izotope plugins (Ozone 9, RX 7 or RX 8 suites) Vegas freezes. Everything worked great before the update. Any one else face similar issues or any one know what I can do to fix it? Thanks

cyro wrote on 9/22/2020, 5:58 PM

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?

Steve_Rhoden wrote on 9/23/2020, 8:54 AM

 

jeffagwm, no issues at all on my end with Izotope suites with this new Vegas update. Try reinstalling them and then refresh your VST folder within Vegas Preferences.

Jonathan-Burnett wrote on 9/23/2020, 10:09 AM

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?

It's not working for me either with my Vega 64 card...

BruceUSA wrote on 9/23/2020, 11:59 AM

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?

My secondary system is an old i7 6 cores 4.5ghjz 4930K cpu with old AMD card R9 290x. I own two very different system configuration. VP18 perform great, passing thru every projects so far. I always update Windows 10 when I am prompt to do and I do so without any issue. I also don't pick and choose my gpu driver, this and that BS. I let Windows do it for me. Over the last 10 years, I only encounter 1 time Windows 10 update caused the GPU usage dropping performance in Vegas . Other than that 1 time. I had nothing bad but all goodies with Windows update and auto gpu driver selection.

CPU:  i9 Core Ultra 285K OCed @5.6Ghz  
MBO: MSI Z890 MEG ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4
RAM: 48GB RGB DDR5 8200mhz
GPU: NVidia RTX 5080 16GB Triple fan OCed 3100mhz, Bandwidth 1152 GB/s     
NVMe: 2TB T705 Gen5 OS, 4TB Gen4 storage
MSI PSU 1250W. OS: Windows 11 Pro. Custom built hard tube watercooling

 

                                   

                 

               

 

Howard-Vigorita wrote on 9/23/2020, 2:38 PM

My 980x system has a Vega 64 and the driver update screen hangs trying to connect if my ethernet cable is plugged into my router. Internet connect works fine for everything else like getting Windows and Vegas version updates. Not a problem on my 9900k with a Radeon VIII. Same amd drivers, Win10 2004, and all updates all around.