Cava

Cava appears in two places in HyprFlux: the normal terminal visualizer and the compact Waybar visualizer. They do not share a runtime configuration.

Terminal Cava

Terminal Cava reads ~/.config/cava/config, which contains an independent static eight-color gradient. That palette is not generated by Wallust or the central HyprFlux color synchronizer.

Input declarations

The shipped file declares active Pulse and PipeWire method/source pairs in the same input section. Cava uses the later pair, so direct Cava effectively selects PipeWire with an automatic source. Remove the obsolete Pulse pair locally to make that intent unambiguous.

Waybar Cava

Waybar does not read ~/.config/cava/config. Its module runs WaybarCava.sh, which writes /tmp/bar_cava_config with:

Setting	Value
Frame rate	30 FPS
Bars	10
Input	Pulse, automatic source
Output	Raw ASCII
ASCII range	7

The script runs Cava against that temporary file and converts numeric output to compact glyphs for Waybar. There is no config-waybar file, click action, or periodic restart setting in the shipped module.

Launch and diagnose

Launch the normal visualizer with:

cava

Run the Waybar adapter directly for diagnostics:

~/.config/hypr/scripts/WaybarCava.sh

Stop only that adapter process with:

pkill -f 'cava -p /tmp/bar_cava_config'

Customization

• Edit ~/.config/cava/config for terminal Cava.
• Edit WaybarCava.sh only if you want to change Waybar's generated temporary configuration, then reload Waybar.
• Bundled shader files stay inactive unless you enable a compatible SDL/GLSL output path.

HyprFlux ships no Cava keybinding, floating window rule, alternate performance profile, or wallpaper-driven color updater.

Related pages

• Waybar
• Kitty