Skip to content

fix: parse legacy and modern FFmpeg format columns - #440

Merged
bramp merged 1 commit into
bramp:mainfrom
mvanhorn:fix/408-ffmpeg-format-columns
Oct 10, 2026
Merged

bramp merged 1 commit into
bramp:mainfrom
mvanhorn:fix/408-ffmpeg-format-columns

Conversation

@mvanhorn

Copy link
Copy Markdown
Contributor

The regex accepts an optional space or d after the two capability columns, supporting both legacy and modern output while preserving the existing capability capture. A new fixture and test cover modern formats and devices, malformed rows, and caching of the parsed result.

FFmpeg.formats() returns an empty list when FFmpeg prints the newer format table, preventing callers from discovering supported formats. The parser expected only the demuxing and muxing columns before the format name. Newer output includes a third column containing a space or a device marker, so those rows failed to match.

FFmpegTest passed all 10 tests with no failures, errors, or skips.

Fixes #408

AI was used for assistance.

The regex accepts an optional space or `d` after the two capability
columns, supporting both legacy and modern output while preserving the
existing capability capture. A new fixture and test cover modern formats
and devices, malformed rows, and caching of the parsed result.

Fixes bramp#408
@bramp

bramp commented Oct 10, 2026

Copy link
Copy Markdown
Owner

Very cool. Thanks!

@bramp
bramp merged commit 9663ac0 into bramp:main Oct 10, 2026
4 checks passed
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.

Formats not parsed for Versions >6.1.1

2 participants