Vegas 23 ProRes files over exposed (PLEASE HELP)

chell wrote on 9/9/2025, 2:25 PM

Been testing out Vegas 23 and opened up the client project I've been working on and while scrubbing through I've realised that every single pro res file and seemingly every transparent element on the timeline has issues. Is this a color space thing? I've tried everything. It was totally fine before but every single composite is super over exposed and orange. Any ideas for a fix so I don't need to roll back? I got a deadline. Really appreciate it.

Β 

Β 

Vegas 22:

Vegas 23:

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

Comments

RogerS wrote on 9/9/2025, 7:11 PM

Is it ProRes XQ4444 or a different variety?

Howard-Vigorita wrote on 9/9/2025, 7:29 PM

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.

chell wrote on 9/9/2025, 7:32 PM

Is it ProRes XQ4444 or a different variety?

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

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

Logan5 wrote on 9/9/2025, 7:45 PM

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.

chell wrote on 9/9/2025, 7:59 PM

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.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

chell wrote on 9/9/2025, 8:01 PM

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.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

chell wrote on 9/9/2025, 8:04 PM

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.

Last changed by chell on 9/9/2025, 8:05 PM, changed a total of 1 times.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

RogerS wrote on 9/9/2025, 8:08 PM

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.

chell wrote on 9/9/2025, 8:16 PM

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.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

yoo-changyun wrote on 9/9/2025, 8:16 PM

Β 

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.

chell wrote on 9/9/2025, 8:19 PM

Β 

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.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

RogerS wrote on 9/9/2025, 8:20 PM

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

chell wrote on 9/9/2025, 8:25 PM

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

my bad, i uploaded a few different files in a folder here!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

yoo-changyun wrote on 9/9/2025, 8:38 PM

이 λ°˜μ†‘μ΄ μ•„λ‹Œ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

제 λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

I also come out as overexposed

chell wrote on 9/9/2025, 8:41 PM

이 λ°˜μ†‘μ΄ μ•„λ‹Œ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

제 λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

I also come out as overexposed

Does it come out normal in 22?

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

yoo-changyun wrote on 9/9/2025, 8:47 PM

이 λ°˜μ§μ΄λŠ” 것이 μ•„λ‹ˆλΌ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

In 23, it appears as overexposure.

22 μ–΄λ””μ—μ„œ?

There is no problem at 22, the problem occurs at 23

Β 

yoo-changyun wrote on 9/9/2025, 8:50 PM

이 λ°˜μ§μ΄λŠ” 것이 μ•„λ‹ˆλΌ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

λ‚΄κ°€ λ„ˆλœλ„ˆλœν•˜λ‹€

22 μ–΄λ””μ—μ„œ?

And another problem is The Look LUT in Vegas Pro does not work when you add an external LUT. Vegas’s built-in LUT is applied, but applying an external LUT makes no difference. LUTs that worked fine in Vegas Pro 22 no longer apply in Vegas Pro 23.

Could you please test it for me?

chell wrote on 9/9/2025, 8:51 PM

이 λ°˜μ§μ΄λŠ” 것이 μ•„λ‹ˆλΌ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

λ‚΄κ°€ λ„ˆλœλ„ˆλœν•˜λ‹€

22 μ–΄λ””μ—μ„œ?

There is no problem at 22, the problem occurs at 23

Β 

Thank you for testing it. Interesting.. i really wonder what's causing it. I could be wrong but perhaps its not a client-side issue.. however, fingers crossed there's a setting somewhere that can fix this lol

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

chell wrote on 9/9/2025, 8:53 PM

이 λ°˜μ§μ΄λŠ” 것이 μ•„λ‹ˆλΌ 곡유 μ‚¬μ΄νŠΈμ— νŒŒμΌμ„ μ—…λ‘œλ“œν•΄ μ£Όμ„Έμš”.

λ°”λ‘œμž…λ‹ˆλ‹€. μ—¬κΈ° 폴더에 μ—¬λŸ¬ νŒŒμΌμ„ μ—…λ‘œλ“œν–ˆμŠ΅λ‹ˆλ‹€!

https://drive.google.com/drive/folders/1rXy6dBJD71OztRPUIxCX5OllRmSIHcjS?usp=sharing

λ‚΄κ°€ λ„ˆλœλ„ˆλœν•˜λ‹€

22 μ–΄λ””μ—μ„œ?

And another problem is The Look LUT in Vegas Pro does not work when you add an external LUT. Vegas’s built-in LUT is applied, but applying an external LUT makes no difference. LUTs that worked fine in Vegas Pro 22 no longer apply in Vegas Pro 23.

Could you please test it for me?

Oh! I actually already had this issue earlier today when I was playing around with 23 but I wasn't using any external LUTs for the client project anyway so I gave up with fixing it. I can take another look tomorrow when I am back on my computer and report back!

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

RogerS wrote on 9/9/2025, 8:57 PM

I don't think there are any settings that can be changed, maybe color space handling in internal preferences. I'll check when I get back to a computer.

chell wrote on 9/9/2025, 8:59 PM

I don't think there are any settings that can be changed, maybe color space handling in internal preferences. I'll check when I get back to a computer.

thank you Roger! I played around with internal preferences earlier. I hope you have more luck than i did!

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

Howard-Vigorita wrote on 9/9/2025, 9:32 PM

Looks better exposed in vp22 on my laptop...

chell wrote on 9/9/2025, 9:50 PM

Looks better exposed in vp22 on my laptop...

Yeah this looks about the same as mine. When i render the same footage with exactly the same settings in 22 and 23 and put it in a VP23 timeline, the 22 render looks like this. Overexposed and the depth of the color is just completely lost. Thanks for trying it out.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

yoo-changyun wrote on 9/9/2025, 9:52 PM

λ…ΈνŠΈλΆμ—μ„œλŠ” vp22둜 같이 λ³΄μ΄λŠ” 게 더 λ‚˜μ€ λ“―...

λ„€, 제 μ˜μƒκ³Ό 거의 λΉ„μŠ·ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€. 22와 23μ—μ„œ μΌκ΄€λœ μ„€μ •μœΌλ‘œ λ™μΌν•œ μ˜μƒμ„ μ „μ†‘ν•΄μ„œ VP23 νƒ€μž„λΌμΈμ— μƒˆλΌμ™€ 22λŠ” λ‹€μŒκ³Ό κ°™μŠ΅λ‹ˆλ‹€. μ™ΈλΆ€μ˜ μž…μž₯μ—μ„œλŠ” μƒ‰μƒμ˜ 관점이 μ™„μ „νžˆ λλ‚˜μ•Ό ν•©λ‹ˆλ‹€. μ΄μš©ν•΄μ£Όμ…”μ„œ κ°μ‚¬ν•©λ‹ˆλ‹€.

This is definitely a bug in Vegas Pro 23. I hope it gets fixed quickly.