Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Why is iOS Photos auto enhance different from MacOS?

Fzang

Fzang

macrumors 65816
Original poster
Did either of them get an update in one of the recent betas? I find that MacOS Photos does a vastly better job, while iOS adds significantly more contrast in many cases.

Seems weird that they would be different. I thought the code would be cross platform.
 
Erm, why would you think so?! Mac OS and iOS aren't exactly copy paste in everything is it?! They're based on the same kernel but are developed by separate teams with separate project timeline and feature goals. Also a desktop editor and a mobile editor don't generally tend to have the everything laid out the same way because of usability concerns.
 
  • Like
Reactions: M. Gustave
akash.nu said:
No, I understand what you mean. I'm just saying that desktop and mobile softwares don't tend to yield the same reason because of the aforesaid reasons.
Click to expand...
They should apply the same algorithm to both for consistency. Unless they're two separate apps, which they are not.
 
  • Like
Reactions: midkay
DaPizzaMan said:
They should apply the same algorithm to both for consistency. Unless they're two separate apps, which they are not.
Click to expand...
Definitely. The algorithm should be consistent.

I think they actually used to use the same algorithm, but on iOS it changed drastically in iOS 10. They added this 'brilliance' function and now the auto-enhance tends to crank that and make things all super high-contrast and over-saturated. I'm guessing they haven't yet brought this new algorithm to Mac OS and that's why there's a discrepancy.

I really loved the old iOS 9 auto-enhance algorithm, it was spot-on 90% of the time. Now I never even touch it in iOS 10 - the result always comes out horribly fake-looking. I manually adjust everything now. Hope they can resolve this in iOS 11.
 
midkay said:
Definitely. The algorithm should be consistent.

I think they actually used to use the same algorithm, but on iOS it changed drastically in iOS 10. They added this 'brilliance' function and now the auto-enhance tends to crank that and make things all super high-contrast and over-saturated. I'm guessing they haven't yet brought this new algorithm to Mac OS and that's why there's a discrepancy.

I really loved the old iOS 9 auto-enhance algorithm, it was spot-on 90% of the time. Now I never even touch it in iOS 10 - the result always comes out horribly fake-looking. I manually adjust everything now. Hope they can resolve this in iOS 11.
Click to expand...
This is why they should start writing their own apps in the same language (Swift) and just update once to apply to all OS. Excuse my ignorance if it is not that easy, but for a company so big there should not be a discrepancy between the same app on two of their OS.
 
DaPizzaMan said:
This is why they should start writing their own apps in the same language (Swift) and just update once to apply to all OS. Excuse my ignorance if it is not that easy, but for a company so big there should not be a discrepancy between the same app on two of their OS.
Click to expand...

Yes it is not that easy and just because a company is big, technical complications don't automatically become small. Plus SWIFT is nowhere close to as strong as objective C, so your solution is not sustainable.
 
Nice shot by the way, macOS shot in my opinion is better
[doublepost=1486479010][/doublepost]
akash.nu said:
Also a desktop editor and a mobile editor don't generally tend to have the everything laid out the same way because of usability concerns.
Click to expand...
Not too sure what you mean in regards to this post
A one tap auto enhance has nothing to do with usability
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back