VEGAS Pro 16 Update 3 (build 352) - General Discussion

VEGAS_CommunityManager wrote on 12/20/2018, 2:33 AM

We have just released VEGAS Pro 16 Update 3 (build 352). Please give us your feedback in this thread and spread some holiday atmosphere!🎉

If you already have build 352 or earlier installed, there is no need to uninstall it. The build 352 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update.

If you are installing VEGAS Pro 16 for the first time, it is generally better to install using a VEGAS Pro download manager. See here for details & links.

Official announcement with Patch Notes

VEGAS Pro 16 (build 352) installer

Comments

barry-v wrote on 12/20/2018, 4:51 AM

Thank you! Merry Christmas to all at Magix Vegas.

Dexcon wrote on 12/20/2018, 5:09 AM

Thank you from me also. Build 352 installed and activated without a problem, and it loaded my rather long project without any problematic dialogue box issues.

A very Merry Christmas and Happy New Year to all at MAGIX - and many thanks to Gary and the dev team. Vegas Pro has certainly come a long way over the last few years and will no doubt evolve even more in the months and years to come.

And many thanks must also go to the Moderators on this forum.

And, of course, Merry Christmas/Happy New Year/Seasons Greetings/Happy Holidays/etc to all forum contributors.

Cheers

Conrad

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

Zaither-P wrote on 12/20/2018, 9:16 AM

Nice, this update is looking really good so far!

Happy holidays to all you epicdudes over at MAGIX

pioneer109 wrote on 12/20/2018, 10:02 AM

Thanks for the Update, seasons greetings to Magix and all here. Can somebody please remind me, do I just run the update and it automatically overwrites the previous version. Sorry to be thick its an age related problem. Cheers John. Sorry should of read the first comment!!!

Marco. wrote on 12/20/2018, 10:44 AM

Which build of VP16 do you use?

james-ollick wrote on 12/20/2018, 1:59 PM

Thank you! Merry Christmas and Happy New Year to all!

 

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply. Windows 11.

VP 19, BCC 2022 Continuum Complete, Titler Pro v7.

k.miroslav wrote on 12/20/2018, 2:59 PM

I have problems with *.mp3

set wrote on 12/20/2018, 4:07 PM

Where is 360Stabilizer ofx?


It is there, as it is.

set wrote on 12/20/2018, 4:08 PM

I have problems with *.mp3

Describe the problem?

k.miroslav wrote on 12/20/2018, 4:30 PM

Import media dont have variant *.mp3 and after import mp3 as all files music is screech

Dimitrios wrote on 12/20/2018, 7:11 PM

doesn't recognize my hitfilm plugins now, tried repairing them, no joy.

VEGASPascal wrote on 12/21/2018, 3:41 AM

@lan-mLMC @Dimitrios

Dear Community,

over the last years we received tons of Error Reports with a similar problem (the biggest problem in our list). The combination of one plugin, the host VEGAS and the driver of your graphic card (NVidea, AMD, Intel) crashed the whole project during your rendering process or in your preview which was frustrating for users and developers. For this reason, we created the barrier at the start-up for instable plugins. They are not instable in general but on your system with your drivers and OS. This protection is no 100% guarantee but it minimize the frustration at start-up or during the rendering.

We are in good contact with the graphic card manufacturer (Intel, NVidea, AMD), Microsoft and the plugin clients (HitFilm, ProDad, BorisFX, NewBlueFX etc.) to bring back the blacklisted plugins as fast as possible.

Happy holidays and a lot of fun with this update,

Your VEGAS team

NickHope wrote on 12/21/2018, 3:58 AM

@VEGASPascal Can you add more detail about exactly what combinations of plugin, drivers & OS cause a plugin to be blacklisted? Are there definitive lists of affected plugins and approved drivers? I feel this change, which wasn't mentioned in the release notes, may cause some furore. Clear, detailed information will help to abate that.

bitman wrote on 12/21/2018, 4:39 AM

Audio Rendering using dolby digital ac3 studio template still gives a silent result file if the render result file has the same name (e.g. if it was rendered before with the same name). I know this was not in the release notes as fixed, but how difficult to fix can this be? It is just an overwrite which does something wrong, as rendering to a new filename works.

Anyway thanks for the other fixes, keep up the good work!

Last changed by bitman on 12/21/2018, 4:41 AM, changed a total of 2 times.

APPS: VIDEO: VP 365 (20), VP 19 post (latest build -643), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 15 HDpro XXL, Boris Continuum 2022.5, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Audio Clean Lab 3, Sound Forge Audio Studio 16, Sound Forge Pro 16, Spectral Layers Pro 9, Audacity, FOTO: Zoner, DXO, Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 22H2
  • CPU: i9-12900K with Cooler: Noctua NH-D15s
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

VEGASPascal wrote on 12/21/2018, 5:52 AM

@VEGASPascal Can you add more detail about exactly what combinations of plugin, drivers & OS cause a plugin to be blacklisted? Are there definitive lists of affected plugins and approved drivers? I feel this change, which wasn't mentioned in the release notes, may cause some furore. Clear, detailed information will help to abate that.

