Linus Torvalds: 2560x1600 Needs To Be Next Standard


Recommended Posts

Try disabling font anti-aliasing and you'll quickly start seeing individual pixels.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

He is right, but the OS must be able to scale with the resolution. I don't want everything to be too small to read because of the crazy resolution. Apple and Google seem to be making a good job at scaling iOS and Android to fit any resolution and still being usable.

But yes, when I see that my Galaxy S3 has more pixels than some laptop, it's getting ridiculous.

You could even have a 10000dpi display but until desktop operating systems will do proper DPI scaling on very high resolutions displays it's completely pointless.

Windows scaling starts looking horrible from 200% DPIs and above (cursors and icons all look jagged) and there are still many applications that look horrible or ignore the scaling like Adobe's (also DPI settings seem to be ignored by Metro), OS X cheats by upscaling a lower resolution unless the application is "retina-aware" and Linux is probably the one with most issues but it depends, it can be either somewhat acceptable or horrible depending on the distro/desktop environment.

It is actually quite funny that it was Linus Torvalds complaining about this issue when most linux distributions recommend lowering the resolution on the retina macbooks basically tossing the extra pixels in the trash. If it's not done properly it just becomes a waste of CPU/GPU/power: it would be far better to have a reasonable resolution (1080p minimum?) that works well with the operating system rather than some insanely high-DPI display where everything looks like crap and movies still show with the annoying bars due to weird aspect ratios.

I think Apple approach was the best because they always tried to double the resolutions on their devices to make the transition the least painful they could and on the retina display their use of a whitelist system (only tested applications will work in native mode) has avoided the issues with all the applications that don't render properly. I still wonder why Windows still uses the cheapest scaling algorithms for some parts the UI, it's not like the recent CPUs couldn't scale a 32x32/48x48 cursor.

NOTE: This post is only exclusively about desktop operating systems, not phones or tablets where the UIs have been tailored for DPI scaling from the start.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

That's kind of the point, we're using anti-aliasing (for nearly everything) because we have such low resolution devices. Increasing the resolution negates the need for anti-aliasing. Photos see an improvement since they're often scaled down for display, showing them at their normal resolution allows for more fine detail.

Compare proper 1920x1080 video to a scaled 960x540 copy, the overall image will be the same, but you'll be missing out on fine detail.

I'm really not sure I understand this trend of squeezing more pixels into the same physical space. Have we suddenly evolved to have mega awesome eyes that can see individual pixels at 5 feet away? :wacko: Using my computer, netbook or phone I can't see the individual pixels unless my eyes are too close to the screen. Maybe I'm not understanding something but it seems like pointless number increases to me, much like camera megapixels.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

On a smartphone or tablet it definitely makes sense and you can clearly see the difference. However, I'm using my 27-inch iMac at a comfortable 50 cm away and it already becomes increasingly hard to see the individual pixels. I have no doubt a "retina" iMac will be nicer, but the issue isn't as pressing as on - let's say - an iPhone.

And we'll pay out the rear for it. I can't see a huge difference between my desktop running 1280*1024 (19" CRT) vs my laptop running 1366*768 (15.6"). Maybe it's my need for glasses that blinds me, or it's just a big marketing scam like most crap is.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

I'd argue 330+ for mobile devices, 270+ for laptops, 200+ for desktop displays.

Currently I have:

iPhone 4: 960x640 @ 326ppi (and really good during normal operation)

Nexus 7: 1280x800 @ 216ppi (noticably lower than the iPhone) - this would be better in 330ppi range for day to day usage.

Thinkpad Edge 11: 1366x768 @ 135ppi (unacceptably low) - I would be very happy if this was in the 270ppi range for day to day usage.

Dell U2711: 2560x1440 @ 109ppi (low but marginally better than the Thinkpad) - it would be better if this was in the 200ppi range for day to day usage.

I'm more in line with these later opinions that understand PPI values should vary depending on device type. Resolution is not a simple matter of pixels and PPI. Anyone who establishes their opinion on display standards with just these two values does not understand display ergonomics.

At the lowest level, you want to begin with how far your eyes are from the screen. A smartphone, laptop, desktop, and television are all viewed at different distances--and even then, those distances aren't common for all people. You might sit comfortably anywhere from 1'-2.5' from your laptop display while doing work. Pixel density will have dramatically different effects depending on where you fall in this range.

