Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Dynamic Range plugin (Read 16362 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Dynamic Range plugin

Reply #100 –
Quote from: omasciarotte on
Quote from: darkflame23 on
We now have DR built into Foobar natively, with this component (and the True Peak Scanner), so can use what we need. It's brilliant for mastering as I can get an instant readout of many different variables, track to track.

Since you’re a mastering engineer, I have to remind you that foobar’s “DR” plug–in is an approximation.

Yeah, it's not a problem for me as I've never taken much notice of DR. I mostly use LUFS-I and peak LUFS-S to give me a quick idea of how loud a track is likely to be before listening. As I said above, those figures have documentation and standardisation, and are widely used in the audio industry, unlike DR which I've rarely heard an engineer refer to.

Re: Dynamic Range plugin

Reply #101 –
@Case

Hi
first i want to thank you for the plugin
do you think could be possibile to add in the Dr Meter context menu ->save results logs to  ?
or maybe in the Dr Meter Results -> save results logs to ?
would so useful and easy .., than change the option in the advanced options
again thanks for the plugin
cheers

Re: Dynamic Range plugin

Reply #102 –
See image

Re: Dynamic Range plugin

Reply #103 –
@Case‍

Question. The dialog shows RMS and Peak values as dBFS, but the log file shows them as dB.
If you ever get in a position to update this component for whatever reason, would it be too much to ask to also show those values as dBFS in the log file?

Now that I am aware of the difference it's not that big of an issue, but it looked confusing at first as these differ from the dBTP values.

crash with mixed file types

Reply #104 –
Hello,

Thank you very much for making a 64-bit version of this.  Installed and used it extensively this past weekend, and it performed extremely well with one exception:  if a folder contained files of mixed type (FLAC + MP3, for example), it crashed foobar2000.  Though probably not very common with single albums, I have multiple folders of mixed files downloaded from various online sellers that would love it if this could be corrected.  Appreciate the consideration.

Thanks,

Steve

Re: Dynamic Range plugin

Reply #105 –
Quote from: Just_Addict on
The dialog shows RMS and Peak values as dBFS, but the log file shows them as dB.
If you ever get in a position to update this component for whatever reason, would it be too much to ask to also show those values as dBFS in the log file?
I tried to keep the log as close to old component's format as possible, that's why I used the same wrong units. Units corrected in version 0.5 of the component.

Quote from: OtherSteve on
if a folder contained files of mixed type (FLAC + MP3, for example), it crashed foobar2000.
That should not be a problem, I was fully prepared for such scenario and log will even report different codecs in use. I found single crash entry from crash logger from this component, it was related to scanning highly corrupted tracks and some tracks looked like they couldn't get decoded at all. The log writer had too light error checking for scan results and it tried to access per-channel data that it never managed to scan.
Should be fixed in the just released version 0.5. I'd appreciate it if you could test with the same files that failed earlier.

Re: Dynamic Range plugin

Reply #106 –
Quote from: Case on
That should not be a problem, I was fully prepared for such scenario and log will even report different codecs in use. I found single crash entry from crash logger from this component, it was related to scanning highly corrupted tracks and some tracks looked like they couldn't get decoded at all. The log writer had too light error checking for scan results and it tried to access per-channel data that it never managed to scan.
Should be fixed in the just released version 0.5. I'd appreciate it if you could test with the same files that failed earlier.

I gave this a test and using the 0.5 version Foobar does in fact crash, it did 3 times in a row on me.  Then after the 3rd crash and restart I was able to run them together without issue on several attempts.  So at this point, it is random, but did happen.....  I tested a FLAC and short MP3 file together.    

Re: Dynamic Range plugin

Reply #107 –
Thank you for persistence. There was nothing in the crash logger as this heap corruption killed even foobar's minidump writer. It took a few tries with different track counts but I managed to trigger the crash here too. I had gotten a little too carried away with c++ templates. There were several bugs like misconception that comparing pfc::string8 with < and > would work for comparing sort orders and the worst issue was use of memmove to reorder the codec arrays.
Now albums consisting of multiple codecs should no longer crash the log writer with version 0.6.

Re: Dynamic Range plugin

Reply #108 –
Quote from: Case on
Thank you for persistence. There was nothing in the crash logger as this heap corruption killed even foobar's minidump writer. It took a few tries with different track counts but I managed to trigger the crash here too. I had gotten a little too carried away with c++ templates. There were several bugs like misconception that comparing pfc::string8 with < and > would work for comparing sort orders and the worst issue was use of memmove to reorder the codec arrays.
Now albums consisting of multiple codecs should no longer crash the log writer with version 0.6.

Thanks for the update! 

Re: Dynamic Range plugin

Reply #109 –
I rescanned the files that failed last time on 0.5 and they scan just find on 0.6.  Thanks! 

Re: Dynamic Range plugin

Reply #110 –
Quote from: Case on
Quote from: Just_Addict on
The dialog shows RMS and Peak values as dBFS, but the log file shows them as dB.
If you ever get in a position to update this component for whatever reason, would it be too much to ask to also show those values as dBFS in the log file?
I tried to keep the log as close to old component's format as possible, that's why I used the same wrong units. Units corrected in version 0.5 of the component.

Quote from: OtherSteve on
if a folder contained files of mixed type (FLAC + MP3, for example), it crashed foobar2000.
That should not be a problem, I was fully prepared for such scenario and log will even report different codecs in use. I found single crash entry from crash logger from this component, it was related to scanning highly corrupted tracks and some tracks looked like they couldn't get decoded at all. The log writer had too light error checking for scan results and it tried to access per-channel data that it never managed to scan.
Should be fixed in the just released version 0.5. I'd appreciate it if you could test with the same files that failed earlier.

Thanks Case.  Although I couldn't remember the exact album that caused the issue, I found five others that had a mix of file types similar to that one.  After installing the latest version 0.6 today, all of them completed without issue.  Thanks!

lots of loud high frequencies?

Reply #111 –
I'm getting some weird readings on the DR Meter component - several of the high frequencies are showing a surprisingly loud signal.  See the snip in the image.  Any ideas?

Re: Dynamic Range plugin

Reply #112 –
I'm not certain how that image relates to DR Meter. But if the horizontal axel is frequency in Hz there doesn't appear to be anything out of the ordinary going on. Normal 44.1 kHz CD sourced material looks a lot like that apart from the dip after 8 (kHz?).

Though I have to wonder about hte scale, it is very strange and hard to read. Majority used for low bass frequencies, tiny bit for most audible mid frequencies and tiny slice for higher audible frequencies. Huge part on the visualization area on the right is wasted for frequencies that don't even exist in the source signal. And absolutely random frequencies chosen to be labeled. I have no idea where that red line is even positioned.

Re: Dynamic Range plugin

Reply #113 –
Quote from: Case on
I'm not certain how that image relates to DR Meter. But if the horizontal axel is frequency in Hz there doesn't appear to be anything out of the ordinary going on. Normal 44.1 kHz CD sourced material looks a lot like that apart from the dip after 8 (kHz?).

Though I have to wonder about hte scale, it is very strange and hard to read. Majority used for low bass frequencies, tiny bit for most audible mid frequencies and tiny slice for higher audible frequencies. Huge part on the visualization area on the right is wasted for frequencies that don't even exist in the source signal. And absolutely random frequencies chosen to be labeled. I have no idea where that red line is even positioned.
As for the red line thing on the spectrum visualization screenshot you pointed at, it is a Nyquist frequency marker (which also appears in Voxengo SPAN, which is a VST plugin for DAWs) and if the visualization shows frequencies higher than the marker, it is just a mirrored spectrum something like this:
X

Re: Dynamic Range plugin

Reply #114 –
Maybe not related but it looks very similar to FLAC files converted from SACD with or without lowpass filter applied upon conversion.

EDIT: Forgot to run a new TPS scan, so the files show the TPS values of the SACD. Did new TPS scan and added thescreenshot.

Re: Dynamic Range plugin

Reply #115 –
Hi, I use DR Meter 0.6. It works great. I'm a non-professional and I'm only interested in the Album DR value. What is the name of the "tag field" so that I can create a new column displaying the value "Album DR"? DR_Album does not work. Thanks for the advice.

Re: Dynamic Range plugin

Reply #116 –
Quote from: marty63 on
Hi, I use DR Meter 0.6. It works great. I'm a non-professional and I'm only interested in the Album DR value. What is the name of the "tag field" so that I can create a new column displaying the value "Album DR"? DR_Album does not work. Thanks for the advice.
I guess you need to use:
%album dynamic range%

Re: Dynamic Range plugin

Reply #117 –
Thank You. It works. :-))

