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
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Case -
Thanks for the recordings, and thanks for time aligning them. Made comparison faster.

I see no signs of playback issues, the samples have retained perfect time alignment and only differ slightly in amplitude. Which is expected since there are two analog-digital conversions with two different devices involved. I'd bet there would be identical differences visible simply by recording the same piece with the exact same setup again.

With the fist track the record timings didn't align as closely between the players as hugely boosted inverse mix allows hearing some music. With the second track sample alignment happened to get very close - inverse mix spectrum even shows moire patterns.
3
General - (fb2k) / How to set active window in player
Last post by CapHCapH -
Hello,

seems like a very basic feature but lately when playing a track I find that Foobar2000 doesn't become the active window which prevents me from immediately using shortcuts, for example, until I click the player to make it active.
Couldn't see any setting relating to that, I must have missed it as it must be there, right?
So, how to make the player the active window when launching and playing a track in it?
This is windows 10 system.
Thanks.
5
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by misio -
Quote from: Case on
Please do. Would be curious to know what kind of DAC you have or if you have measured its performance. Pretty hard to beat the quality of that ESI card, which goes to waste in such use.

Ok, here we go.
Foobar 1.6 vs Foobar 2.1.5 (64 bit) - both in portable mode. Pure Foobar, no DSP or plugins, only ASIO component v2.2.2.
Both player configured in the same way, ASIO, ESI Juli@, Windows 10/64 bit.
DAC = old good E-MU 0404 USB in stand alone mode (in stand alone mode E-MU can work with no USB connection)
Sound chain:
Foobar 1.6/Foobar 2.1.5 -> ASIO component -> Juli@ digital optical out -> DAC optical input / DAC analog output -> Juli@ analog input (44.1kHz/24bit).
Playing samples were in 44.1khz/16bit.
Of course I can use another DAC if someone would like to repeat the experiment - I have got Xiang Sheng, Behringer DEQ2496, Behringer SRC2496, Sony SDP-EP90ES, Sony SDP-EP9ES, Advance Acoustic MDX-600, Denon DA-500, AMC US 24192i.

Take 1 / Take 1a = Foobar 1.6
Take 2 / Take 2a = Foobar 2.1.5

10
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Case -
WASAPI is supported natively in both foobar2000 v1.6.x and 2.x. All the default outputs are WASAPI. The ones without extra marking use shared mode, the ones with [exclusive] in the name use WASAPI exclusive mode. Thus the old component is obsolete. It has been kept online mainly for people with older foobar2000 versions.

The separate WASAPI Shared mode component you downloaded is my first attempt of making an output component. It was created in the time when default foobar2000 output used DirectSound and had poorly working smoothing for sudden sound changes. For it to work correctly the sound card drivers need to support event based reporting when buffers need filling - something that has been WHQL requirement for drivers since Windows Vista days.

The ASIO output picks best supported sample format automatically, you are correct. You should probably know that the ASIO output is done completely in the output component. It's the exact same code doing all the heavy work in all foobar2000 versions. There can be no audible differences.