Profile cover photo
Profile photo
Abdullah Tarawneh (trwnh)
ibn ibn ibn ibn...
ibn ibn ibn ibn...


Post has shared content
This is pretty cool, but how does the resulting website perform? Is it optimized? Is it easily understandable if you want to make a slight tweak, or do you need to rerun the entire computation from scratch based on a new picture? How would it implement animations?

Still a long way away from replacing frontend designers ;)

Twitter banner sizing

Twitter uses a 1500x500 image that is scaled responsively across its apps and website, in a semi-consistent way. However, Flamingo's banners are cropped. Is there a way to fix this, or is this an arcane API limitation?

Post has shared content
Apple vs Google on their color management launch with wide-gamut displays

Everyone's talking about display and color now, and that's fantastic

The mobile industry is stepping up big time this year by adding color management on both largest platforms.
In a turn of event that won't surprise most observers, Google is having a tougher start than Apple for multiple reasons:

Apple started from iPhones and iPads targeting at best sRGB.

But Google evolves in Android's ecosystem where super-vibrant displays have been on flagships since the Galaxy S first gen in 2010 when Android really took off in market share.

From the standpoint of habits and expectations
Apple's move was lower-risk.
Starting here, they mostly nailed the panel sRGB calibration. Then everything past that, in gamut and over time came as a progressive color enhancement.
Third-party apps adding support for wide-gamut, reworking first-party apps and home screen icons little by little. No breaking change, no regression, only improvements.

Compare that with Google Pixel 2's story

Historically most sold Android devices:
- have been stretching sRGB content to the AMOLED panel's native gamut, which is substantially more saturated than P3 and not exactly the same hues.
- run a gamma curve of 2.4 average - which you can observe when measuring using a constant-adaptive brightness test patterns. Darker response curve mechanically boost saturation
- on many Samsung devices - all AMOLEDs, extra mDNIe tuning boosts vibrancy even further. After a couple years they tweaked this boost with skin tone protection to solve an obvious red face issue.

Since even the Pixel 1 was doing the usual AMOLED color stretching, Google found itself in the opposite situation to Apple's.
No matter what, for a large portion of their customers, happily unaware of color management details, Google would remove colors by doing the right thing.
Not adding anything, just stealing these fascinating hues acting as visual antidepressant in these uncertain times.
Therefore, not an easy context.

And then, hardware things

- We might never know what happened to HTC's Pixel 2XL; what we got is an LG-built flagship with an LG POLED panel.

- Google made the call to include a circular polariser which may have come at the expense an increased color shifting if you compare to the LG V30.
With color shifting at the slightest angle, it's hard to get used to a change you might already perceive as regression.
Speculation: Circular polariser seemed most important to execs living in sunny California, a car-centric society. My bias as a subway rider in a Nordic capital would lead to a different choice.

- The non-XL Pixel seems okay tho, but everyone is focused on the more desirable flagship.

Also, factory calibration thing

- While according to early measurements the gamut of the Pixel 2 almost nails sRGB coverage¸ the Pixel 2 XL is not which leads to substantially muted colors (red & blue), wrong hue (red) compared to what they should be with a precise sRGB calibration.
Note : these measurements were done using the i1 Display Pro colorimeter, which is by default tuned for WLED LCDs spectrum. On AMOLED and without correction profile built using a spectrophotometer, the colorimeter might not "see" the same as your eyes (therefore: more research needed)

Still, I encourage you to look at Phonearena's unique database in the Color charts, gamut/accuracy section
Admirable work here over the years +PhoneArena

- Inconsistent EOTF (gamma curve) on the Pixel 2 XL, most notably identified as crushed shadows. The lower the brightness level the higher the shadow compression then clipping.
This is dark movies watchers nemesis, but also affect color rendition overall.
IPS' panels are not affected by any of that had: safe bet from Apple.

