NVIDIA Works: ANSEL & VRWorks Audio

Along with the various hardware aspects of Pascal, NVIDIA’s software teams have also been working on new projects to coincide with the Pascal launch. These are a new screenshot tool, and a new audio simulation package based on path traced audio.

We’ll start with NVIDIA’s new screenshot utility. Dubbed ANSEL, after famous American environmental photographer Ansel Adams, ANSEL is a very different take on screenshots. Rather than taking screenshots from the player’s perspective at the game rendering resolution, ANSEL allows for an entire scene to be captured at a far higher resolution than with standard screenshots. NVIDIA is pitching this as an art tool rather than a gaming tool, and I get the impression that this is one of those pie-in-the-sky kind of ideas that NVIDIA’s software group decided to run with in order to best show off Pascal’s various capabilities.

At its core, ANSEL is a means to decouple taking screenshot from the limitations of the player’s view. In an ANSEL-enabled application, ANSEL can freeze the state of the game, move the camera around, and then generate a copious amount of viewports to take screenshots. The end result is that ANSEL makes it possible to generate an ultra-high resolution 360 degree stereo 3D image of a game scene. The analogy NVIDIA is working towards is dropping a high quality 360 degree camera into a game, and letting users play with it as they see fit.

But even this isn’t really a great description of ANSEL, as there isn’t anything else like it to compare it to. Some games have offered 360 degree capture, but they haven’t done so at any kind of resolution approaching what ANSEL can do. And this still doesn’t touch features such as HDR (FP16) scene capture or the free camera.

