Not hard to blame AMD when it isn't just Vegas that lacks support. At least in Vegas, everything but decode works just fine, and in some cases still better than Nvidia. It isn't just Vegas in the NLE world that is struggling to get decode support working properly, either, so until I see otherwise, my finger still points at AMD.

@Damian

Here, the extension works fine.

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

For me not, I always get this error mesage after applying the extension.

For me not, I always get this error mesage after applying the extension.

The "Adjust Length of Slow Motion Plugin" extension is working OK for me in VP17 build 321 (English version).

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.

Same for me.

i7 7700k

gtx 1080 16gb ram

For me not, I always get this error mesage after applying the extension.

I will write you a personal message. :)

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.

Same for me.

i7 7700k

gtx 1080 16gb ram

@LongIslanderrr Maybe see if the temporary fix for this in the above thread works for your system also, i.e. setting Dynamic Ram preview to zero.

Vegas 17 uses a ton of "committed ram" Here's an example of what happens when I import 60 gigs of random videos taken over the last 4 years into v16 vs v17. Additionally; neither program succeeds with the mass import. They both crash. but v16 comes closer. 😂

@LongIslanderrr Theres definitely a memory/resource issue with VP17, VP16 is better, they need to fix this.

Did the temporary fix work?

@Damian

After the update my VP17 returned to German language (in the next days I will change back to English); but slowmotion and adjusting length (in "Extras" -> "Erweiterungen") is ok, no error

Also running a AMD card here. Love to hear from the Nvidia users regarding the updated NVENC support.

On another note, I noticed the claim of improved loading times on large projects. And I am working on a number of very large and complex projects. At first I thought it was my imagination, but no. 321 most definitely opens these projects much faster. Every second helps when working on multiple massive productions.

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

@Grazie Same for many of my NewBlueFX plugins. And rebooting didn't solve the problem. Even worse, when trying to put in the serial numbers for them (I have them all duly recorded), the serial #s are not recognized. As I have relied on many of those plugins for a very long time, this is a pretty big setback. Glad I still have VP16 still installed.

Going to the NB site where my purchases should be available for re-download, etc., many of them are not there. Yes, I know some came with various Vegas upgrades. Can anyone tell me where those might be found? NB doesn't support (at least as far as serial #s go) those plugs that came with various Vegas upgrades.

@Len Kaufman see if https://www.newbluefx.com/download-dash/ helps. Check Legacy to see NLE/Host options.

Also running a AMD card here. Love to hear from the Nvidia users regarding the updated NVENC support.

On another note, I noticed the claim of improved loading times on large projects. And I am working on a number of very large and complex projects. At first I thought it was my imagination, but no. 321 most definitely opens these projects much faster. Every second helps when working on multiple massive productions.

 

It isn't just that, it no longer freezes when zooming in/out, scrolling, or undoing... anything that makes Vegas have to redraw the thumbs on the timeline used to make VP17 stock release choke in complex projects that had hundreds of thumbs. It works as it should now.

Les options de menu pour ouvrir un fichier dans FXhome HitFilm ont été consolidées pour une présentation plus compréhensible. Dans VP 17 Edit version 321, aucun menu n'apparaît dans l'onglet "Outils"; Ceci est pourtant le cas dans VP16. Pourquoi? Est-ce un oubli? Les personnes possédant une licence de Hitfilm, ne vont pas, à mon avis, migrer vers Vegas Post. Un tel oubli me semble malsain, et pas très conforme dans l'esprit de partenariat.

Quelqu'un pourrait-il me répondre?

Merci

Tout est OK avec la version 13.1 d'Hitfilm

JCD😬

Was this patch supposed to fix HDR media not displaying in preview window/corrupted renders with HDR media, while on a dual graphics card system? (2x GTX 1080s in SLI)? The only way to fix this is to disable hardware acceleration all together, enable NDVEC decoding, and it shows fine - but I lose out on much power for encoding.

I'm still having the problem from these bug report pages:

https://www.vegascreativesoftware.info/us/forum/vp17-rendering-hlg-4k-uhd-file-w-hardware-acc-sli-corrupts-video--116803/

https://www.vegascreativesoftware.info/us/forum/vp17-hdr-video-won-t-show-in-preview-with-sli-unless-hw-acc-disabled--116659/

One more odd thing, NVidia Geforce Experience sees the preview window as a game and starts recording it as such, with shadowplay, even before this update.

Great update for me at least, fixing the issue with the Boris plugins seems to also have improved their overall stability in vegas.

AMD card user here too. I have little issues with VP16 and my aging RX480.

VP17 initial release 4K benchmark project played OK on the timeline. (Sys1 signature)
VP17 (321) timeline plays up to the 'fps' region & stops. Control now lost & closure via taskmanager required.
Reboot, open VP17 & reload project. Place cursor in the 'fps' region yields a red preview window.

Have little faith in new version.  How do I revert to the origonal release.

Edit: Restored sys image to get back to origonal version. Checked V16&17 were OK. Made notes on Prefs settings. Updated to 321 & back to problems. Noted that video had changed from nvidia to intel. Changed to nVidia and stability returns. Is this the new nornal when updating? Not met this before.

UI issue for Hamburger Menu, 4k Panel, items are not visible

Is the zoom restored in the trimmer window, on the build 321? Thanks

@oliverSpain see https://www.vegascreativesoftware.info/us/forum/update-for-vp17-any-further-information--117234/?page=1#ca730380 and the following comments. See also this one.