FLAC playback fails on Windows with exit status 0xbebbb1b7

[pankrusheff]

Description

FLAC files fail to play on Windows 11 with error:

ERR: decode: ffmpeg decode: exit status 0xbebbb1b7

MP3 files play correctly on the same system.

Steps to reproduce

1. Install cliamp v1.27.8 (cliamp-windows-amd64.exe) on Windows 11
2. Install ffmpeg 8.1 (via winget install ffmpeg)
3. Run cliamp.exe path/to/file.flac

Expected behavior

FLAC files should play normally, as ffmpeg decodes them without issues:

ffmpeg -i file.flac -f wav -t 5 NUL

completes successfully.

Environment

• OS: Windows 11 Pro 10.0.26200
• cliamp: v1.27.8 (cliamp-windows-amd64.exe from releases)
• ffmpeg: 8.1-full_build (Gyan.dev, installed via winget)
• FLAC files: 44100 Hz, stereo, s16

[pankrusheff]

Additional note: According to the README, FLAC should be supported natively (ffmpeg is listed as required only for AAC, ALAC, Opus, and WMA). However, on Windows the player first reports:

ERR: decode: ffmpeg is required to play .flac files — install it with your package manager

After installing ffmpeg, the error changes to:

ERR: decode: ffmpeg decode: exit status 0xbebbb1b7

So it seems the native FLAC decoder doesn't work on Windows, and the ffmpeg fallback also fails.

[pankrusheff]

Update: The issue appears to be related to special characters in directory/file names, not FLAC decoding itself.

Failing path (with brackets):

F:\VA - Steven Wilson Presents Intrigue (2023) [CD FLAC] {EDSL0133}

Working path (no special characters):

F:\Steven Wilson - Intrigue 2023

After renaming the folder to remove (), [], and {} characters, FLAC playback works correctly on Windows.

It seems cliamp (or its ffmpeg invocation) doesn't properly escape/quote file paths containing parentheses and brackets on Windows.