# Exploring more formats, channels and audio controls

> A wider Windows audio experiment before the later simplification.

Canonical page: https://pyrosoft.pro/blog/exploring-more-formats-channels-and-audio-controls

Live development journal; no publication date.
Work period: 2025-11-14 to 2025-11-14
Updated: 2026-10-20

Once the speaker and microphone endpoints existed, the next experiment was expanding what they advertised to Windows. The November 14 work added much broader format tables, then multichannel and signal-processing mode changes, followed by topology and property-handler work for audio controls.

The format commit included PCM and IEEE floating-point entries across more sample rates. The speaker work also explored surround configurations, while both endpoint paths gained additional signal-processing mode declarations. In practical terms, the goal was to give applications more ways to negotiate an audio stream.

The following change added tone-control, effects and acoustic-echo-cancellation related nodes and handlers using WDK patterns. Those additions are visible in the source history. They should be described as implementation work, because a topology node or exposed property alone doesn't prove the expected processing is audible, effective or stable in a real call.

That's an easy distinction to lose when reading a feature list. Seeing an option in Windows, successfully opening a stream and measuring what comes out of that stream are separate checks. A wider table also creates more combinations to test for channel layout, sample conversion, long-running delivery and cleanup.

This was a short, concentrated stage of development, and it wasn't the final shape of the driver. The January work later removed much of the extra topology and broad format expansion. I'm including this chapter because it explains that decision and prevents the later source from looking like an accidental loss of undocumented features.

For anyone following the project, this is what was being explored at that point. The next milestone is about bringing the supported surface back to something more focused, with actual stream behavior still the standard for compatibility claims.