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

Max. momentary erratic results with EBU test files(?) #93

Closed
nofishonfriday opened this issue Oct 11, 2018 · 3 comments
Closed

Max. momentary erratic results with EBU test files(?) #93

nofishonfriday opened this issue Oct 11, 2018 · 3 comments

Comments

@nofishonfriday
Copy link

@nofishonfriday nofishonfriday commented Oct 11, 2018

Hello,

first a bit of background:
I'm a contributor to the SWS Extension (Github repo), an extension for the REAPER DAW. which implements offline Loudness scanning using libebur128.

I've scanned the files from the EBU loudness test set with our Loudness scanner and they all pass, except for test set 13.
In tech3341 it specifies for these files:

Max M = −23.0 ±0.1 LUFS, for each segment

However with our current implementation we get the following results:

loudness for libur128

I'm now trying to determine if there's a bug in our implementation (we use a modified version of libebur128) or if this may be an issue with the library itself.

Thank you.

@jiixyj
Copy link
Owner

@jiixyj jiixyj commented Oct 11, 2018

Huh, this is weird. We have some tests for test set 13, and they run successfully:

#define TEST_MAX_MOMENTARY(filename, expected) \

Maybe this helps tracking down the problem.

@nofishonfriday
Copy link
Author

@nofishonfriday nofishonfriday commented Oct 11, 2018

Ah missed these tests, thanks for pointing me to it.
So the issue must be on our end, that's at least good to know.

Closing this, thanks again.

@audionuma
Copy link
Contributor

@audionuma audionuma commented Oct 11, 2018

See

/* 10 ms buffer/ 100 Hz refresh rate as 10 Hz refresh rate fails on several tests */
.

The EBU test files for max momentary cannot produce expected result with a 75 % (100 ms) overlap when measuring momentary blocks. In some of the test files, the audio blocks of length 400 ms are offseted to multiple of 50 ms, which means you never get a full 400 ms block of audio measured, therefore an underestimation of the max momentary.

This has to be taken into account when implementing max momentary measure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants