Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minor: fix ffmpeg 7 compatibility #1274

Merged
merged 1 commit into from
May 19, 2024
Merged

Conversation

totallytavi
Copy link
Contributor

* Add capture for all whitespace
* Change copied from fluent-ffmpeg#1265, minus the style changes
@coveralls
Copy link

Pull Request Test Coverage Report for Build 9143973524

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 90.801%

Totals Coverage Status
Change from base Build 6856211874: 0.0%
Covered Lines: 1145
Relevant Lines: 1261

💛 - Coveralls

@njoyard njoyard merged commit ac561a5 into fluent-ffmpeg:master May 19, 2024
8 checks passed
@njoyard
Copy link
Member

njoyard commented May 19, 2024

Fix published in 2.1.3

alexger added a commit to alexger/node-fluent-ffmpeg that referenced this pull request May 23, 2024
when running with ffmpeg 7, some formats are not properly parsed
by `getAvailableFormats` and thus can not be used.

ffmpeg 7 adds a new column to the output of `-formats` command:
```
..d = Is a device
```

fluent-ffmpeg#1274 partially
addressed that issue, but only for formats where the new column is a space.

Formats that have `d` do not match the existing regex and are silently ignored.

One example is `lavfi` format which right now can not be used due to this issue.

The fix is to ammend the parsing regex to expect an optional space or 'd'. This way both
new and old versions of ffmpeg are supported.

I've added a test for `lavfi` which fails without this fix when run with
ffmpeg 7.
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.

Fix to Output format [***] is not available
3 participants