Magenta cast in highlights on import.

[swenpaylay]

After installing iPad OS 13 last night and also deleting/reinstalling AP due to another issue, all my photos are importing with a strong magenta cast, especially in the highlights. This never happened before and I’m finding it difficult to remove from the highlights. Almost like pink coma is being added by AP. Ruins the photos, really. 

2018 iPP 1TB on iPad OS 13 (not beta)

Fuji RAF files from an XT3.

[swenpaylay]

1 hour ago, swenpaylay said:

After installing iPad OS 13 last night and also deleting/reinstalling AP due to another issue, all my photos are importing with a strong magenta cast, especially in the highlights. This never happened before and I’m finding it difficult to remove from the highlights. Almost like pink coma is being added by AP. Ruins the photos, really. 

2018 iPP 1TB on iPad OS 13 (not beta)

Fuji RAF files from an XT3.

Screen shots of Camera Roll vs Affinity. Can confirm the files look fine in LR/PS. Was really hoping to use AP exclusively and fully divorce Adobe but this is a huge dealbreaker and I've been tinkering and reporting bugs all summer to no avail. The time lost equals or exceeds the money saved by cancelling Adobe. Very disappointing. Should have just left it as it was at 1.6. 

 

 

[DM1]

Hi @swenpaylay sorry to hear you are having issues. Hopefully mods will be able to help. 
If you want to upload a photo here I’d be happy to check and see if I get same issue.
Also have you tried turning off apply tone curve to raw images to see if that improves it. You can find it under Document menu / Assistant. Note that camera roll is only showing a low res jpg of your raw file. 

[Chris B]

Hey swenpaylay,

As DM1 suggested, we could really do with a copy of this raw file.

There is a bug logged with the developers were we are seeing a slightly magenta cast over blue areas and I wonder if this could be similar. We won't be able to tell for sure without a copy of the file.

It's strange that it seems to be happening all of a sudden though. 

[swenpaylay]

Thanks for the replies. I tried disabling the tone curve setting and it actually made the magenta cast worse. And in fact no adjusting of white balance even seems to affect the hue at all, even maxed out yellow temp/ green tint. i wonder if its a fuji RAF issue. I have been going back and forth between canon and fuji all summer and this is the first major project ive done on fuji in a while. 

[p_mac]

This is also an issue with the Sony a7r3 and Sony lenses.  
It is not an issue with CaptureOne as the camera and lens profiles are included.  
Has the camera profile been included in Affinity Photo yet for both iPad and Macs?

Edited September 30, 2019 by p_mac

[swenpaylay]

6 hours ago, p_mac said:

This is also an issue with the Sony a7r3 and Sony lenses.  
It is not an issue with CaptureOne as the camera and lens profiles are included.  
Has the camera profile been included in Affinity Photo yet for both iPad and Macs?

Yeah the Fuji XT3 profile has been in there for a while and I didn’t notice the color issue until recently. I sent devs a RAW so fingers crossed. I assume it’s a bug that occurs to the color profile on import. Hopefully there’s followup to this issue as it has totally stalled my workflow. 

[swenpaylay]

On 9/25/2019 at 12:15 PM, swenpaylay said:

After installing iPad OS 13 last night and also deleting/reinstalling AP due to another issue, all my photos are importing with a strong magenta cast, especially in the highlights. This never happened before and I’m finding it difficult to remove from the highlights. Almost like pink coma is being added by AP. Ruins the photos, really. 

2018 iPP 1TB on iPad OS 13 (not beta)

Fuji RAF files from an XT3.

Sad to report this issue is still present in ipad os 13.1.2 an AP 1.7.3

[p_mac]

I see that the Sony a7r3 is now included.  It wasn't the last time I looked.  My images have been looking somewhat better lately. 
It is my belief from also working on the Mac that this is more of a chromatic aberration issue as if I run the chromatic aberration filter the colour corrects. However one cannot run this filter in AP on the iPad even turning it on does nothing. Defringing doesn't work.  

[swenpaylay]

1 hour ago, p_mac said:

I see that the Sony a7r3 is now included.  It wasn't the last time I looked.  My images have been looking somewhat better lately. 
It is my belief from also working on the Mac that this is more of a chromatic aberration issue as if I run the chromatic aberration filter the colour corrects. However one cannot run this filter in AP on the iPad even turning it on does nothing. Defringing doesn't work.  