Re: Dynamic Range plugin

Reply #118 –
Quote from: Case on
I'm not certain how that image relates to DR Meter. But if the horizontal axel is frequency in Hz there doesn't appear to be anything out of the ordinary going on. Normal 44.1 kHz CD sourced material looks a lot like that apart from the dip after 8 (kHz?).

Though I have to wonder about hte scale, it is very strange and hard to read. Majority used for low bass frequencies, tiny bit for most audible mid frequencies and tiny slice for higher audible frequencies. Huge part on the visualization area on the right is wasted for frequencies that don't even exist in the source signal. And absolutely random frequencies chosen to be labeled. I have no idea where that red line is even positioned.

The scale I use is Octaves from C0 to B11, but I display it in Hz.  The red line has already been described by TF3RDL.  I didn't think this was a DR Meter issue, but as you pointed out, it seems very odd that there's a dip between 8kHz and about 12kHz.  Playing Toto "Rosanna" - which is almost completely flat across the 20 - 20kHz spectrum - there is still a slight dip in that region but not nearly as severe.  Must just be the way I have the component frequencies configured.  Thanks for the feedback everyone!

Re: Dynamic Range plugin

Reply #119 –
Visualizations show the audio data after it has been through your DSP chain. If you for example have EQ lowering those frequencies it will be visible in the spectrum.

