deemix: Downloads That Go Straight to Review

Review happens immediately

Files from Usenet and deemix go to the review queue at once rather than after Aurral tries everything else. The reason is that these sources declare identity through the release they belong to, so a duration mismatch is a stronger signal of a wrong file than it is on a peer-to-peer network.

Each review row shows the requested track, artist and album, the path of the downloaded file, the match scores and the duration. Preview it, then approve or deny.

• Approve moves the file into the library.
• Deny deletes it and reruns the search without that file.
• Aurral never deletes a file in the Downloads Folder or a Lidarr root folder this way, so a deemix file saved outside the Aurral area is left alone.

Files Aurral will not delete

Aurral does not delete Usenet or deemix files it cannot prove it owns. If a client finishes after a playlist was removed, check the client's completed-download folder for anything left behind.

This is a deliberate limit rather than an oversight. Deemix in particular can place files in locations Aurral did not choose, and deleting something because it looks like ours is the kind of mistake that is not recoverable.

Source priority in practice

deemix sits in the source order alongside slskd and Usenet. For missing tracks, the first client that produces a valid file wins. For quality upgrades, deemix is consulted last, after slskd and Usenet, and only if they came up empty.

The maximum wait setting in the review queue applies here as it does elsewhere. With the default of 0, a file can sit indefinitely. Setting a cap is worth doing if you import large playlists, because otherwise a burst of unverified downloads can accumulate.