I tried running that one in conjunction with the VST support plugin for Music Bee, but I haven't had any luck yet.
Still looking into alternatives.
The documentation indicates that there is both a stand-alone and VST version in the TT-DR installer--did you try the standalone version? I was thinking that might be convenient to run via MB Tools on selected libray files. I'd try it myself but DR analysis has really no interest for me, but Mr. Trev might give it a shot. I did extract the installer via 7-Zip and it shows a "DR-Offline.exe" file and its own folder structure with own graphics as well as a VST dll in a separate folder.
FOR %a IN ("*.mp3") DO (ffmpeg -i "%a" -af ebur128=peak=true -f null - 2>&1 | FINDSTR /BIC:" ") Integrated loudness:
I: -12.9 LUFS
Threshold: -23.3 LUFS
Loudness range:
LRA: 11.2 LU
Threshold: -33.3 LUFS
LRA low: -20.7 LUFS
LRA high: -9.5 LUFS
True peak:
Peak: 0.2 dBFSFOR %a IN ("*.mp3") DO (ffmpeg -i "%a" -af ebur128=peak=true -f null - > %a-output.txt 2>&1)Neat! If this were a MB plug-in that optionally writes the info to metadata as well, this would be well useful. With additional txt files (if I understood correctly) I'll need to see if this would fit my library. But very interesting to see this realized either way!
Thanks a lot!
c.
Nice. I'll play around with this later.
Quick question…
Am I correct to assume that tag 12 (LRA) is the equivalent of the numbers spit out on http://dr.loudness-war.info?
Does this also give an album average or just on a per track basis?
Nice. I'll play around with this later.
Quick question…
Am I correct to assume that tag 12 (LRA) is the equivalent of the numbers spit out on http://dr.loudness-war.info?
Does this also give an album average or just on a per track basis?
Yes - LRA (Loudness Range) is the rough equivalent to the dynamic range number spit out by MAAT.
https://ask.audio/articles/demystifying-the-confusion-around-loudness-metering-levels
It uses a different algorithm so it doesn't always line up perfectly, but EBU R128 is generally considered a better standard.
This does not currently give an album-rating. To be honest, I'm not sure why that number is useful beyond comparing/complaining about the Loudness War. I'm not an audio engineer, so let me know if there's another reason.
Thanks! It would probably be best to move the whole content of your Reply#5 post to the the first post, so finding the current version and the installation/usage instructions is easy.
System.IO.FileNotFoundException: Could not find file 'C:\Users\User\AppData\Roaming\MusicBee\Dependencies\LoudnessTextFiles\Broken,Beat&Scarred-Metallica-FLACaudiofile-625.txt'.
File name: 'C:\Users\User\AppData\Roaming\MusicBee\Dependencies\LoudnessTextFiles\Broken,Beat&Scarred-Metallica-FLACaudiofile-625.txt'
Is it essential to name the custom tags...? I didn't...
This was the problem...
C:\Users\User\AppData\Roaming\MusicBee\Dependencies>ffmpeg
This version of C:\Users\User\AppData\Roaming\MusicBee\Dependencies\ffmpeg.exe is not compatible with the version of Windows you're running.
Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
I downloaded the latest static, 32-bit x86 build from https://ffmpeg.zeranoe.com/builds/ and I can now run ffmpeg from the command line. And the EBU R128 tagger now runs, launching lots of copies of ffmpeg, taking quite a long time on my bedroom media all-in-one PC...
So it looks like your plug-in will need to have 32-bit & 64-bit option downloads, or else refer people to get their own ffmpeg.
I might also suggest the plug-in be configurable to allow the maximum number of ffmpeg instances it will launch in parallel to be user specified.
Thanks for this plug-in; I've been looking for a DR tagger for some time. I'll have to install it on my main PC to get it to process all 70k tracks I've got...
Great idea and work zkhcohen!
I have a suggestion/request:
Would it be possible to add the option to populate a custom tag with the Integrated Loudness of a track, taking into account the adjustment that will be made by the calculated adjustment value present in the Tack Gain tag?
Then you could easily see if the resulting integrated loudness after gain adjustment is what you are aiming for.
For example, I am usually aiming for -21 LUFS for my non-classical library tracks. (-3 on MB's slider)
But currently it is hard to know if tracks that have a track gain tag present were calculated with the aim of -21 LUFS, and thus, how loud they will actually be playing.
Would you simply want the option to map the input_i parameter with with IL and MusicBee's track gain, or did you want to just input your own target value?
Would you simply want the option to map the input_i parameter with with IL and MusicBee's track gain, or did you want to just input your own target value?
How I am guessing this would work is that your plugin does everything it is already doing, but additionally looks for an existing track gain tag value in a track, and adds/substracts that value to/from the integrated loudness value that your plugin has calculated, and writes that value to a custom tag.
So e.g. if a track already has a track gain tag present of let's say +3 dB, and your plugin calculates an integrated loudness of -20 LUFS for it, you can have it write a custom tag saying -17 LUFS.
That will make it possible to see how loud the track will actually be playing.
That is something MusicBee cannot do.
Thanks for the update and the additions.
I'm sorry to say that after only doing very quick testing I have had a few crashes, error popups, MB closing, etc.
Also I noticed that for one album that I checked for Current Loudness, the plugin reported various levels between -140 and -190 LUFS for the tracks.
(which obviously can't be right, since in this specific case it should have been -23 LUFS, and the same value for all tracks)
This reply is just a primal and brief notification of issues I experienced.
Of course you deserve and need a more detailed report on when what and how these issues occur, and I will do that within a couple of days.
But considering the MB crashes I experienced I thought to let you know this asap.
Thanks for the update and the additions.
I'm sorry to say that after only doing very quick testing I have had a few crashes, error popups, MB closing, etc.
Also I noticed that for one album that I checked for Current Loudness, the plugin reported various levels between -140 and -190 LUFS for the tracks.
(which obviously can't be right, since in this specific case it should have been -23 LUFS, and the same value for all tracks)
Did you overwrite the config file with the new one I put in the Dependencies folder?
Did you overwrite the config file with the new one I put in the Dependencies folder?
I used a recent and clean portable MB installation that didn't have your plugin installed before.
(I have a couple of those for different usage/testing)
If you still get miscalculations, can you send me the file?
A quick observation:
The weird and very high 'current loudness' values are probably due to regional settings. I noticed that I have Track Gain decimals comma separated, but the values that your plugin writes are period separated.
Except for the current loudness, which is comma separated again.
Something is wrong.
When I have tracks with existing Track Gain values, their TG values are displayed correctly in the column browser.
If I then only enable your plugin (not even running it on the files) and I rescan the files, the TG values for all the files in the column browser suddenly display as "0.0 dB".
(https://i.imgur.com/0HyZDCT.png)
If after that I disable your plugin, restart MB, and rescan the files, they will show the correct TG value in the column browser again.
Any chance you can send me your MB settings?
Any chance you can send me your MB settings?
I'll do better, I've send you my complete portable testing installation.
(see PM)
Thanks for taking a further look at this.
What surprised me also about this, is that when you have only activated the plugin but haven't performed any action with it, it obviously affects how MusicBee displays this field.
So it looks like it is running some process in the background even when you have not triggered any action. Is that needed?
I was expecting that only when you run it, it would do an analysis, then write the requested tags, and then terminates.
Is it however nesting itself a bit deeper into the functioning of MusicBee?
Is this plugin still being actively developed?
Is this plugin still being actively developed?
You make a lot of great suggestions, but I haven't had the time to work on any of my plugins for a very long time.
Unfortunately I barely knew what I was doing when these were written, so there are a lot of improvements that could be made.
That being said, the source code for all of my plugins is public on my GitHub: https://github.com/zkhcohen/mb_Loudness-Analyzer
Hi zkhcohen.
Is it safe to assume this plugin will not be developed any further?
(I'm probably asking the obvious, since you have already explained elsewhere how busy you are in real life these days)
Hi zkhcohen.
Is it safe to assume this plugin will not be developed any further?
(I'm probably asking the obvious, since you have already explained elsewhere how busy you are in real life these days)