VEGAS Pro 17 Update 1 (build 321) - General Discussion

VEGAS_CommunityManager wrote on 9/23/2019, 9:15 AM

We have just released VEGAS Pro 17 Update 1 (build 321). Please give us your feedback in this thread.

The build 321 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update. Have a great day, everyone!

Official announcement with Patch Notes

Comments

j-v wrote on 9/23/2019, 9:53 AM

Screencapture still not working well.
I made a small capture and when placing the files on a Vegas timeline audio and video are not synchronised

Look to the MediaInfo of both files

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
551.61 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 551.61 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

BobMoyer wrote on 9/23/2019, 10:07 AM

I know my Window7 is not supported any longer in version 17 but I am not alone in using it.  There seems to be no way to update my version 17 to the new version as it leaves a process running and the update will not allow you to run it and there seems to be no way to end it before the upgrade ends with an error. Any solutions or suggestions (besides upgrading to Win10 which is not a rational option).

fr0sty wrote on 9/23/2019, 10:10 AM

Good catch. At least that is an annoyance that can be easily worked around (a slight adjustment on the timeline should fix it), and not something that prevents work from being done.

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)

j-v wrote on 9/23/2019, 10:38 AM

Good catch. At least that is an annoyance that can be easily worked around (a slight adjustment on the timeline should fix it), and not something that prevents work from being done.

Not for me😌
Still no option for other framerates and while 30 is not my favorite and also no other options I shall not use it untill it has (almost) te same options as OBS has.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
551.61 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 551.61 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Former user wrote on 9/23/2019, 11:14 AM

Tried the new lossless intermediate on my laptop, produces a zero byte file.

I'll try it soon on my PC, waiting on download to complete.

KaraUSA wrote on 9/23/2019, 11:21 AM

Not new codecs for exportation video ! I'm sad !

Former user wrote on 9/23/2019, 11:24 AM

Same result on my PC, renders out a zero byte file. https://www.vegascreativesoftware.info/us/forum/vp-17-new-lossless-intermediate-for-avc-and-hevc-zero-byte-uhd-rende--116546/#ca725138

D7K wrote on 9/23/2019, 11:41 AM

Windows 10 pro, AMD 480RX 8 gig, 4K screen on HDMI #1 No Screen capture. Generic Box in capture still black.

D7K wrote on 9/23/2019, 11:41 AM

No AMD decode, thought that was the priority?

Julius_ wrote on 9/23/2019, 11:45 AM

I know my Window7 is not supported any longer in version 17 but I am not alone in using it.  There seems to be no way to update my version 17 to the new version as it leaves a process running and the update will not allow you to run it and there seems to be no way to end it before the upgrade ends with an error. Any solutions or suggestions (besides upgrading to Win10 which is not a rational option).

I'm in the same boat...it downloadsm I try to update and it says it can't update while 17 is still running...you close the window and the process also stops. Ouch

Len Kaufman wrote on 9/23/2019, 12:06 PM

Wow! Must be a whole buncha' folks downloading this upgrade, as the download is taking forever on my very fast connection.

RonB_USA wrote on 9/23/2019, 12:20 PM

Yes, I agree. The download is slower than normal. We hope that it is worth the wait. Exciting!

RonB_USA

Operating System: Windows 10 Pro

Dual Monitors: Now have TWO Samsung 4K 27-in (3840x2160) monitors both using DisplayPort

Desktop Sound: Stereo speakers with sub-woofer. Headphones. Earbuds.

VEGAS Pro 21.0, version 208. Have used VEGAS Pro since Sony days. Movie Studio also.

Voukoder 1.7.1.0

Source Footage: Mostly XAVC-S 4K MP4 with some MTS HD at times. Have used Samsung S21Ultra 5G footage.

Some upscaling of older videos. Many videos are more than 10 years old. Trying to learn more color correction and grading techniques. Any help with flicker reduction without motion blur is welcome!

Motherboard: ASUS PRIME X299-A II (3.7GHz)

CPU: Intel i9-10920X 12 Core 24 Thread

GPU: Quadro RTX-4000 8GB

RAM: 64GB DDR4

C-Drive SSD: M.2 2TB + Video SSDs: Two M.2 2TB + Internal HDDs: Several TB + External HDDs + External SSDs

Former user wrote on 9/23/2019, 1:08 PM

Memory issues haven’t been addressed ... The system is low on memory etc, identical project renders ok on VP16, bombs out on VP17 ...

