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
21
General Audio / Re: Downsampling 192/96 to 48 kHz - best SoX setting?
Last post by Squeller -
I've had another idea. I search the very loud albums and only for those I start the conversion with a very tiny (-0.2 db) amplification (foo_dsp_amp). For my testing set, this brought all loudest files into the [0.99..]1 area. Also now I'm displaying a marker in my ColumnsUI "$ifgreater(%__replaygain_track_peak%,0.98,..)" to get some awareness there.

Code: [Select]
(%SAMPLERATE% IS 96000) AND (%__replaygain_album_peak% GREATER 0.98)
22
3rd Party Plugins - (fb2k) / Re: ReplayGain DSP - Alternative ReplayGain implementation by Case
Last post by boxerfan88 -
Thank you for explaining the meaning of the log entries.

I am still testing out various scenarios ... may need some protection for some scenarios as shown below...
( Yes, these are rare noise files that are not music content... the auto-applied gain is quite scary ... )

Quote
Opening track for playback: "F:\MUSIC\z_Subwoofer wakeup\Pink_PN_64k_50_10000_-48_dBFS_44.1k_PCM24_LR.flac"
ReplayGain DSP: gain data is missing but the DSP managed to scan the track. Found gain +29.09 dB
Opening track for playback: "F:\MUSIC\z_Subwoofer wakeup\Pink_PN_64k_30_6000_-60_dBFS_48.0k_PCM24_LR.flac"
ReplayGain DSP: gain data is missing but the DSP managed to scan the track. Found gain +41.83 dB

It'll be great to have some sort of maximum gain limit as a form of protection, be it 6dB or 12dB or ...

ps: As a workaround, I scan the files and override the track & album gain with pre-determined values, and this component will pick up the pre-determined value.
23
3rd Party Plugins - (fb2k) / Re: [fb2k v2] Random Pools (foo_random_pools)
Last post by amiti -
A couple of questions:
1. If I choose to add 3 groups and limit "number of tracks to add" to 3, will the 3 tracks be from 3 different groups?
2. If I am sorting without sorting/limiting each group, will all groups be sorted and then 3 tracks from the 3 top groups will be added?

Thank you for the help.
24
3rd Party Plugins - (fb2k) / Re: ReplayGain DSP - Alternative ReplayGain implementation by Case
Last post by Case -
The log entries tell that the DSP managed to fully scan the track you were about to play. The track seems to be very quiet and its playback level needs to be increased by 8.95 dB to get similar playback level as other tracks under ReplayGain specifications.
The peak 0.346279 means -9.21 dBFS, so even if playback level is increased by 8.95 dB it would not clip (there would be 0.26 dB headroom). But since you had requested the headroom to be 1 dB, the playback level needs to be slightly reduced. The loudness will be increased by 8.21 dB.

The new checkbox prevents positive gain when it's uncertain if the boost would clip or not. But when peak information is known, you can protect against clipping even without dynamics compression.
25
Support - (fb2k) / Re: fb2k fails sampling rates below 1000 Hz
Last post by Case -
Correcting this may require recompiling some third party components too, as these limits are included in the SDK. The SDK defines valid sample rate to be >= 1000 and <= 20000000. The minimum has (always) been the same, the maximum used to be 1000000 before DSD.
30
3rd Party Plugins - (fb2k) / Re: ReplayGain DSP - Alternative ReplayGain implementation by Case
Last post by boxerfan88 -
Quote
ReplayGain DSP: gain data is missing but the DSP managed to scan the track. Found gain +8.95 dB peak 0.346279
ReplayGain DSP: reducing gain by 0.74 dB to prevent clipping

Based on the above log entries, may I know what the log entries mean?
a. Gain of -0.74dB applied?
b. Gain of +8.21dB applied?  ( 8.95-0.74 )

Configuration settings:
  • Processing mode = Apply track gain
  • Target = -18 LUFS
  • Max peak = -1 dBFS
  • Estimation = Scan local files that are missing RG data
  • Allow positive gain = unchecked

( I was hoping when I unchecked the "Allow positive gain" setting, there would not be any positive gain, only negative gain allowed. )