@AOM_Management more info is needed. What GPU, drivers up to date, etc...

Thank you !!!! for fixing the 'auto resize plugin chain" thing.

Update on accessing files via Explorer: I see that you fixed a bug whereby it would try to rename a file when clicking (once) on it. Here's the other issue: whenever I access a folder of files via Explorer, it often freezes If I haven't used this in, say, 10 minutes, or if I even click over to Project Media tab and then back into Expl Window, and I try again, nothing happens. If I close the Expl window (with the X ) and ALT-1, it comes right back. However, upon clicking on a folder, it takes sometimes up to a full minute for the contents of that folder to appear, and the application is not usable until then. Sometimes it comes back in less than 10 seconds, but compared with older versions of Vegas, this is new and I've never witnessed this big lag in populating the Expl window.

Previous version was rather stable. This version frezze in a couple of minutes after I start adding film clips or pictures. Not doing anything special. Never get a chance to try out new features.

Anyone having any issues over the last 2 days?

I've had no issues with the update until 2days ago, everything seems really slow. Laggy preview window, laggy rendering, and sometimes rendering just stops. No error, or not responding message, it just stops.

Yesterday, after editing I hit render. It stopped at 33%. Had to open task manager to close program. Re open, hit render, it stopped at 3%. Same thing again. I reopen, hit render and it did it, but half the speed it usually does.

Another edit this morning, I hit render, it stopped at 65%. I reopen, hit render, it did it but at half speed.

Another edit this evening.. im still looking at the render screen as I type. Its at half speed. Average fps 9.55.

Info on top of my head:

Vegas Latest update

Ryzen 9 5900x 12core

Rtx 3070 8gb (latest studio driver)

64gb 3200mhz

Sabrent rocket 4.0 m.2 (OS and Vegas)

Window 10

Project file on Samsung External USB SSD

3x video tracks (a7iii, a6600, a6600 all 4k cine4 footage)

1 audio track (tx660 mp3)

Rendering into 1440p

30 minute film, usually this would be rendered in 20 minutes. Currently rendering duration 1hr 13mins.

No changes have been made to my project or render settings, and was all fine until 2days ago. Sounds like hardware issues but all my drives appear to be fine from benchmarking. Vegas is the only software I'm having issues with. Very baffled.

Other than that, being a user since 14, i'm loving the update and look forward to more colour grading functionality and science. Would be good to see some more camera LUT's such as S-Gamut3 Cine / Cine 4 > rec709.

Previous version was rather stable. This version frezze in a couple of minutes after I start adding film clips or pictures. Not doing anything special. Never get a chance to try out new features.

Might have found the fix. Removed the GPU optimization. Steady after that.

@HelgeK, best to start your own post and provide the information from HERE in your post.

My computer specs are in my signature. I work with MOV 10bit UHD 4K 4:2:2 and I've noticed no change in performance between the previous VP20 build and the current one.

@HelgeK Looks like an issue between your AMD video driver and your monitor. If you also updated the graphics driver lately, that could be the cause. I've had good success with v22.11.2 with a 6900xt but many folks here are sticking with the older v22.5.1 for better compatibility with 3rd-party plugins.

Crosspost, see https://www.vegascreativesoftware.info/us/forum/vegas-20-freezes-when-undoing-a-melda-plug-in--139751/

Thanks for reporting this. Please make a new thread, you can copy and paste the above post in it... this enables us to easily keep track of your issue and respond directly to it without it getting buried under a bunch of other posts. We'll do what we can to help you get that sorted, and if we cannot, we'll notify the development team of the issue so they can work on whatever they can on their end (it may also require some intervention from the developers of your plugin).

@HelgeK Looks like an issue between your AMD video driver and your monitor. If you also updated the graphics driver lately, that could be the cause. I've had good success with v22.11.2 with a 6900xt but many folks here are sticking with the older v22.5.1 for better compatibility with 3rd-party plugins.

I started to use the "Pro version". Supposed to be tested with leading editors. Right now its the version called 22.Q4.

@HelgeK Looks like an issue between your AMD video driver and your monitor. If you also updated the graphics driver lately, that could be the cause. I've had good success with v22.11.2 with a 6900xt but many folks here are sticking with the older v22.5.1 for better compatibility with 3rd-party plugins.

I started to use the "Pro version". Supposed to be tested with leading editors. Right now its the version called 22.Q4.

