Severe visual glitch (pink/purple block covering the bottom half of the frame) during playback of Canon C50 Open Gate .CRM files.

I cant believe we are being ignored for this.

Can we get an actual update on this issue? It is a huge problem that Premiere can’t handle Canon’s raw files. This should be handled with a fire alarm all hands on deck code red seriousness. I’m shocked to see no real updates on a major problem that's been around for quite some time.

As a researcher, I use the Canon EOS C50 as my primary camera for my PhD research in Artistic Studies – Film and Image at the University of Coimbra. The critical bug generating artifacts and glitches during the decoding of Cinema RAW Light (.CRM) files has made my native Premiere workflow completely unviable for months.

I have been following this thread since last year, and the lack of resolution is alarming. In April 2026, I attended NAB Show in the US and spoke in person with a senior engineer at the Adobe booth. He confirmed what many of us already suspected: there is no ETA whatsoever for a fix.

During the same event, in conversations with Canon’s technical representatives, I got the strong impression that the issue has an architectural root cause: Adobe apparently opts for a proprietary decoding pipeline for .CRM files rather than using the native SDK provided by the manufacturer. Not coincidentally, DaVinci Resolve — which uses Canon’s native engine — processes the exact same files without any issues.

The continuity of my PhD research depends on a functional tool. I am being forced to pause my research, purchase a DaVinci Resolve license, and seriously compromise my academic timeline in order to learn an entirely new editing platform — all as a consequence of Adobe’s architectural decisions, not an insurmountable technical limitation.

I am directing this question to the Product Managers and Engineers responsible for this area: what is the real barrier to adopting Canon’s native SDK on macOS? A camera format of this significance cannot continue to be left broken across multiple consecutive software releases.

When will this issue be fixed?

After 16 years of adobe products I am switching to Resolve. There’s no excuse to not be able to fix an error for this long. No updates, higher price. I’ve cancelled all my adobe products. Ridiculous and disappointing. Hey but at least they have ai clip extender!! GIVE ME A BREAK 

Hi,

since December25 this is a issue, still not resolved. What resolved though is that I decided to quit on adobe and switch to Davinci Resolve, at this point im not blaming adobe, im blaming myself I didn't do this way earlier! cheers!

just saw that the recent update didn’t fix this issue. 

is there any news or comment from adobe on when is this going to get fixed? it’s messing the raw workflow really hard. I’m shooting with the R6 III

Did the April 16 update fix this?

Any update on this Adobe? It’s been almost half a year since the camera was released.

I’m a bit disappointed that the issue we pointed out last December was delayed. It seems that the thread or forum we were discussing about this issue was completely removed from your end.

If we don’t have a fix for this problem, it’s probably best to address it now rather than waiting.