Skip to content
Requests

What the requester sees

The detail page says up front where the title stands, not requested, requested, searching or already downloaded.

Jump there →
Screenshot: What the requester sees
Requests

The state sits on the poster

Once sent, nobody has to ask again.

Jump there →
Screenshot: The state sits on the poster
Requests

One season. Or two episodes to try it out.

For a series it does not have to be the whole series.

Jump there →
Screenshot: One season. Or two episodes to try it out.
Requests

My requests

Anyone wanting to know what became of their wishes finds them under My requests, with date, state and the quota they have left. Longer lists page in twenties.

Jump there →
Screenshot: My requests
Requests

Approve, or let it straight through

By default a request lands with you first.

Jump there →
Screenshot: Approve, or let it straight through
Requests

From one click to a finished file

Somebody sees a movie they want and presses a button. What happens next should not concern them, but you, running the thing, want to know exactly what goes where. This page walks the whole way once.

Step 1

What the requester sees

The detail page says up front where the title stands, not requested, requested, searching or already downloaded. The request button only appears if it is actually missing.

Then a panel opens with two fields: quality profile and target folder. Both are read live from Radarr and Sonarr, the only options offered are the ones that really exist there. If people should not choose at all, they never see the fields.

Series get a third field: individual seasons instead of the whole show. That is the difference between 40 GB and 400 GB.

Screenshot: a movie's detail page with the request panel open, showing the choice of quality profile and target folder
Before adding. Profile and folder are read from Radarr, not from a list inside Nexview. The line under the button says what happens next.
Step 2

The state sits on the poster

Once sent, nobody has to ask again. Every card in the catalogue carries its state visibly: what is already there is marked already downloaded, what is running is marked searching.

This is more than decoration. It prevents the single most common duplication, three people requesting the same movie one after another because none of them could see it was already on its way.

Screenshot: the catalogue's card grid, titles carrying badges such as “searching” and “already downloaded”
Three states at a glance. The badges come from the running sync with Radarr and Sonarr, not from a snapshot.
Not always everything

One season. Or two episodes to try it out.

For a series it does not have to be the whole series. In the request dialogue you can pick a single season or a handful of individual episodes, counted the way Sonarr counts them, not the way we thought was right.

That changes cancelling too: only what you ordered gets cancelled. The series stays for everybody else who wanted it, before, one cancellation took the request away from all of them.

A quota counts what was actually ordered, accordingly. Two episodes are two episodes, not a series.

Screenshot: the season list of a series with five seasons, each with its number of episodes and first air date, each one expandable
Every season opens up. Inside are the individual episodes, and which of them are already in the library.
Step 3

My requests

Anyone wanting to know what became of their wishes finds them under My requests, with date, state and the quota they have left. Longer lists page in twenties.

The bell up top reports every change: approved, found, finished. Anyone who would rather not know switches it off in their own profile, per event.

Screenshot: the “My requests” list with state, date and the reader's own quota
What became of the wish. Everyone sees this list only for themselves.
Step 4

Approve, or let it straight through

By default a request lands with you first. You see it in the approval list, grouped by person, and decide. Only with your yes does it go to Radarr or Sonarr, before that, nothing happens there.

People you trust get automatic approval; their requests then run straight through. Separately for movies and series, and separately for 4K.

The full story is on the page about approvals, roles and quotas.

Screenshot: the approval list with one waiting request and the approve and reject buttons beside it
Everything waiting, in one place. The row above filters by state, including what failed or was deleted again.
Afterwards

What Nexview does in the background

After handover Nexview keeps asking what became of the title and writes the state forward. That is why a card flips to already downloaded on its own, without anybody clicking.

When something goes wrong, the difference matters: a timeout only means the answer went missing, not that the request failed to arrive. Such cases stay at approved and resolve themselves on the next pass.

Only a real failure is shown as one. And a title that failed, was rejected or deleted again can be requested afresh, one mishap does not lock it away forever.

When Nexview procures through nexcrate, the handover goes there instead of to Radarr and Sonarr, and the title also says what it is waiting for right now. What else changes is on the nexcrate page.

Cancelling really deletes. If somebody cancels a running request, the title is removed from Radarr or Sonarr, including files already downloaded, and since 1.0.0 the download in the download client stops as well. In nexcrate mode the files go into nexcrate's recycle bin and can be brought back from there. The requester's quota is freed again in the process.

The callback

Radarr calls, instead of being asked

Nexview asks Radarr and Sonarr on a fixed schedule what became of a request. But minutes pass between two rounds, and during them the poster still says “searching” although the file arrived long ago.

So Nexview enters itself in both as a callback: when Radarr reports an import, the next round is pulled forward immediately instead of waiting for the tick.

The entry is only made after the connection has been proven, and whatever somebody else created there stays untouched. If the call stops arriving, that shows as a finding on the dashboard: not as an error, but as what it is, things still work, just more slowly.

As a side effect the word on the title is right too: while something is downloading it says “downloading”, not “searching” any more.

Optional

The same movie twice, in 4K

Optionally you enter a second Radarr and Sonarr instance. The same title can then be requested once in 1080p and once in 4K, two files, two folders, two requests that stay out of each other's way.

Root folders and quality profiles belong firmly to their instance. Nexview refuses a profile that does not belong, the ids of the two instances overlap, and Radarr accepts an unknown one without complaint. Without that check the mistake would surface only when the file lands in the wrong folder.

Each user has three switches, 4K movies, 4K series, 4K without approval, all off by default. Enter no second address and none of it is visible anywhere.