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

Auto LUFS tester for patches. #6833

Open
Andreya-Autumn opened this issue Feb 3, 2023 · 0 comments
Open

Auto LUFS tester for patches. #6833

Andreya-Autumn opened this issue Feb 3, 2023 · 0 comments
Labels
Content Issues related to Surge bundled content (skins, wavetables, patches...) Discussion Have A Plan The issue has a description of how we will solve it, just we haven't done it yet
Milestone

Comments

@Andreya-Autumn
Copy link
Collaborator

Context: Discussing the patch library over on the Discord, we're trying to clarify the expectations on loudness in the patch library. It would be good to have a clear loudness target for patch creators, and it would also be good if the factory patches all hit that target.

Tricky thing as always is: human-perceived loudness is only weakly correlated with peak levels.
It would be trivial to automatically adjust all patches to peak at -1db under reasonable playing conditions, but that would result in some patches sounding much louder than others.

LUFS is the closest thing we have to a measurement of actual perceived loudness. In order to avoid doing all this work manually, it'd be useful to make a little tester that takes a MIDI input, plays it with all relevant patches, then outputs a LUFS readout for each patch.

It should be able to do this per category, since mono vs poly, bass vs lead etc etc will require different test MIDI cases.

This will help: https://github.com/klangfreund/LUFSMeter

@Andreya-Autumn Andreya-Autumn added UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. Content Issues related to Surge bundled content (skins, wavetables, patches...) Discussion Have A Plan The issue has a description of how we will solve it, just we haven't done it yet labels Feb 3, 2023
@Andreya-Autumn Andreya-Autumn added this to the Currently Unscheduled milestone Feb 3, 2023
@mkruselj mkruselj removed the UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. label Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content Issues related to Surge bundled content (skins, wavetables, patches...) Discussion Have A Plan The issue has a description of how we will solve it, just we haven't done it yet
Projects
None yet
Development

No branches or pull requests

2 participants