Discussion | ICC Profile Has Been Removed From Some Images When Processed

I’m working with artwork files (both Tiffs and Jpegs), to upscale and make suitable for printing at larger sizes. Since upgrading to Photo AI v4, some of my images are coming out with a significant colour shift and the profile is showing as “Untagged RGB”, when they went in as Adobe RGB or Profoto.

On these files, I’ve only been running a 3-4x upscale process through Standard or Hi-fidelity… no other processes involved.

Some images seem to struggle more than others… On some, I’ve had the issue, resaved the original as a jpeg and then it’s worked, but on others it hasn’t. With some, I’ve copied and pasted the image into an entirely new file and it’s worked (but then again on others, it hasn’t).

I’m currently running an Intel Mac and I know it’s scraping through on the min. requirements but it makes processing these upscales a lengthy process and makes rerunning any failed ones quite a headache.

When I’ve raised the issue, I’ve been rebuffed because my original had been edited (which I still don’t understand what the issue is). As I can’t send out full, high res files of the artwork (not my © to distribute), I cropped one down to make it unuseable, re-ran the process and it still came out untagged and with the colour shift, so I sent both that cropped down original and the resulting file, but was told they couldn’t look at it due to the original being edited.

Just wanted to see if this resonated with anyone, as I was told they’d had no other reports of this happening.


I replied to your email but yes, in order to do an investigation, we would need the original file. Some files cannot be shared, we understand that, but you can test to find a random shot file or random scanned file and replicate this, and we could continue the troubleshooting, for us to pinpoint what is happening!

An original would be It would an out of camera file or original scanned file. This is because the file you sent was already edited in Adobe and we need to compare the results to one that was not. It could be a simple change to do in how it’s saved from Adobe. You mention that it does not occur on all your files, and that Saving the file to JPEG again fixes the issue for the problematic ones. This confirms something is happening the first time you save them and we can test more one we have one of those problematic originals. It could also be an issue on our side and if more users here post that they can replicate and sent us the original, we can gather information from other users - and go from there and troubleshoot with them and add a development team ticket.

1 Like