-
-
Notifications
You must be signed in to change notification settings - Fork 685
fix(dsp): BS.1770 integrated loudness misses the 997 Hz calibration anchor #860
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
Merged
lucasnewman
merged 2 commits into
Blaizzy:main
from
gaoflow:fix-bs1770-integrated-loudness
Jul 31, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is quite correct?
hop_samplesis getting rounded up front now and will accumulate error at 11.025kHz (aka 44.1kHz / 4) since the hop sizes won't be exactly uniform, right? Can you add a test for 11.025kHz to make sure the hop sizes are correct?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hop is now a constant integer, so spacing is exactly uniform — that's the fix, not the problem: the old code derived each boundary from
block_size * block_index * step * ratein floats, which is what could drift. At 11.025 kHz the hop is round(1102.5) = 1102 samples (0.1 s to the nearest sample, per BS.1770), and every block starts at an exact integer multiple of it. Addedtest_integrated_loudness_block_hop_11025hz(7c44e39) asserting the block/hop values, uniform spacing, and the 997 Hz anchor (−26.010 at 48 kHz vs −25.969 at 11.025 kHz, within the per-rate filter redesign tolerance).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, fair enough, we're splitting hairs a bit and I agree the uniform step is likely ideal so I'm good with this. Thanks!