← All topics View on GitHub ↗

💬 General

Config — what the engine actually has on disk

StartSWest ·

This thread is for the Config tab.

What it's for: seeing what the engine actually has on disk — the FluidEQ Engine's or Equalizer APO's — not what FluidEQ intends. The two differ exactly when it matters: after a hand edit, another tool, or a restore from backup.

How it works: every layer is a file of its own, included per output, and the tab shows that include tree as it really is — what each file holds, which layers are on, and any include pointing at nothing. Each output also gets one file FluidEQ creates and never rewrites, applied last, for the commands that have no interface here; its filters are drawn on the graph and counted in the preamp. From here a whole chain exports to a .fluideq file and imports back onto the output you are listening to.

Ask here about the config layout, hand edits, and moving chains between machines.


Rewritten for 2.1. This thread was "Config — what Equalizer APO actually has on disk".

Formatting: **bold** _italic_ `code` - list [link](url)

Images: the box here takes text only — giscus cannot upload files. To attach a screenshot, write the post on GitHub and it appears here.

Loading the discussion from GitHub…

Topics Read the FAQ first

Your first five minutes

First steps with FluidEQ