MOV / Apple ProRes Color problem

Anvil wrote on 12/8/2025, 6:01 AM

Hello, I work a lot with transparent MOV files.
With Vegas Pro 22 (Build 250), I never had any issues with the color of the files I was using.

However, after a recent NVIDIA update, I couldn’t render anymore, so I had to switch to Vegas Pro 23. At first, the software crashed immediately when opening a MOV file, even with the QuickTime plugin installed. I enabled HEVC and AVC decoding, and now it opens correctly, but the color of my MOV files is desaturated, making them unusable.

At this point, I don’t know what to do: on one side, I can’t render with Vegas Pro 22 anymore, and on the other side, Vegas Pro 23 gives me washed-out colors on export…


Vegas pro 22 and the good coloring :


Vegas pro 23 and the desaturated color :



Here is the information about my file:
Fichier MOV (.mov)
Format : ProRes 4444

Media information :
  Stream format: MPEG-4
  Video stream #1
    Video format: ProRes
    Resolution: 1080 x 1920 px
    Aspect ratio: 0.562
    Frame rate: 29.970 fps
    Scan type: Progressive
    Bit rate mode: Variable
    Bit rate: 47550102 bps

Here is the information about my computer :

Système d'exploitation
  Édition Windows : Windows 11.0 (64-bit)
  Version : 10.00.26200
  Langage : French
  Locale système : French
  Locale utilisateur : French

CPU
  Classe : Intel(R) Core(TM) Ultra 7 265KF
  Identificateur : GenuineIntel
  Nombre de processeurs : 20
  MMX disponible : Oui
  SSE disponible : Oui
  SSE2 disponible : Oui
  SSE3 disponible : Oui
  SSSE3 disponible : Oui
  SSE4.1 disponible : Oui
  SSE4.2 disponible : Oui

GPU
Nvidia RTX 5070

Here is the information about my vegas pro 22 and 23 :
Vegas pro 22 (Build 250)
Vegas pro 23 (Build 302)

Extra information about vegas pro 23 settings :

and about the mov settings :



I really need help because this is an important project for me, and I’m stuck ! :( thank you so much

Comments

3POINT wrote on 12/8/2025, 6:08 AM

Known ProRes issues of Vegaspro23. Temporary solution is to to render to image sequences (.PNG) for transparency.

RogerS wrote on 12/8/2025, 6:14 AM

Why not install an NVIDIA driver that still works with 22? I'm on the latest studio driver (581.57) myself.

For 23 you are reporting a gamma issue with ProRes 4444 that I think we've seen before and hopefully which will be fixed soon. ProRes doesn't use Quicktime so that doesn't need to be checked. In general you shouldn't check legacy HEVC/experimental HEVC in 23.

For now I'd suggest working in 22 or using a different ProRes variant like 422 (or an alternative like MagicYUV) in 23.

Last changed by RogerS on 12/9/2025, 8:55 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 5070 (12GB) with 581.57 studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with 581.57 studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250
VEGAS Pro 23.302

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Anvil wrote on 12/8/2025, 7:25 AM

Why not install an NVIDIA driver that still works with 22? I'm on the latest studio driver myself.

For 23 you are reporting a gamma issue with ProRes 4444 that I think we've seen before and hopefully which will be fixed soon. ProRes doesn't use Quicktime so that doesn't need to be checked. In general you shouldn't check legacy HEVC/experimental HEVC in 23.

For now I'd suggest working in 22 or using a different ProRes variant like 422 (or an alternative like MagicYUV) in 23.

I'll do that !
I've downgraded my Nvidia card and I'll stay on the 22 until the 23 is more complete in that regard! Thank you for your message.
My rendering on 22 is now working again