Goom-Online ~ Web Visualization Player


A forgotten music visualizer, revived straight into your web browser.

Goom Display

goom-online.github.io
github.com/goom-online/goom-online.github.io

Rainmeter ~ Elegant Music Player


vsthemes.org

vsthemes.org/en/skins/rainmeter/45451-elegant-music-player
www.rainmeter.net

foo_vis_wispan ~ Winamp Spectrum Analyzer


foo_vis_wispan is a Foobar2000 spectrum analyzer visualization implemented with GDI. It is a port of the Classic Spectrum Analyzer (vis_classic) Winamp visualization plug-in by Mike Lynch.

Features:

  • Accurate, detailed, customizable spectrum analyzer.
  • vis_classic library has been upgraded to compile with a modern toolset.
    • Upgraded the resolution of the waveform passed into the library from 8 bits to 16 bits.
    • Other changes are mainly to integrate with foobar2000 instead of Winamp.
    • That means bugs in the original are still likely to be present.
  • Options can be modified and their effects viewed in real-time as the component is running.
  • Compatible with the Default User Interface (Default UI) and the Columns User Interface (Columns UI).
  • Tested on foobar2000 v2.25.3 (x86 32-bit and x86 64-bit) and Microsoft Windows 11 (Build 26200).

www.foobar2000.org/components/view/foo_vis_wispan
wiki.hydrogenaudio.org/…/Foobar2000_visualization_components

foo_outinfo ~ Foobar2000 Output Information


Installing foo_outinfo allows for accessing the actual specs of the audio being played and the output device information using titleformatting.

The fields exposed by this component are:

%output_samplerate%Returns the sample rate entering output component
%output_channels%Returns the number of channels entering output component
%output_channel_mask%Returns the description of above channel configuration
%output_bitdepth%Returns the bitdepth used by output component, or best guess in case output doesn’t specify
%output_device%Returns the name of the output device
%output_dsps%Returns the list of active DSPs
%output_dsp_preset%Returns the name of the active DSP chain preset
%output_volume%Returns the playback volume in dB
%output_rg_source%Returns the ReplayGain source mode
%output_rg_mode%Returns the ReplayGain processing mode
%output_rg_gain%Returns the effective ReplayGain gain value in dB
%output_rg_peak%Returns the effective ReplayGain peak value
%output_rg_peak_db%Returns the effective ReplayGain peak value in dBFS
%output_buffer_length%Returns the output buffer length in ms

foobar.hyv.fi/?view=foo_outinfo
hydrogenaudio.org/index.php/topic,127228.0

Basic Status Bar Example Using foo_outinfo Fields

The foo_outinfo component exposes information about the current audio output and signal, such as the active output device, sample rate, bit depth, and channel count. These fields are especially useful in the status bar, where you want quick technical confirmation without cluttering playlists.

A simple and practical example is:

Now Playing: %artist% - %title% | %output_samplerate% Hz / %output_bitdepth% bit


What This Displays

When a track is playing, the status bar would show something like:

Now Playing: Miles Davis - So What | 44100 Hz / 16 bit

This tells you at a glance:

  • What is playing
  • The actual output sample rate
  • The output bit depth being sent to your audio device

Step By Step Explanation:

Music Metadata (Standard Fields)

%artist% - %title%
  • %artist% → Track artist tag
  • %title% → Track title tag

These are standard foobar2000 title formatting fields and work everywhere.


Separator

 |

This is just plain text. It visually separates the music info from the technical output info. You can replace it with a dash, bullet, or brackets if you prefer.


foo_outinfo Output Fields

%output_samplerate%
  • Displays the actual output sample rate in Hertz
  • Reflects resampling, DSP changes, or output driver behavior
  • This is more reliable than %samplerate% when DSPs are active
%output_bitdepth%
  • Displays the bit depth used by the output
  • Shows what is being sent to the DAC, not just what is in the file

More Informative Versions

If you want to include channels and output device name:

Now Playing: %artist% - %title% | %output_samplerate% Hz / %output_bitdepth% bit / %output_channels% channels

Displays:

Now Playing: Aphex Twin - Xtal | 48000 Hz / 24 bit / 2 channels

If you want to add the current Replaygain mode:

Now Playing: %artist% - %title% | %output_samplerate% Hz / %output_bitdepth% bit / %output_channels% channels | RG %output_rg_source%

Displays:

Now Playing: Aphex Twin - Xtal | 48000 Hz / 24 bit / 2 channels | RG Album

If you want to display the active DSP

$if(%output_dsp%, | DSP: %output_dsp%)

Displays the separator and active DSP, otherwise displays nothing:

| DSP: Resampler (SoX)

Minimal Technical Version (Very Clean)

For users who want only output confirmation:

Output: %output_samplerate% Hz / %output_bitdepth% bit

Displays:

Output: 96000 Hz / 24 bit

