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
23
Support - (fb2k) / Re: Foobar seems to ignore LFE channel.
Last post by Case -
The default outputs you have without any components are WASAPI outputs since foobar2000 v1.6. The ones without "[exclusive]" in the name use shared more and they resample/downmix the signal to match Windows mixer, just as the shared mode is designed to work. They won't try to play anything else. If they did, it would only result in an error.
The outputs marked "[exclusive]" send the signal to audio drivers without any alteration. If your hardware doesn't support the format you will get an error like you quoted.

The additional WASAPI component from Peter is old WASAPI exclusive mode component. You don't need it, it's for people using foobar2000 v1.5 or older.

Quote from: mzso on
Edit:
So I do get LFE with your wasapi component. But do I understand that it's outputted as stereo now?  Or was that always the case?
Your output has always been stereo if Windows mixer says you have stereo speakers.
24
General - (fb2k) / Re: Win Volume Integration
Last post by Case -
The option you are after is found at Preferences -> Advanced -> Display -> Integrate with Windows Universal Volume Control. It's a built-in feature and audioscrobbler does not affect it.
25
Support - (fb2k) / Re: Foobar seems to ignore LFE channel.
Last post by mzso -
Quote from: Case on
My reply from yesterday was incomplete. I was certain foobar2000 loses LFE intentionally in some downmix but was confused yesterday as I tested the bundled "Downmix to stereo" DSP and it retained it. And I have 5.1 speaker setup - without DSPs there is no reason to lose the LFE channel as I have a speaker for it.

The default output will lose LFE if you have configured your speaker setup not to have .1 channel. For example if you have just stereo output or 4 channel surround setup.
XAudio2 output component uses OS channel mixer, it too intentionally removes LFE if you don't have that speaker.
WASAPI exclusive mode can play the LFE even if speakers are set into stereo mode if you actually have a speaker for it.
My 'WASAPI (shared)' component retains the LFE in its internal downmix.

In conclusion, if you have only stereo setup and you want to ensure LFE stays intact, use the downmix DSP.
It seems like most issues I run into is caused by Foobar trying to be smarter than it can be.

Edit:

I don't seem to have wasapi outputs available though. (Oh I see now that it's provided via components) Only "default" whatever that means. And I get "Unrecoverable playback error: Unsupported stream format: 48000 Hz / 24-bit / 6 channels (0x3F)" when I try to use exclusive mode.

Downmixing in foobar would rather defeat the purpose of the surround virtualization that I have.

Edit:
So I do get LFE with your wasapi component. But do I understand that it's outputted as stereo now?  Or was that always the case?
27
Support - (fb2k) / Re: [BUG?] Foobar fails to function with Windows Sonic, why?
Last post by paregistrase -
Quote from: Case on
It might work better or more efficiently than other outputs on some setups. It lets OS do all the resampling and channel mixing. I also pass the original source sample rate along as much as possible so potentially for example Wine people can get as direct output to their native audio interfaces as possible. Current default WASAPI outputs will get resampled by foobar.

Indeed it does.
Code: [Select]
Opening track for playback: "file.mp3"
XAudio2 initialized: 44100 Hz, 2 channels (FL FR)

No resampling at all.
Thanks to discover me this output plugin.
28
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by jaro1 -
It's indeed as you wrote. I also apologize for the "false alarm".
For viewing was used Isotope RX editor trial and when loading the file encoded via hmp3 the whole file is shifted 25ms to the right with the length being the same and thus the last 25ms was missing. I was misled by this. When converting the hmp3 file back to a wav file (as you wrote) the length and shift again corresponded to the original wav file. I didn't check this previously, sorry again and thank you! Somehow hmp3 is not recognized by this specific editor the same way as Lame mp3 is.. this misled me as well. Therefore, I did not see a possible problem at this point (Lame tag, gapless info etc.).
29
Support - (fb2k) / ASIO output taskbar wiggles backwards and forwards when paused.
Last post by A_Man_Eating_Duck -
I'm using ASIO output with my Topping DAC and have noticed that when pausing a song the seekbar and Waveform Minibar (mod) will keep wiggling backwards and forwards. Sometimes it takes a few pauses to get the seekbar to "wiggle" but it tends to trigger more often than not. Changing the seekbar position while it paused and wiggling will stabilise the seekbar. Outside of the wiggling there doesn't seem to be any impact on playback.

