This clears every station, track, log, playlist and user from the local Interlude database. Interlude rebuilds the empty schema by itself the next time it starts. Nothing needs reinstalling.
This cannot be undone. Everything in the database is deleted. Your audio files on disk are not touched.
Close the Interlude window and make sure it is gone from the system tray too. Quitting also stops the Interlude server and the air agent. Leave the PostgreSQL service running.
A normal PowerShell window is enough. You do not need to run it as administrator.
Interlude generated a unique password for this machine when it installed PostgreSQL. It is stored in %APPDATA%\Cadence\cadence-config.json (the folder keeps Interlude’s earlier name). Paste these two lines to read it from there. Nothing is printed.
$cfg = Get-Content "$env:APPDATA\Cadence\cadence-config.json" -Raw | ConvertFrom-Json
$env:PGPASSWORD = [uri]::UnescapeDataString(([uri]$cfg.databaseUrl).UserInfo.Split(':')[1])If you'd rather type the password yourself, open the file in Notepad and look for "databaseUrl": "postgres://cadence:PASSWORD@127.0.0.1:5432/cadence". Skip this step, and psql asks for the password at each command.
psql came with the PostgreSQL that Interlude installed, but it is not on the PATH, so call it by its full path. Run the three lines in order.
$psql = "$env:ProgramFiles\PostgreSQL\16\bin\psql.exe" & $psql -h 127.0.0.1 -U cadence -d postgres -c "DROP DATABASE cadence WITH (FORCE);" & $psql -h 127.0.0.1 -U cadence -d postgres -c "CREATE DATABASE cadence OWNER cadence;"
You should see DROP DATABASE and then CREATE DATABASE. WITH (FORCE) disconnects anything that is still connected, so a stray Interlude process can't block the delete.
The air agent keeps a local queue of plays it hasn't uploaded yet, plus an audio cache. If you keep them, plays from the old database can be uploaded into the new one. Delete both folders:
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Cadence\AirAgent\asrun", "$env:LOCALAPPDATA\Cadence\AirAgent\cache" -ErrorAction SilentlyContinue
Keep agent.token in that folder. It is how the agent identifies itself to the server.
At startup the server finds an empty database and applies every schema migration. That takes a few seconds. You then have a blank system: no stations, no library and no users. Because there are no user accounts, you won't get a login prompt until you create the first user.
%APPDATA%\Cadence\cadence-config.json, including the database connection and paths.audio.json).postgresql-cadence Windows service.If a step fails with password authentication failed, step 3 didn't pick up the password. Run it again in the same PowerShell window you use for step 4.