Why Use foo_outinfo in the Status Bar?

  • Confirms what your DAC is actually receiving
  • Helps verify exclusive mode, resampling, and DSP behavior
  • Avoids cluttering playlists with technical data
  • Ideal for users who care about signal integrity but want a clean UI

Beginner Notes and Caveats

  • All output_* fields require foo_outinfo to be installed
  • These fields only show values while audio is playing
  • If nothing is playing, the fields will appear empty
  • Output fields are best used in:
    • Status bar
    • Window title
    • Custom display panels

OpenMusic ~ Music Composition Language


OpenMusic (OM) is a visual programming language based on Common Lisp. Visual programs are created by assembling and connecting icons representing functions and data structures. Most programming and operations are performed by dragging an icon from a particular place and dropping it to an other place. Built-in visual control structures (e.g. loops) are provided, that interface with Lisp ones. Existing CommonLisp/CLOS code can easily be used in OM, and new code can be developed in a visual way.

OM may be used as a general purpose functional/object/visual programming language. At a more specialized level, a set of provided classes and libraries make it a very convenient environment for music composition. Above the OpenMusic kernel, live the OpenMusic Projects. A project is a specialized set of classes and methods written in Lisp, accessible and visualisable in the OM environment. Various classes implementing musical data / behaviour are provided. They are associated with graphical editors and may be extended by the user to meet specific needs. Different representations of a musical process are handled, among which common notation, midi piano-roll, sound signal. High level in-time organisation of the music material is proposed through the concept of “maquette”.

openmusic interface

openmusic-project.github.io
openmusic-project.github.io/openmusic
github.com/openmusic-project
en.wikipedia.org/wiki/OpenMusic

Partiels ~ Audio Analysis Application


Partiels is an audio analysis application that allows you to explore the content and characteristics of sounds.

Features:

Partiels allows analysis of one or several audio files using Vamp plug-ins loading data files, visualizingeditingorganizing, and exporting the results as images or text files that can be used in other applications such as Max, Pure Data, Open Music, etc.

  • Windows, Mac & Linux support
  • Multiformat support
  • Multichannel support
  • Multiaudiofile support
  • Analyzing audio with Vamp plug-ins
  • Visualizing results as spectrogram, lines, and markers
  • Textual and graphical editing of results 
  • Organizing and ordering analyses in groups
  • Exporting results to PNG, JPEG, CSV, LAB, JSON, CUE, REAPER & SDIF formats
  • Loading results from CSV, LAB, JSON, CUE & SDIF formats
  • Batch processing
  • Command line interface to analyze, export, and convert results
  • Consolidating documents for sharing

Alongside Partiels, a wide range of analyses based on audio engines developed at IRCAM and outside are ported to Vamp plug-ins. These plug-ins allow you to perform FFT, LPC, transient, fundamental, formant, tempo, TTS and many other analyses. You can also find a large number of analysis plug-ins on the Vamp plug-ins website.

github.com/Ircam-Partiels
www.vamp-plugins.org

Rainmeter ~ Desktop VU Meter Display


www.deviantart.com/adni18/art/VU-Meter-For-Rainmeter-773359043
www.rainmeter.net

Foobar2000 ~ Installing A Lyrics Display Panel


Installing and Configuring OpenLyrics (foo_openlyrics) in foobar2000

OpenLyrics (foo_openlyrics) is the most actively maintained lyrics display component for foobar2000. It provides an integrated lyrics panel, automatic lyrics downloading, local storage, and optional editing support. This guide walks through installation, panel setup, and recommended configuration options.


Step 1: Download OpenLyrics

  1. Visit the official OpenLyrics component page:
    www.foobar2000.org/components/view/foo_openlyrics
  2. Download the latest .fb2k-component file.

Step 2: Install the Component

  1. Open foobar2000.
  2. Go to File → Preferences → Components.
  3. Click Install….
  4. Select the downloaded foo_openlyrics.fb2k-component file.
  5. Click Apply.
  6. Restart foobar2000 when prompted.

After restarting, OpenLyrics will be available as both a lyrics provider and a UI panel.


Step 3: Add the OpenLyrics Panel to the Layout

Default UI

  1. Go to View → Layout → Enable Layout Editing Mode.
  2. Right-click inside the layout where you want the lyrics panel.
  3. Choose Add New UI Element → Visualisations → OpenLyrics.
  4. Resize and position the panel as desired.
  5. Disable layout editing mode when finished.

Columns UI

  1. Go to Preferences → Display → Columns UI → Layout.
  2. Insert a new panel where desired.
  3. Select OpenLyrics from the panel list.
  4. Apply changes.

Step 4: Basic Playback Test

  1. Play a track with standard artist and title metadata.
  2. OpenLyrics will attempt to fetch lyrics automatically.
  3. If lyrics are found, they will display in the panel.
  4. If nothing appears immediately, allow a few seconds or manually trigger a search (see below).

