Skip to main content
Participating Frequently
May 3, 2021
Answered

Strange color shift in MXF files in version 18

  • May 3, 2021
  • 6 replies
  • 5902 views

Hello, all - please see the attached images. The "correct" one is from version 17.6. When I opened the AE file in version 18, suddenly the color shift in my MXF source file is bizarre (note the CG elements all look the same).  In the new version of AE (as well as Premiere) all the MXF files (from a Canon C300 ii: 12-bit, 444 color MXF) are bizarrely purple and gray. I've been working flawlessly with these files for months in AE and Premiere; the color shift is happening only with the update. I will try to go back to 17.6 but would greatly prefer not to. Anyone have an idea? Did the new version shift the color space? No setting is currently active in the Project Settings -> Color -> Working Space. Working on a 2020 imac with plenty of RAM. Help - this is making me nuts! I can't finish this film!

This topic has been closed for replies.
Correct answer ArminKenedi

We have not anymore the Problem in AE 18.02 !

6 replies

nishu_kush
Community Manager
Community Manager
May 11, 2021

Hi all,

 

The issue has been fixed in the latest release of After Effects and Premiere Pro. Please update your apps and see if it helps.

Let us know how it goes.

 

Thanks,

Nishu

ArminKenedi
ArminKenediCorrect answer
Inspiring
May 12, 2021

We have not anymore the Problem in AE 18.02 !

Participating Frequently
May 10, 2021

I have figured out the issue, although not the cause. For some reason, the newest version of Premiere and After Effects (version 18) is inverting a color channel on MXF 12-bit 444 files.  Please see the attached stills.  The first is what it looks like in Premiere / After Effects.  Skin tone is blue.  The second still has the "Invert" effect applied, with the "In Phase Chrominance" option selected.  Poof - back to normal.  It's an easy enough workaround to just drop that effect on your footage, but still needs to be fixed / addressed.  Clearly a bug but at least a simple solution.

ArminKenedi
Inspiring
May 10, 2021

Thanks for this solution. However, The issue needs to be fixed by Adobe to ensure 100% color unanimity and safe handling of AE and Pr.

nishu_kush
Community Manager
Community Manager
May 7, 2021

Hi all,

 

Could you share a sample file with us to test? If you don't want it to be public, feel free to DM a download link.

 

Thanks,

Nishu

Participating Frequently
May 7, 2021

Hello, Nishu - how do I DM a link to you?

ArminKenedi
Inspiring
May 6, 2021

We have the same Problem in UFA Film prodution with our MXF videos. We cant move to AE 21 (18)!

 

Participating Frequently
May 10, 2021

Armin, please see my above post - simple work around to this issue.  Hope it helps, although still annoying.

ArminKenedi
Inspiring
May 10, 2021

Thank you.

nishu_kush
Community Manager
Community Manager
May 3, 2021

Hi claytonb69055831,

 

Sorry for your issue. Please share the following details:

  1. Have you noticed it with multiple MXF files or this particular one?
  2. What are your system specifications (CPU, GPU, RAM, OS)?
  3. Looks like it could be related to the GPU. Is your GPU diver updated?

Let us know, we're here to help.

 

Thanks,
Nishu

Participating Frequently
May 4, 2021

Hi, Nishu - thanks for the reply.  

1. Yes, it is with every MXF file, no exceptions.

2. iMac (Retina 5K 27-inch) 3.6 GHz 10-Core Intel Core i9, 72 GB memory. AMD Radeon Pro 5700 XT 16 GB. Big Sur 11.2.3

3. Not sure about GPU driver update.  This seems directly related to the Adobe upgrades.  I upgraded both After Effects and Premiere, and both applications showed identical symptoms.  I reverted back to the previous version in After Effects (haven't done so with Premiere) and the problem disappeared.  To me it feels like some problematic way the Adobe software is working with the MXF files - perhaps a color space issue.  Remember these are 12-bit 444 files. Thanks for any assistance!

Participating Frequently
May 3, 2021

I reverted back to version 17.6 and the problem has disappeared. Any thoughts?