TrueAudio

As part of the Kaveri package, AMD is also focusing on adding and updating their fixed function units / accelerators. Due to the jump on the GPU side to GCN we now have the TrueAudio DSP to allow developers to increase the audio capabilities in game, and both the Video Codec Engine (VCE) and Unified Video Decoder (UVD) have been updated.

All the major GPU manufacturers on the desktop side (AMD, NVIDIA, Intel) are pushing new technologies to help improve the experience of owning one of their products. There are clearly many ways to approach this – gaming, compute, content consumption, low power, high performance and so on. This is why we have seen feature like FreeSync, G-Sync, QuickSync, OpenCL adoption and the like become part of the fold in terms of these graphics solutions.

AMD’s new feature is TrueAudio - a fully programmable dedicated hardware element to offload audio tasks to.

The main problem with developing new tools comes down to whether they should be implemented in a general fashion or with a dedicated element. This comes down to the distinction of having a CPU or an ASIC do the work – if the type of work is specific and never changes, then an ASIC makes sense due to its small size, low power overhead and high throughput. A CPU wins out when the work is not clearly defined and it might change, so it opens up the realm of flexibility in exchange for performance per watt.

CPUs are now significantly powerful that a range of audio based techniques are available to them and the algorithms are optimized. The only limitation in this regard is the imagination of the developer or audio artist, which actually becomes part of the problem. When implementing an audio filter on the fly to a video game, the processing via the CPU can be overly taxing, especially when the effect is persistent over a long time. The example AMD gave in their press slide deck is one of adding reverb to an audio sample. The longer the reverb, the bigger the draw on CPU resources:

AMD cites this CPU usage as the effect of one filter on one audio sample. Imagine being in a firefight situation in a video game, whereby there are many people running around with multiple gunshots, splatter audio and explosions occurring. Implementing effects on all, and then transposing audio location to the position of the character is actually computationally expensive, all for the sake of realism. This is where the TrueAudio unit comes into play – the purpose is to offload all of this onto a dedicated bit of silicon that has the pathways built in for quicker calculations.

TrueAudio is also implemented on AMD's latest-generation R9 260 and R9 290 video cards – basically anything at least GCN 1.1 and up. Meanwhile we also know that the PS4’s audio DSP is based on TrueAudio, though given the insular nature of console development it's not clear whether the APIs are also the same on both platforms. AMD for their part is working with major audio middleware plugins (wwise, Bink) in order to help develop the TrueAudio ecosystem, so even in the case where the APIs are dissimilar, middleware developers can abstract that and focus on the similarities in the hardware underneath.

As is usually the case for these additional hardware features, games will need to specifically be coded to use TrueAudio, and as such the benefits of TrueAudio will be game specific. At the same time there are not any games currently on the market that can take advantage of the feature, so the hardware is arriving before there is software ready to use it. The first three games on AMD's list that will support TrueAudio are Murdered: Soul Suspect, Thief, and Lichdom. Much like FreeSync, I expect the proof is in the pudding and we will have to wait to see how it can affect the immersion factor of these titles.

Unified Video Decoder and Video Codec Engine

I wanted to include some talk about the UVD and VCE with Kaveri as both are updated – we get UVD 4, an update to error resiliency for H.264, and VCE 2, as shown below:

Of the two blocks, the improved VCE has the more interesting improvements to discuss. With the addition of support for B frames in H.264 encoding, the resulting ability to do backwards frame prediction should help improve the resulting image quality from VCE and/or reduce the required bitrates for any given quality level. Meanwhile the addition of support for the higher quality YUV444 color space in the H.264 encoder should help with the compression of primarily linear lineart/text, which in turn is important for the clarity of wireless displays.

Llano, Trinity and Kaveri Die: Compared A Deep Dive on HSA
Comments Locked

380 Comments

View All Comments

  • jjj - Tuesday, January 14, 2014 - link

    lol now that AMD is paying you,you jumped at the other extreme , what do you get over Richland and how does that deserve a positive conclusion? (and maybe a reminder is needed A10-6800K is 140$)
  • Drumsticks - Tuesday, January 14, 2014 - link

    The author recognized that 100W TDP isn't really any different...? The 45W more mainstream range is where things are a lot more interesting, but please, ignore the 30+% gains.
  • Conduit - Tuesday, January 14, 2014 - link

    I have been waiting almost 2 years for a mobile Kaveri telling myself the wait will be worth it. Looks like it actually may be as Kaveri performs better at lower TDP's than Trinity and Richland.
  • Hubb1e - Tuesday, January 14, 2014 - link

    This guy actually gets it. These should make very nice cheap laptops able to actually play a game or two without vomiting all over themselves. At 95W the gains are not there, but at 45W it's impressive
  • JDG1980 - Tuesday, January 14, 2014 - link

    What an odd choice of benchmarks. Why not use Photoshop (which supports OpenCL and is an important real-world application) instead of Agisoft (who?) I can't help but wonder if Agisoft paid for their inclusion in Anandtech's benchmark suite.
  • ddriver - Tuesday, January 14, 2014 - link

    You may notice that the entire review is not exactly OpenCL compute rich... I mean even for gaming cards AT usually includes several OpenCL benchmarks, but not for this product, where it is supposed to be its strongest point???
  • Conduit - Tuesday, January 14, 2014 - link

    I have to say, the 45W A8-7600 kicks ass. It's competitive with the 100W A10-5800K, I think that's where the benefit of Kaveri lies, in the low TDP department.
  • UtilityMax - Tuesday, January 14, 2014 - link

    Indeed. However, I personally would like to see benchmarks that measure the power draw. The 65watt TDP Richland A10s were nearly as power thirsty as the +100watt TDP parts. A8 does look interesting.
  • thegreatjombi - Tuesday, January 14, 2014 - link

    Any chance we can get HD5200 and HD5400 benches? The 5000 series has started to catch up with AMD in terms of GPU Compute. I am curious if AMD has left Intel in the dust once again, or has Intel actually made a big enough leap to stay in the game.
  • thegreatjombi - Tuesday, January 14, 2014 - link

    Oh! It seems the 5000 series is just omitted in the CPU Performance benchmarks? Why is that?

Log in

Don't have an account? Sign up now