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
2
Support - (fb2k) / Re: Can't update
Last post by cwb -
In some instances, such as the Windows 11 that I use. After clicking "More info" in the dialog box as korth showed above, you may need to bring the cursor to the bottom of the dialog box to reveal a white colored bar area that is then clicked on to bring up the "Run Anyway" option.

See attached screenshot
4
Support - (fb2k) / Re: v2.x doesn't play ASX
Last post by Gus. -
Try the latest 2.2 Preview:
2024-03-04

    Worked around audio glitches with very low output buffer size introduced in previous build.
    Fixed glitchy seekbar movement in certain scenarios.
    Prevented nonsensical video codec names from being reported for certain MP4 files.
    Fixed regressions in ASX playlist loader.
    Converter: More detailed error messages for specific file creation errors.
5
General - (fb2k) / Re: foobar2000 for mac
Last post by xacto -
Thank you for this version of Foobar2000 for Mac!

[Feature Request] A status bar displaying the total duration and the number of tracks in the currently displayed playlist.

Enable or disable the status bar using a toggle similar to the standard Finder shortcut:
View > Show Status Bar (Cmd /)
View > Hide Status Bar (Cmd /)

An example of the basic information to include in the status bar:
63 tracks, 2 hours 38 minutes 58 seconds
Estimated completion time of the playlist: 22:33
This is akin to the Estimated Time of Arrival (ETA) feature in GPS systems.

I believe this information is vital, especially for those using foobar2000 on macOS for DJing at social events.
7
WavPack / Re: WavPack 5.6.4 Has Multithreading Option
Last post by shadowking -
Thanks for the explanation David.  Fortunately this sample responds well to -hx6 or  better -hhx6 .  Except DNS
 and even -s0 doesn't work too good .  I agree -s1 is something that always stood out for me . Not really bad but a bit
too correlated to the signal . -s.5 is more natural and 'spread out' not as much as -s0 but enough to go undetected and even then still sounds good.
8
Support - (fb2k) / Can't update
Last post by Retrowave -
I have ver. 2.1 32bit installed and want to update to the latest.
I download the .exe from the website, double click it and... nothing happens. I tried running it is admin mod but... same.
Am I doing something wrong?  :-\
9
Listening Tests / Re: Great killer sample, easy to ABX on most codecs
Last post by shadowking -
@synclagz you are right (i proposed similar bitrate and settings) but I ended up on an alternative path for now.
I did a long abx session last night and after hearing the increased security that the heavy settings bring I went that way.
I wrote a similar post in the past about maximising quality without blowing bitrate. It works similar here too.
Higher -x and  -h levels = decreased motivation vs totally 100% transparent.   That became my new goal.

I arrived at two settings and its a quality 1st approach 'while keeping bitrate constrained ' to save space . Some speed is sacrificed if needed for both encoding and decoding (esp for encoding).  I don't see it as lowering quality to keep bitrate down (hopefully I succeeded to an extent in the goal)- but keep quality high and bitrate low as possible while :

a) decreasing likelyhood of finding problems
b) even if found its impact will hopefully be limited and harder to confirm for multiple listeners.
c) decrease chances of feeling need for higher bitrates & less efficiency. I want to save half or more lossless bitrate.

So the settings
1-   A behemoth heavy duty   -b384hhx6s.5  used with or without correction files.
2-   A fast encoding method with practically tiny impact on quality  -b384hhs.5c

The alternative -b metric is 4.35

I guess this could be adopted to the -h mode with -b400hx5-6s.5 or maybe a bit higher.