@HelgeK I didn't get any lockups with 22q4 but got screen jitter with Vegas so I removed it with DDU and reinstalled 22.11.2.

Thanks for reporting this. Please make a new thread, you can copy and paste the above post in it... this enables us to easily keep track of your issue and respond directly to it without it getting buried under a bunch of other posts. We'll do what we can to help you get that sorted, and if we cannot, we'll notify the development team of the issue so they can work on whatever they can on their end (it may also require some intervention from the developers of your plugin).

I discovered so extreme many bugs in V20.326 that I updated the post.

https://www.vegascreativesoftware.info/us/forum/lot-s-of-bugs-vegas-20-freezes-when-undoing-melda-plug-in-and-more--139751/

Hello. I'm having this issue while rendering Apple ProRes format videos with the current VEGAS Pro Build; specifically ProRes 444 profiles (444 and 444 XQ with and without alphas). Check the screenshot bellow. All ProRes 444 videos I render include a black bar on the right and bottom edges of the frame. All other ProRes profiles such as ProRes 422 render fine. Are you experiencing this issue as well? Try it out yourself, render a small test video using a solid color from Media Generator that is not black and try to import that rendered ProRes 444 file again and you'll see it has this black borders (easier to check if you set your Video Preview window to a white background or even easier if you check with the Event Pan/Crop window). I have this issue since VEGAS Pro 19...

Question, I've been a Vegas user since Sonic Foundry. took a few years from editing. Recently upgrade to Vegas 20 with the newsiest software upgrade. I am having very unstable performance. any time I attempt to use the Pro Titler, Vegas crashes. I'm working on a project with pics from Iphones (1.6mb) which essentially cause the software to slow to a crawl. Using pics from my camera (.6mb), the software is not effected. Mu question, Is my computer specs up to par? Video card? RAM?

System Information report written at: 02/18/23 09:56:33
System Name: COOPER
[System Summary]

Item    Value    
OS Name    Microsoft Windows 10 Enterprise    
Version    10.0.19045 Build 19045    
Other OS Description     Not Available    
OS Manufacturer    Microsoft Corporation    
System Name    COOPER    
System Manufacturer    System manufacturer    
System Model    System Product Name    
System Type    x64-based PC    
System SKU    SKU    
Processor    AMD Ryzen 5 2600 Six-Core Processor, 3400 Mhz, 6 Core(s), 12 Logical Processor(s)    
BIOS Version/Date    American Megatrends Inc. 4801, 4/25/2019    
SMBIOS Version    3.1    
Embedded Controller Version    255.255    
BIOS Mode    UEFI    
BaseBoard Manufacturer    ASUSTeK COMPUTER INC.    
BaseBoard Product    PRIME A320M-K    
BaseBoard Version    Rev X.0x    
Platform Role    Desktop    
Secure Boot State    Off    
PCR7 Configuration    Binding Not Possible    
Windows Directory    C:\WINDOWS    
System Directory    C:\WINDOWS\system32    
Boot Device    \Device\HarddiskVolume2    
Locale    United States    
Hardware Abstraction Layer    Version = "10.0.19041.2251"    
User Name    COOPER\Owner    
Time Zone    Pacific Standard Time    
Installed Physical Memory (RAM)    16.0 GB    
Total Physical Memory    15.9 GB    
Available Physical Memory    11.4 GB    
Total Virtual Memory    63.9 GB    
Available Virtual Memory    58.4 GB    
Page File Space    48.0 GB    
Page File    C:\pagefile.sys    
Kernel DMA Protection    Off    
Virtualization-based security    Not enabled    
Device Encryption Support    Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable    
Hyper-V - VM Monitor Mode Extensions    Yes    
Hyper-V - Second Level Address Translation Extensions    Yes    
Hyper-V - Virtualization Enabled in Firmware    No    
Hyper-V - Data Execution Protection    Yes    

@Thomas-Cooper
Here are the specifications for Vegas pro 20
https://www.vegascreativesoftware.com/us/specifications/#productMenu

If you don't need to zoom around or move around in your images, you should resize them to the size of your project settings in an image editor beforehand.

It's better if you open a new thread - you can be better helped with problems there. This is just a thread for feedback, and your problem would get lost in the abundance.
You only need to copy past your text into the new thread.

Hello !

