New Open Source Tool: Windows Audio Device Enumerator with Loopback Detection

Hey everyone! 👋

I'm excited to share a new open-source PowerShell utility I've developed for working with Windows audio devices. This tool helps you understand and work with your system's audio infrastructure, particularly for loopback recording scenarios.

## What Does It Do?

I've created two PowerShell scripts that leverage the Windows Core Audio API (MMDeviceEnumerator) to give you deep insights into your audio devices:

### 1. **Enumerate-AudioDevices.ps1** - Basic Audio Device Discovery
This script enumerates all audio interfaces on your Windows 10/11 system and shows:
- Complete list of all audio devices (playback and recording)
- Unique device IDs for each interface
- Current device state (Active, Disabled, Not Present, Unplugged)
- Ability to filter by device type (Render/Capture) or state

### 2. **Check-AudioLoopback.ps1** - Loopback Capability Detector
This enhanced version identifies which devices support loopback recording and shows:
- Friendly device names (e.g., "Speakers", "Headphones")
- Device type (Render vs Capture)
- **Loopback support status** - the key feature!
- Which devices are currently active and ready for loopback recording
- Color-coded output for easy identification

## Why Is This Useful?

### For Audio Developers
- **WASAPI Development**: Get the exact device IDs needed for WASAPI loopback recording
- **Audio Routing**: Identify all available audio endpoints programmatically
- **Testing**: Quickly see which devices are available without writing test code
- **Debugging**: Understand why certain audio devices aren't appearing in your application

### For Power Users & Content Creators
- **Screen Recording**: Identify which audio device to use for capturing system audio
- **Streaming Setup**: Understand your audio routing options
- **Troubleshooting**: See all audio devices, even hidden or disabled ones
- **Virtual Audio Cables**: Verify that virtual audio devices are properly installed

### For System Administrators
- **Inventory**: Document all audio devices on a system
- **Remote Diagnostics**: Run on remote systems to troubleshoot audio issues
- **Configuration Management**: Verify audio device states across multiple machines

## The Loopback Recording Insight

Here's something interesting I discovered while building this: **All Windows render (playback) devices inherently support loopback recording** through WASAPI Loopback Mode. You don't need special drivers or virtual cables for basic loopback - Windows provides this capability natively!

The script automatically identifies:
- Which devices are render devices (can do loopback)
- Which devices are capture devices (cannot do loopback)
- Which devices are currently active and ready to use

This is determined by the device ID prefix:
- `{0.0.0.` = Render device → Supports loopback ✅
- `{0.0.1.` = Capture device → No loopback ❌

## Example Output

When you run the loopback checker, you get output like this:

```
Device #13
----------------------------------------
Name: Speakers (Qualcomm(R) Aqstic(TM) Audio Adapter Device)
Device ID: {0.0.0.00000000}.{b65a1f33-a4b7-4151-a207-50294234d8b6}
State: ACTIVE
Type: Render (Playback)
Loopback: Loopback available (WASAPI Loopback Mode)

========================================
Summary:
  Total devices: 15
  Loopback capable: 15
  Active with loopback: 1
========================================
```

Active devices with loopback are highlighted in green, making it instantly clear which device you can use for recording system audio.

## Technical Implementation

For those interested in the technical details:
- Pure PowerShell with C# COM interop (no external dependencies)
- Direct access to Windows Core Audio API via MMDeviceEnumerator
- Proper COM object lifecycle management
- Works on Windows 10 and Windows 11
- No administrator privileges required

The implementation was an interesting challenge - getting PowerShell to properly interact with COM interfaces required careful handling of interface definitions, GUIDs, and marshaling. The result is a clean, dependency-free tool that just works.

## Get It Now

The tool is available on GitHub under the MIT License:
**[github.com/MagnusJohansson/detect-audio-device-loopback](https://github.com/MagnusJohansson/detect-audio-device-loopback)**

Simply download and run:
```powershell
.\Check-AudioLoopback.ps1
```

No installation, no dependencies - just PowerShell and Windows.

## Use Cases I'm Excited About

I built this because I needed to programmatically identify loopback-capable devices for an audio recording project, but I can see this being useful for:
- OBS Studio users wanting to understand their audio routing
- Developers building audio applications
- Musicians working with DAWs and virtual audio routing
- Anyone troubleshooting "why can't I record system audio?"

## What's Next?

I'm considering adding:
- Property enumeration (sample rates, bit depths, channel counts)
- Default device detection
- Audio endpoint volume levels
- Export to JSON/CSV for documentation

Let me know if you have suggestions or use cases I haven't thought of!

---

As always, the code is open source and contributions are welcome. If you find this useful, give it a star on GitHub or share it with others who might benefit from it.

Happy coding! 🎵

*P.S. - If you're working on audio projects and want to chat about WASAPI, loopback recording, or Windows audio APIs in general, feel free to reach out!*