This barrier is a small start of each plugin to test the compatibility with the OpenCL driver. If the plugin crash in this test, it is blacklisted for GPU-usage and would only work with CPU. Some plugins do not have a CPU fallback and are complete blacklisted. At this moment we know that there is a problem with some new Intel drivers in combination with Hitfilm and our 360° stabilizer (OpenCL conflict). This barrier was a last minute bugfix but we believe this fix would give the user a lot of stability in the rendering process (before this barrier VEGAS crashed here).

Dimitrios wrote on 12/21/2018, 8:32 AM

@VEGASPascal Can you add more detail about exactly what combinations of plugin, drivers & OS cause a plugin to be blacklisted? Are there definitive lists of affected plugins and approved drivers? I feel this change, which wasn't mentioned in the release notes, may cause some furore. Clear, detailed information will help to abate that.

This barrier is a small start of each plugin to test the compatibility with the OpenCL driver. If the plugin crash in this test, it is blacklisted for GPU-usage and would only work with CPU. Some plugins do not have a CPU fallback and are complete blacklisted. At this moment we know that there is a problem with some new Intel drivers in combination with Hitfilm and our 360° stabilizer (OpenCL conflict). This barrier was a last minute bugfix but we believe this fix would give the user a lot of stability in the rendering process (before this barrier VEGAS crashed here).

Guess I'm staying on 307 for a while.

raWer-Studio wrote on 12/21/2018, 8:37 AM

Merry Christmas and Happy New Year to you :-)

My problem with VP16 - build 307 and below - render and editing with LUT filter fx on timeline - gradually increasing the GPU memory to reach critical limits and crashing the program or turning off the render before finishing.

Now the problem is solved, but i have another problem and it is a very slow render with LUT filter fx.

My tests - fotage: 4K 10bit 422 from GH5.

Render:

2160p - 32bit floating point (video level), 3mins project with 30s Neat video fx and 10s (legacy) text over video

build 307 Render time with LUT: 6:18 - w/o LUT: 6:07

build 352 Render time with LUT: 12:55 - w/o LUT: 6:20

1080p - 8bit, same project

build 307 Render time with LUT: 2:04

build 352 Render time with LUT: 2:45

 

My PC: i7-7820x, gtx 1080ti, 32Gb ram.

NickHope wrote on 12/21/2018, 9:36 AM

..At this moment we know that there is a problem with some new Intel drivers in combination with Hitfilm and our 360° stabilizer (OpenCL conflict)...

@VEGASPascal Thanks for the clarification. Is there any recommended solution if users lose access to their plugins such as Hitfilm or 360° Stabilizer? For example, something they can disable, or a different driver?

VEGASPascal wrote on 12/21/2018, 10:15 AM

..At this moment we know that there is a problem with some new Intel drivers in combination with Hitfilm and our 360° stabilizer (OpenCL conflict)...

@VEGASPascal Thanks for the clarification. Is there any recommended solution if users lose access to their plugins such as Hitfilm or 360° Stabilizer? For example, something they can disable, or a different driver?

Sorry... no real solution yet. We know it is a problem with the latest drivers and the latest Intel GPU (530 and 630). Maybe a member knows the latest working Intel driver.

fr0sty wrote on 12/21/2018, 10:45 AM

One big update that some of you may have not caught... this update enables DirectX rendering, which means you no longer have to have a pro-level GPU to get 10 bit video output (HDR) directly from Vegas. This makes Vegas the only NLE I know of that supports this, and will save those of us who are looking to get into HDR a lot of money by not having to upgrade our GPU. I've tested it with a GTX 970, it works very well. Vegas now has the easiest and most fully featured HDR workflow of any NLE I've ever seen. It can play back HDR without specialized hardware, it can edit HDR natively with a simple project setting change that takes 10 seconds, it can insert HDR metadata into your file so you can specify MAxFall and MaxCLL values (no other NLE I've seen has this), and it can encode a HDR ready file without the need of any third party apps (again, no other NLE I've seen will do this).

 

Kudos to the Magix team for leading the way with HDR.

Last changed by fr0sty on 12/21/2018, 10:49 AM, changed a total of 4 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Marco. wrote on 12/21/2018, 10:56 AM

Don't know if Intel HD Graphics 520 would be same, I think it shares same driver as 530 does.

On my notebook with Intel 520 and driver version 25.20.100.6444 (updated to this version a few days before) these FX appear and work fine (in the way they do not crash nor freeze Vegas Pro 16 build 352).
I tested with "Vegas 360° Video Stabilize" and a bunch of the Ignite Pro plug-ins like "Chroma Key", "Skin Retouche", "Cine Style", "Bleach Bypass", "Denoise". Also the Vegas integrated HitFilm FX like "Vibrance", "Witness Protection", "Three Strip Color" work fine.

So it seems like with Intel HD Graphics 520 and driver version 25.20.100.6444 there is no problem with all these plug-ins mentioned.