Merge metering standards#4
Merged
Merged
Conversation
jlnstrk
force-pushed
the
jlnstrk/merge-standards
branch
2 times, most recently
from
October 31, 2025 15:01
76d4831 to
4286216
Compare
jlnstrk
force-pushed
the
jlnstrk/merge-standards
branch
from
October 31, 2025 15:02
4286216 to
1427623
Compare
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
2 participants
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.
Combines the
peak-sampleandtrue-peakmetering standards into one.While
true-peakgives a better approximation of actual perception of a signal's loudness,peak-samplemakes it easy to adjust a signal based on metering without introducing clipping. This is because at any given time, the peak amplitude is known, and consequently so is the maximum factor that may be applied to it so that it doesn't exceed 1.Combining both into one metering result should allow us to achieve both goals.