Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

gearbest.com

CEATIC 2016: Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

While we’re not CEATEC, a Japanese technology show, news has come via PC Watch regarding a new publicly announced milestone in monitor production. For any journalist that has attended either IFA, Computex, CES or MWC over the past year, it would be hard going to miss one of the super large (80-inch plus) 8K monitors doing the rounds. While highly impressive in their own right, current 8K displays on show typically have a low pixel-per-inch value in order to achieve a good panel off the production line. So despite the fact we can get 4K panels on smartphones (Sony Xperia Z5 Premium is 4K in 5.5-inch, or 806 PPI), expanding the size at that pixel density is difficult with panel yields. Also, moving 8K down to a ‘monitor size’ has been hidden at the panel companies internal research divisions until now.

CEATIC 2016: Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

So this is where the Sharp monitor on display at CEATEC gets interesting. The IGZO display is down at 27-inches, marking a 326 PPI, just hitting at the door of large FHD smartphone displays. The panel is also listed at 1000 nit brightness. But to double down on specifications, the stand listed the display as supporting 120 Hz while in 8K mode, and also supporting High Dynamic Range, or HDR. This requires a large amount of data to be pumped into the display, and as a result a photograph of the rear shows eight separate DisplayPort cables being used in order to give the display the data it needs. 8K120 with HDR is no easy task, suggesting 7680×4320 at 10 bits per color channel (so 30-bit for RGB) at 120 times a second would suggest needing 120 gigabits per second of bandwidth at a minimum (or 15 GB/sec). That’s even before you discuss overhead, which will push that higher.

CEATIC 2016: Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

 

gearbest.com

CEATIC 2016: Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

Needless to say, this is a prototype panel. Businesses with large enough checkbooks are free to try and estimate a figure for such a display, because it will be a while before a device of these specifications hits commercial availability.

CEATIC 2016: Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

Also in the display was a 2.87-inch display, offering 1920×2160 resolution and rolling in at over 1000 pixels per inch (1008 PPI). This was described as ‘4K to both eyes’, affording a combined display suitable for head-mounted units or virtual reality headsets. Compare this to the HTC Vive, which uses a 1200×1080 screen per eye at 3.62 inches per panel, making it 447 PPI. This gives the Sharp panel a specification of over double the amount of pixels in a given area. Of course, with that comes cost and the ability to feed that display with enough data either over cable or other means. Still, it’s an interesting prospect.

 

Source: PC Watch

Source: anandtech.com

pontofrio.com.br
Facebooktwittergoogle_plusredditpinterestlinkedinmail

10 thoughts on “Sharp Showcases 27-inch 8K 120Hz IGZO Monitor with HDR, also 1000 PPI for VR

  1. Only the limits that have not been achieved yet. 4k on a monitor has pixels too small to see. We have an angular resolution limit. 4k for sure covers that on a phone. An 8k phone is one you don't need to buy ever. An 8k monitor at my current size of 32″ and 2 foot or so viewing distance is likely overkill but I would order one to see. 16k+ would be stupid.What is not real about a photo has nothing to do with pixels anymore and everything to do with the lack of 3D and motion and color representation issues (both color space available and low HDR capability). After that becomes “real” you would then need to start fooling the other senses as well.

  2. Do not write such comments, progress must be made to the limits. 8K (and futher 16K or 32K), give you quality so high, that computer generated artifical life will be preceived as real. 4K is not enough for it. You must see literally every hair to preceive that it is real.

  3. I have a 32″ 4k from Asus. I do not want smaller because I want my face full of monitor. However, I do not want a larger monitor either, too much swiveling of the head to the sides then leading to strain.It is pretty amazing programming on it. Two full code pages, side by side with all their widgets.If it doubles as your TV then I guess you also need wider and taller and a massage therapist for your neck.

  4. I'll be more happy with 29~43 incher 21:9 @ 5K resolution ( that's 5120×2160 for those who hate math ) with full HDR and something high in Adobe RGB ( like over 90% )…but I'll be much more happy if this had a USB 3.1 Gen 2 hub few Type-A and Type-C ports with power delivery standard also… okay that will be a dream after 2-3 years…

  5. That's nice, but part of me would almost want a wider 34″ 3440×1440 variant just because of that kickass display real estate. Also, wider fov is hawt. But I agree that hidpi displays require too much gpu muscle to justify themselves. High refresh is worth more imo.

  6. Could be something lower than UHD and higher than 1440p – 2880×1800 for instance. Not sure why we need such a big jump between 1440p and UHD, when we could go just a bit higher.

  7. I'd like a 1440p 120hz+ 27″ freesync with HDR. That's probably my perfect monitor right now.4K is still too high of a resolution for current video cards to consistently push 100+ FPS on the most demanding games.

  8. Nice. Although I'll be happy with a 4K, 27″, 120/144Hz monitor.

  9. Nice to see Sharp pushing the boundries, even despite Sharp (the company) being sold off to the highest bidder because the business wasn't doing so well.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>