Participant

R3D proxies show a gamma shift when attached to the original R3D clip. Happens only in Premiere 26+

Forum|Forum|8 days ago
September 21, 2026
4 replies
37 views

R3D proxies show a gamma shift when attached to the original R3D clip. The same proxy file looks correct when imported as a standalone clip. The issue occurs in Premiere Pro 26.0.2 and 26.5.1, even with Color Management disabled, while Premiere Pro 2025 displays the same R3D and proxy correctly.

Steps to reproduce:

Import an R3D clip into Premiere Pro.
Create or import a proxy that visually matches the R3D source when viewed as a standalone clip. I tested proxies generated both in DaVinci Resolve and Media Encoder/Premiere Pro.
Compare the R3D and the proxy as separate clips: gamma/contrast match correctly.
Attach that same proxy file to the R3D using Proxy > Attach Proxies.
Enable Toggle Proxies.
The attached proxy now shows a visible gamma/contrast shift compared with the original R3D.
Detach/import the exact same proxy as a normal standalone clip and it displays correctly again.

Additional information:

Reproduced in Premiere Pro 26.0.2 and 26.5.1.
The same R3D and proxy combination works correctly in Premiere Pro 2025.
The issue still occurs with Color Management disabled.
The proxy file itself does not appear to be the problem, since it matches correctly when viewed independently.
The behavior suggests that Premiere Pro 26.x is applying a different interpretation or processing path to the proxy once it is attached to an R3D master clip.
The issue is reproducible with proxies generated by different applications, so it does not appear to be encoder-specific.

KatieToo

Community Manager

Hi @alexnight

Thanks for stopping by the Premiere forums! We could use some system specs to try and match during a reproduction. I do see you mention v26.0.2 and v26.5.1 as sharing this issue with the gamma shift.

Operating System: Specify Windows or macOS, along with the version.
Mac Chip (Mac Only): Please let us know what M-series chip you have. If Intel please include GPU.
GPU and Driver (Windows only): Please let us know your video card and driver version. We recommend updating to the most recent version; for NVIDIA users, we strongly recommend the Studio version of the driver.

It could also be helpful to know if you have a LUT applied to the R3D file, and is the proxy generated with this LUT baked in? Sounds like you might not, but need to check as it’s possible Premiere is applying the LUT a 2nd time to the proxy if the Master R3D file it is attached to has the LUT applied.

Would you be willing to send us a sample of your R3D clip and a proxy that’s having this issue happen, so we can take a better look? I can send you our private Dropbox upload link, if so.

Hope to help!
Katie

A

alexnightAuthor

Participant

Hi Katie,

Thanks for looking into this. Here are my system details:

Operating System: macOS 15.7.9
Mac Chip: Apple M3 Max
Premiere Pro: reproduced in both 26.0.2 and 26.5.1

There is no LUT involved in my test. The R3D is being viewed in its log state, and the proxy is also generated as log with no LUT baked in. I also reproduced the issue with Color Management disabled. So I confirm there are no LUT issues involved with this.

Sample files have been sent.

Thanks,
Alex

KatieToo

Community Manager

@alexnight Oh wow, yes I see exactly what you’re talking about. I was also able to recreate this issue as you say in v26.0.2, v26.5.1, and also did a quick check in our v27.0 latest Beta, all with the same result.

I’ll be putting together a report about this issue, and we will return here to update or ask anything further in the near future.

Appreciate your time and effort reporting on this issue (and for sending us those files to more easily recreate it) so thank you!
Katie

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.