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
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
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).
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.
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.
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.
Not new codecs for exportation video ! I'm sad !
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
Windows 10 pro, AMD 480RX 8 gig, 4K screen on HDMI #1 No Screen capture. Generic Box in capture still black.
No AMD decode, thought that was the priority?
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
Wow! Must be a whole buncha' folks downloading this upgrade, as the download is taking forever on my very fast connection.
Yes, I agree. The download is slower than normal. We hope that it is worth the wait. Exciting!
Memory issues haven’t been addressed ... The system is low on memory etc, identical project renders ok on VP16, bombs out on VP17 ...
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.
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?
Memory issues haven’t been addressed ... The system is low on memory etc, identical project renders ok on VP16, bombs out on VP17 ...
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.
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.
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?
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.
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.
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?
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?
Here, the extension works fine.
The slow motion effect has improved, but rendering to see the end result now takes an eternity.
Unexpected behaviour. Not all my 3rd Party Licences Settings were immediately recognised. Updating required a PC Reboot to reactivate my BORIS MOCHAPRO19 License.
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?
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 :)
"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.