To give an historic context on this one: like LG with OLED, Samsung struggled with their AMOLED EOTF calibration just as well until the Galaxy S5.
With this generation, they stepped-up massively which allowed them to introduce a 2 cd/cm² low-brightness mode with alright deviation (pushed down further to 1 cd/cm² with the Note 4)
On the Pixel 2 XL, LG's EOTF performance is years behind. In terms of results including the visible (ignoring the much higher pixel density) This is reminiscent of Galaxy Nexus AMOLED (2011, October)
6 years, time flies.

And then, apps and ecosystem things

- Android OS and apps' assets have not been tuned to use the new wide gamut capabilities.
While Pixel 2's Oreo seemed to remove color, for most it didn't dazzle right away by showing off the lovable benefits of color management paired with wide-gamut displays.

Desirable things to have:
* Wide-gamut "real-life" camera viewfinder
* Wide-gamut photo and video capture
* Wide-gamut photo gallery, like Google photos.
* Tasteful blend of subtle colors, and wide-gamut vivid icons and wallpaper in the launcher
* A handful of major third-party apps full of wide-gamut content.
* Wide-gamut games.

Pixel 2 launched without any of that, which would have been totally fine if all previous Nexus and Pixels had been only sRGB.
The good thing: these bullet points will happen in the following months.

This was why Apple and Google had diametrically opposed stories launching color-management.

Oh yeah initially I wanted to write to say I'm trying to migrate my Sensormaster program used for display calibration to IDEA & Gradle from an old Eclipse project I didn't touch since 2015.
And Gradle and I are not good friends quite yet.

My apologies, I lost the plot a bit.

Post has shared content
And they named it Trigger Warning, which is the best thing I have heard in weeks.

Trigger Warning members meet once a month to shoot still targets and saucer-shaped pigeons. The 18 dues-paying members are all LGBTQ, many just learning about guns.

“I identified as a pacifist really through most of my life,” said McSpadden, 37, who has attended a self-defense seminar and now owns a 20-gauge shotgun.

Post has shared content

Post has shared content
FINALLY someone does a writeup of this. Got tired of dealing with this stuff in comments sections.
Since getting in touch with +Marques Brownlee after his explanation video on Pixel 2 XL color which contains various errors, he said he didn't have the time available for a talk, but that he could do emails.

Usually I prefer discussions with a more hands-on approach to teach color science applied to mobile due to the amount of complexity involved.

But eh why not!
Here is what I sent him, following a reaction style because this is about YouTube after all. I post this because I want to share the knowledge with you, my dear readers as well.

Video itself:

9:38 "For whatever reason Google decided on Oreo on the Pixel 2 XL they would show just sRGB"

The main reason is that most Android phones nowadays show arbitrary colors, which is a pain for content creators as you demonstrate at 11:36 in the same video.
A problem that is not existing on iOS since iPhone 7, since it implement color management for everything, with sRGB being the default for un-tagged content. Exactly like Oreo on a supported device.
- Untagged is anything to be displayed that doesn't specify "Hey my RGB values are encoded within AdobeRGB colorspace"
Google have been a bit lazy with color since the beginning of Android, and since Apple stepped up they decided to finally address the problem using the industry's solution: color management.

Pixel 2 is also color managed to sRGB default. It doesn't attract as much criticism for its color's display tho. More on that later.

9:55 "Most phones are now showing that wider range of colors, they all have P3 displays"

All phones with AMOLED panels have a native wide gamut capability. However depending on the panel generation and unit variation, it's not necessarily matching P3. They're wide-gamut but not really P3.

A lot of IPS panels are aiming at sRGB coverage. The main reason is that it's more power-efficient to have a narrow gamut since the color primaries fall closer to the spectrum where our retina is more sensitive. Also, the sRGB or narrower panels are cheaper to source.
A notable exception however is all Apple products with IPS wide-gamut panels. That's many.
Overall, we could guesstimate regular vs wide-gamut display for devices out here today to what, 50-50%?