I've attached a screen capture showing the issue.

Code: [Select]
Core (2024-05-01 16:32:20 UTC)
    foobar2000 core 2.2 preview 2024-05-01
foo_benchmark (2018-07-18 20:55:48 UTC)
    Decoding Speed Test 1.2.5
foo_bitcompare (2022-11-09 00:13:02 UTC)
    Binary Comparator 2.3.2
foo_converter (2024-05-01 16:32:50 UTC)
    Converter 2.2 preview 2024-05-01
foo_convolve (2019-12-15 21:18:58 UTC)
    Impulse Response Convolver 0.3.3
foo_cover_utils (2024-03-02 16:17:22 UTC)
    Cover Utils 1.0
foo_dop (2020-02-02 17:28:14 UTC)
    iPod manager 0.7.2
foo_dsp_effect (2024-03-31 15:27:18 UTC)
    Effect DSP 0.50
foo_dsp_eq (2024-05-01 16:32:54 UTC)
    Equalizer 1.2.3
foo_dsp_meiercf (2018-01-06 10:27:18 UTC)
    Meier Crossfeed 1.1.1
foo_dsp_src_resampler (2023-03-16 01:05:56 UTC)
    SRC Resampler 1.0.14
foo_dsp_std (2024-05-01 16:32:56 UTC)
    Standard DSP Array 2.2 preview 2024-05-01
foo_facets (2011-08-18 20:06:16 UTC)
    Facets 1.0
foo_fileops (2024-05-01 16:33:00 UTC)
    File Operations 2.2 preview 2024-05-01
foo_freedb2 (2024-05-01 16:33:04 UTC)
    Online Tagger 0.10
foo_input_monkey (2023-03-22 21:34:46 UTC)
    Monkey's Audio Decoder 10.07
foo_input_std (2024-05-01 16:32:44 UTC)
    CD Audio Decoder 2.2 preview 2024-05-01
    FFmpeg Decoders 6.0
    FLAC Decoder 1.4.3
    Monkey's Audio Decoder 10.61
    Opus Decoder 1.5.2
    Standard Input Array 2.2 preview 2024-05-01
    WavPack Decoder 5.7.0
foo_musicbrainz (2023-02-23 11:53:04 UTC)
    MusicBrainz Tagger 0.5.0
foo_musicbrainz64 (2024-04-29 09:25:56 UTC)
    MusicBrainz64 2.5
foo_out_asio (2023-11-27 22:35:46 UTC)
    ASIO Output 2.2.2
foo_simplaylist (2011-08-18 20:01:36 UTC)
    SimPlaylist 1.0
foo_ui_std (2024-05-01 16:32:32 UTC)
    Album List 2.2 preview 2024-05-01
    Decoding Speed Test 2.2 preview 2024-05-01
    Default User Interface 2.2 preview 2024-05-01
    File Integrity Verifier 2.2 preview 2024-05-01
foo_unpack (2024-05-01 16:33:12 UTC)
    ZIP/GZIP/RAR/7-Zip Reader 2.2 preview 2024-05-01
foo_verifier (2023-04-17 02:43:48 UTC)
    File Integrity Verifier 1.4.3
foo_vis_milk2 (2024-02-19 09:51:42 UTC)
    MilkDrop 2 Visualisation 0.0.230-alpha
foo_wave_minibar_mod (2024-01-16 00:24:18 UTC)
    Waveform Minibar (mod) 1.2.58
30
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Case -
I verified your settings, they do not cause any offset issues. And sounds like you also saw that foobar2000 decoder reports there is no offset.
You don't mention what you use to see the offset. I'm not familiar with all audio editors in the world, but for example Adobe Audition / Cool Edit / Audacity can't open MP3s with the gapless info taken into account. You need to decode the mp3 first with a proper decoder like I mentioned in the previous post.