I had an issue like that for some ProRes resolutions a short while ago. I fixed it by selecting all the ProRes clips in Project Media and forcing their clip properties to Full-Range instead of Undefined. I don't think that property can be changed, however, if the project is legacy 8bit limited... but it's editable with all the other project choices.

Is it ProRes XQ4444 or a different variety?

let me run a quick test and see if both end up doing the same thing

Wish I had a fix for you. I'd go back to v22 if your deadline is close. Not a good time to beta test. If you do have some time, try dropping in some of that prores footage into a new project to see if that has the same issue.

Is it ProRes XQ4444 or a different variety?

Alright so, I didn't end up learning much and it all makes very little sense.. When I render as pro res within vegas 23 using the exact preset i made that was ported from 22, its absolutely fine. When I render the EXACT same clip with the exact same preset in 22 and put it into 23, it doesn't like it at all. Better yet it doesn't matter which if I'm using 4444 or 422, exact same result when it's a pro res file rendered/encoded anywhere but Vegas 23. I'm so confused. I screen recorded to try and show y'all what I mean. I'd still like to fix this even if it works when rendered within Vegas 23 because ALL of my assets/overlays that I use for client work were made in 22 and none of them work. I really want to use 23 because of these new features, particularly the new keyframe curve editor within the timeline but I can't be remaking ALL of my assets haha. i appreciate any input or ideas.

Wish I had a fix for you. I'd go back to v22 if your deadline is close. Not a good time to beta test. If you do have some time, try dropping in some of that prores footage into a new project to see if that has the same issue.

I've still got both versions here so I'm finishing up the client project on 22 but I'm hoping that this is something I'm able to fix and not something only Magix can fix.😥 Attached a video above demonstrating how the same footage acts in each version.

I had an issue like that for some ProRes resolutions a short while ago. I fixed it by selecting all the ProRes clips in Project Media and forcing their clip properties to Full-Range instead of Undefined. I don't think that property can be changed, however, if the project is legacy 8bit limited... but it's editable with all the other project choices.

Appreciate the response. I spent a good chunk of today trying this (if im understanding correctly), various combinations and settings to see if there was something I was missing and nothing worked. In individual event media settings, color management settings are completely greyed out and in project settings I can only change things if I have my project set to 32bit full range, and even then the color is still very very wrong, no matter which combo I used. I don't know if I've misunderstood what you mean.

Could you share a sample file for testing? I saw an issue before with XQ media but this is strange! For now I'd suggest finishing your work in 22.

Could you share a sample file for testing? I saw an issue before with XQ media but this is strange! For now I'd suggest finishing your work in 22.

Sure, let me throw you one of these files. I'm really hoping this is on my end lmao.

ProRes 4444 alpha values ​​also have the same issue. Exposure and color information are displayed incorrectly. Vegas Pro 22 on the left, Vegas Pro 23 on the right.

 

ProRes 4444 alpha values ​​also have the same issue. Exposure and color information are displayed incorrectly. Vegas Pro 22 on the left, Vegas Pro 23 on the right.

When you render as ProRes 4444 within 23 using the exact preset same preset, is it fine for you? I attached a video above showing this.

Please upload files to a sharing site, not this forum.