Microsoft Enhances Chrome’s Audio Encoding Speed for Windows 11 ARM

Revitalized AAC Encoding for Chrome on Windows 11 ARM Devices

Great news for users involving Windows 11 and ARM devices! Chrome has successfully reinstated enhanced Advanced Audio Coding (AAC) encoding capabilities for devices powered by Snapdragon processors, including the Snapdragon X Elite and X Plus. This capability emerged following a collaboration between Microsoft and Google to resolve a critical bug affecting audio processing within the operating system.

Having monitored the situation for over a year, right from the early days of Snapdragon-powered PCs hitting the market, it’s evident that the AAC format plays a pivotal role in audio compression, providing high-quality sound files that occupy less storage space.

Benefits of Hardware-Accelerated AAC Encoding

The introduction of hardware-accelerated AAC encoding not only enhances performance for audio recording through Chrome but also significantly improves experiences on platforms such as YouTube and Spotify. This advancement means users can enjoy smoother audio playback without taxing their system resources excessively.

Understanding the Technical Background

PlatformAudioEncoder: Chrome utilizes a hardware-accelerated encoder named PlatformAudioEncoder, which effectively offloads AAC encoding tasks to integrated hardware. This strategic division enhances performance while minimizing battery and power consumption.
Bug Origins: Initially, Google disabled hardware AAC encoding on Windows ARM64 devices due to test failings, under the impression that issues stemmed from the ARM architecture. However, it became evident these complications were linked to bugs in Windows 11.
Media Foundation Role: The Media Foundation component of Windows 11, responsible for audio and video processing, played a pivotal role in the resolution of these issues as per Microsoft’s documentation.

Responding to the problems at hand, Microsoft gathered trace data and rolled out fixes in various Windows 11 builds, specifically in versions 22H2 and 23H2, targeting enhancements and fixing the audio processing issues.

Successful Collaboration and Recovery

By January 29, 2025, Google successfully reinstated the PlatformAudioEncoder following their collaborative efforts with Microsoft. As per a commit by Erik Anderson, it was clarified that the initial assumption concerning ARM64-specific problems was incorrect; this regression stemmed from Windows 11 itself. The ARM architecture simply encountered these problems earlier due to using a more recent Windows version for testing.

Enable PlatformAudioEncoder on Windows 11 ARM64

Implications for Users

With these updates, Chrome can now optimize audio encoding, delivering faster processing without excessively burdening the Snapdragon CPU. This improvement not only contributes to performance but also leads to better battery efficiency, making it a significant advantage for users with Snapdragon-based PCs.

This represents a pivotal achievement within the evolving landscape of ARM computing, paving the way for better user experiences as more reliable applications emerge.

Frequently Asked Questions

1. What is AAC encoding and why is it important for Chrome on Windows 11 ARM devices?

AAC encoding, or Advanced Audio Coding, is a highly efficient audio compression format that delivers high-quality sound without using excessive file size. Its implementation in Chrome on Windows 11 ARM devices allows users to enjoy smoother audio playback and faster audio processing, enhancing overall media experiences.

2. How does hardware-accelerated AAC encoding improve performance?

Hardware-accelerated AAC encoding leverages specialized components within the device’s hardware, allowing audio encoding tasks to be executed more efficiently. This leads to improved performance, lower CPU usage, and extended battery life, especially on devices using Snapdragon processors.

3. What was the cause of the initial AAC encoding failure in Chrome on ARM?

The initial failure of AAC encoding on Windows 11 ARM devices was mistakenly attributed to the ARM architecture. However, investigations revealed that the root cause was a bug in Windows 11’s Media Foundation, which required the involvement of Microsoft engineers to rectify.

Source & Images