Packages and install order

openmixer ships as a small family of RPMs spread over three repositories. Only the openmixer ones are needed for a mixer that takes audio from the host's own sound devices; the REAC packages are added when the rig drives a Roland stagebox.

The packages

Package	Repository	What it installs
`openmixer`	`FreeMixer/openmixer`	A meta-package. Installs nothing itself; pulls in the server and the web UI.
`openmixer-server`	`FreeMixer/openmixer`	The engine and control plane under `/usr/lib/openmixer/server`, the command-line wrappers `/usr/bin/openmixer-server`, `/usr/bin/openmixer-console` and `/usr/bin/openmixer-patchbay`, the default `/etc/openmixer/config.json`, and the two systemd user units.
`openmixer-web-ui`	`FreeMixer/openmixer`	The static web surface under `/usr/share/openmixer/web-ui` and the nginx drop-in `/etc/nginx/conf.d/openmixer-web-ui.conf`. Its `%post` issues the console's own certificate under `/etc/openmixer/tls` and enables the https origin once the leaf is there. Requires `nginx` and `openssl`.
`openmixer-plugins-*`	`FreeMixer/openmixer`	Meta-packages that pull in a curated set of LV2 plugins (`-live`, `-live-extra`, `-studio`, …).
`reac-pw`	`FreeREAC/reac-pw`	`/usr/bin/reac-pw`, the REAC transport daemon. The binary only — the systemd unit that integrates it belongs to `openmixer-server`.
`libreac`	`FreeREAC/libreac`	The shared REAC library `reac-pw` links against. Installed automatically as a dependency.

openmixer-server recommends reac-pw. A weak dependency is only considered at the moment openmixer is first installed: if you enable the FreeREAC repository afterwards, a later dnf upgrade will not pull reac-pw in on its own. Install it explicitly in that case.

Install order

Package dependencies handle the order for you when you install from a repository:

sudo dnf install openmixer          # server + web UI
sudo dnf install reac-pw            # only if this rig drives a REAC stagebox

reac-pw pulls libreac in as an ordinary shared-library dependency.

Installing from local RPM files instead — for example a set you built yourself — the order does matter, because dnf will not resolve the FreeREAC packages for you:

sudo dnf install libreac-*.rpm
sudo dnf install reac-pw-*.rpm
sudo dnf install openmixer-*.rpm openmixer-server-*.rpm openmixer-web-ui-*.rpm

Plugins

The channel and output insert chains use LV2 plugins. Install one of the curated sets:

sudo dnf install openmixer-plugins-live

If no plugins are installed the desk still runs — faders, EQ, dynamics, buses and routing are all native — but the plugin picker will be empty. See the empty-catalog troubleshooting page.

What the install does to the host

firewalld: openmixer-web-ui opens TCP 8880 permanently. Removed again on a full uninstall, not on an upgrade.
SELinux: openmixer-web-ui labels /usr/share/openmixer/web-ui as httpd_sys_content_t so nginx may serve it.
Capabilities: the reac-pw package applies cap_net_raw,cap_sys_nice=ep to /usr/bin/reac-pw in its own scriptlet. openmixer never runs setcap on anything. Raw packet capture and real-time scheduling are what those grant; without them the REAC transport cannot see the wire.
Services: nothing is enabled automatically. See Services.

Verifying the install

rpm -q openmixer openmixer-server openmixer-web-ui reac-pw libreac
getcap /usr/bin/reac-pw          # expect cap_net_raw,cap_sys_nice=ep
openmixer-server --help