Re: Dynamic Range plugin

Reply #120 –
Quote from: Case on
Visualizations show the audio data after it has been through your DSP chain. If you for example have EQ lowering those frequencies it will be visible in the spectrum.
Ah I got it, so if I wanted to visualize audio signal accurately, remove all DSPs from "Active DSPs" part of DSP Manager part of foobar2000 preferences, but beware that graphs are useless for hearing the difference between similar but not identical audio files and must ABX (or double-blind test) them per ToS #8

Re: Dynamic Range plugin

Reply #121 –
@Case

Thanks for being the hero who brought this plugin into the new era. I've been testing it out today and it's been working great! I had a couple of suggestions I wanted to share with you.

First suggestion is regarding the filename of the output log, "foo_dr.txt". I know this is what the old plugin used also, but I've found that filename to be completely useless. I actually have a batch file that I created that I can run from the root of a folder and it will recursively search and rename all of the "foo_dr.txt" files to the "Official DR value: DR12" value located inside each file. So "foo_dr.txt" becomes "DR12.txt". For me personally, it's been way more useful having the DR Value as the filename than "foo_dr.txt". Perhaps maybe you'd consider hard coding this in? A few other ways I envision this being done would be...

- Have a textbox in the Preferences where the user could enter in the filename they want to use?
  - Create a placeholder such as %drvalue% that the user could use in the textbox.
  -OR-
  - If a placeholder is to cumbersome, then perhaps just a Checkbox that when enabled would disable the textbox and instead just name the output log with the Official DR Value.

Second suggestion is regarding the handling of Writing Logs and/or Tags in Quiet Mode. Right now the user is forced to Write Tags to their files if they want to use Quiet Mode. But what about if they just want an output log only? Or maybe they want both? Please see the attached pics for some samples I threw together for you to consider.

Thanks in advance!

Re: Dynamic Range plugin

Reply #122 –
Not bad suggestions. Everything should be implemented in version 0.7.

Re: Dynamic Range plugin

Reply #123 –
It's working great now! Thank you for implementing those changes.

Only thing I noticed is that you might consider adding some kind of note or tooltip letting the user know they can use the %drvalue% to get the "Official DR Value" in their filename. You and I and anyone else reading this thread will know, but other users won't.

For anyone else who comes across this and wants the output log to be named with the Official DR Value, use this pattern...
Code: [Select]
Log name pattern: DR%drvalue%.txt

Thanks again for your work, Case!

Re: Dynamic Range plugin

Reply #124 –
Hello Case,

thank you very much for the new Dynamic Range plugin. It works great with normal albums.
Unfortunately I have problems with sampler albums.

With the old Dynamic Range 1.1.1 I get normal values ​​for samplers (see foo_dr).
With the new plugin, however, no album range is determined, but rather each title is calculated individually (see foo_dr2). The individual values ​​match the DR track values ​​of the old plugin.

What could that be about? An example of the properties of a sampler can be seen in picture1.