Major Update for VP17?

Grazie wrote on 2/20/2020, 2:58 AM

How about this, then?:

New Features

White Balance improvements
5.7k render template now available for 360 projects
AMD decoding support for AVC and HEVC media
Bug Fixes

Color Grading panel now updates when a preset is selected
Problem with saving keyframe changes for some parameters is now resolved
Some white balance parameters are now no longer reset after project is reloaded
Fixed crash in Slow Motion plugin
Fixed issued where some HDR render templates are not displayed for HDR projects
Improve experience when using unsupported Intel drivers
Crash while using NewsPrint effect has been resolved
Rendering a project with Video Stabilization applied will no longer crash
Playback of some media with Video Stabilization applied will no longer crash
Smoothing parameter in Video Stabilization effect will now work for all media
Reset of Mesh Warp effect will now work for all points
Crash on launch which some users have experienced has been resolved
Audio effects are now stored properly for project archives, nested timelines or projects read from scripts
Overlays will now show up properly for Media effects
Crop plugin now works properly for HDR projects
Picture-in-picture effect now works properly for HDR projects
Out-of-sync indicator no longer shows up in some cases where the media is not out of sync
Resolved issue where some media with AC3 audio which had previously been able to be read but now results in an error
Resolved crashing issues while reading and writing HEVC media
Fixed a video preview redraw issue when maximizing VEGAS Capture window
Fixed potential stall in VEGAS Capture when starting a preview or recording
Fixed video preview issue in VEGAS Capture when webcam source resolution doesn't default to 640x480

Grazie wrote on 2/20/2020, 3:04 AM

AH! Build 421!

joost-berk wrote on 2/20/2020, 3:04 AM

@Grazie it is Build number 421

fifonik wrote on 2/20/2020, 3:12 AM

AMD decoding support for AVC and HEVC media

Holy Cow!

Grazie wrote on 2/20/2020, 3:13 AM

I know, I know , I know . . too excited.

Grazie wrote on 2/20/2020, 3:18 AM

@fifonik - Ah! Thar he be . . !

alifftudm95 wrote on 2/20/2020, 3:20 AM

Idk why I have no luck with the updates download. It still stuck at 1%. I have to wait for the official release to manually download the updates from Google

Martin L wrote on 2/20/2020, 3:25 AM

Seems like a good update. Just installed it. However, it promted me to dectivate one of my two PC's. I have always been able to have Vegas on two devices, is that possibility reduced to one now?

vkmast wrote on 2/20/2020, 3:28 AM

The "official" announcement likely later today as it's still early hours (03:27) in Wisconsin, USA (Central Standard Time (CST) -0600 UTC ).

@Bri-Hageman

Dexcon wrote on 2/20/2020, 3:35 AM

… it prompted me to deactivate one of my two PC's. I have always been able to have Vegas on two devices, is that possibility reduced to one now?

@Martin L ... I had that happen once with VP16. All I did at the time was to deactivate via My Account and then activate the new update. It seems to be just a quirk of the registration system - perhaps its assuming the update is being installed on a 3rd device.

joost-berk wrote on 2/20/2020, 3:37 AM

I am happy to see that the Time-line Nesting function-bug is fixed! It no longers drops audio/video FX's any more when toggeling to and from nested time-lines. Hooray! Thanks for the update Vegas-Team!

j-v wrote on 2/20/2020, 3:46 AM

Idk why I have no luck with the updates download. It still stuck at 1%. I have to wait for the official release to manually download the updates from Google

This is an official release which you can also find in your Magix account.

vkmast wrote on 2/20/2020, 3:48 AM

As @j-v says. And MAGIX Download Center.

VegasUser wrote on 2/20/2020, 4:00 AM

Still does not work Auto Adjust White Balance on Color grading panel ...

Stratman wrote on 2/20/2020, 4:53 AM

tried upgrading to 421 by agreeing with update prompt within Vegas, followed the install prompts and now when 421 attempts to load it just hangs on "creating video plugin factory" and does not proceed

I rebooted after install of 421 and before I attempted to run build 421 for the first time......bummer. Had to kill task. It sent Magix error report then I tried again, same thing :(

Radomir wrote on 2/20/2020, 7:01 AM

Well, this patch don't have promised "fix" on XAVC file :( :( :( so sad!

Reyfox wrote on 2/20/2020, 7:38 AM

Seems like a good update. Just installed it. However, it promted me to dectivate one of my two PC's. I have always been able to have Vegas on two devices, is that possibility reduced to one now?

After the last Win10 update, I had problems with VP17 since I too. Looking at my account, I saw that also VP14-16 also had 2 activations to the same computer. I deleted the oldest one and all was well after that. The last Win10 update messed up several things with my computer devices.

Downloading now the update after launching VP17. Real slow download... but it's happening. So glad for AMD support with HEVC!

Martin L wrote on 2/20/2020, 7:42 AM

I've been editing with the new build now for a few hours. So far so good!

fr0sty wrote on 2/20/2020, 8:13 AM

tried upgrading to 421 by agreeing with update prompt within Vegas, followed the install prompts and now when 421 attempts to load it just hangs on "creating video plugin factory" and does not proceed

I rebooted after install of 421 and before I attempted to run build 421 for the first time......bummer. Had to kill task. It sent Magix error report then I tried again, same thing :(

@Stratman try to do a clean install, uninstall Vegas completely and re-install it.

This issue typically pops up when you have a plugin conflicting with Vegas, so if this doesn't work, we'll need to isolate which one is causing the problem and disable it.

fr0sty wrote on 2/20/2020, 8:41 AM

Gave AMD hardware decoding a spin... 5 4K angles, one of those 4k angles being 10 bit. No Proxies. Results:

at good (full), playback was roughly the same as CPU decoding.

At good (auto), playback stayed at a solid 24fps (native framerate) no matter which camera it switched to, and the annoying pause we've grown used to seeing between camera cuts was mostly eliminated. A couple small dips in framerate from time to time, but it stayed mostly solid, I could definitely skip making proxies from now on.

I did NOT test with preview mode, as I had already made proxies and enabling preview or draft mode would enable the proxies.

Stratman wrote on 2/20/2020, 4:30 PM

@Stratman try to do a clean install, uninstall Vegas completely and re-install it.

This issue typically pops up when you have a plugin conflicting with Vegas, so if this doesn't work, we'll need to isolate which one is causing the problem and disable it.

thanks fr0sty, I booted up this morning after reading your reply ready for a clean install and thought I would try it one more time.....421 loaded! So all good for now. Looks like Kernel base issue is fixed. Now for some editing!

LanceMGY wrote on 3/28/2020, 7:44 PM

Updated to build 421. After the update, the shortcut was deleted from my task bar. When I launched VP17, it wanted me to register and activate again. ???? That does NOT sound like normal behavior just for an update. Why would it require activation again only after updating? It wasn't a fresh install on a new system, just an update.

Plus I see the VST audio fx glitching issue still persists. Use any 3rd party VST plugin, then move ANYTHING on the UI including all VP17 features (such as master volume, etc)... glitch glitch glitch. And the UI freezes along with it. Problem has been persistent in all 64bit Vegas versions starting with 10. Truly unbelievable this hasn't been fixed. I had hopes when Acid Pro came out supporting 64bit VST3 plugins. Works great, no glitching, unlike VP. Guess most customers do not use VST audio plugins, so they just don't care about fixing this sadly.

fr0sty wrote on 3/29/2020, 2:03 PM

That is common. The same is true if you uninstall and re-install Vegas, which is essentially what is happening when you update.

I've been bugging the team about showing VST some love, including VST3, for a while now. It is on their list, but as you said, Vegas is not a DAW, even though it used to be, so the video features get priority. For now, there is still a lot on the video end that needs to be tightened up or updated completely, so unfortunately, audio might have to take the backseat for a little while longer.

LanceMGY wrote on 4/23/2020, 4:39 PM

That is common. The same is true if you uninstall and re-install Vegas, which is essentially what is happening when you update.

I've been bugging the team about showing VST some love, including VST3, for a while now. It is on their list, but as you said, Vegas is not a DAW, even though it used to be, so the video features get priority. For now, there is still a lot on the video end that needs to be tightened up or updated completely, so unfortunately, audio might have to take the backseat for a little while longer.

This was never the case with all updates in previous versions, going all the way back to Vegas Video 4 I believe. An update did not request any activations or authorizations, it just updated the app, like most any app update works. An uninstall/reinstall is different and does require activation again which is to be expected. At least since Vegas has been with Magix, I don't remember seeing this need to activate again after an update.

And thank you for bugging them about the VST issue. I've been bugging them for years but still haven't given up since the work I do relies on some features of Vegas I can't find in any other DAW. I know things need to be fixed on the video end, but this audio issue has taken a back seat for about 10 years now, since the first 64bit version of Vegas was released with version 10.

And Vegas desperately needs to be able to allow more than one plug-in window open at a time! It's too bad you can only have one fx plugin open at a time, audio or video.