Magix Vegas Pro 16 Update 3 (build 352)

[Chris Young]

Just having a strange experience with v16 b352. Since this has been installed playing back an XAVC S-LOG3 HD 50p timeline with 3D LUT and Curves grade the CPU usage has gone through the roof to average around 96-100% and struggles to playback Best Full at 25-30FPs.

The exact timeline, same LUTs and grade in v15 b416 has an average CPU usage of 25-27% at Best Full and plays back at the full 50Fps.

Any ideas anyone? Latest Nvidea drivers installed, v417.35 installed

Win 10, K8700k OC’d to 5GHz and GTX1080 Ti.

[John Norton]

Maybe to do with this … see the post by MagixPascal …
https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-update-3-build-352-general-discussion–114171/?page=1

[Chris Young]

Thanks John. I’m already posting over there on this issue. This is what I posted:

Exactly, destroyed preview. Win 10 8700k OC’d to 5GHz with GTX 1080 Ti. On this box with v15 build 461 I can play an S-LOG 3 1080 50p timeline with 3D LUts and grades at Best/Full at the full 50 FPs.with around 25-27% CPU usage. Perfect in other words. With v16 b 352 the exact same timeline staggers at around 25-30 Fps with CPU usage running at anywhere where between 96-100% CPU. Don’t know what has happened but I had to go back to v15 b461.

v16 b 307 has the issue where any legacy text on the timeline shows up in Project Media with random icons such as .AVI. If I change file associations in MPC-HC player then the Project Media Legacy Text icons can change to some other type of icon. This was fixed in b352 but sadly the playback issue is a major one. Have notified the Beta team of this. Hopefully hear something fresh in the New Year.

Hopefully a solution will arise in the new year! ☺

Cheers
Chris

[Chris Young]

Heard back from Magix on the above issues. Neal Granroth replied with the following info so now we know what is happening in build 352. Looking forward to the update ☺

“Hello Chris,

Thanks for the heads-up on this issue.

I took a close look at what is happening. It is clear that this is an unintended side-effect of the protective crash-prevention changes that were added to VEGAS Pro 16, update 3 (build 352).

The LUT Filter plugin is being prevented from utilizing the GPU and is instead using the CPU to apply the LUT color adjustments. Use of the GPU to apply the LUT color adjustment is critical for proper playback performance.

We are currently reviewing a set of changes that will correct this.

Thanks again for promptly bringing this to our attention.

Regards,

Neal G.”

[Dimitrios Papadimitriou]

352 Really was a lump of coal for christmas.