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
1
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: Case on
@Defender - Here's a new build that should address your concerns. I didn't replace the old and stable build yet because I may still do some tweaking. I may even re-use the same version number for further experiments.
Download: https://foobar.hyv.fi/foo_truepeak_0.6.4.fb2k-component

@paregistrase - I hope you noticed that I made a DR Meter component just for that originally: https://hydrogenaud.io/index.php/topic,123905.msg1044254.html#msg1044254.

I'm starting to wonder if the name of this component should be renamed to something like Loudness scanner. I could give separate scanners own context menu entries, but the extra stuff has accumulated in because people wanted to scan multiple things at one go.
I'll probably add the extra commands anyway, hidden by default, especially if Defender likes the new idea of moving the context commands into a separate group of their own instead of camping in the ReplayGain menu.

Functionality of 0.6.4 is excellent.

I do not have any input about renaming the component or not a as long as functionality stays like this please.

BTW. I don't understand requests for partially scanning when some information (like rg) is already known.
You do one scan (I assume) to accumulate the various truepeak, clipping, lra and dr stuff. So how much time would be won if for instance the DR part would be excluded?
IMO it's quite efficient to do them all when I request a scan.
2
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by paregistrase -
Quote from: Case on
@Defender - Here's a new build that should address your concerns. I didn't replace the old and stable build yet because I may still do some tweaking. I may even re-use the same version number for further experiments.
Download: https://foobar.hyv.fi/foo_truepeak_0.6.4.fb2k-component

@paregistrase - I hope you noticed that I made a DR Meter component just for that originally: https://hydrogenaud.io/index.php/topic,123905.msg1044254.html#msg1044254.

I'm starting to wonder if the name of this component should be renamed to something like Loudness scanner. I could give separate scanners own context menu entries, but the extra stuff has accumulated in because people wanted to scan multiple things at one go.
I'll probably add the extra commands anyway, hidden by default, especially if Defender likes the new idea of moving the context commands into a separate group of their own instead of camping in the ReplayGain menu.

There is a standalone one, good.

The idea of make a Loudness scanner menu with all the commands sounds pretty good.

3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
@Defender - Here's a new build that should address your concerns. I didn't replace the old and stable build yet because I may still do some tweaking. I may even re-use the same version number for further experiments.
Download: https://foobar.hyv.fi/foo_truepeak_0.6.4.fb2k-component

@paregistrase - I hope you noticed that I made a DR Meter component just for that originally: https://hydrogenaud.io/index.php/topic,123905.msg1044254.html#msg1044254.

I'm starting to wonder if the name of this component should be renamed to something like Loudness scanner. I could give separate scanners own context menu entries, but the extra stuff has accumulated in because people wanted to scan multiple things at one go.
I'll probably add the extra commands anyway, hidden by default, especially if Defender likes the new idea of moving the context commands into a separate group of their own instead of camping in the ReplayGain menu.
10
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Porcus -
Quote from: Case on
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.

No disagreement over improved handling, please keep it - I only intended to raise the "are discrepancies to be expected?" question to a 1.0 version.

By the way, I tested CDDA stored losslessly, so it is not about resampling.