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
3
General - (fb2k) / Quiet Foobar2000
Last post by Klymins -
Hello. My Foobar2000 sounds quieter than other players (for example Flash Player) even if I set the volume to 100%. I only use MultiResampler DSP. What can be the reason of this?
5
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Just_Addict -
@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.
6
General - (fb2k) / Re: Reprocessing ReplayGain Values
Last post by Defender -
Thank you for the reply.  I should clarify that I only utilize %REPLYGAIN_TRACK_GAIN% as I play everything in my collection on Shuffle Play.  I like your suggestion of scanning for Album ReplayGain, but many of my files are not very well tagged, so this would present a few blockers.
As long as the files you want to scan are in a separate folder, you don't need tagging to treat the files as an album.
Just use RG with Scan as albums (by folder).

Not all of my collection is lossless either.  I have not noticed any major changes in tracks while listening except for a track here and there, so will likely abort this mission.  It would be nice, though, as a suggestion to add an option for, when scanning for ReplayGain by track, to scan files that already have a value.  Personally, I find it odd that foobar2000 assumes that, just because a ReplayGain Track value already exists, that the ssame standard was used to attain the value.  But, I guess suggestions are for another category on here. :)
Which is exactly the reason I asked Case to also write RG values from his foo_truepeak scanner.
Here https://hydrogenaud.io/index.php/topic,125719.msg1042344.html#msg1042344
So you can just check if the truepeak tags are the same as the rg tags. If they are, quality of the RG values is verified.

Of course you need to rescan all files with Truepeak scanner with options set to write RG values. Good news the tool can do a ton more and you don't need separate scans anymore for RG, DR and the likes.
Read more info in the foo_truepeak thread.
7
Other Lossy Codecs / Re: Quite OK Audio (QOA)... anyone ?
Last post by Case -
@mycroft, the QOA encoder in librempeg glitches because you disabled the reference encoder's weights overflow penalty check.
Here's win64 compile of qoaconv modified with mycroft's encoding changes but with weight checks in place. Doesn't glitch in my test file and produces audibly identical results from Klymins' samples with librempeg.
8
General - (fb2k) / Re: Reprocessing ReplayGain Values
Last post by gravitron_pgh -
Thank you for the reply.  I should clarify that I only utilize %REPLYGAIN_TRACK_GAIN% as I play everything in my collection on Shuffle Play.  I like your suggestion of scanning for Album ReplayGain, but many of my files are not very well tagged, so this would present a few blockers.  Not all of my collection is lossless either.  I have not noticed any major changes in tracks while listening except for a track here and there, so will likely abort this mission.  It would be nice, though, as a suggestion to add an option for, when scanning for ReplayGain by track, to scan files that already have a value.  Personally, I find it odd that foobar2000 assumes that, just because a ReplayGain Track value already exists, that the ssame standard was used to attain the value.  But, I guess suggestions are for another category on here. :)