Discovered a bug on Vegas 21 Pro 315

pg_edits wrote on 12/14/2024, 10:17 AM

Hi, I have been using Vegas 16 since 2018 with all types of files and never had an issue. Earlier this year I upgraded to Pro 21 and I haven't been able to use it at all.

My machine:

CPU: Intel i9 9900KF
GPU: NVIDIA 3090TI on 566.36 driver
RAM: 32gb
Windows 11 with the latest updates
All disks are NVME.

When I import a 4K MOV file taken with my Z6 II, Vegas 21 starts to act up. The preview is unusable even in draft mode. It never plays the frames and I only hear the audio. It lasts only a few seconds and then it crashes. Sometimes it even crashes the entire machine and I need to manually reboot.

If I import the same exact file in Vegas 16 that's installed on the same machine, I can edit just fine and use the preview in max quality if I want to.

I tried a solution suggested in another post to rename the so4compoundplug folder but that didn't help either because Vegas 21 won't launch after renaming the folder.

While trying many things, I got a notification from Windows asking if I was having audio issues? That seemed odd so I decided to try change the output method in the Windows settings. And Vegas 21 decided to start working properly!

So here is the thing, I am using the audio output from my 4K monitor using the NVIDIA High Definition Audio option that goes out from the card via the Display Port. This works fine with Vegas 16 btw.... Once I changed the option to the on-board Realtek output, Vegas 21 started working smoothly.

Let me know if you want more details so you replicate the issue.

Comments

pg_edits wrote on 12/14/2024, 10:31 AM

A follow up... Now Vegas 21 is stable and it won't crash but my preview goes black after a few seconds... Sometimes it comes back for 1s and then goes black again.

This is the media info:

General
  Name: DSC_2651.MOV
  Folder: E:\DCIM\100NZ6_2
  Type: AVC
  Size: 1.37 GB (1,400,896,962 bytes)
  Created: Friday, December 13, 2024, 8:01:22 PM
  Modified: Friday, December 13, 2024, 8:01:22 PM
  Accessed: Friday, December 13, 2024, 8:01:22 PM
  Attributes: Archive

Streams
  Video: 00:00:37.037, 59.940 fps progressive, 3840x2160x32, AVC
  Audio: 00:00:37.037, 48,000 Hz, Stereo, PCM

Summary
  [TCFM]: 6

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 21.0 (Build 315)
  Company: MAGIX Computer Products Intl. Co.

pg_edits wrote on 12/14/2024, 3:02 PM

When it's now "somewhat" usable... it's still a pain. If I add a new clip to the timeline, I need to save the project, quit Vegas and re-open it again. Just then, I will be able to see the preview working. But if I make any changes to the clip, I need to do the same again. Really annoying...

RogerS wrote on 12/14/2024, 6:06 PM

Don't mess with program folders. You appear to have enabled the older so4compound by checking legacy AVC decoding in preferences file io. It doesn't work with that unchecked?

Personally I stayed with build 208 of 21 as the most mature but it depends on media.

jetdv wrote on 12/15/2024, 7:18 AM

Why not test version 22?

pg_edits wrote on 12/15/2024, 9:45 AM

Don't mess with program folders. You appear to have enabled the older so4compound by checking legacy AVC decoding in preferences file io. It doesn't work with that unchecked?

Personally I stayed with build 208 of 21 as the most mature but it depends on media.


 

These are my options. I do have the quicktime old plugin enabled tho...

Gid wrote on 12/15/2024, 10:47 AM

When adding a .mov (ProRes not AVC) Vegas uses the so4compound ..?

Vegas Pro 18 - 22
Vegas Pro/Post 19
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
NewBlue TotalFX
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, & an Acer 24" monitor.

At the moment my filming is done with a Samsung Galaxy S23 Ultra 5G & a GoPro Hero11 Black

I've been a Joiner/Carpenter for 40yrs, apprentice trained time served, I don't have an apprentice of my own so to share my knowledge I put videos on YouTube.

YouTube videos - https://www.youtube.com/c/Gidjoiner

 

RogerS wrote on 12/16/2024, 1:52 AM

To return to the OP's issue (not ProRes!) I'm confused.

Why is 4K AVC opening with so4compound? What build of 21 is this? 208 or 315?

pg_edits wrote on 12/16/2024, 11:20 AM

To return to the OP's issue (not ProRes!) I'm confused.

Why is 4K AVC opening with so4compound? What build of 21 is this? 208 or 315?

It’s 315.

RogerS wrote on 12/16/2024, 5:56 PM

Thanks for clarifying!

Does checking enable legacy AVC decoding in preferences/ file io improve the playback? I'm curious what plugin that brings up if you could check media properties for that, too (does it go back to compoundplug?)

I am assuming that any changes you made to the VEGAS files or internal settings were restored to defaults (reinstall and reset VEGAS).

Is it possible to provide a sample of the media for testing? I have two NVIDIA systems here. Google Drive, Dropbox, etc. would all be fine for this. I can also see if this was fixed in 22 as it really refined the changes made in 21.