Exclusive: DisplayLink Demonstrates Foveated Compression for Better Wireless VR

Making Metro Exodus Was Apparently a Breath of Fresh Air
January 12, 2019
Ace Combat 7 Trophy List Revealed
January 12, 2019

DisplayLink has been building out its wireless VR compression technology for the last few years, eventually finding its way into the recently released Vive Wireless Adapter. But VR headsets are inevitably moving toward higher resolutions—as we’ve seen this week at CES 2019—making it increasingly harder to make them wireless. Luckily DisplayLink has a few tricks up its sleeve to boost compression efficiency without impacting latency, one of which they demonstrated exclusively to Road to VR this week at CES 2019.

Many readers of Road to VR will be familiar with the concept of foveated rendering: since our eyes only see in high fidelity within a few degrees of the center of our field of view, it’s possible to achieve higher quality (or more efficiency) by rendering lower quality imagery in the peripheral regions and higher quality in the very center. Eye-tracking then can be used to make sure that the high quality region always stays at the center no matter how you move your eye. Done right (with good eye-tracking and smart rendering algorithms) this can be completely invisible to the end users.

DisplayLink is using this same concept, except for compression instead of rendering. Compression is critical to wireless VR because you need to be able to send high resolution imagery at high framerates over a wireless connection that sometimes experiences sudden drops in bandwidth due to the imperfect nature of wireless connections.

Maintaining smooth visuals is key to preventing freezing and stuttering which would hamper any wireless VR experience. To maintain consistency in the imagery, DisplayLink has designed their compression technology to be able to respond to changes in bandwidth on the fly—even in the middle of a frame—so that if, for instance, a user’s hand briefly blocks an antenna, the system can apply more compression to make sure the image can fit over the reduced bandwidth.

Beyond just maintaining consistent imagery under situations of reduced bandwidth, there’s also the need to be more efficient with compression so that larger frames for future headsets with higher resolution can fit in the same available bandwidth.

Both reasons are why DisplayLink is developing foveated compression which takes advantage of eye-tracking data to understand where to compress the frame the most and where to leave it sharp. In doing so, the company claims some pretty huge gains in compression efficiency.

Photo by Road to VR

Using a Vive headset equipped with Tobii eye-tracking, DisplayLink showed me a demo using their wireless adapter reference design. Initially the adapter was set to use the same amount of bandwidth available in the Vive Wireless Adapter to get the image to the headset. Then they turned on foveated compression and cut the available bandwidth down to 1/3.

To my eyes the difference between the full bandwidth image and the 1/3 bandwidth image (with foveated compression) looked effectively identical. Even as I raced my eyes around the scene in an effort to catch the edges of the more highly compressed regions, I was wasn’t able to see anything more than a fleeting glimpse of a slightly blocky region in my peripheral, and this is as I was actively trying to spot any visual artifacts.

.IRPP_kangoo , .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl , .IRPP_kangoo .centered-text-area min-height: 100px; position: relative; .IRPP_kangoo , .IRPP_kangoo:hover , .IRPP_kangoo:visited , .IRPP_kangoo:active border:0!important; .IRPP_kangoo display: block; transition: background-color 250ms; webkit-transition: background-color 250ms; width: 100%; opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #eaeaea; box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -moz-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -o-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -webkit-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); .IRPP_kangoo:active , .IRPP_kangoo:hover opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #e6e6e6; .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl background-position: center; background-size: cover; float: left; margin: 0; padding: 0; .IRPP_kangoo .postImageUrl width: 30%; .IRPP_kangoo .imgUrl width: 100%; .IRPP_kangoo .centered-text-area float: right; width: 70%; padding:0; margin:0; .IRPP_kangoo .centered-text display: table; height: 100px; left: 0; top: 0; padding:0; margin:0; .IRPP_kangoo .IRPP_kangoo-content display: table-cell; margin: 0; padding: 0 10px 0 10px; position: relative; vertical-align: middle; width: 100%; .IRPP_kangoo .ctaText border-bottom: 0 solid #fff; color: #1ABC9C; font-size: 13px; font-weight: bold; letter-spacing: .125em; margin: 0; padding: 0; text-decoration: underline; .IRPP_kangoo .postTitle color: #34495E; font-size: 16px; font-weight: 600; margin: 0; padding: 0; .IRPP_kangoo .ctaButton background-color: #e6e6e6; margin-left: 10px; position: absolute; right: 0; top: 0; .IRPP_kangoo:hover .imgUrl -webkit-transform: scale(1.2); -moz-transform: scale(1.2); -o-transform: scale(1.2); -ms-transform: scale(1.2); transform: scale(1.2); .IRPP_kangoo .imgUrl -webkit-transition: -webkit-transform 0.4s ease-in-out; -moz-transition: -moz-transform 0.4s ease-in-out; -o-transition: -o-transform 0.4s ease-in-out; -ms-transition: -ms-transform 0.4s ease-in-out; transition: transform 0.4s ease-in-out; .IRPP_kangoo:after content: “”; display: block; clear: both;

Eye-tracking is a Game Changer for VR That Goes Far Beyond Foveated Rendering

Even when I asked them to switch rapidly back and forth between full bandwidth mode and 1/3 bandwidth mode with foveated compression, it was difficult to spot any meaningful differences between the two. Had they handed me the headset from the start with foveated compression enabled (without telling me), I don’t think I’d have any idea it was happening, and that’s exactly how it should work.

Photo by Road to VR

There’s a few caveats of course: this was a proof of concept demo and I only got to see one piece of content (just standing around in the SteamVR home area). So I don’t know if this foveated compression approach will be valid for all or even most content. It’s possible that it won’t work so well with more complex colors, contrast, and lots of motion. The demo I saw was also on the original Vive, which has a fairly low resolution compared to what else is out there. Higher resolution (like the Vive Pro Eye, which DisplayLink plans to support, and even better lenses) might make it harder to hide the foveated compression.

However, the foveated compression is fundamentally based on DisplayLink’s existing compression technology, which works pretty darn well for today’s VR headsets, so I wouldn’t be surprised to find the the foveated approach works well too.

The post Exclusive: DisplayLink Demonstrates Foveated Compression for Better Wireless VR appeared first on Road to VR.

This content is blocked. Accept cookies to view the content.

Source link

This website uses to give you the best experience. Agree by clicking the 'Accept' button.