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.
Recent Posts
22
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Case -
Quote from: Porcus on
Did a few brief tests. On a couple of tracks, yours returns a dB more than foo_dynamic_range . No problem unless it is a symptom of something, I'm just assuming it is roundoff.
I read somewhere the default component resamples everything to 44.1 kHz. My component doesn't do that as that shouldn't be necessary and the PDF paper describing the measurement doesn't speak anything about resampling. Another difference is that the old component clips at least sample peaks to 1.0. I do not clip anything as I consider that incorrect. Though if people disagree I can modify the behavior.

There can be other weirdnesses going on too. The algorithm paper for example tells to split the audio for RMS scanning to blocks that are 3 seconds in length. Then it says that in their example 3 seconds of audio at 44.1 kHz equals 132480 samples. That's 180 samples too much. 44100 * 3 = 132300.
24
Support - (fb2k) / Re: Foobar seems to ignore LFE channel.
Last post by mzso -
Quote from: dexter86 on
I think there's something wrong LFE channel in that file. Check out my files that I use to test surround playback, they play fine in latest foobar.
I can see but can't hear the LFE with any of the your files either.

PS: I tried with xaudio2 output as well. No LFE that way either, but it is much louder on FB 2.1.5 instance I have for testing. (Sounds the same on my main instance, but that's 1.6.17)
30
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Defender -
Quote from: Case on
Thanks marc2k3. I certainly don't like bright decorations that don't belong.
I added the DR scanning as an option to True Peak Scanner, and implemented the darkening changes there first. It was surprisingly difficult to make Windows use the new style, I couldn't make it work except by programmatically adjusting the dialog size.


I enabled dr scanning in the settings for truepeak scanner and removed components foo_dynamic_range and foo_dr_meter since they are obsolete (for scanning). Truepeakscanner 0.6.3 works excellent.

There are some minor UI issues though.

The text in the context menu is incomplete. It says Truepeak and positions but nothing about DRA,
I would not if it would only say Truepeak (and does all the things you enable in settings).

The popup window that comes up after the scan does not remember it's last size settings and there is now a couple of columns extra which I cannot see unless I everytime resize the popup window.

Finally ... I cannot clear DRA tags from the context menu, since I removed both foo_dynamic_range and foo_dr_meter.
Same as above I would not mind a context menu item that says remove Truepeak tags which removes all the things you set in truepeak scanner settings (including replaygain stuff).

Thanks for this great addition.