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

Nice, this update is looking really good so far!

Happy holidays to all you epicdudes over at MAGIX

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!!!

Where is 360Stabilizer ofx？

Which build of VP16 do you use?

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

I have problems with *.mp3

Where is 360Stabilizer ofx？

It is there, as it is.

I have problems with *.mp3

Describe the problem?

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

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

Where is 360Stabilizer ofx？

It is there, as it is.

My system is win7 and it cannot show 360Stabilizer ofx

The script “Copy Motion Track to PiP” can not remind "You must first add the Picture in Picture plug-in to the event that you want to pin to the motion tracked event." if the PIPfx does not apply the event.

@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

@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.

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!

@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).

@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.

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.

..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?

..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.

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.