9:59 "The effect of Google's decision is that it makes the colors more dull or more toned down that we're used to"

An iPhone/iPad user would be used to sRGB by default on most content, unless the app explicitly supports wide-gamut. Instagram posted about that in January:

Indeed will look toned down to A Samsung Galaxy S user. (default: no color management, content colors stretched to full panel gamut + extra saturation boost), a Google Pixel 1 (same, without the extra saturation added)

10:29 "Now the weird part is that developers can flip a switch to enable showing wide color gamut in their apps"

Not weird: fully color-managed OS all function that way.

iOS added that to color-managed the P3 display of the iPhone 7: it's the UIGraphicsImageRenderer thing in Instagram's post linked earlier.
Without specifying anything: the OS converts it all to show accurate sRGB colors on display.

Windows OS lacks color management, so everything looks wrong by default on wide-gamut displays except for the too few programs implementing color management independently (example: Adobe suite does)

10:51 "The only place you will find that is in the camera viewfinder app and Firefox interestingly enough. If you grab Firefox from the Play Store it will show all the P3 colors on this display"

You've been mislead by the test:, which assumes it's running on a color-managed browser: aka Safari, from Webkit's authors.

Google Chrome for Android added color management - converting everything to sRGB in software (not long ago, because earlier versions had no color management at all)

Since Chrome outputs on sRGB, it clips the red more intense than sRGB max red: both "sRGB" and "Display P3" images look the same.

Firefox Android doesn't enable color management by default. It'll send the RGB values of the image's pixel unmodified to the OS. On the Pixel 2 XL, this is down-converted to sRGB gamut.
You can enable color management like Chrome in Firefox with these steps:
open about:config
- search gfx.color
- set gfx.color_management.mode to 2
- set gfx.colormanagement.enablev4 to true
- kill and start firefox again

Your video shows that the P3 sample red in Chrome and Firefox look the same.
If you redo the comparison with an iPhone, you'll see that this one gives an extra saturation, instead of de-saturating the Webkit logo inside.

11:13 "Showing it in Firefox show how much you're missing"

The rose example displayed illustrate Firefox Android has no color management here

We can see the image is very de-saturated instead of more vibrant.

12:00 "And boom this super saturated photo shows up on everyone else's device, because they're all show more colors"

All iPhone and iPads will show the right colors in this example, all iMacs, MacBooks

All AMOLED and rare wide-gamut IPS Android devices will indeed show wrong colors: a bit incorrect hue and far too high saturation.

Given iPhone's and cheaper IPS (non-wide gamut) market share, a minority of devices will show incorrect colors.

12:03 Conclusion

Google marketing has been presenting Pixel 2 XL as "accurate/natural sRGB" and it you take the claim for granted, it is easy to blame sRGB and color management for all the issues. Why not scrap it all, right - it looks arguably worse than nothing at all, nobody so far likes the result.

Thing is,
Google's claims of color accuracy have not been verified.
Erica Griffin measured (using software I made - I can vouch on the precision of her analysis) her Pixel 2 XL displays and saw that they are not correctly calibrated to sRGB.
In fact the red primary in her units is lacking in intensity and their hue is too orange/yellow. Only from measurements, you can predict that red will be kind of muted and orange, and that a lot of things will kind of look brown.
Including known icons and worse: faces. And humans are extremely sensitive to skin tones. We can tell right away.
Also she mentioned that the gamma curve is darker than it should, which will compromise the result further.

You know, if the problem was sRGB and color management, then reviewers and owners would have complained the same about iPhone displays since the iPhone 7, up to the iPhone X which also uses a calibrated & color managed OLED panel.
Here, something went wrong with the factory calibration process in LG's factories and that is the cause of the color issues.
I don't have enough data on the the smaller Pixel to comment, what do you think?

Post has shared content

Post has shared content
There's still a common perception that iOS is the dominant smartphone platform and Android is the "alternative" option.

About that...

Post has shared content
Wait while more posts are being loaded