Topics

Screen resolution

Geoff Boyle
 

I’ve just been looking at the data that we have stolen from you 😊

 

Just under 30% view CML on mobile devices, 75% of those have a resolution of around 640 * 360.

 

I can’t split cml.news and messages from the main website at the moment but I have visions of people using those 640 * 360 screens to try and look at the camera evaluations.

 

On the subject of mobile screens… for the 30% of you using Android phones there’s a setting available if you turn on developer options that allows you to set the screen to sRGB…

 

Cheers

 

Geoff Boyle NSC FBKS

Cinematographer

Netherlands

www.gboyle.nl

 

Daniel Rozsnyó
 

The 640 x 360 is just a placeholder, does not reflect the reality. The idea behind that is to just have the correct aspect ratio and tell the source that its a small 4-5-6 inch mobile screen. You usually do not want to work in native resolution of FHD or 2K5 on such a small panel.

https://ux.stackexchange.com/questions/98985/why-the-360x640px-resolution-is-currently-the-most-used-one

Regards,

Daniel Rozsnyo
camera developer
Prague, Czech Republic



On 06/27/2018 07:53 AM, Geoff Boyle wrote:

I’ve just been looking at the data that we have stolen from you 😊

 

Just under 30% view CML on mobile devices, 75% of those have a resolution of around 640 * 360.

 

I can’t split cml.news and messages from the main website at the moment but I have visions of people using those 640 * 360 screens to try and look at the camera evaluations.

 

On the subject of mobile screens… for the 30% of you using Android phones there’s a setting available if you turn on developer options that allows you to set the screen to sRGB…

 

Cheers

 

Geoff Boyle NSC FBKS

Cinematographer

Netherlands

www.gboyle.nl

 

Paul Curtis
 


On 27 Jun 2018, at 06:53, Geoff Boyle <geoff@...> wrote:
On the subject of mobile screens… for the 30% of you using Android phones there’s a setting available if you turn on developer options that allows you to set the screen to sRGB…

Funnily enough modern iPhones and iPads are very well calibrated out of the box. 

But colour management on all mobile devices is more a pandoras box than resolution IMHO.

For example. All modern iDevices support widecolor. This is pretty much P3 on the displays. By default, Apple interprets images as sRGB and they will look as expected. But if an image is tagged as P3 (embedded profile) then it will be able to show a more saturated image.

If you go into photoshop in normal working sRGB mode. Draw a square of pure red (255 value). Convert to P3. Then if you eye drop that red it won't be 255 anymore, it will be more 'orange' and lower in the red value. If you draw another box of pure red then depending on your monitor if it looks like same as the first red you're not able to discern P3 gamut. If you then save that image and view on different devices then on a modern idevice you should be able to see a difference between the reds. This is great, it's wide color and well defined.

But that is happyland.

Sadly on other device you may have no idea what's going on. For example. Some will just show sRGB meaning that both patches will look the same red (good). But some will remap that P3 image into sRGB so you will see a difference between the reds yet now that image has lost any sense of baseline reality - because it's a high gamut image mangled into some local display space in an uncontrolled way. That's bad. And unless you have fantastic vision or are able to side by side with what it should look like it will totally mess up how the image is.

So the choices when displaying those test images online are important.

IMHO if there are  going to be web previews of the frames then i would do two. sRGB and P3 and actually note which is which so that people on devices can see both versions - if they look the same then they're sRGB but if they look different, either they're viewing P3 or their device has mangled them.

Webkit (inside Safari) has some great colour management extensions but they're all very new and not adopted beyond Safari (yet)

(not sure if this post helps or muddies everything)

cheers
Paul

Paul Curtis, VFX & Post | Canterbury, UK



Geoff Boyle
 

It’s all as clear as mud Paul 😊

 

Cheers

 

Geoff Boyle NSC FBKS

Cinematographer

Netherlands

www.gboyle.nl

 

 

(not sure if this post helps or muddies everything)

 

cheers

Paul

 

Paul Curtis, VFX & Post | Canterbury, UK

 

_._,_._,_

Paul Curtis
 



On 27 Jun 2018, at 08:58, Geoff Boyle <geoff.cml@...> wrote:
It’s all as clear as mud Paul 😊

Thought that might be the case...

It never surprises me how often i have to check workflow after multiple manufacturers 'update' their SDKs and then the applications get updated, to see if things still work only to find they don't. (tried getting an ACES EXR from RedCine lately...?)

Once the tests are done, i'll use the EXRs to rustle up some examples and then we can experiment. Figure it's easier to look at 'real' examples

cheers
Paul

Paul Curtis, VFX & Post | Canterbury, UK