Premiere Pro v25.1 - Proxy Color Management Randomly Fails

[Krismk]

I’ve encountered an issue in Premiere Pro v25.1 where the color management for proxy files is lost.

I’m working with footage from Sony FX3 cameras, which is correctly recognized as Sony S-Log3/S-Gamut3.Cine. After creating proxy files, every clip in my timeline initially has its color space properly recognized.

However, when I closed the app and reopened it the next day, I noticed that some random clips lost their color management while proxies were enabled. Disabling proxies restores proper color management for all clips, but this isn’t a viable solution.

The only workaround I’ve found is to re-add each clip from the bins to the timeline—an incredibly time-consuming and frustrating process.

I’ve tried clearing cache files, but the problem persists. The issue appears inconsistent while closing and repoening the project, different clips lose their color management each time (while proxies are enabled).

I eventually reverted to Premiere Pro v25.0, and so far, everything seems to be working correctly again.

Attaching a video showcasing what I was facing.
Will continue working on 25.0 for now ...

Specs

• Asus TUF Gaming X570-Plus

• AMD Ryzen 7 3700X

• HyperX Fury 32GB DDR4-3200MHz

• ASUS TUF Gaming GeForce RTX 3060 OC Edition 12GB

• Windows 11 on a Samsung 970 Evo Plus 500GB

• Projects and media files imported via Media Browser and located on a Samsung 970 Evo Plus 1 TB

• Cache/Peak files located on their own separate ssd drive

• Premiere v.25.0

[Rach McIntire]

Hi @Krismk , 

Thanks for the message. Welcome to the forums.  Out of curiosity, were you using adjustment layers?  I'm glad 25.0 is working for you so you're able to move forward.

[Krismk]

No, nothing at all. I'm currently in the process of reviewing my footage, so it's too early to include anything in my timeline besides the clips. You can see that in the video I attached to my post.

That said, I'm working on version 25.0 of the same project with the same proxies and no changes, and everything is running smoothly without any issues.

It seems to me like the problem lies with version 25.1.