You can associate foobar2000 with different file types at 'Preferences → File types'.
Upgrading from any 0.9.x version to the latest version will leave your settings intact, provided you install the new version on top of the old one. Do not uninstall the old version first! The uninstaller will delete all your settings.
Installing 0.9.x on top of 0.8.3 or an older version will delete your settings and components, since these old versions are incompatible to 0.9.x. However the installer will warn you about this.
Yes, foobar2000 does work on Windows Vista. However you should take care to only use components compiled after July 30th, 2006 (including foobar2000 itself and bundled components). Older versions of the foobar2000 SDK contained a bug that would cause “bad allocation” errors on Windows Vista.
To install components from the foobar2000 installer that you did not choose to install during the initial installation, just rerun the installer and select them; your settings will be kept intact. Please read on to learn about installing other components.
Component DLLs are placed in the “components” subfolder of the foobar2000 application folder by convention, however foobar2000 will scan its application folder recursively for DLLs matching the foo_*.dll naming scheme, so you can place in another subfolder if you wish. Note that additional DLLs that come with a component usually have to be placed in the foobar2000 application folder itself, unless they are installed systemwide. You should check the component's documentation, if it needs additional DLLs or data files and how these need to be installed.
Most technical problems can be solved by removing any third-party components and resetting the configuration (or doing a fresh reinstall). It is recommended that you backup your foobar2000 directory before doing that, so you can try to restore your old settings/components later, or help us with identifying the exact source of the problem.
Please disable any unneeded DSPs (such as resampler). Some of them require a lot of resources to operate.
Some DSPs such as crossfader or gap remover need extra memory buffers to operate; you can reduce the memory usage by changing their settings. Also, certain output modes (Kernel Streaming) have been reported to use excessive amounts of CPU time on certain systems.
Finally, some third-party components such as Panels UI (foo_ui_panels) are known to use high amounts of CPU time.
Please post your question on third-party component forum. As we don't take responsibility for components other people make, this FAQ can't help you any further.
The MP3 format doesn't natively support sample-accurate seeking, and sample accurate seeking is absolutely required by some features of foobar2000 (such as .CUE playback). MP3 seeking can't be optimized neither for CBR files (frame sizes aren't really constant because of padding used), nor for VBR files (both Xing and VBRI headers in those files contain only approximated info and are useless for sample-exact seeking). Therefore MP3 seeking works by bruteforce-walking the MPEG stream chain and is appropriately slow (this gets faster when you pass through the same point of file for the second time because seektables have been built in the RAM).
Your foobar2000 installation has been damaged, most likely by deleting DLL files required for foobar2000 to function correctly. Please re-run foobar2000 installer to resolve this issue.
There are multiple reasons why this could happen. If there is no error message, the component has been banned - most likely for violating the foobar2000 SDK license. Otherwise please see the following list of error messages and the possible solutions for each.
Right-click one or more tracks, choose 'Properties' from the context menu. Various additional functionality can be accessed by selecting one or more fields in the Properties dialog and right-clicking them.
Note that you can mass-edit tags of a group of track by opening the Properties dialog on multiple items.
No. If you want to edit tags of multiple tracks, you can do it more efficiently by just selecting them all and opening the Properties dialog for them.
foobar2000 updates existing tags and adds ID3v1 – and ID3v2.4 if necessary – to MP3 files without tags. ID3v2.4 is added to files with ID3v1 tags when the information you are trying to write cannot be fully stored in ID3v1.
Just use the 'Tagging → MP3 tag types' feature from the context menu. The dialog appearing is not an option dialog. The changes you are doing there are applied to the selected files only.
You have probably selected one or more non-MP3 files. The feature is only available for MP3 files.
Only ASCII characters are allowed in ID3v1. Any other characters are replaced by question marks on rewrites.
foobar2000 writes ID3v2.4 tags encoded as UTF-8 by default. To deal with broken software/hardware with partial support of the ID3v2 standard, an “ID3v2 writer compatibility mode” has been added ('Preferences → Advanced → Tagging → MP3 → ID3v2 writer compatibility mode'); it results in non-standard-compliant tags being written (ID3v2.3 instead of ID3v2.4, UTF-16, no unsynchronization, no padding), but attempts to dodge known bugs in other ID3v2 implementations.
You can find this feature at 'File operations' from the context menu (you need to enable the 'Optional features → Tools → File operations' during installation).
Invalid file name characters - such as slashes or backslashes - are replaced before metadata originating from the file is processed by title formatting functions. This is necessary to allow slash or backslash characters placed by you in your file name formatting pattern to be interpreted as path delimiters without the side effect of each slash contained in metadata fields included in your file name formatting pattern being interpreted as a path delimiter as well.
Load tracks you want to convert into a playlist, right click, choose 'Convert' from the context menu, click one of sub-options. Converting functionality requires the Converter component to be installed ('Optional Features → Tools → Converter' during installation). First time you convert to some format, you will be asked for a location of a commandline encoder executable required to encode to that format (unless relevant executable can be found in your standard paths or in foobar2000 application directory). Commandline encoders for most audio formats can be found on RareWares.
You can safely rename oggenc2.exe to oggenc.exe and point foobar2000's Converter to its location.
See Birthday paradox. Random mode doesn't prevent track repetitions other than the same track played twice in a row. You probably want to use 'Shuffle (tracks)' mode instead.
Shuffle modes keep an internal reordered list of tracks in your playlist. If you manually start playback from some track that you've already played, you'll get the same tracks played after it as last time. Use the 'Playback → Random' menu command to pick a random track in your playlist to resume from.
These modes can be used to reorder your playlist on album basis rather than track basis and play tracks in each album in sequential order. Shuffle (albums) is usable when your files are tagged properly (”%album artist% | %date% | %album%” evaluates to unique value for each of your album and doesn't vary between tracks in one album); Shuffle (directories) is meant as a fallback when your tagging scheme renders Shuffle (albums) useless but you keep each album in a separate folder. Note that the album identification pattern can be customized in 'Preferences → Advanced → Playback → Shuffle → Album grouping pattern'.
Please choose 'Titleformatting Help' from foobar2000's 'Help' menu.
Right-click the status bar, toggle relevant option.
As for foobar2000 0.9.5 or newer, you can do most of what the Masstagger component did with other components or built-in functionality, typically with less effort and less chance of unintended effects:
Since not all of Masstagger's functionality is available through other components, Masstagger is still available for download.
In foobar2000 0.9.5 or newer, you can create autoplaylists by right-clicking an Album List branch. In order to create a query-based autoplaylist using Album List, use the 'filter' box to enter a query and create an autoplaylist from the 'All Music' item.
Please see the Replaygain page on the Hydrogenaudio Knowledgebase.
Go to 'Preferences → Display → Context Menu', right-click a group you want to add an entry to, select 'Insert item → Command…', choose the command you're looking for from the list. If the command you need can't be found, you're missing a component that provides it.
If the command you're looking for is already in the context menu structure tree under Context Menu Preferences yet you can't see it in your context menus, it might be context-sensitive and available only for specific tracks; for an example, MP3-specific utility commands are available only when all selected tracks are MP3 files.
Context menu commands require a list of tracks on which to operate. If you execute them from the context menu or using a normal (non-global) keyboard shortcut, this list is provided by part of the program where you used the context menu or the keyboard shortcut (the context). For global keyboard shortcuts there is no way to chose a list of tracks automatically when they are used, so you have to chose a context when you bind the command. To do so, select a command from the [context / now playing] or [context / playlist] branch to make the command use the playing track or the selected items on the active playlist when you press the global keyboard shortcut.
The FPL format is not meant to be interchangeable with other software or editable by users. Its primary design goals are carrying all necessary track information (metadata, last seen modification time, etc) between foobar2000 sessions while remaining as fast to read and write as possible, since reading/writing FPL files bottlenecks app startup and shutdown with large Media Library or playlists. Making the FPL format user-editable would introduce massive startup/shutdown delays for certain users.
Additionally, the format is strictly tied to foobar2000 track information caching architecture; potential design changes in that area in future foobar2000 versions will inevitably require a new non-backwards-compatible revision of the FPL format.
The configuration file format is not meant to be interchangeable with other software or editable by users. Making it user-editable would result in third party component developers using it as an excuse not to provide proper user interface to change their components' settings, just like many components use title formatting as an excuse not to provide a more accessible way to customize them. Additionally, keeping the entire configuration file structure human-readable would result in slower startup/shutdown and code bloat as well as break compatibility with existing configuration files (or require even more bloat to import old settings).
No. Most of “sound quality differences” people “hear” are placebo effect (at least with real music), as actual differences in produced sound data are below their noise floor (1 or 2 last bits in 16bit samples). foobar2000 has sound processing features such as software resampling or 24bit output on new high-end soundcards, but most of other mainstream players are capable of doing the same by now.