5 ms·
The ideal would be to use hexagonal pixels for camera sensors, displays, and printer dither/halftone patterns, the same way human retinas arrange their cone cel
by jacobolus 10y ago
The ideal would be to use hexagonal pixels for camera sensors, displays, and printer dither/halftone patterns, the same way human retinas arrange their cone cells. :-) Cf. https://scholar.google.com/scholar?q=hexagonal+image+processing https://scholar.google.com/scholar?q=hexagonal+image+process...
Since we have so much variety in screen shapes and resolutions today, most of the time we’re resampling images on the fly to rotate/scale them into their position on screen anyway, so the pixel data representing an image in a file isn’t getting directly sent to the same on-screen grid. Thus for most of what we display on screen, there’s no inherent need to stick to the same grid shape used for storage, and a hexagonal pixel grid would in practice look better for the same number of pixels (hexagonal grids are particularly good for representing curved shapes and reducing moiré artifacts). For that matter, there’s no inherent need to store square grids of pixels in our image formats; we could use hexagonal-pixel files and easily resample them for display on arbitrary display grids. The only thing stopping us is technical fluency with rectangular grids, and cultural/historical inertia.
(Think of the iPhone 6+, where software can’t even address the native screen pixels, and literally everything gets rendered to one size grid and then resampled for a different display grid.)
Beyond that, people really need to stop using the extremely misleading CIE 1931 (x, y) chromaticity diagram when comparing color gamuts. The CIE 1976 (u', v') UCS diagram is much more uniform, and just as easy to plot (it’s just a simple linear transformation of the (x, y) diagram). We’ve known the problems with the (x, y) diagram for >50 years now, there’s really no excuse for its continuing ubiquity.
For making diagrams of pixel grids, it would also be better to show less intensely colored RGB pixels, so that the G’ pixel doesn’t so look obviously less intense.
- ssalazar 10y ago> (Think of the iPhone 6+, where software can’t even address the native screen pixels, and literally everything gets rendered to one size grid and then resampled for a different display grid.) This isn't really how this works. If everything was being upsampled, youd see obvious jaggies and upsampling artifacts. The only reason iOS can do this reasonably well is because the actual resolution is exactly 2x or 3x the resolution presented to the software. The actual rendering takes place at native resolution; graphics assets are produced in the native resolution. Upsampled rendering/assets look very obviously bad. > The only thing stopping us is technical fluency with rectangular grids, and cultural/historical inertia. These are factors, but theres also not much evidence that resampling from arbitrary virtual to physical resolutions will actually look good.
- mark-r 10y agoI thought the genius of Apple resizing was that everything is resampled down, not up.
- jacobolus 10y ago> The only reason iOS can do this reasonably well is because the actual resolution is exactly 2x or 3x the resolution presented to the software. On the iPhone 6+, this is not accurate. Most apps are rendered to a 1242 × 2208 pixel resolution (3× the “logical” 414 × 736 resolution) and then downsampled to the screen’s physical 1080 × 1920 resolution afterward. On OS X, the default behavior for “retina” displays is to render everything precisely to screen pixels at 2x the “logical” size, but users can alternatively select a different virtual display size, whereupon all content will be resampled for display. > theres also not much evidence that resampling from arbitrary virtual to physical resolutions will actually look good Every photographic or video image you look at on your computer or phone has been resampled to different pixel grids several times in the course of its production, and is typically resampled one final time when rendered to screen. There is thus lots of evidence that we can relatively seamlessly resample just about everything, and only dedicated pixel peepers will care strongly. As for non-photographic content like line art, maps, text, rendered video game output, etc., we could just render these directly to a different grid.
- dietrichepp 10y agoOn the iPhone 6+, software can, in fact, address native screen pixels. This is even quite easy. However, that is not the default API behavior, the application must specifically request device native pixels by setting a certain flag. Typically, general GUI apps would not bother because it's easier that way, games would flip the switch for performance, and more sophisticated apps (photo apps, perhaps) would flip the switch as well.
- jacobolus 10y agoAh, okay. I guess I misunderstood precisely how it worked. I haven’t actually ever used an iPhone 6+ myself. Thanks for the correction. Still though, the point remains that most apps use the setting with resampling and most users don’t seem to obviously mind.
- panic 10y agoHere's more info about how the iPhone 6+ scales pixels in various situations if anyone's curious: http://oleb.net/blog/2014/11/iphone-6-plus-screen/ http://oleb.net/blog/2014/11/iphone-6-plus-screen/