https://www.vegascreativesoftware.info/us/forum/the-system-is-low-on-memory-4k-render-error-when-it-clearly-is-not--116565/

There was no mention of this in the bug fixes, so I wasn’t expecting much. This is some sort of memory/resource issue, as there is enough memory in my system, and anyway no problem in VP16.

Damian wrote on 9/23/2019, 3:10 PM

An extension has been added to automatically adjust the length of an event after applying a playback rate change with the Slow Motion OFX plug-in

How does it work? Can someone explain?

fr0sty wrote on 9/23/2019, 3:17 PM

Memory issues haven’t been addressed ... The system is low on memory etc, identical project renders ok on VP16, bombs out on VP17 ...

https://www.vegascreativesoftware.info/us/forum/the-system-is-low-on-memory-4k-render-error-when-it-clearly-is-not--116565/

There was no mention of this in the bug fixes, so I wasn’t expecting much. This is some sort of memory/resource issue, as there is enough memory in my system, and anyway no problem in VP16.

Seems to be related to Nvidia systems, my cousin was having this same issue on his GTX 970 system, and it also would crash when rendering if dyanamic ram preview was set to anything but 0. however this update did fix his problem.

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)

fr0sty wrote on 9/23/2019, 3:22 PM

No AMD decode, thought that was the priority?

A priority doesn't mean that it's going to be ready by the next update. There were some bug fixes in this update (like the dreaded thumbnail bug for complex projects that ground even powerful systems to a halt) that they really needed to get out the community asap, regardless of if AMD decoding speed and stability was where they felt it should be yet. I'm glad they didn't make us wait for that, if it isn't ready.

Former user wrote on 9/23/2019, 4:27 PM

An extension has been added to automatically adjust the length of an event after applying a playback rate change with the Slow Motion OFX plug-in

How does it work? Can someone explain?

@Damian

This means that you no longer have to manually set the new duration of the event to which the slow motion effect was applied.  

Example:

Let's say you set the playback rate to 0.50 in the slowmotion effect in a 2-second event. In the past you would have to manually set the event duration to 4 seconds on the timeline. Now just use the extension this will be done automatically.

Kinvermark wrote on 9/23/2019, 4:31 PM

RE: AMD decode support.

FWIW, another competing NLE is having a heck of a time getting this to work. IMO, much better not to release this feature too early and have junk frames in your final renders because of it!

Personally, I am looking to upgrade to an Nvidia card.

Damian wrote on 9/23/2019, 4:54 PM

An extension has been added to automatically adjust the length of an event after applying a playback rate change with the Slow Motion OFX plug-in

How does it work? Can someone explain?

@Damian

This means that you no longer have to manually set the new duration of the event to which the slow motion effect was applied.  

Example:

Let's say you set the playback rate to 0.50 in the slowmotion effect in a 2-second event. In the past you would have to manually set the event duration to 4 seconds on the timeline. Now just use the extension this will be done automatically.

 

It doesn´t work, maybe a bug in the german language pack.... Could someone test it, please?

 

Former user wrote on 9/23/2019, 6:00 PM

@Damian

Here, the extension works fine.

The slow motion effect has improved, but rendering to see the end result now takes an eternity.

Grazie wrote on 9/23/2019, 8:24 PM

Unexpected behaviour. Not all my 3rd Party Licences Settings were immediately recognised. Updating required a PC Reboot to reactivate my BORIS MOCHAPRO19 License.

Grazie wrote on 9/23/2019, 8:31 PM

RE: AMD decode support.

Personally, I am looking to upgrade to an Nvidia card.

@Kinvermark - Understood. Not having an AMD, are you running your AMD in Graphic Acceleration?

Kinvermark wrote on 9/23/2019, 10:21 PM

@Grazie

Still on Vegas 16, so that means just standard OpenCL acceleration. I will look at upgrading to V17 sometime in the new year after I do a "hardware refresh." I am dreaming of Threadripper 3's and RTX's :)

fr0sty wrote on 9/23/2019, 10:29 PM

"FWIW, another competing NLE is having a heck of a time getting this to work. "

Why I'm REALLY regretting my Radeon 7 purchase. It's amazingly fast at what it does right, but there is so much it either does wrong or simply cannot do at all because apparently Nvidia hired all the good driver programmers for GPU drivers. Neat Video couldn't get it working for a while, Vegas is still struggling with it, as you say, other NLE's are as well... Nvidia is king for a reason.

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)