Author Topic: A new loudness measurement tool from the un4seen folks  (Read 2283 times)

sveakul

  • Sr. Member
  • ****
  • Posts: 2469
Saw a new thread in the Bass forums about their new library/tool bassloud.dll that can perform EBU R128 loudness and true-peak measurements.  Other methods are in use now for similar normalization in MusicBee but the "live/windowed" thing would be cool:
"It's main purpose is to measure the loudness of entire files (using the BASS_LOUDNESS_INTEGRATED option), which can then be used to normalize the loudness of them. But it can also be used for live/windowed loudness measurements (the BASS_LOUDNESS_CURRENT option), which could be the basis of an auto-gain feature."

https://www.un4seen.com/forum/?topic=20129.0
Last Edit: June 07, 2023, 04:41:59 AM by sveakul

hiccup

  • Sr. Member
  • ****
  • Posts: 7884
Thanks for keeping an eye on stuff like this sveakul!

Another benefit of implementing this as a replacement for the current algorithm might be performance. (speed)
Do you happen to know if it is able to use multi-threaded processing?
MusicBee's current implementation doesn't, and therefor it is quite slow.

sveakul

  • Sr. Member
  • ****
  • Posts: 2469
Not sure about the multi-threading.  Using the loudscan.exe test file that was included in the zip (also has the usual bass help file that needs a developer to really interpret) I got the following result just running that against a single mp3:



I'm sure that has to be a way to have that data added to a custom column or file tag as part of a regular file scan in MusicBee;  hopefully Steven will take a look at the possibilities.


hiccup

  • Sr. Member
  • ****
  • Posts: 7884
This has recently been updated and released with full documentation, https://www.un4seen.com/download.php?bassloud24 .
Are you envisioning new possibilities when that would be used by MusicBee?
One aspect that would interest me, is if it will allow to make use of more cpu cores when analysing tracks.
The current implementation can be a bit slow because it can only use 1 core.

sveakul

  • Sr. Member
  • ****
  • Posts: 2469
Well it would be cool if Steven could integrate this new functionality into MusicBee in a way so that getting the values it produces could be optionally chosen as Track Information additions, and/or part of the "Set displayed fields" choices in track list displays.  Or even as a context menu choice like "Show LUFS/LRA/Peak."