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 13634 times) previous topic - next topic
0 Members and 2 Guests 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!