My images are very flat and no amount of color correction has any effect. They’re just washed out in magenta. Color temp sliders have no affect at all. As if it’s only importing a piece of the gamut and overwhelmingly so on magenta channels. Literally impossible to edit. 

[swenpaylay]

On 9/26/2019 at 3:11 AM, Chris B said:

Hey swenpaylay,

As DM1 suggested, we could really do with a copy of this raw file.

There is a bug logged with the developers were we are seeing a slightly magenta cast over blue areas and I wonder if this could be similar. We won't be able to tell for sure without a copy of the file.

It's strange that it seems to be happening all of a sudden though. 

So the issue here seems to be iOS has decided to save only the thumbnails locally on any of my ios devices. I think the cause of my import issue is that affinity can only ‘see’ the rendered jpeg. The strange thing is that it only happens with this one particular photo set im working on. Everything before and after is fine. The cause eludes me and I cant get ios to leave the files as they are. My theories are this particular set was loaded into lightroom mobile and it did something. I had also tried to sync via icloud photos, which I have since disabled. I think it may have been that. Finally, i also imported them via usb to my mac via the mac photos app because i was having a hard time uploading via icloud drive like usual and it just left me the previews. But again this problem exists only for this set of files and occurs on both my ipad and iphone. So my guess is somehow the cache of icloud photos thinks it has the raws soits only saving thumbnails regardless of device. Strange though that lightroom can open the raws no sweat. Im stumped.
 

Does anyone know how to fix this on ios? 

[p_mac]

Are you importing to Photos directly from your camera?

[swenpaylay]

13 minutes ago, p_mac said:

Are you importing to Photos directly from your camera?

That's a loaded question. But generally speaking, I save into the camera roll first from SD, cull, then pull into AP. 

I just spent two hours on the phone with an apple engineer to discuss the problem. They are bewildered and are following up. 