Once you establish your comfort zone with displays, you need to determine which range of PPI values match it. That is, which PPIs make pixels indistinguishable at the high and low end of this zone (turn off font smoothing if you want to get really serious about it, but at that point you're going beyond what reality will ever throw at you--your choice). Hang on to these two values, because you can map these against the final cost of the display when you make your decision.

Now, take your preference for aspect ratio. Throw it away. It's meaningless. It doesn't matter. It's one of those things people take way too seriously and defend to the death with nothing but flawed anecdotal evidence and studies on FoV they don't even understand. What matters is perceived space. A 24" 16:9 display will have just as much physical vertical space as a 23" 16:10 display, and cost the same or less simply because 16:9 panels are in higher demand. It's not a matter of losing vertical space with 16:9--you're gaining horizontal space.

It's a lot easier to wrap your mind around if you give these two ratios a common denominator. It isn't about 16:10 vs. 16:9 (where the vertical value appears lower). It's 160:90 [16:9] vs. 144:90 [16:10]. This more accurately represents what you get for your dollar.

Now, ask yourself what the vertical height was of the 16:10 display you so fell in love with, and find out what diagonal length a 16:9 monitor has to be to have the same vertical height. Make this your minimum display size.

At this point, you know the physical size of the monitor you want, and the pixel densities to match. Congratulations, you have an informed opinion.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

I think he's right. It's kind of ridiculous to have a 1280x720 (and higher) screen res. on a 4.5" phone, yet have a laptop's 13" screen be only 1366x768px. Maybe the screens don't need to be 2560x1600, but at least have 1600x900 instead of 1366x768.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

You're being snarky, but for making it to the bottom of my post, you completely missed the point.

Think, for a second, in terms of actual physical space: actual inches in the physical real world. A 23" 16:10 display gives you extra vertical space to work on 16:9 video, yes. But a 24" 16:9 display gives you the same extra vertical space, PLUS extra horizontal space, while the amount of actual physical space the video takes up on the screen is the same.

THAT is my point. Aspect ratio doesn't matter when the fact is a PHYSICALLY LARGER display is more affordable at 16:9 than 16:10. Let me actually draw a picture for you, because I think this is something people are genuinely having trouble making their brains process. Note that the attached picture is to compare the two aspect ratios where the video frame is given the exact same real-world physical space. You have the exact same space for the video frame, the exact same extra vertical space for editing controls, plus bonus extra horizontal space for whatever you desire, all on a monitor that costs the same price. You only lose the extra vertical work space if you decide to give the video frame more physical area, but at that point you'd need a physically even larger 16:10 display, which would add to the pricetag, and--guess what--a larger still 16:9 display will be available yet again at that same new higher price.

Entirely because of the effect TV panels are having on the cost of displays, it remains economically feasible to always just buy a LARGER 16:9 monitor that can contain the same work space as the smaller 16:10.

This is very, very simple math here. Middle school level stuff. Please, please tell me this isn't still going over your head.

/something to think about: for 2560px wide displays, 16:9 will run you $700, 16:10 will run you $1200. you can either pay $500 dollars for those extra 160px in height, or buy two of the 16:9 monitors. $1200 for 2560x1600, or $1400 for 5120x1440. I would rather buy two slightly shorter displays than be punished with a 50% markup per pixel for one slightly taller display. In pure economical feasibility, telling yourself that 16:10 is the "better choice" is downright lunacy.

post-10281-0-84041300-1351972610.png

It's not about math, it feels unwieldy and doesn't work. You're missing the human element here.

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Your point of view is nonsense, extreme detail, or otherwise. If it doesn't take you 5 seconds to realize the practical benefits of using a 16:10 monitor to edit 16:9 frames, then you're just dense.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Onkyo Dolby Atmos AV receivers are really solid deals by Sayan Sen Recently we covered great deals on several soundbar models from the likes of Sony, JBL, Samsung and others for really good prices (the lowest in several months). Aside from that we also reported on the Edifier S3000MKII, a hi-fi two-way bookshelf monitor that's available for only $800. Today we bring a list of AV receivers from Onkyo that are available at great prices including the Onkyo NR7100, RZ30, and 8470 (purchase links under the specs table down below). The Onkyo TX-NR7100 and Onkyo TX-RZ30 are both 9.2-channel AV receivers designed for immersive home theater setups but they occupy slightly different tiers within Onkyo’s lineup with the RZ30 positioned as the more advanced model. The TX-NR7100 is a THX Certified 9.2-channel receiver offering up to 100 W per channel (8 ohms, 2 channels driven). It supports Dolby Atmos, DTS:X, and IMAX Enhanced formats, with flexible configurations such as 5.1.4 or 7.1.2 speaker layouts. A key highlight is its built-in Dirac Live Room Correction which should help optimize sound based on your room and its acoustics. In comparison, both models share several core capabilities though the RZ30 is geared toward enthusiasts seeking more precise calibration and system flexibility, while the NR7100 is positioned as a slightly more accessible, value-focused option with strong all-round performance. The technical specs of the RZ30 and NR7100 9.2 AVRs are given in the table below: Specification Onkyo TX-RZ30 Onkyo TX-NR7100 Power Output (FTC, 2ch driven) ~100 W/ch (8Ω, 20Hz–20kHz, 0.08% THD) 100 W/ch (8Ω, 20Hz–20kHz, 0.08% THD) Dynamic / Peak Power 9 × 170 W (6Ω, 1kHz, 1% THD, 1ch driven) 220 W/ch (6Ω, 1kHz, 10% THD, 1ch driven) Frequency Response 5 Hz – 100 kHz (+1/-3 dB) 10 Hz – 100 kHz (+1/-3 dB) THD 0.08% 0.08% Room Correction Dirac Live (full bandwidth) Dirac Live (with AccuReflex support) Immersive Audio Dolby Atmos, DTS:X, IMAX Enhanced Dolby Atmos, DTS:X, IMAX Enhanced Speaker Layout Support Up to 7.2.2 / 5.2.4 / 9.2 processing Up to 7.2.4 / 5.2.4 / 9.2 processing HDMI Inputs / Outputs 6 inputs / 2 outputs (eARC) 6 inputs / 2 outputs (Main + Sub/Zone 2) HDMI 2.1 Support 8K/60, 4K/120, VRR, ALLM, QFT, DSC, eARC 8K/60, 4K/120, VRR, ALLM, QFT, DSC, eARC Video Formats HDR10+, Dolby Vision, HDCP 2.3 HDR10+, Dolby Vision, HDCP 2.3 Streaming / Network Wi-Fi, AirPlay 2, Chromecast, Bluetooth, DTS Play-Fi Wi-Fi, AirPlay 2, Chromecast, Bluetooth, DTS Play-Fi Get them at the links below: Onkyo TX-RZ30 9.2-Channel AV Receiver: $797.00 (Sold and shipped by Electronic Expo) Onkyo TX-NR7100 9.2-Channel AV Receiver: $699.00 (Sold and shipped by Adorma) Onkyo TX-8470 2 Ch Stereo Receiver: $449.00 (Sold and Shipped by Adorma) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links or authorized dealer links (at the time of article publishing); ensure that you purchase from such links only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • A different thing with Russia. When you say is it better, depends on things. It is better that we don't have the E.U making rules and laws that have nothing to do with them. Is the trading part better? No, that is really mucked up, but then we knew that was going to happen and we would have make agreements, like we do with other parts of the world. Freedom of movement is certainly better, but could be improved, we still need more control over our borders. do you live in the U.K?
    • So what am I quoting from them? I never listened to what Farage or his cronies said. I wanted the U.K to leave the E.u years before the referendum and it had nothing to do with Farage and his cronies. So what country do you live in? Did we work much better together? We were always at logger heads with the E.U because we disagreed with them so much. Maggie was always on at them. I would have thought the E.U was glad to get rid of us as we stopped the integration or made it a two tier. Now without us they can integrate more. I would not have voted out if it was just a trading block and we can still work together on somethings.
    • MPC-BE 1.9.0 by Razvan Serea Media Player Classic - BE is a free and open source audio and video player for Windows. Media Player Classic - BE is based on the original "Media Player Classic" project (Gabest) and "Media Player Classic Home Cinema" project (Casimir666), contains additional features and bug fixes. The BE mod (Black Edition Mod) is a skinned version of Media Player Classic Home Cinema, much better looking than the plain old MPC. MPC-BE 1.9.0 changelog: Splitters Fixed crashes in some situations. AudioSplitter Added support for the RF64 format. Fixed reading of channel layout for some WavPack files. Added support for ID3 tags for Wave64 files. Unknown Wave64 chunks are now ignored. AviSplitter Added support for 'y408' video. Improved support for 'HEVC' video. FLVSplitter Added support for VVC video. MP4Splitter Improved handling of corrupted files. MatroskaSplitter Expanded support for V_UNCOMPRESSED video codecs. Fixed support for frame rotation (ProjectionPoseRoll). Improved support for "V_MS/VFW/FOURCC / HEVC". MpcDvdVideoDecoder Fixed conversion to YUY2. Fixed display of menus for some DVD-Videos. RoQVideoDecoder Output in NV12 and YV12 formats is allowed. Full range is used. MPC Video Decoder RGB32 format will be output as a top-down bitmap by default. Added support for the "IID_MediaSideDataDOVIMetadataV2" interface. Removed support for the deprecated "IID_MediaSideDataDOVIMetadata" interface. Fixed retrieving the name of the video adapter when using NVDEC. Fixed crashes in some situations. MPC Video Converter Added support for AYUV video format. MpcAudioRenderer Improved input format validation. Optimized retrieval of supported formats for exclusive mode. Added the "Keep audio device active when paused" setting. Fixed crashes and freezes in various situations. Subtitles Added the ability to open the properties of an external subtitle renderer in the "Subtitles" settings panel. Fixed external subtitle connections for VSFilter. Fixed a crash when rendering PGS/SUP subtitles when using AVX2. YouTube Improved support for yt-dlp. The built-in YouTube parser is no longer used. Player The HTTP read strategy has been changed. If the playlist contains one entry, more key combinations can be used to control the player (jump through chapters, adjust volume). Improved support for reading ASX playlists. The translation of the MediaInfo report for Chinese, Korean and Japanese has been removed. Added blocking of 32-bit filter "PICVideo Lossless JPEG Decompressor" (pvljpg20.dll), because it crashes. Added blocking of the system filter "AVI Decompressor", which will eliminate the crash of VFW codecs. Fixed a rare crash when using the "/slave" key. Fixed a crash when getting a list of fonts for OSD. Added the ability to load an external audio file using hotkeys. Fixed opening a network path starting with \?\UNC. The "Determine duration when adding" playlist setting now works for YouTube video URLs. The "Online media services" settings panel has been redesigned. Added a "Merge files using FFmpeg" option to the file saving dialog. This option is activated when playing multiple streams obtained using yt-dlp. Added loading of local .dpl playlists ("DAUMPLAYLIST"). Fixed a hang when the user closes the player during the URL opening process. Various interface fixes. Installer Updated MPC Video Renderer 0.10.5. Updated MPC Script Source 0.2.17. Added MPC Image Source 0.3.6. Translations Updated Japanese translation (by tsubasanouta). Updated Chinese (Traditional) and Dutch translation (by beter). Updated Romanian translation (by Andrei Miloiu). Updated Hungarian translation (by mickey). Updated Turkish translation (by cmhrky). Updated German translation (by Klaus1189). Updated Chinese (Simplified) translation (by wushantao). Updated Italian translation (by mapi68). Updated Korean translation (by Hackjjang). Updated Chinese (Traditional) (by udfbe). Updated libraries dav1d 1.5.3-6-g04b69f9; ffmpeg n8.2-dev-1857-g4653e68aab; libpng git-v1.6.55-9-g7d52a8087; Little-CMS git-lcms2.18-26-gf739cda; MediaInfo git-v26.05-38-g702c9b7fd; ZenLib git-v0.4.41-91-g073f297; zlib 1.3.2. Download: MPC-BE 64-bit | Portable MPC-BE 64-bit | ~20.0 MB (Open Source) Download: MPC-BE 32-bit | Portable MPC-BE 32-bit Link: Media Player Classic - BE Home Page Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Apple reportedly looks to blacklisted Chinese memory chips as RAM prices climb by Karthik Mudaliar Image via Apple Apple is reportedly trying to get a clearance from the Trump administration to buy memory from ChangXin Memory Technologies (CXMT) to get some relief from soaring DRAM prices. As per a report by the Financial Times, Apple approached the Commerce Department more than a month ago and also spoke to other officials and allies in Washington. For starters, CXMT is a company that's already been placed on the Pentagon's list of Chinese military companies. The Chinese company is the country's top DRAM maker. For Apple, the timing is certainly awkward but not surprising. Tim Cook had recently warned that Apple would have to raise prices because AI companies are buying up large amounts of memory for data centers, and just like that, Apple raised MacBook and iPad prices. Micron also recently revealed that customers have committed billions of dollars to secure memory supply years in advance, which shows us how aggressive securing infrastructure has become. This gives suppliers such as Samsung, SK Hynix, and Micron more leverage, while pushing hardware makers to look for alternatives. CXMT is one of those alternatives, but not the simplest one. Apple has spent many years trying to diversify parts of its supply chain away from China, especially for final assembly, while still depending heavily on Chinese manufacturing and suppliers. Even domestic brands from China are moving towards CXMT and YMTC instead of relying on Samsung, Micron, and SK Hynix. For Apple, though, it would invite more scrutiny than local Chinese companies. For now, this is more like a lobbying effort rather than a confirmed supply deal. There's no official statement from either of the parties. What is clearer, though, is the pressure behind such a request. AI demand has certainly made hardware a bottleneck, and companies are trying everything they can to bring things back to normal, even if that means making politically sensitive choices. Source: Financial Times
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      491
    2. 2
      +Edouard
      224
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!