Fix: Custom audio filters and loudnorm do not work with ffmpeg enabled#150
Merged
tatsumoto-ren merged 1 commit intoAjatt-Tools:masterfrom Sep 21, 2025
Merged
Conversation
Fix a bug in the ffmpeg filter processing where the `filters` string was never actually updated and remained empty (lua strings are immutable).
Member
|
Makes sense, thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a bug in the ffmpeg filter processing where filter options are never actually passed to to the
ffmpegcommand. As a consequence, both user-provided filters and the loudnorm processing did not work.The bug is caused by code that seems to assume reference semantics for strings, whereas Lua strings are immutable:
mpvacious/encoder/encoder.lua
Lines 279 to 299 in 86ab104
Note that the
filtersstring is not updated and remains empty.