With me on laptop Windows without programs loaded takes 3,7 GB memory


After loading Vpro 18 in 15 seconds the use is 4,2 GB


After loading VPro 19 in 14 seconds the use is 4,5 GB

Both the RAM and delayed startup problems are related to the Transition, Video FX and Media Generator windows. If those are closed on startup, you will not see the problems.

Both the RAM and delayed startup problems are related to the Transition, Video FX and Media Generator windows.

Seems logic to me👍😑

I noticed the Creating Windows problem as well.

I have the same windows and setup as with VP18. I also have in VP18 HOS window. In VP19 I don't.

Yeah - same startup slowness here... I own Vegas 18 Pro and testing Vegas 19 Pro. The "Creating Windows" step is almost instantaneous in Vegas 18, but takes more than a minute with Vegas 19 on the same machine.
If I remember correctly - there was a similar issue with Vegas Movie Studio 16 which got fixed in 17. I hope this gets fixed faster than that now ;)

Both the RAM and delayed startup problems are related to the Transition, Video FX and Media Generator windows. If those are closed on startup, you will not see the problems.

Thanks for the info Derek.

It may not be something you can answer but it would be good to know if this is likely to be a "hotfix" release. ie. Coming soon. Reason being it is kind of impractical to have those windows closed on startup in my environment. (btw I am aware we can save Window Layouts, I already have many). :-)

So if it looks like a long wait, I will roll back.

nb. No complaints here, I understand that these things sometimes slip through the net (I do QA testing for a number of companies). It would just be nice to have a bit of info if possible.

Thank you. P.

We do not really have a way of doing hot fixes at the moment. Beta testing for update 2 will begin in another week or so.

We do not really have a way of doing hot fixes at the moment. Beta testing for update 2 will begin in another week or so.

Thanks for the info Derek, much appreciated.

We are aware of a major delay in the "Creating Windows" step of the startup process. The more FX and other plugins you have on your system that VEGAS can use, the longer this step is. We do have a fix for this that will hopefully be available for update 2.

I will ask someone to investigate the RAM usage increase. This is likely due to the new components associated with VEGAS Hub.

@VEGASDerek

Here, in addition to the initialization delay in Creating Window, there is also a delay followed by an error in View/Window Layouts. It doesn't always happen, but when it does, the only way to correct it is to choose the Default Layout first and only later choose the desired Layout. See my screen recording below showing the problem.

I don't know if this is happening to other users, but if this is confirmed by you, it would be good to fix this in the next update.

@joelsonforte.br Thanks for the report. We will look into this. It will not be fixed for the next update but it looks like we are not properly resetting the project media window upon exiting those layouts. Those layouts (add video transitions...etc) were initially intended to be used with only Movie Studio in simple edit mode. We will look to clean all that up. Thank you.

@VEGASDerek thanks for the response.

I understand there are priorities right now and I appreciate your effort and attention. My goal is just to inform you to help improve VEGAS.

I want to take this opportunity and report a bug I found in the Adjustment Track feature. See my screen recording below that Composite Envelope does not work when GPU is disabled.

I would also like to give a suggestion for a feature that would use the technology used in the new Slow Motion Real Time plugin to convert the frame rate of videos. This feature would replace the Smart Resample which, when enabled, most often creates ghost images when trying to interpolate frames and which when disabled ends up causing repeated frames. See my screen recording below to better understand.

It would be very useful for those who work with videos with different frame rates and need to standardize the frame rate. Best of all, the result will be seen in real time without the need for rendering or dynamic RAM.

I don't know if this will be possible, or if it's a good idea, but in any case, this is the tip.

Thank you for your attention and for the work you have done!