VP18 Update 334 released

Dexcon wrote on 9/21/2020, 2:56 AM

Just opened VP18 and the update dialogue box came up. The list of new features is:

Changes in Update 1 build 334

Features

Support for HEVC HDR presets available for NVENC

AMD support for Driver Update dialog

NVIDIA Quadro support for Driver Update dialog

Smart proxy generation based on GPU capabilities

Greater ability to move the Region of Interest for Video Stabilization

Interface to VEGAS Image

Direct control of Motion Tracking from withing the Bezier Masking FX

Progress bar on the Motion Tracking panel is now clickable

Bug Fixes

Better handling GPU auto selection

Fixed crash on startup related to some Intel GPU drivers

Flicker Control FX thumbnail now displays properly in Plugin window

Colorization FX thumbnail now displays properly in the Plugin Window

Auto update for VEGAS Image and VEGAS Effects now functions

VEGAS Pro 17 projects that have the Slow Motion FX will no longer cause a crash

Grids in Expert mode on the Video Stabilization FX now work properly

Style Transfer and Colorization plugins now work on all supported hardware

Motion Tracking icon in the timeline toolbar correctly opens the Motion Tracking panel

Render progress dialog now remains in focus when open

VEGAS no longer freezes when clicking into another application while the Render Progress dialog is open

Proxy generation and use of Proxy files now work as expected

Motion data now properly applied to 2D parameters

Fixed problem where some Notebook GPUs are not detected by the Driver Update dialog

Exposure control in the Color Grading panel no longer clips in full-range projects

Fixed crash when reading in a file that was rendered from a 360 project with a non-hardware accelerated template

Improved performance of Plugin window thumbnail generation

Some iPhone files will no longer appear inverted in the Explorer window

Clicking on a Panasonic P2 template in the Render As dialog and then clicking a different format now allows editing of the file name

Fixed crash on shutdown

Adding Motion Tracking to a Lens Flare FX will no longer cause a crash

Picture in Picture FX now works properly in Free Form mode

Pan and Crop will no longer crash if "Collapse loop region" option is enabled in preferences

Hide the Third Party tab in the plugin window if no third party plugins are installed

Default format for Save Snapshot feature is now PNG

HDR templates now displayed when they should be available in the Render As dialog

Change the default render formate in the Render As dialog

Video Stabilization no longer causes VEGAS to hang on playback with some AMD GPUs

Interlaced templates now available in the MAGIX AVC/AAC render plugin

Fixed problem with selection of animation keyframes that are not aligned with frame boundaries

Crash when clicking on the Creative Tab in the Video FX plugin window is fixed

Saving and loading of Favorites in the Plugin Windows now works as expected

Collapsing track groups with a fade applied to events no longer results in crash

Opening the Motion Tracking panel from an event's burger menu now properly selects the event

Fixed a crash when reading some MP4 files with an unusual AAC format

Back to post

Comments

alifftudm95 wrote on 9/21/2020, 11:14 AM

