Vegas Pro 17 Picture in Picture FX problem when using AMD RX5700 (navi

ZigoH wrote on 3/24/2020, 2:36 PM

Hi!! i have this weird problem where the background of the PiP clip turns Black instead of transparent...this issue disappear when i disable GPU acceleration

GPU ENABLED:

 

GPU DISABLED:

 

Does anyone had this issue beforefore? I'm running the latest build 421. This doesn't happen on my old AMD R9 390X.

Thanks!

 

 

Comments

Vegas_Sebastian wrote on 3/25/2020, 2:54 AM

It seems there something wrong with the AMD driver. Is a newer driver version available?

Sassylola wrote on 3/25/2020, 7:36 AM

I agree with Vegas_Sebastian. What driver version are you using? 20.3.1 is the newest. I am running a XFX Radeon VII and I am using the Pro drivers 20.Q1.1 for the last few weeks I have not had any problems. The older drivers pre 20.2.2 would crash my system when viewing 4K content ( not in vegas ) from my Sony AX 700.

If you install the newest drivers Pro or Radeon. Get DDU from online its free. And it will uninstall your old drivers in safe mode. Make sure in DDU options you have checked do not let windows update video drivers. AMD also makes a uninstall driver program. DDU is real easy to use.

If you are running a AMD CPU, depending on what chipset you are using, AMD just released a new chipset driver Revision Number: 2.03.12.0657. I have installed it with no problems.

Also make sure Windows is up to date.

My System Home Built

Intel 13900K Latest Intel Chipset. Latest Intel Management Engine Installed. NO OC (PL 1 Set to 253W PL 2 set to 253W)

Arctic Liquid Freezer ll 360mm AIO

Gigabyte Aero G Z790 MB Latest BIOS

ZOTAC GAMING GeForce RTX 4090 AMP Extreme AIRO Latest Nvidea Studio Drivers Installed. With GPU OC results were about the same as GPU set to default settings. I have kept GPU at default settings

64 GB G Skill DDR 5 6000mhz Ram 2X32

Corsair 1000W RMx Power Supply

SK Hynix P41 NVMe 1TB Operating Drive. ( Boot Drive )

WD 2TB SN 850X SSD 1st Render Drive NVMe

SK Hynix P 41 2 TB NVMe Storage Drive

2 TB Sk Hynix P 41 SSD 2nd Render Drive For final renders NVMe

Win 11 Pro all currant updates applied

Fractal Design R6 Case

Samsung - M7 Series 43" Smart Tizen 4K UHD Monitor

Vegas Pro Suite 22 Ver 194

1 Audigyfx Sound Card

SSK USB C External NVMe drive Enclosure with 500GB Samsung 970 EVO Plus for backups.

PROBOI 10G Hard drive Enclosure. USB C. 4 4TB Spinning Drives for Backups.

 

 

ZigoH wrote on 3/25/2020, 9:29 AM

Thanks for the responses ! i will try that driver, This is a new build .. Ryzen 9 3900x + RX 5700 + 64GB of ram ..latest windows... right now i'm running AMD drivers 20.2.2...i think i've already installed 20.3 when i first install everything a few days ago...but i'll give them a try again and i'll report back. Thanks!

David-Woodman wrote on 6/23/2020, 9:34 AM

I have exactly the same problem using PIP and GPU acceleration enabled with RX 5600 XT, latest build of Vegas Pro (452) and latest stable Radeon drivers (20.5.1). It's nearly 3 months since ZigoH's post. Did you get a resolution? I'm wondering where the problem lies, is it a VegasCreativeSoftware bug or an AMD bug?

ZigoH wrote on 8/7/2020, 8:32 AM

Vegas 18 came out, this bug still persist. It weird that its not addressed since its a very popular GPU.

 

Howard-Vigorita wrote on 8/7/2020, 10:33 PM

Problem confirmed here too on my machine with a 5700xt that has the latest and greatest v20.8.1 driver released 7/29. Other machines here running the same driver on other amd boards like the Radeon 7, Vega 64, and Vega-M do not experience the issue.

Howard-Vigorita wrote on 8/10/2020, 6:09 PM

Doesn't seem to be a driver issue... more like a bug in the pip-fx masking. Here's a workaround using the bezier mask fx which does not have the bug. Btw, did this on Vegas 18 with an h.265 4k video so it's also a work around if track motion and pan/crop are blowing up on you.

David-Woodman wrote on 8/26/2020, 4:31 PM

I'm still running Vegas 17 but have discovered that if I set Dynamic Ram Preview to zero and then re-enable GPU acceleration the bug disappears.

ZigoH wrote on 8/26/2020, 4:56 PM

I'm still running Vegas 17 but have discovered that if I set Dynamic Ram Preview to zero and then re-enable GPU acceleration the bug disappears.

That's not working for me, if i disable gpu acceleration everything works regardless of the dynamic ram setting, when i enable gpu accel. and restart Vegas it doesn't work again.

michael-harrison wrote on 8/26/2020, 5:37 PM

PIP in general has issues. I've seen it, combined with other some other fx cause lockups and other forms of screen corruption and I'm using Nvidia. Which is a shame because it's a useful tool.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

yi-h wrote on 10/10/2020, 9:54 PM

You're wasting your time here.
Because a lot of people ask about the RX5700 and then talk about GPUs that have nothing to do with it, or they don't have an RX5700 and then talk about it in their imagination!

I have an RX5700 and I'm having the same problem.

Send a message to the support center!

https://www.vegascreativesoftware.info/us/support/search/?searchphrase=bug

yi-h wrote on 10/11/2020, 3:54 AM

As a countermeasure until the bug is fixed.

Use Smart Zoom and Track motion to replace PiP

The rest can be substituted by using fade in, fade out, etc. as appropriate.

yi-h wrote on 10/11/2020, 5:17 AM

In case you're wondering, I had this RX5700 issue on June 3.
I reported it to MAGIX support.

But it hasn't improved yet.
 

After reporting the problem
I received a message from MAGIX support saying that they will contact me if the bug is fixed or if there is any new information, but I haven't heard from them even after 4 months.

 

More people should send messages to MAGIX support and
I think we need to get MAGIX to recognize the problem and make it better.

Writing on the forum won't solve anything.

vkmast wrote on 10/11/2020, 5:22 AM

VEGAS Support.

Howard-Vigorita wrote on 10/11/2020, 11:32 PM

Just tested it again on my Xeon/5700xt system with v18 build 334 and the bug has not been fixed. Still have to resort to my workaround with bezier mask fx immediately behind pip fx to mask off the black. The other 2 systems I've tested (9900k/Radeon 7 and 980x/Vega64) don't require this extra masking. All have the same os and amd driver revs.