Okay well now I get something even weirder

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 302)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 23.0\FileIO Plug-Ins\mxcompoundplug\APPLEPRORES.dll
   Fault Address:       0x00007FFFE225BDF6
   Fault Offset:        0x000000000002BDF6

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Process Version:     Version 23.0 (Build 302)
   Process Description: VEGAS Pro
   Process Image Date:  2025-09-26 (Fri Sep 26) 23:42:20

I'm definitely very confused here

Now, I tried using a recording I did around two weeks ago, seemingly IDENTICAL in terms of codec, only difference is the video's width, aswell as this difference I found with ffprobe on both
Encoder: Lavf61.1.100
Encoder: Lavf61.7.100

This older recording somehow.. works?

One that works uses mxcompoundplug.dll, and the one that crashes, as you can see above, tries to use appleprores.dll (in the same folder as mxcompoundplug)

This is confusing me more and more with how very weird and inconsistent it is...
Someone named Luigiplier said it outright doesn't work at all for them
So it definitely seems unstable in some way

Color was a big issue for me with prores files, and that seems to have been fixed - however, to second and third some of the folks above. As @Weegeepie said, transparency no longer works.

Clip 1: I've loaded up another project of mine and demonstrated how it looks rendered in 22, then showed the lack of transparency within the timeline on 23.

Clip 2: Here I drag a transparent composit I'd made for another project onto the timeline to test the color and placed a checkered background to test transparency. The colors are perfectly fine now (which is a brilliant start, thank you).

BONUS BUG:

This is a really strange one.. I often use reverse on my animations, etc - and as I've loaded up one of my timelines, I've noticed that reversal doesn't just reverse the clip - but it also flips the event vertically? I haven't got around to testing it more but this has never happened before.

Clip:

Overall, I'm glad colours are fixed but transparency is definitely an issue now. However, i'm really happy that you listened to our feedback and worked so quickly on a patch. I can't use 23 as of right now because I require transparency for my work, but I'm looking forward to the next patch. I hope my clips help somehow!

Additional info:
In the eventuality that you guys are testing with standard, non transparent MOV, here are OBS settings that get you Transparent Prores 4444 files, which I assume is going to be the common setup for most users here:

Color format was somehow wrong here, I normally have it to BGRA, issue obviously persists though

For ProRes 4444 please check that 'Alpha Channel' is set correctly in the event Properties

@chell As a workaround if you manually set the transparency (right-click on properties and change to straight (matted) does it work? Also setting event opacity to 99% seems to make transparency work (which must be a bug).

That reverse/upside down bug is bizarre. Thanks for flagging it!

@VEGASFlorian By default the older version sees the media as straight/matted alpha which yields a proper result. In 23 it's none.

We will look into this.

We will look into this.

And also the others that produced by mxcompoundplug:

• HEVC-HDR10.mp4 rendered from VEGAS, the plug decodes it as HEVC but no identifying as Rec.2100-PQ: HDR Video...
• ProRes-HDR10.mov rendered from VEGAS, as mentioned earlier totally no identification, the plug decodes it as AVC.

Both can be read correctly with legacy plugs.
But as you @VEGASFlorian said in another post, legacies will not be continued. So I'd suggest to abolish them from the tab and concentrate qualifying the mxcompoundplug and solve those issues in the next beta release.

It seems the separate controls of ACESv1.3 under Space and IDT is again a new challenge to VEGAS.

I've reported the problem of lag and overall slowdowns in large projects many times. Moving tracks on the timeline can be very delayed. CGP starts to freeze and lag significantly. One forum member suggested that this could be due to the processor, which Vegas isn't compatible with. There's no improvement in versions 21, 22, and now 23. I should also add that when I colorize using tools like Color Corrector in the VideoFX tab, everything runs smoothly.

I thought they had a brand new engine now? Powered by DirectX 12 or something along those lines? Shouldnt it be much better with large projects?
I couldn't get to test because.. well... I cant even use my Prores 4444 videos to give it a go

I don't see any improvement. I only work on large projects, 30-60 minutes long. As long as the project lasts 6-8 minutes, everything works fine, but once it gets longer than 10 minutes, it's a disaster. Colorizing the project is a pain. In version 22, I did colorization through the Video FX tab, dragging effects onto clips, but that's probably not how it's supposed to work, is it?

I thought they had a brand new engine now? Powered by DirectX 12 or something along those lines? Shouldnt it be much better with large projects?
I couldn't get to test because.. well... I cant even use my Prores 4444 videos to give it a go

@Weegeepie What do you mean you can't use your ProRes 4444 videos? Are you using build 302 which fixes an issue with exposure? You may have to manually set transparency by right-clicking on the media. You might consider a reset as VEGAS should be using mxcompoundplug. If there's something non-standard about your ProRes please share a file for testing and let us know how you made it.

Yes it's a new engine and I see big throughput improvements with my NVIDIA hardware. Benchmarks in signature if you want to try it on your own system.

@RogerS Setting the transparency could work, however for my workflow it is just not feasible, I get like hundreds maybe a thousand recordings, and put all that together in under a week, manually setting the transparency is way too tedious

But it doesn't even matter here because I don't know why, now my newer recordings ...which use the exact same codec and everything, the only difference is the width of the video... causes it to instead use appleprores.dll, which crashes build 302, even with a reset of preferences

Here are the MOV files
https://weegeepie.com/veg/older_Project64_2025_09_28_16_52_29.mov
https://weegeepie.com/veg/newer_Project64_2025_10_02_01_41_04.mov

the older one doesn't crash, the newer one does

https://weegeepie.com/veg/extra_Project64_2025_08_25_15_36_25.mov
actually there's actually this extra one, same settings, but it's transparent out of the box? overall very inconsistent and confusing

I shared my OBS config earlier in the thread, only difference is I use a BGRA color format, but everything still applies unfortunately

V23's Explorer seems not completely supporting UTF-8.
In my Favorit I have a folder named $oundFX which shows most time a doppelganger while in V22 no such phantom.

@Weegeepie Thanks for these, will take a look later.

I agree that it should read the alpha properly and I think that's a bug vs earlier versions. For now you should be able to highlight all of your ProRes media in project media, change the properties on one and have it apply to all at the same time.

I need to second what @Weegeepie is saying here. I just tested manually setting the alpha to unmatted and it's worked, however it's really not feasible for me to go through and do this manually every time.

@RogerS Do you know if there's any way to change the default, or, if there's a way to filter items in the project media bin by file type?

We will look to fix the auto-detect of the transparency fields in ProRes as quickly as possible.

still no support for rtx 5000 series?
h265 422 10bit doesn't show preview, rtx 5070ti

Nadal wsparcie hamulca dla serii RTX 5000?
H265 422 10-bitowy podglądu, RTX 5070TI

On my RTX 5080, rendering takes longer than on MainConcept AVC and AMD VCE. What's up?

Nadal wsparcie hamulca dla serii RTX 5000?
H265 422 10-bitowy podglądu, RTX 5070TI

On my RTX 5080, rendering takes longer than on MainConcept AVC and AMD VCE. What's up?

I'm getting much better performance from a 5080 and all my shoots are now hevc. Mostly concert projects typically 2 hrs or longer. Life has been good since I switched to 4k hevc 420 multicam after a decade of single-camera hd422.

NVidia 4:2:2 support coming...not quite ready yet. Watch for progress on this in the user insights section of the Hub pane.