VEGAS Pro 14 Update 6 (build 252)

Comments

LindaSunshine wrote on 4/22/2017, 2:26 PM

Trident doesn't work properly I tested trident, best is using 2 sticks G.skills flare X cl15 and disable a-xmp in bios I tried multiple memory and frequencies. Vegas is using 19GB as I run the performance monitor. I have not test how much take rendering Full HD I'm running 1800x m.2 512 GB 32GB Gskills flare x 2400Mhz much better than 3200 flare x in performance or 3600 Mhz and Sapphire rx 480 nitro+ 8GB i was not happy with Other brands I tested rx 480. For sure as I tested my second rig 6950x I'm getting better performance. Open CL performance RX 480 is not the best for BCC but it will do the service until the Vega will arrive I hope it will be at least FirePro 24GB Vega. With 3 Vegas windows running I'm getting 3.6fps on my at the moment second rig 6950x I was getting max 2.4fps running 3 Vegas windows. For sure rendering CPU is not as fast if you using rendering GPU.

Nick Hope wrote on 4/22/2017, 10:25 PM

This is turning into the "stream of consciousness" thread. Hint.

GTX 1080ti doesn't support open CL...

It does.

...Radeon RX 480 GPU, not overclocked, all newest bios,chipset windows ETC updates. Apparently Vegas Pro is not using my graphic card open CL in this new system. My old system (Phenom II 1090T with a Radeon HD 6800) really used the graphic card well while rendering out using MainConcept AVC/AAC...

...any advice on how to speed up my render times and for my Ryzen system would be great.

Put the HD 6800 in the new box as well as the RX 480. Use the HD 6800 for rendering ("Encode mode") and the RX 480 for GPU acceleration of video processing. You'll need lots of slots on your motherboard and plenty of power and cooling.

LindaSunshine wrote on 4/23/2017, 12:30 AM
 

Put the HD 6800 in the new box as well as the RX 480. Use the HD 6800 for rendering ("Encode mode") and the RX 480 for GPU acceleration of video processing. You'll need lots of slots on your motherboard and plenty of power and cooling.

Not in version 252 there is rendering using CUDA or open CL is automatically overridden by Vegas that will automatically switch into render using CPU. Boris FX released new version 13.4.2017 10.0.0.6.2 that is much stable and quicker even with mid range RX 480 8GB. Im able to have 4K preview in Full Auto, Full full is still not smooth, but it is limited by RX 480, GTX 1080 Ti nothing. He need for main concept using open CL 244 version to check render using Open CL. I made the test using 1 min 1080p footage using 2 Vegas filters render time was 1minute 32seconds. Using Boris FX complete continuum filters 6 minutes 15 seconds. I checked A-XMP on in Bios makes no difference with speed 2400 Mhz. Hope it helps you.

JesusSheep wrote on 4/23/2017, 7:12 PM

VegasPro 14 252 Keeps Giving me a service notice for the Patch after it is installed And Has Crahed  Serveral times with Chroma Key.

raWer-Studio wrote on 4/24/2017, 1:29 AM

Hi, have any trouble like me ? After Update on 252 stop working stabilize and white balance :-/

JesusSheep wrote on 4/24/2017, 8:44 AM

I Keep Getting A Service Notice For the patch When the patch is already installed.

252 Is unStable When Doing Chroma Keying.

DDDyson wrote on 4/24/2017, 8:52 AM

I Keep Getting A Service Notice For the patch When the patch is already installed.

Check earlier in this thread. You'll have to dismiss the notification by checking "Don't show this message again". It doesn't check what version you have installed, so the message will repeat until you dismiss it.

JesusSheep wrote on 4/24/2017, 9:29 AM

Net Notice is in Sony Vegas not in mail or Forum "Don't Shows this message again" gets unchecked after I check it. When I Restart the program.

LindaSunshine wrote on 4/25/2017, 11:44 AM

VegasPro 14 252 Keeps Giving me a service notice for the Patch after it is installed And Has Crahed  Serveral times with Chroma Key.