Step 5: Configure Lyrics Sources

  1. Go to File → Preferences → Tools → OpenLyrics.
  2. Open the Sources section.
  3. Enable or disable lyrics providers as desired.
  4. Adjust source priority if available.

Notes:

  • Online lyrics availability depends on track metadata accuracy.
  • Some sources may return timed lyrics; others return plain text.
  • Source reliability can change over time, which is why OpenLyrics allows multiple providers.

Step 6: Configure Lyrics Saving and Storage

  1. In Preferences → Tools → OpenLyrics, locate the Saving or Storage options.
  2. Enable automatic saving of lyrics if you want lyrics cached locally.
  3. Choose a storage method:
    • External .lrc or .txt files
    • Embedded lyrics tags (if supported by your workflow)
  4. Define a lyrics file naming and folder structure if saving externally.

Recommended:

  • Saving lyrics externally allows reuse across systems and avoids repeated downloads.
  • Keeping lyrics alongside audio files simplifies backup and portability.

Step 7: Display and Behavior Settings

Within Preferences → Tools → OpenLyrics, review the display options:

  • Automatic scrolling
  • Alignment and text behavior
  • Timed lyrics synchronization behavior
  • Fallback handling when timed lyrics are unavailable

These settings affect how lyrics are rendered in the panel but do not affect stored data.


Step 8: Manual Search and Editing

If lyrics are not found automatically:

  1. Right-click inside the OpenLyrics panel.
  2. Choose Search lyrics or Edit lyrics (wording may vary by version).
  3. Manually paste or edit lyrics as needed.
  4. Save the lyrics so they persist for future playback.

OpenLyrics includes a built-in editor, allowing corrections or manual entry without external tools.


Step 9: Metadata Best Practices

For best results with OpenLyrics:

  • Ensure %artist% and %title% tags are accurate.
  • Avoid extra text such as “(Remastered)” or “feat.” in titles unless required.
  • Album artist tags can improve search accuracy for compilations.

Clean metadata significantly improves lyrics retrieval success.


Step 10: Troubleshooting

If lyrics do not appear:

  • Verify OpenLyrics is enabled under Preferences → Components.
  • Confirm the panel is visible and active.
  • Check that playback is active (lyrics are not fetched for stopped tracks).
  • Try manual search from the panel context menu.
  • Review source availability in the OpenLyrics preferences.

Summary

OpenLyrics is currently the most complete and actively maintained lyrics solution for foobar2000. Once installed and configured, it provides automatic lyrics retrieval, reliable local storage, and flexible display options suitable for both minimal and advanced layouts.

For new foobar2000 installations or users modernizing older setups, OpenLyrics is the recommended lyrics display component.

foobar2000 ~ foo_vis_spectrum_analyzer


foo_vis_spectrum_analyzer is a foobar2000 component that implements a spectrum analyzer panel. It is an attempt to recreate the foo_musical_spectrum component by fismineur for foobar2000 64-bit.

hydrogenaudio.org/index.php/topic,125031.0
www.foobar2000.org/components/view/foo_vis_spectrum_analyzer
github.com/stuerp/foo_vis_spectrum_analyzer

Rainmmeter ~ Digital VU-Meter With 7.1 Channels


Display a 7.1 channel VU meter on your desktop via Rainmeter.

www.deviantart.com/hitbit-pa/art/Digital-VU-Meter-7-1-channels
www.rainmeter.net

foo_vis_goom ~ What a GOOM! Visualisation


foo_vis_goom is a port for foobar2000 of the “What a GOOM!” music visualizer. It renders the library-provided pixels using OpenGL 4.6.

GOOM in an “incredible trippy visualization plugin!!”

Features:

  • Uses OpenGL 4.6 for rendering.
  • The Goom-2k4 library has been extensively cleaned up.
  • Compatible with the Default User Interface (Default UI) and the Columns User Interface (Columns UI).
  • Tested on foobar2000 v2.25.3 (x86 32-bit and x86 64-bit) and Microsoft Windows 11 (Build 26200).

www.foobar2000.org/components/view/foo_vis_goom

Cavasik ~ CAVA Based Audio Visualizer


This is an audio visualizer based on CAVA with extended capabilities.

Features:

  • Change background and foreground colors through a DBus interface!
  • Five normal drawing modes!
  • Two circle drawing modes!
  • Three mirror drawing modes!
  • Four drawing directions!
  • Customizable LibAdwaita interface!
  • Set a single color or up to a 10 color linear gradient for background and foreground!
  • Select different foreground colors for the mirrored images in mirror mode!
  • Set up a color animation that changes the colors gradually in a loop!
  • Configure smoothingnoise reduction and a few other CAVA settings!

github.com/TheWisker/Cavasik
flathub.org/apps/io.github.TheWisker.Cavasik