Quality profiles without having read the TRaSH Guides
A good quality profile in Radarr is forty decisions about resolution, audio tracks, release groups and scores. The TRaSH Guides explain every one of them — as a reference work, not as a walkthrough. Nexview asks a few questions instead and builds a finished profile from the answers.
In Nexview — which instances they land on is a separate question
A profile does not belong to an instance here. It sits in Nexview, and you decide separately which instances it gets pushed to. The same profile can sit on several — and be in a different state on each, if somebody tweaked it there by hand. The view shows exactly that.
The building blocks come from the TRaSH Guides and ship with Nexview, with a cut-off date. A button fetches the latest set if you want it — nothing happens on its own, and everything keeps working without a network.
The whole store can be saved to a file and read back somewhere else. Setting up a second installation does not mean entering the profiles again.
Six questions instead of forty decisions
The guide asks in plain language: what is this profile for, what resolution at minimum, how long may you wait, which sources are acceptable, which languages do you need. Out of the answers comes a complete profile, scores included.
Two paths, the same result: the simple one asks six questions and takes the guides' recommendation for everything else. The detailed one adds three steps about audio, video and release groups — for the cases where the recommendation is not enough.
Both build the same base profile; the extra questions only add further building blocks on top. So you cannot box yourself in by taking the short path — a second profile with different answers is always possible.
What actually sits on the instances — including what Nexview never touched
Everywhere else Nexview shows only what it made itself. Here it shows everything: every quality profile and every custom format in Radarr and Sonarr, including the ones from before.
The reason is a very concrete annoyance. A foreign profile holding a name, or blocking a delete, used to be invisible — you searched in Radarr without knowing what for. Because on a delete attempt Radarr only says “profile is in use” and does not tell you by whom. Nexview puts what depends on it right next to it: media, import lists, collections.
Plus the number you actually look for when tidying up: how many profiles on an instance are lying around unused.
What is in the file name survives losing the database
The TRaSH Guides recommend a naming scheme that writes the non-recoverable details into the file name: source, release group, edition. Those details are in no other file — lose the database and they are gone, unless they are in the name.
Nexview compares your current scheme with the recommendation, shows the difference and adopts it if you want. Which variant is recommended depends on the media server you have connected — Plex, Emby and Jellyfin do not read names the same way.
And because a new scheme would only apply to new files, Nexview can bring the existing ones along: Radarr and Sonarr do the renaming themselves.
Radarr can tell your media server
Radarr and Sonarr only tell your media server about imports, upgrades and renames if a connection is set up there. Without one, Plex, Emby or Jellyfin point at old paths until their own next scan — and in the meantime a film that was just upgraded simply will not play.
Nexview knows both sides — which instances exist and which media servers are connected — and can create the missing connections in one step.
Every connection is tested first. What the instance cannot reach does not get written. An entry pointing nowhere would be worse than none: it looks like the job is done.
Each its own tile — and a warning Radarr cannot give
Radarr, Radarr 4K, Sonarr, Sonarr 4K: every instance is its own tile with its address and its state. A click opens the form below it; what applies to both sits once above instead of twice beside.
Remove an instance and Nexview says first what depends on it — and leaves nothing half-connected behind.
⚠️ The warning Radarr cannot give itself: when two instances share a category in the download client, each grabs the other's downloads. Requests hang, files land in the wrong library — and no error appears anywhere, which is why the search usually starts at the network. Radarr cannot warn about it, it does not know the second instance exists. Nexview does. If you share on purpose, dismiss the warning; a third instance on the same category speaks up again.
