@Barton-Santello there is a problem with one of your plugins, which you've failed to list what you have.

So can you tell us if a previous build started with the same plugins?

@Paul-O I don't use audio plugins so can not comment on anything concerning them. But what i would suggest is that you start your own post with the issues, and include specifically named plugins that do not work. In order for Vegas Pro to improve, specific information is needed to get a possible fix.

@Paul-O I don't use audio plugins so can not comment on anything concerning them. But what i would suggest is that you start your own post with the issues, and include specifically named plugins that do not work. In order for Vegas Pro to improve, specific information is needed to get a possible fix.

@Reyfox Thanks for replying, I'm a first time poster and thought I had started a new post 😀 I'll have another look and see how to do that!

@Paul-O no worries. Also, I suggest in your User Profile>My Signature, that you add your computer specs like mine listed below. A lot of times, this information can be helpful. Most of us have that information listed in our Signatures.

@Barton-Santello there is a problem with one of your plugins, which you've failed to list what you have.

So can you tell us if a previous build started with the same plugins?

@Paul-O I don't use audio plugins so can not comment on anything concerning them. But what i would suggest is that you start your own post with the issues, and include specifically named plugins that do not work. In order for Vegas Pro to improve, specific information is needed to get a possible fix.

I will submit a support ticket, but I find it ironic that the v248 release notes say specifically: "Incompatible Video plugins will no longer cause Vegas to crash on startup" and that's exactly the problem I'm having. Also, whatever plugin is causing the start-up crash, was not an issue on the previous build of VegasPro.

Let us know what happens with the support ticket and if they offer a solution.

Anyone else having problems with scene detection in this release? Was working fine in previous release but now goes through the process to 100% using default settings (slowly), but no keyframes are shown and program becomes unresponsive. Build 248, Deep learning models 22.2.

did you fix the problem with 239 LUT FX which was eating RAM?

Hello,

Because it simply doesn't work at the moment, can you please remove the "Set Default Track Properties" in VP22 Suite, Build 248 as it confuses me and sends the wrong message. I see the options there to use the feature but it doesn't work, if you see a button in any software giving you the option to do something that it doesn't actually do basic logic tells me that perhaps at least, it should be removed until it actually works as a tool within that software.

I don't want to go into the Applications hidden settings and preferences making changes on such things as the default track properties when it actually has a menu on the front end that should handle such matters. Is it possible to at least remove this option within the software until you can get it to work. I've mentioned this issue previously.

I need to be able to quickly create customized tracks. Thanks in advance for an actual fix on this, my VP Build and system specs are in the Signature area.

Kind Regards,

@Blaque  ... would you please describe in what way "Set Default Track Properties" doesn't work. In what way does it send the wrong message?

@Blaque I've just set the default track properties (height, volume, compositing mode) in VP22 and they all work. I've no reason to suspect that the other properties don't work either. How precisely are you setting the default properties? You have to change the properties of a track, then make sure that the track is selected, right-click on the track header, select the properties with the check boxes, then select OK. Any new tracks of the same type will inherit the properties from the selected track that you've set as default. The properties that you've set will be carried over to any new project that you create.
I repeat, I've tested and it works.

@Blaque I've just set the default track properties (height, volume, compositing mode) in VP22 and they all work. I've no reason to suspect that the other properties don't work either. How precisely are you setting the default properties? You have to change the properties of a track, then make sure that the track is selected, right-click on the track header, select the properties with the check boxes, then select OK. Any new tracks of the same type will inherit the properties from the selected track that you've set as default. The properties that you've set will be carried over to any new project that you create.
I repeat, I've tested and it works.

@Jack S Yeah, I've been using the default track settings for a long time and know how it works. I'm happy to hear the feature within the software works for you.

Again, thanks in advance for an actual fix on this that enables this to work for all who are on the current build within VP22. Not working in VP 21 Post Build 315 either on my system.

Kind Regards,

Could you share a screenshot or video of what's not working specifically? I have a similar laptop I can test on (also NVIDIA RTX 4060 with 22.248.)

After installed build 248, I cannot download more than one video from Stock Media in Hub. It just don't start download. After first video is downloaded, I need to logout/login to Hub again or restart program to download next video I need for project. This happens only in Windows 11 (Home). Tried the same on Windows 10 (Pro) - no problems with downloading. I remember that after previous one/two updates there wasn't such problem and I have downloaded many videos per session.