Skip to content

fix(windows): WASAPI 16-bit PCM fallback and CLAP scan JSON extraction - #2

Open
lxndrbe wants to merge 1 commit into
maolan:mainfrom
lxndrbe:main
Open

fix(windows): WASAPI 16-bit PCM fallback and CLAP scan JSON extraction#2
lxndrbe wants to merge 1 commit into
maolan:mainfrom
lxndrbe:main

Conversation

@lxndrbe

@lxndrbe lxndrbe commented Aug 3, 2026

Copy link
Copy Markdown

Two Windows-specific fixes:

  1. WASAPI: Fall back to 16-bit integer PCM when the audio device does
    not support 32-bit IEEE float. Most consumer onboard audio devices
    (Realtek, etc.) only support 16/24-bit integer formats in shared mode.
    The hardcoded 32-bit float format caused 'WASAPI device does not support
    32-bit float at 48000 Hz' and AUDCLNT_E_UNSUPPORTED_FORMAT errors.

  2. CLAP scan: Extract JSON payload from mixed stdout. CLAP plugin DLLs
    (e.g. Charlatan3) write debug output to stdout during DllMain/init,
    which corrupts the JSON output from the plugin-host scanner. Now we
    locate the first '{' and parse from that position onward.

Both fixes tested on Windows 11.

Two Windows-specific fixes:

1. WASAPI: Fall back to 16-bit integer PCM when the audio device does
   not support 32-bit IEEE float. Most consumer onboard audio devices
   (Realtek, etc.) only support 16/24-bit integer formats in shared mode.
   The hardcoded 32-bit float format caused 'WASAPI device does not support
   32-bit float at 48000 Hz' and AUDCLNT_E_UNSUPPORTED_FORMAT errors.

2. CLAP scan: Extract JSON payload from mixed stdout. CLAP plugin DLLs
   (e.g. Charlatan3) write debug output to stdout during DllMain/init,
   which corrupts the JSON output from the plugin-host scanner. Now we
   locate the first '{' and parse from that position onward.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant