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

adding a sound volume property for the postprocessor #181

Open
Techbot121 opened this issue Sep 29, 2018 · 4 comments
Open

adding a sound volume property for the postprocessor #181

Techbot121 opened this issue Sep 29, 2018 · 4 comments

Comments

@Techbot121
Copy link
Member

Techbot121 commented Sep 29, 2018

This is something I've been thinking for a while.
When the preprocessor runs it gets the length of the soundsample, wouldn't it be also useful to have other information as well? For example sample-volume (or similar) so you could filter all sounds by volume and potentially, for instance, filtering out loud sounds locally.

@PotcFdk
Copy link
Member

PotcFdk commented Sep 29, 2018

Having an existing setup (i.e. the preprocessor) that inspects all files makes it easy(-ish) to further enhance it.
I've always thought about what else might be useful other than just the duration itself.
I'll look into volume/gain analysis and report back as to how easy it would be.

@PotcFdk
Copy link
Member

PotcFdk commented Sep 29, 2018

Ok, apparently it might be possible with just ffmpeg/libav.
To be specific, libavfilter's loudnorm filter seems to be able to do what we'd be interested in, but I have no idea how to use it.
Using a separate lib would be an idea, or just slapping standard ReplayGain on all files and transferring that to the lists.
Needs more investigation.

@Techbot121
Copy link
Member Author

or eventually calculate it yourself with a RMS measurement.

@edunad
Copy link
Contributor

edunad commented Jul 6, 2019

can we not cap the ^ to the listening client? Would not remove loud annoying sounds but it would at least prevent my ears from exploding

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

No branches or pull requests

3 participants