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 Blew -
Quote from: Case on
But now I did some more testing as I remembered an old troublemaker. Turns out https://www.foobar2000.org/components/view/foo_arg component breaks RG scanner instantiation. If you have had that component installed all your RG scan results are invalid.

I've been alternating between the alternate RG component and the inbuilt one. I have no idea which I was using at the time of scanning many of my albums., and I've always tagged the files once scanning is done. Does this mean that I will need to rescan and retag them, or does the issue merely prevent the scanning from happening in the first place? If it's the latter then I would have noticed and I don't need to do anything.
2
General - (fb2k) / Re: Quiet Foobar2000
Last post by Case -
Note that exclusive mode is exclusive, it allocates the output device for foobar2000 and nothing else can play audio during that time. And it will error out if you try to play material your audio device doesn't support. Using shared mode output is more user friendly.

Did you notice that new foobar2000 versions remember volume setting per output? Make sure you actually have foobar2000 volume at maximum for the normal output you use. Also make sure that Windows mixer doesn't for any reason use lowered volume for foobar2000 process. Just to be sure you can reduce foobar2000 volume in the mixer once and then restore it to maximum, that will reset any possible issues there.
And finally, when not using exclusive mode foobar2000 outputs its data as floating point, unlike most audio software that clip their signal to whatever bitdepth they happen to support. Windows mixer has built-in clipping prevention - if your files happen to have high peaks above digital fullscale the mixer will audibly lower the loudness of the incoming signal. That not only can cause foobar2000 to sound quieter, but it will also make the most audio sound awful because the volume will pump up and down.
If you wish to prevent the lowered volume without fixing the clipping by using ReplayGain or by lowering the playback level with other means, you can use Hard Clip DSP to clip the signal same way other players and exclusive mode clip it, without having to resort to using exclusive mode.
4
Support - (fb2k) / Re: foobar2000 don't search subfolders of ..\..\music\mods folder ???
Last post by Case -
foobar2000 will scan subdirectories as deep as they go. Are you certain foobar2000 has permission to the directories in question? Do you have a decoder for the file formats stored in the location? Have you checked what errors Media Library reports (there's a button 'Show errors' on the Media Library Preferences page). Have you checked what errors console reports?
6
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Case -
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.
7
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Just_Addict -
Quote from: Case on
Turns out https://www.foobar2000.org/components/view/foo_arg component breaks RG scanner instantiation. 
Bingo, that was the culprit, completely forgot about that one. 
Nevertheless, like I said in my earlier post, half of the values it shows I have no idea how to interpret, they don't mean anything to me. The ones that I am comfortable interpreting I can derive with title formatting (Album/Track Peak, Album/Track PLR) and DR Meter gives me the rest. Although it's too bad the latter only saves the DR values and not the Peak and RMS dBFS values. If I knew how to calculate those with title formatting script I'd have my cake and eat it too.
10
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by Porcus -
May 13th news from ffmpeg.org:

The FFmpeg community is excited to announce that Germany's Sovereign Tech Fund has become its first governmental sponsor. Their support will help sustain the maintainance of the FFmpeg project, a critical open-source software multimedia component essential to bringing audio and video to billions around the world everyday.


Not quite Putin.