@alifftudm95, @andyrpsmith: Can you run the hardware detection application (called 'So4HardwareDetection.exe' in a command window, and let me know what happens. The steps to do so are as follows:

Open Command Prompt Window (type "cmd" in the Windows Search/Run box next to the Start button in the lower left corner of your screen)

Navigate to the VEGAS folder by typing in the following: cd "\Program Files\VEGAS\VEGAS Pro 18.0"

Execute the following command: So4HardwareDetection.exe, and please let me know what happens. Under normal circumstances, something like the attached image will show up.

If the application freeze up, you should see it in Task Manager -> Details tab, as shown below:

If the application crashes, there may or may not be a prompt from Windows, but you may be able to see it show up in the Task Manager for a few seconds, and then go away.

Hmm...

andyrpsmith wrote on 9/21/2020, 11:22 AM

I get the same as alifftudm95. But running Vegas now I get no video decode showing in task manager where before I did.

Video_flaneur wrote on 9/21/2020, 11:23 AM

@Video_flaneur: Do you also have your Windows 10 machine up to date? We have found that sometimes the latest drivers will not work correctly with older versions of Windows.

Yes, my Windows 10 is up to date. My driver is 10.18.10.5146 but the VEGAS driver update window says the online version is 15.33.51.5146. However using the Intel driver updater does not give me that option. Also my Nvidia card does not appear to support studio drivers but it appears to be working fine. Hardware and software details in my signature.

Thank you for your feedback and in the meantime manually disabling the Intel device before using VEGAS is not a major inconvenience. Your work on continuous improvements is appreciated.

andyrpsmith wrote on 9/21/2020, 11:34 AM

Just downloaded the studio driver and it is the same - Vegas18 has stopped using video decode on timeline playback. If I run V17 it uses video decode 36% for timeline playback.

VEGASHeman wrote on 9/21/2020, 11:36 AM

@alifftudm95, @andyrpsmith: Thank you for that information. Based on your observations, it seems that the hardware detection process seems to be fine in both of your cases, but the output file ("So4HardwareDetectionOutput.xml") is not created in the "C:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0" folder for some reason, and hence VEGAS thinks no suitable hardware decoders are present. We will need to research this, and get back to you.

@Video_flaneur: We are aware of problem updating Intel drivers on certain machines, and unfortunately, yours seems to be such a case. As far as the NVIDIA drivers go, "Studio" drivers are helpful, but not essential.

pierre-k wrote on 9/21/2020, 12:00 PM

FOR VEGAS TEAM

I've been observing for a very long time that in beta testing you probably lack the kind of computers we have. We regularly discover mistakes that you do not have in the team. Try testing Vegas on a normal computer with firefox, internet, games, and other third-party software. Not every user always has clean windows only with Vegas. That would be uneconomical

alifftudm95 wrote on 9/21/2020, 12:05 PM

@alifftudm95, @andyrpsmith: Thank you for that information.

I've been observing for a very long time that in beta testing you probably lack the kind of computers we have. We regularly discover mistakes that you do not have in the team. Try testing Vegas on a normal computer with firefox, internet, games, and other third-party software. Not every user always has clean windows only with Vegas. That would be uneconomical

So ur saying it best for me to test VEGAS on a computer that have bunch of other stuff installed? (games, softwares etc etc)

pierre-k wrote on 9/21/2020, 12:08 PM

that message was for the Vegas team.

alifftudm95 wrote on 9/21/2020, 12:13 PM

that message was for the Vegas team.

ouh lol my bad ahah

LauraA wrote on 9/21/2020, 2:53 PM

@VEGASHeman please see attached screenshot. I ran So4HardwareDetection.exe and received the message "The code execution cannot proceed because OpenCl.dll was not found." What should I do? My CPU is running overtime and my gpu is barely being used. Was not having this issue with the previous version.

VEGASHeman wrote on 9/21/2020, 3:11 PM

@LauraA: OpenCL.DLL is typically shipped with the GPU drivers. I will send you a PM to go over your hardware configuration.

Jonathan-Burnett wrote on 9/21/2020, 4:40 PM

I just installed the 334 update and when I went to try the Driver Update to see what it would find for my AMD card, it just seems to hang at "Loading...". I've tried it a couple of times and let it run for as long as 15 minutes without any further updates than this:

I've repeatedly tried the driver update and in some cases, left it trying for many hours but it never returns from the screen shown above.

Any suggestions?

andyrpsmith wrote on 9/21/2020, 5:02 PM

Does it find you card in the video tab and File I/O tab?

Yelandkeil wrote on 9/21/2020, 5:23 PM

@VEGASHeman

Sir, files from Sony HDR-TD10 (Camcorder with 5.1 channel audio) still have no sound on timeline.

I replaced the mvcplug.dll with the same one from VP17Build284.

cadudesun wrote on 9/21/2020, 6:31 PM

Hi,

a) As shown in the snapshot below (Preferences>File I/O), does it make sense Vegas auto-selecting "Intel QSV" instead of "NVIDIA NVDEC"?

The specs of my system are:

Graphics Intel UHD 630

NVIDIA GTX 1050Ti 4GB

b) Should I manually select "NVIDIA NVDEC", since it is supposed to be superior to Intel QSV"?

Thank you!

RogerS wrote on 9/21/2020, 7:20 PM

Hi,

a) As shown in the snapshot below (Preferences>File I/O), does it make sense Vegas auto-selecting "Intel QSV" instead of "NVIDIA NVDEC"?

The specs of my system are:

Graphics Intel UHD 630

NVIDIA GTX 1050Ti 4GB

b) Should I manually select "NVIDIA NVDEC", since it is supposed to be superior to Intel QSV"?

Thank you!