Go to Options>Preferences>Video>GPU acceleration of video processing and set it from card to OFF. Apply restart Vegas 14. I had same problem today it looks Vegas developers instead of fixing GPU acceleration pushing customers using CPU :-((((((

LindaSunshine wrote on 4/25/2017, 4:21 PM

This is turning into the "stream of consciousness" thread. Hint.

GTX 1080ti doesn't support open CL...

It does.

GTX 1080TI is twice slower than R9 290 in Open CL performance. That means It does,but it is so slow that you cannot count it.

NormanPCN wrote on 4/25/2017, 11:08 PM

This is turning into the "stream of consciousness" thread. Hint.

GTX 1080ti doesn't support open CL...

It does.

GTX 1080TI is twice slower than R9 290 in Open CL performance. That means It does,but it is so slow that you cannot count it.

Not generally true.

http://www.luxmark.info/top_results/Hotel/OpenCL/GPU/1

It is quite well known that Vegas sucks on Nvidia. It that the fault of Nvidia or the Vegas code?

A little history about the Luxrender as it was often used as a bench by the Vegas community to "prove" that Nvidia OpenCL sucked. I speak of Luxmark 3.0. Luxrender is open source, so Nvidia could see the code, and Nvidia told the developers what things they we doing poorly. Luxrender now has more optimal code and in the Luxmark 3.1 benchmark Nvidia performs quite well indeed. Look for yourself.

You cannot compare Luxmark 3.0 to 3.1 scores since both Nvidia and AMD scores are higher due to the optimized OpenCL code.

Adi-W wrote on 4/26/2017, 7:33 PM

Could anybody confirm that the Magix Vegas plugin "éclat d'étoile" (in english it should be : "Starburst") crash VegasPro 14 252 if GPU acceleration is ON. I have an AMD Fury X and this plugin crash Vegas instantly with a Kernell.dll error. Doesnot happens in previous version.

Thanks !

NormanPCN wrote on 4/26/2017, 9:58 PM
http://www.luxmark.info/top_results/Hotel/OpenCL/GPU/1

Why so few AMD in those results? I don't see any retail AMD until an HD7970 at #139.

On the first page you see "Fiji". That is the current generation AMD architecture. No idea why it lists the architecture and not a card model number. It might be a current AMD GPU id thing versus Nvidia.

Nick Hope wrote on 4/26/2017, 11:16 PM

Could anybody confirm that the Magix Vegas plugin "éclat d'étoile" (in english it should be : "Starburst") crash VegasPro 14 252 if GPU acceleration is ON. I have an AMD Fury X and this plugin crash Vegas instantly with a Kernell.dll error. Doesnot happens in previous version.

No problem here but I have an old HD 6970 with a pretty old driver, and my Windows 10 is back at version 1511. What GPU and driver do you have, what Windows version, and what type of footage?

On the first page you see "Fiji". That is the current generation AMD architecture. No idea why it lists the architecture and not a card model number. It might be a current AMD GPU id thing versus Nvidia.

Thanks. Nonetheless, perhaps I should change my tune from "Nvidia is worse at OpenCL than AMD" to "Vegas works better with AMD's implementation of OpenCL than Nvidia's".

Adi-W wrote on 4/27/2017, 12:52 AM

Could anybody confirm that the Magix Vegas plugin "éclat d'étoile" (in english it should be : "Starburst") crash VegasPro 14 252 if GPU acceleration is ON. I have an AMD Fury X and this plugin crash Vegas instantly with a Kernell.dll error. Doesnot happens in previous version.

No problem here but I have an old HD 6970 with a pretty old driver, and my Windows 10 is back at version 1511. What GPU and driver do you have, what Windows version, and what type of footage?

Windows 7 (64bit) SP1 with an AMD Radeon R9 Fury X, driver Package Version 16.40.2715-161004a2-307919C. No need of any footage, I just load the plugin in an empty video track and get a nt.dll or kernell.dll crash.

 

 

set wrote on 4/27/2017, 1:36 AM

Win10 user (with latest Win10 creator update) with AMD RX470 GPU, Radeon Crimson 17.4.3 version.

> Still able to run VP14.252

Nick Hope wrote on 4/27/2017, 1:38 AM
Windows 7 (64bit) SP1 with an AMD Radeon R9 Fury X, driver Package Version 16.40.2715-161004a2-307919C. No need of any footage, I just load the plugin in an empty video track and get a nt.dll or kernell.dll crash.

Did your graphics driver get updated recently by you or Windows Update?

walter-i. wrote on 4/27/2017, 8:59 AM

No problem here but I have an old HD 6970 with a pretty old driver,

Nick, which driver do you have installed?
I have i7-2600K 3,4 GHz, and Radeon HD 6870, and the actual driver 15.7.1 - ist it OK in your opinion or would you recommend an older driver?

JesusSheep wrote on 4/27/2017, 10:25 AM

Sony would do well If they Corrected the GPU Rendering Problem With NVidia and Made Their Plugins DirectX11+ And DirectShow For Others.

JesusSheep wrote on 4/27/2017, 10:28 AM

AMD Has OpenCL  2.x Nvidia is 1.x. For NVIDIA They Could USE NVEnc.

Nick Hope wrote on 4/27/2017, 11:02 AM
Nick, which driver do you have installed?

I have i7-2600K 3,4 GHz, and Radeon HD 6870, and the actual driver 15.7.1 - ist it OK in your opinion or would you recommend an older driver?

Windows Control Panel > Device Manager > Display Adapter > AMD Radeon HD 6900 Series > Properties > Driver says 15.201.1151.1008 but I think this got installed by a file called amd-catalyst-15.7.1-win10-64bit.exe. Not totally sure because it's a long time since I paid it any attention. It just works. My Windows 10 is pre-Anniversary, version 1511. What version does your Device Manager say?

Adi-W wrote on 4/27/2017, 2:15 PM
Windows 7 (64bit) SP1 with an AMD Radeon R9 Fury X, driver Package Version 16.40.2715-161004a2-307919C. No need of any footage, I just load the plugin in an empty video track and get a nt.dll or kernell.dll crash.

Did your graphics driver get updated recently by you or Windows Update?


No recent driver update at all, but for trying, I just installed the last AMD driver "non-whql-win7-64bit-radeon-software-crimson-relive-17.4.4" and the Starburst plugin still crash Vegas . However, the good news is that this last AMD driver don't crash Vegas globally so I may keep them installed.

How do I send a ticket for it ? Thanks for your help !

walter-i. wrote on 4/27/2017, 2:39 PM
Nick, which driver do you have installed?

I have i7-2600K 3,4 GHz, and Radeon HD 6870, and the actual driver 15.7.1 - ist it OK in your opinion or would you recommend an older driver?

Windows Control Panel > Device Manager > Display Adapter > AMD Radeon HD 6900 Series > Properties > Driver says 15.201.1151.1008 but I think this got installed by a file called amd-catalyst-15.7.1-win10-64bit.exe. Not totally sure because it's a long time since I paid it any attention. It just works. My Windows 10 is pre-Anniversary, version 1511. What version does your Device Manager say?

 

Windows 7 Home Premium.
My Device Manageer says: 15.200.1062.1004
I installed it, I think months ago by AMD Catalyst Control Center.
When I check software actuality it says it's up to date. Windows 7
Very old already, I know, but it works more or less satisfactory