Skip to main content


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
General - (fb2k) / Re: UPnP MediaRenderer output | discussion
Last post by ΛRTΣM -
Thanks to the author of the plugin, all works well. My configuration:

Sony TV KD-55XF8505
Code: [Select]
# Specific Sony device fixes
manufacturer=Sony Corporation

Support - (fb2k) / Re: Surprise Crash! F2k not booting up
Last post by isaiah36 -
I am following up on the suggestion by Marc2k3.
Please point out the word portable in my post. I can't see it.

The folders in %appadata% are for use by standard installs. Re-installing 1.6 in standard mode should have worked. Only a buffoon would point a 64bit portable installer directly at it.  :/

I installed version 2.0 as a standard installation, which updated the standard installation that was already there. It never booted up because it failed to import the configuration from the old %appdata% folder. The attempted upgrade to 2.0 occurred AFTER 1.6.7 stopped booting up. The old appdata folder is there, but it is corrupted. The 64 bit portable was installed in foobar2000-v2 but it failed to boot in exactly the same way as the standard.

I re-installed the 32 bit portable in the old %appdata% folder and the same problem persisted. The box said "Internal error -" followed by text saying something is corrupted in that folder. (I don't remember the exact words.)

I have restored the folder from my secondary desktop, and will resume the journey from a few weeks behind. Thanks for the unhelpful suggestions and the insults. You get what you pay for I suppose.
3rd Party Plugins - (fb2k) / Re: Crossmix DSP
Last post by Case -
Thank you. This turned out to be a problem in foobar's output code and should be fixed for the next build.
For now you can circumvent it by enabling the smooth fader in the output config.
Development - (fb2k) / Re: New SDK with foobar2000 v2.0 features released (2022-08-10)
Last post by Peter -
You should call CoInitialize() + CoUninitialize() yourself if you need COM. As far as I can see, everything in my code matches CoInitialize() with CoUninitialize(), so you worker thread clients should always assume that COM hasn't been initialized on entry.

If I change it now and you rely on prior COM init, your code no longer works under foobar2000 v2.0, so you need a workaround on your side anyway.
Development - (fb2k) / Confused about the meta data API
Last post by pqyt -
After trying to understand the meta data API the last couple of months with foo_midi, I'm still confused:

Consider a valid MIDI file that is not in a library path.

* metadb_index_client::transform() gets called when I add it to a playlist. However, removing the file from the playlist and re-adding it does not call transform() again; not even after closing the foobar2000 instance. How does foobar2000 know it has seen the file before? When I rename the file, transform() gets called again. So, where does the association between the file path and the hash get verified?
* Playing the file calls input_stubs::decode_get_dynamic_info() but when I set an Info tag it does not appear in the Properties panel nor does it contain a value when I display the tag in the status bar f. e.
* Using the "Tagging/Remove tags from file..." context menu item does not remove any meta data from the database (tags do not get written back to the MIDI file). How do I "reset" the tagging process and can I force foobar2000 to re-construct the meta data?

I'm not sure if the original component (pre-2.0) did it right or that I broke something along the way.