I have almost the same system as you. It's a tradeoff. QSV works with more file types and may be more stable (I had a lot of issues with Nvidia decoding in the past). Nvidia is faster. I get acceptable performance with the default so I leave it on that these days.

Former user wrote on 9/21/2020, 7:29 PM

They're pretty similar as far as their ability to decode video formats you'd use in Vegas. Advantage to using NVDEC is that is it a faster decoder, and the heat generated via decoding is easily absorbed by your GPU cooler, the negative of using intel 630 for decoding is that it creates more heat on your cpu, and if cpu cooling not adequate will help with cpu becoming thermally throttled.

The advantage of using intel630 for decoding is not confirmed, there may be no advantage. Some people believe it's use makes vegas more stable, others think it's cool that both their gpu's are doing something instead of just their main GPU

Former user wrote on 9/21/2020, 7:31 PM

lmost the same system as you. It's a tradeoff. QSV works with more file types

Now that I didn't know, What does intel 630 decode that Pascal NVDEC doesn't in relation to vegas?

Howard-Vigorita wrote on 9/21/2020, 9:09 PM

Did the update on 2 of my systems running v18. It fixed the issue I had on both systems which were crashing if I dropped a keyframe in track motion if "Collapse loop region when no time select is present" is enabled. The driver update screen on the 9900k system also looked at AMD updates which is new.

I still get a hang on my 9900k system if I set decode with amd and render qsv to an fhd frame with the 4k hvec version of Red Car. Oddly, doing the same thing but rendering to a 4k frame works fine. I usually set the decoder to Intel on that machine so it's not a show stopper for me. Did an update to the Intel driver (per advice of the v18 driver update screen) from 27.20.100.8673 to .8681 with no change to the problem or previous benchmark results.

Another problem not fixed is on my 980x machine. A lack of the render progress screen. Noticed that there was a cumulative Win10 v2004 update as well as a cumulative one for .NET Framework... but no change after installing those. Also noticed the driver update screen gets stuck on this machine looking for updates. If I turn off my Internet connection, however, it at least reports the installed version (amd enterprise q3). This machine has an ethernet connection to my router rather than wi-fi. Which worked fine pulling in the v18 update but doesn't seem to work for the driver update check.

andyrpsmith wrote on 9/22/2020, 5:19 AM

I can confirm GPU video decode does not work for Nvidia or INTEL. This is a shameful embarrassment. You need to cancel whoever is beta testing for you, Send a kill signal on this version to disable, and never admit to ever releasing it. I am returning to previous version

No issues here on my 1080ti.

Although, I should note that I did install the Studio Driver they released a couple of days ago.

Also QSV rendering is functioning appropriately.

So far, so good.

Is your 1080Ti showing video decode in task manager when previewing the timeline at best full (4K if possible). Thanks. Mine is not so dropping frames like a sieve.

VEGASPascal wrote on 9/22/2020, 8:20 AM

I just installed the 334 update and when I went to try the Driver Update to see what it would find for my AMD card, it just seems to hang at "Loading...". I've tried it a couple of times and let it run for as long as 15 minutes without any further updates than this:

I've repeatedly tried the driver update and in some cases, left it trying for many hours but it never returns from the screen shown above.

Any suggestions?

Some seconds are okay but you do not have to wait for 15 minutes. I believe the web response is hanging. I try to reproduce the issue with a nonexistent card... but it works for me.

I will write you a PM

andyrpsmith wrote on 9/22/2020, 8:38 AM

I'm still stuck with no video decode V18 latest build. 1080Ti is in video tab but Vegas thinks there is no Video decoder.

andyrpsmith wrote on 9/22/2020, 8:56 AM

Hey, I found a fix - in the internal menu the hardware decoder to use with So4compund was set to 0 (default 1) changing it to 1 has now enabled the timeline to use GPU video decode. Worth noting that the So4HardwareDetection.exe does not generate the "So4HardwareDetectionOutput.xml" file on start in my setup. Also placing the copy of the "So4HardwareDetectionOutput.xml" file sent to me by VEGAS developer team did not enable video decode. Of course always be careful in changing anything in the internal menu as it is possible to screw Vegas up completely.

VEGASHeman wrote on 9/22/2020, 10:15 AM

@andyrpsmith: Thank you for the update - under normal circumstances, you should not really need to modify that internal preference. As you mentioned that you still do not see the XML file, I have sent you a private message with some other instructions - could you please try those, and see if it helps?