The zoom jumping glitch is back with video stabilisation. It has appeared in previous Vegas versions as well, but it got fixed... until now. People who used the "video stabilisation" FX on a footage were getting glitched (zoom jumping) results. I am using the latest version of Vegas Pro (build 326) and after rendering, those clips that got video stabilisation applied are acting strange, for 1-2 frames they zoom in then out. Mostly at the start of the clips, sometimes randomly in the middle. In the preview it does not show up, only after render. If I remove the zoom, black borders will show up which is equally bad. I relied on this feature, but now I can't deliver my work because most of the video stabilised footage is glitched. Hoping for a hotfix, thanks for your help

Specs:
- Windows 10 22H2
- Asus ROG STRIX X570-E
- Ryzen 3700X + RTX 3080 + 32GB DDR4 RAM
- Vegas 20.0 (build 326)

@Ricsardka As @walter-i. said a few posts back - "It's better if you open a new thread - you can be better helped with problems there. This is just a thread for feedback, and your problem would get lost in the abundance.
You only need to copy past your text into the new thread."

@Ricsardka As @walter-i. said a few posts back - "It's better if you open a new thread - you can be better helped with problems there. This is just a thread for feedback, and your problem would get lost in the abundance.
You only need to copy past your text into the new thread."

Thank you, I opened a separate thread, just wanted leave the feedback here as well so you know about the glitch

I have installed Vegas Pro 20 and it appears to be working well. My question is, New Blue Titler Pro 7 included is installed as part of the package, accessible through Media Generators. However, there is also a Standalone version on my Desktop. I did not intentionally install it there and I wonder why it exists? What is the benefit or otherwise of two versions of the same application. And would anybody agree that it is a more complicated and unwieldy beast than the NB 7 Express.

NB Titler Pro has for many years included both plugin and standalone versions. If you don't want the SAL version on your desktop, just delete the icon.

In Vegas Pro, TP7 should be available as either an FX plugin or as a media generator event.

@des-condon Titler Pro 7 can be used three different ways:

1. Standalone - this will let you just open the interface and design. It can also be exported as a PNG Sequence MOV file but VEGAS would require Quicktime to be installed and turned back on in order to read those files. It would be better to save as a .nbtitle file, add Titler Pro to the timeline, and then open that .nbtitle file.

2. As a Media Generator. It can be added to a track above your video and used the same as any other titler to show the title over your video.

3. As an Effect. Titler Pro can actually be added as an effect to a single video event as well. This will show the title over the video but will not use another track. It will automatically be the same length as the video event and the biggest advantage is that you should be able to preview the video background within Titler Pro.

I've been a Vegas user for almost 20 years now since version 4. It's arguably the best software on the planet to use to edit videos. (when it works) However, version 20 has been atrocious for me. Slow speeds, having to scour the web for fixes to things that should never be broken. All other versions of this software work on my computer - but this version is frustrating beyond belief at every turn. Slow and choppy preview, unpredictable problems, crashes during rendering, wasting SO much time on things that shouldn't have to be thought about.

Searching for hours online shouldn't be a normal thing for any program. Tweaking random settings buried in menus which don't make any logical sense to the layperson without a degree in computing. The basics should just work. My edits aren't that complicated. (basic cuts, text, color grading) I have a maxed out machine that has always worked on all other previous versions and was meticulously researched to work with Vegas. No updates made to have that change other than video card drivers are always updated to the latest (but again, all other versions work just not 20.)

Yes I can use version 19 without problems - but why should I be forced to do so? This is extremely disappointing, frustrating and draining of real resources in my small business. Yes this is a rant, and I've seen others crap on rants, but again no other professional program I have has been this un-intuitive in finding answers. I could understand if some very complex features didn't work and needed to be ironed out - but these are the basics.

I would list my machine or RAM preview settings or any of those things - but the frustrating part is I've tried all those things. V19 works perfectly, V20 does not work reliably at all. Preview is very choppy and rendering goes to about 30% and stops (no matter what codec, I've tried all the normal Vegas hacks after being a user for so many years.)

I only humbly ask this - before adding any more features - please work on stability first and foremost. Real people are loosing tens of thousands of dollars when these simplest of basics aren't addressed. It's not an unreasonable request. I really do appreciate the program and the years I've been able to use it. I can't fathom the work it takes to put this all together and make it work. It just desperately needs basic stability as a priority - especially on a machine that has worked for years (almost) flawlessly.