Most of you have probably heard of the term Internet of Things (IoT) which refers to the fact that millions and soon, probably billions of devices will be connected to information via the Internet.
Recently Andrew (Drew) Jamison at Scalable Displays has been chirping about what he calls the “Internet of Display” (IoD). Since reading his article introducing the concept, I have been having spirited debates with a number of people about this concept – and trying to decide if the term has merit and if so, a concise way to describe it. In this article, I will lay out the concept in more detail as I understand it and I invite you to chime in with comments and your input.
One of the trends behind IoT and IoD is that functionality and data that used to reside on PCs, workstations or company servers is moving to the cloud. The result is that the conventional display/workstation paradigm is changing and moving in the direction of simply a “dumb” display being all that an end user needs to do complex tasks.
For example, this means that a CAD designer can interact and render designs in the cloud delivering just images to his display. A digital signage media player can migrate to the cloud delivering the content playlist in real time. A control room can use the cloud to aggregate multiple sources of data and video using management software resident in the Internet to deliver images to the display solution. A 360-degree video of computer-generated or video images can reside in the cloud streaming to VR headsets or mobile devices.
What is common to these and many other applications is that there are huge data sets that the user is accessing. Let’s call them content pixels. For example, the data behind a game or a CAD model is three dimensional with great detail – hundreds of millions of content pixels. 360-degree video data has a lot of content pixels as well. Any broadcast of an event featuring multiple cameras has a huge number of content pixels.
But what we often see is only a subset of the content pixels. Let’s call these display pixels. Returning to our examples above, the CAD or game designer sees one view (or two views if stereo) that is limited by the pixel count of the display. To see more of the game or model, interface devices allow navigation. With 360-degree content in a VR headset, you only see a portion of the environment at one time with different views presented as you move your head. In broadcast, all those cameras are switched to provide one stream whose view is limited by the screen size and pixel count of your display.
Display pixels are almost always a lot less than content pixels. And, just as importantly, the window into the content pixel world is typically focused on a single user. To paraphrase David Park’s comment on LinkedIn, when the display pixels are much less than the content pixels, it is like looking at the world through a straw – you only see a tiny portion at a time.”
There are solutions that enable the display pixels to rival the content pixels. A control room with a whole wall of displays, a massive digital sign, simulators with curved screens, five- or six-sided CAVEs, or planetariums with domed screens are some examples. And notice that these displays are now focused on group and not single-person use.
For the most part, these are expensive systems but with content and processing moving to the cloud, it seems likely that wide field-of-view multi-megapixel display solutions will become more common place. That means 2-3 monitor desktops or giant curved screens will be common. Meeting rooms will be equipped with 2-3 (or more) blended projectors or wall-sized LCD or LED screens. Theaters are even embracing the trend with the Barco Escape 3-screen format.
I think it is also likely that small personal domed or toroidal display systems will become much more popular as non-headset VR viewing devices. And why not extend this to theme parks or special venues with multiple people in 360-degree “immersion” rooms for entertainment purposes such as being at a concert or sporting event.
The TV wall of the future is doable today and cost effectively with blended short-throw projectors. It does not seem so far fetched to imagine mobile devices from family members throwing up all kinds of content while other sources serve up TV shows, multiple sporting events, data, video chats and more.
The content pixels have already expanded well beyond the display pixels so it seems logical that end users will understand this and demand more display pixels. And interest in 180- and 360-degree video is exploding with the VR craze. Cameras to capture the content just got a big boost too, with the announcement of GoPro and Google teaming up in this area. The content is and will be there, but will the displays?
So how many display pixels is enough and under what circumstances? Scalable says that in a conference room where the typical viewing distance is 12’ a benchmark of 1 megapixel per person is a number that has historically been used in many of their installations. I think that in many situations the number should be far higher – depending on the application, your distance from the display and the field of view. Since we want to get away from the “view the world through a straw” mentality, I suggest that a 90-degree field of view (FOV) is a good benchmark for viewing rich multimedia.
Figure 2 shows a simple rule for calculating the needed display pixels per person for such wide FOV displays.
To see if this is about right, let’s consider some examples. On my desktop, for instance, I have two 1920×1080 monitors (2 megapixels). They are side-by side creating about a 90 degree field of view from where I sit (about 30 inches (72cm) away ). The chart suggests I should have about 3.5 megapixels as a single user, which indeed I would like to have.
In a single-user VR headset with a virtual distance of 1 to 5 feet (.3 to 1.5m), you want 2-4 megapixels of resolution for a 90 degree field of view, according to Figure 1. Around 2 megapixels in about this FOV is what the Oculus Crescent Bay headset delivers today and it could use a few more pixels. Want to allow 4 people to view the 180-degree content at 7 feet using blended projectors, without having to wear a headset? You need about 8 megapixels.
Let’s consider a meeting or small huddle room. It is not uncommon for these rooms to have a single projector or flat panel display for 2-4 people to use in the meeting or collaboration. But such a display solution creates a very narrow field of view for each participant. That may be fine for sharing a PowerPoint document, but for multiple pieces of data or a big data set, such a display is inadequate.
Using the chart, four people viewing data in a 90-degree FOV display at 13 feet (4 m) requires 4 megapixels. A single flat panel can achieve the megapixels, but not the wide FOV. Blended projectors are needed or a LED or LCD wall.
What needs to be added to the discussion is the reality that when displays fill more than 90-degrees participants don’t all look at the same data when viewing a large screen. The display needs to support sufficient pixels to accommodate the visual acuity of all participants.
If there is the expectation that participants will be close to the display to look at finer details, you need to decide how close when determining the megapixel requirement. If participants are 3 feet (1 m) away for example, you need about 15 megapixels for 4 people.
The market for these wide field of view display solutions that allow rich access to content on the Internet or from other sources is exploding. The market drivers are:
- Access to massive data sets from anywhere in the world
- Wide field of view
- Single to multiple person viewing
- Eye limiting resolution based on interaction distance
- Display pixels matched to content pixels
What is your “FOV” on “Internet of Display”? Let’s take a “straw” poll on which term best captures the scope of this discussion
- Internet of Display
- Immersive Content Viewing
- Field of Vision Viewing
- Human Vision Displays
- Directview VR
Please post your votes or comments below.