What seems to have happened is i imported to my mac via the photos app and it told my ipad not to keep originals. Somehow latent metadata in icloud is continuing to tell it do to do so, but only for this particular set of photos. The raw file is technically still in the background but has to be downloaded when the file opens, just like an 'optimized for storage' file would. Lightroom was able to still pull raws out of these messed up files but AP was not. I prefer AP and only downloaded LR as a temporary solution to what I thought was an AP bug (my bad..it's ios) 

I can successfully import to AP via the files app, where I have the RAFs stored in icloud drive. It pulls them in no problem. It's just that when I save the raws to my main camera roll, icloud photos or the photos mac app, is still telling my ipad to only show me the rendered jpegs. Hence I can't import them from the camera roll without this magenta issue or the multi-import crashing issue I reported in a different thread. 

AP devs might consider coding the imports such that AP searches for background raws for optimized photos. LR seems to have that ability. 

I generally don't import to mac via usb/photos or via icloud photos but at the time my icloud drive was bugged up and wouldn't upload raws. That was another issue that doesn't seem to exist anymore. 

The really strange thing is the photos app on mac continues to get my raws in the background as I import to ipad and it only gets jpegs, even though icloud photos, and any syncing settings that should connect the two libraries is disabled. The photos don't even appear in mac photos, just in the 'masters' folder accessed by right click > show package contents. 

So I think theres some latent metadata in icloud photos telling my ipad to prioritize the jpegs due to my usb import and/or temporary icloud photos enabling. 

Moral of the story: don't back up with USB/Photos or iCloud photos. Just pop the SD card into both machines separately. Annoying but the safest bet, per the Apple photos engineer. 

For now I'm attempting to save the files back to my ipad camera roll via itunes sync as suggested by Apple. 

 

 

 

 

 

[swenpaylay]

19 minutes ago, swenpaylay said:

That's a loaded question. But generally speaking, I save into the camera roll first from SD, cull, then pull into AP. 

I just spent two hours on the phone with an apple engineer to discuss the problem. They are bewildered and are following up. 

What seems to have happened is i imported to my mac via the photos app and it told my ipad not to keep originals. Somehow latent metadata in icloud is continuing to tell it do to do so, but only for this particular set of photos. The raw file is technically still in the background but has to be downloaded when the file opens, just like an 'optimized for storage' file would. Lightroom was able to still pull raws out of these messed up files but AP was not. I prefer AP and only downloaded LR as a temporary solution to what I thought was an AP bug (my bad..it's ios) 

I can successfully import to AP via the files app, where I have the RAFs stored in icloud drive. It pulls them in no problem. It's just that when I save the raws to my main camera roll, icloud photos or the photos mac app, is still telling my ipad to only show me the rendered jpegs. Hence I can't import them from the camera roll without this magenta issue or the multi-import crashing issue I reported in a different thread. 

AP devs might consider coding the imports such that AP searches for background raws for optimized photos. LR seems to have that ability. 

I generally don't import to mac via usb/photos or via icloud photos but at the time my icloud drive was bugged up and wouldn't upload raws. That was another issue that doesn't seem to exist anymore. 

The really strange thing is the photos app on mac continues to get my raws in the background as I import to ipad and it only gets jpegs, even though icloud photos, and any syncing settings that should connect the two libraries is disabled. The photos don't even appear in mac photos, just in the 'masters' folder accessed by right click > show package contents. 

So I think theres some latent metadata in icloud photos telling my ipad to prioritize the jpegs due to my usb import and/or temporary icloud photos enabling. 

Moral of the story: don't back up with USB/Photos or iCloud photos. Just pop the SD card into both machines separately. Annoying but the safest bet, per the Apple photos engineer. 

For now I'm attempting to save the files back to my ipad camera roll via itunes sync as suggested by Apple. 

 

 

 

 

 

One correction: Lightroom may only be importing the rendered jpeg and calling it a raw due to the error. Now that i pull the sliders it seems the photos lack dynamic range of a raw, and that the better color vs AP is due to the baked in color profiles. 

Also, using itunes to sync the photos back to the ipad doesn't work. Still only jpegs. 

The tech told me icloud auto clears its cache about every 30 days so maybe I'll just wait 'til then to try again. 

[Chris B]

Thank you for updating us, swenpaylay. I am quite surprised to be honest. 

[swenpaylay]

5 hours ago, Chris B said:

Thank you for updating us, swenpaylay. I am quite surprised to be honest. 

Yeah. Strange issue.  But heres another unfortunate on topic update: I’m still getting magenta in the highlights that can’t be corrected very easily, even now that I am able to pull in the raw files. CA and Defringing toggles dont help. Adjusting white balance does a little, as does split toning, but not 100% and not without losing good colors I ant to keep. Devs should certainly still consider this unsolved. 

[Chris B]

Well there is a bug logged with them that seems to affect other cameras too so I haven't considered this resolved yet. 

[swenpaylay]

Seven weeks have passed with no updates and no communication from devs even though I sent a multitude of crash files and raw photos for this and other issues. I yearn to use AP on my ipad but I simply cannot with these problems and my workflow has moved away from it as a result. 

[DM1]

4 hours ago, swenpaylay said:

Seven weeks have passed with no updates and no communication from devs

Actually it’s only 4 weeks since last update but this is surely the most negative aspect of dealing with Serif/Affinity. Bug reports appear to disappear into a vacuum. Updates are far and few between and, when an update is released, it’s often unclear which faults have actually been addressed.  Often it just states 'Performance and stability improvements'. Not very informative. 
Can't blame the forum mods for this but Serif,s developers could surely take a leaf from Luma Touch's approach to dealing with user issues.

[p_mac]

After reading this thread I needed to stop and say a bit.   To DM1, who I acknowledge really does contribute a great deal to this forum, I have a bit of problem with your comment 

On 11/4/2019 at 7:43 PM, DM1 said:

Can't blame the forum mods for this but Serif,s developers could surely take a leaf from Luma Touch's approach to dealing with user issues.

Luma Touch, which does look like an awesome product, has two products and one format, iOS.  To compare, serif has three products on macOS, iOS, and Windows is a stretch. It has also created a bridge that is not comparable in any of the other products that are constantly mentioned in this forum. 
We have all known how these devs work from the start, yes sometimes it does feel like we are all being ignored, but step back for a moment, take a breath and read some of the grievances and wants of people here. Really, is there not a point at which any of us would seem to turn off for a bit. Really!!!!
 

As for swenpaylay, I did some research into the Fuji and their problems.   There is all kinds of complaints with Adobe, and many different kinds of colour issues with Fuji cameras.  not only magenta but green, banding, etc.   
As I have said before, with my Sony a7rM3, I have a problem with chromatic aberration on the iPad mainly because it can’t be run like one can do with the Mac.  Yes if I run these images through Capture One, I can easily remove this and so I would expect LR.  They are a different kind of software.  

On 11/4/2019 at 3:31 PM, swenpaylay said:

Seven weeks have passed with no updates and no communication from devs even though I sent a multitude of crash files and raw photos for this and other issues. I yearn to use AP on my ipad but I simply cannot with these problems and my workflow has moved away from it as a result. 

The new Sony a7rM4 has issues because of image size and some Sony users recognize the issue when shooting in low light and colour casting.  Some have suggested that shooting in uncompressed format removes colour and noise issues, albeit doubling the size of the image.

So I suggest that this is an issue with all the camera makers each of which is trying to outdo the other.  

swenpaylay, you are an individual and therefore have the right and ability to do whatever you want to do, move on if you need to but please stop making these comments.  
For me anyway it is getting a bit tiring.

 

Edited November 6, 2019 by p_mac

[swenpaylay]

p_mac if you don’t like my commentary then don’t post in threads I create, or change the subject so its about your sony cameras.

My fuji files are totally fine in adobe and were fine in AP until recently. I do prefer APs rendering and the exported product better, which is why I’m here. I truly prefer the product..when it works...its been over 6 months since it did. Adobe has only been reliable. I turn around photos efficiently and clients are happy. Can’t say the same for AP anymore. The first 6 months of 2019 were a lot different. AP enticed me to move my workflow to iPad. Then it pushed me back to Adobe when it got broken. Turns out LR on iPad is great.
 

DM1 is correct...bug reports and files go into a blackhole. I sent devs half a dozen crash reports and some of my photo files with absolutely zero response. I took half a day of my time on several occasions over the summer to help fix the product and got nothing back...except a tearful emoji from a mod on my last post in the thread (thanks a lot Chris...glad you care.)

that attitude...your attitude is frustrating and enflames the tone of my feedback no doubt.

Sorry not sorry to be a full time pro photographer who processes thousands of photos monthly who desperately wants to use Serif’s product. It’s clear now AP is made for hobbyists and most participants in this forum are just that. The unfortunate reality is the Adobe is truly the only option for pros who want to use ipads. 

[p_mac]

8 hours ago, swenpaylay said:

It’s clear now AP is made for hobbyists and most participants in this forum are just that.

That's insulting considering that most of the notable photographs of the world were shot by hobbyists.  
You know the definition of a professional photographer is one that has sold one photograph.  
 

8 hours ago, swenpaylay said:

. I took half a day of my time on several occasions over the summer to help fix the product and got nothing back...except a tearful emoji from a mod on my last post in the thread (thanks a lot Chris...glad you care.)

that attitude...your attitude is frustrating and enflames the tone of my feedback no doubt.

Nice comment swenpaylay.  That will go a long way with the devs and mods. 

The attitude that is 'frustrating and enflames the tone of your feedback no doubt'; belong to you and you alone. 

Again you have choices and nobody has or will twist your arm to stay with software that is not working for you.  Surely as you are a successful professional photographer you can afford the cost of adobe.  

Not quite sure about you but I live in a democracy and can and will post wherever and whenever I read such insulting comments.  




 

[swenpaylay]

11 hours ago, p_mac said:

That's insulting considering that most of the notable photographs of the world were shot by hobbyists.  
You know the definition of a professional photographer is one that has sold one photograph.  
 

Nice comment swenpaylay.  That will go a long way with the devs and mods. 

The attitude that is 'frustrating and enflames the tone of your feedback no doubt'; belong to you and you alone. 

Again you have choices and nobody has or will twist your arm to stay with software that is not working for you.  Surely as you are a successful professional photographer you can afford the cost of adobe.  

Not quite sure about you but I live in a democracy and can and will post wherever and whenever I read such insulting comments.  




 

Touchy touchy. 

All I have to say is you get what you pay for and AP’s price point is definitely too good to be true. 
 

[Chris B]

Hi swenpaylay,

My reaction was out of my own sadness that your issue has not been resolved yet. The mods on the forum (as well as everyone else working for Serif) are here because we care about the software and its users. 

Sadly, (and I have said this numerous times) the mods, QA, tech support etc. have little influence on what the developers fix. 

I am sorry your bug still isn't resolved.

 

 

 

[DM1]

10 hours ago, Chris B said:

My reaction was out of my own sadness that your issue has not been resolved yet.

Hey Chris, don't feel too bad, you guys (Moderators here) do a great job and can't be expected to 'fix' bugs as well!.