Under the hood, ANSEL is at times a checklist for Pascal technologies (though it does work with Maxwell 2 as well). In order to capture scenes at a super high resolution, it forces a scene to its maximum LOD and breaks it down into a number of viewports, implemented efficiently using SMP. To demonstrate this technology NVIDIA put together a 4.5Gpix image rendered out of The Witcher 3, which was composed of 3600 such viewport tiles. Meanwhile stitching together the individual tiles is a CUDA based rendering process, which uses overlapping tiles to resolve any tone mapping conflicts. Finally, ANSEL captures images before they’re actually sent to a display, grabbing HDR images (in EXR format0 in games that support HDR.

Meanwhile given its level of deep interaction with games, ANSEL does require individual game support to work. This is in the form of a library provided by NVIDIA, which helps ANSEL and NVIDIA’s driver make sense of a scene and pause the simulation when necessary. Unsurprisingly, NVIDIA is eager to get ANSEL into more games – it just launched on Mirror’s Edge: Catalyst – and as a result is touting to developers that ANSEL is easy to implement, having taken only 150 lines of code on The Witcher 3.

Ultimately NVIDIA seems to be throwing ANSEL at the wall here to see what sticks. But it should be neat to see what users end up doing with the technology,

VRWorks Audio

Not to be outdone by the ANSEL team, other parts of NVIDIA’s software group has been working on a slightly different kind of project for NVIDIA: audio. As a GPU company, NVIDIA has never been deeply involved with audio (not since getting out of the chipset business, at least), but with the current focus on VR, they are taking a crack at it in a new way.

VRWorks Audio is the latest library as part of NVIDIA’s larger VRWorks suite. As given away by the name, this library is focused on audio, specifically for VR. In a nutshell, VRWorks is a full audio simulation library, using path tracing to power the simulation. The goal of VRWorks Audio is to provide a realistic sound simulation for VR, to further increase the apparent realism.

Under the hood, VRWorks audio leverages NVIDIA’s existing OptiX path tracing technology. Only rather than tracing light it’s used to trace sound waves. Along with simulating audio propagation itself – including occlusion and reverb – VRWorks Audio is also able to run the necessary Head Related Transfer Functions (HRTFs) to reduce the simulation down to binaural audio for headphones.

All of this is, of course, executed on Pascal’s CUs in a manner similar to path tracing or PhysX, running alongside the main graphics rendering thread. The amount of processing power required for VRWorks Audio can vary considerably depending on the detail desired (particularly the number of reflections); for NVIDIA’s VR Funhouse demo, VR Works audio can occupy most of a GPU on its own.

Ultimately, unlike some of the other technologies presented by NVIDIA, VRWorks Audio is in a relatively early stage. As a result while NVIDIA is shipping the SDK, there aren’t any games that are announced to be using it at this time, and if it gets any traction it’ll be farther into the future before we see the first games using it. That said, NVIDIA is already reaching out to the all-important middleware vendors on the subject, and to that end their own VR Funhouse demo is using FMOD with a VRWorks Audio plugin to handle the sound, demonstrating that they already have VRWorks Audio working with the popular audio middleware.

GPU Boost 3.0: Finer-Grained Clockspeed Controls Meet the GeForce GTX 1080 & GTX 1070 Founders Edition Cards
POST A COMMENT

200 Comments

View All Comments

  • Ninhalem - Wednesday, July 20, 2016 - link

    There's 32 freaking pages in this review. Maybe people have other jobs instead of writing all day long. Did you ever think of that?

    I'll take quality and a long publishing time over crap and rushing out the door.
    Reply
  • Stuka87 - Wednesday, July 20, 2016 - link

    Thanks for the extremely in depth review Ryan! Reply
  • cknobman - Wednesday, July 20, 2016 - link

    I cannot help feel just a bit underwhelmed.

    Of course these Nvidia cards kick some major butt in games that have always favored Nvidia but I noticed that in games not specifically coded to take advantage of Nvidia and furthermore games with DX12 that these cards performance advantage is minimal at best vs an old Fury X with half the video RAM.

    Then when you take into account Vulcan API and newer DX12 games (which can be found elsewhere) you see that the prices for these cards is a tad ridiculous and the performance advantage starts to melt away.

    I am waiting for AMD to release their next "big gun" before I make a purchase decision.
    I'm rocking a 4k monitor right now and 60fps at that resolution is my target.
    Reply
  • nathanddrews - Wednesday, July 20, 2016 - link

    1080 is close to being that 4K60 card, but can't quite cut it. I'm waiting for "Big Vega" vs 1080Ti before dropping any money. Reply
  • lefty2 - Wednesday, July 20, 2016 - link

    Great review - one of the few that highlights the fact the Pascal async compute is only half as good as AMD's version. Async compute is a key feature for increasing performance in DX12 and Vulkan and that's going to allow the RX 480 to perform well against the GTX 1060 Reply
  • Daniel Egger - Wednesday, July 20, 2016 - link

    "... why the memory controller organization of GP104 is 8x32b instead of 4x64b like GM204"

    Sounds like it's the other way around.
    Reply
  • Ryan Smith - Wednesday, July 20, 2016 - link

    No, that's correct. 8 32bit wide controllers rather than 4 64bit wide controllers.

    http://images.anandtech.com/doci/10325/GeForce_GTX...

    http://images.anandtech.com/doci/8526/GeForce_GTX_...
    Reply
  • DominionSeraph - Wednesday, July 20, 2016 - link

    >It has taken about 2 years longer than we’d normally see

    ... for a review of a flagship card to come out
    Reply
  • sgeocla - Wednesday, July 20, 2016 - link

    The old Maxwell was so optimized it was always full and didn't even need Async Compute. The new Pascal is so much more optimized that it even has time to create the "holes" in execution (not counting the ones in your pocket) that were "missing" in the old architecture to be able to benefit for Async Compute. Expect Volta to create even more holes (with hardware support) for Async Compute to fill. Reply
  • tipoo - Wednesday, July 20, 2016 - link

    That's demonstrably untrue.

    http://www.futuremark.com/pressreleases/a-closer-l...

    Plenty of holes that could have been filled in Maxwell.
    Reply

Log in

Don't have an account? Sign up now