Servarr - User contributions [en]

Sonarr FAQ

2021-03-14T15:34:16Z

PhilxBefore: /* How does Sonarr handle scene numbering issues (American Dad!, etc)? */

== How does Sonarr find episodes? ==
<span id="how_does_Sonarr_find_episodes"><small>[[#how_does_Sonarr_find_episodes|anchor]]</small></span><br>

* Sonarr does ''not'' regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted episodes, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a show, you'll need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you don't need to initiate a search.
* Put another way, Sonarr will only find episodes that are newly uploaded to your indexers. It will not actively try to find episodes you want that uploaded in the past.
* If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can use the filters of <code>Missing</code> and <code>Cut-off Unmet</code>.
* If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.

== Why didn’t Sonarr grab an episode I was expecting? ==
<span id="Why_didnt_Sonarr_grab_an_episode_i_was_expecting"><small>[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]]</small></span><br>

First, make sure you read and understand the section above called ''“How does Sonarr find episodes?”'' Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
# Click the ‘Manual Search’ icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
# '''If there are results from step 1''', check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
# '''If there is at least one valid manual search result from step 2''', then an automatic download should have happened. If it didn’t, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
# '''If there is no manual result from a show, but you can find it when you browse your indexer’s website''' - This is a common problem that is most frequently caused by having an insufficient number of indexers. Different indexers index different content, and not all shows on your indexer may be tagged properly, which would cause Sonarr’s search to fail. Having several indexers active is the best solution to this problem.

== How are possible downloads compared? ==
<span id="how_are_possible_downloads_compared"><small>[[#how_are_possible_downloads_compared|anchor]]</small></span><br>
'''Generally Quality Trumps All'''

The current logic [https://github.com/Sonarr/Sonarr/blob/phantom-develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 1/19/2021 the logic is as follows'''''
# Quality
# Language
# Preferred Word Score
# Protocol
# Episode Count
# Episode Number
# Indexer Priority
# Peers (If Torrent)
# Age (If Usenet)
# Size

== Preferred Words FAQs ==
<span id="Preferred_Words_FAQs"><small>[[#Preferred_Words_FAQs|anchor]]</small></span><br>

For the score of the on disk file:
The existing name of the file and the "scene name" of the release are evaluated for preferred words. The higher score of the two is taken.

How are preferred words included in renaming?

For Sonarr you can make use of the `{Preferred Words}` token in your renaming scheme. and also check mark `Include Preferred when Renaming` in the release profile.
take a look [https://trash-guides.info/Sonarr/V3/Sonarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Sonarr.

For Radarr you can make use of the `{Custom Formats}` token in your renaming scheme. and you need to enable it in your Custom Format
take a look [https://trash-guides.info/Radarr/V3/Radarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Radarr.

Using the tokens in your renaming scheme could help with download loop issues.

== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
<span id="how_does_sonarr_handle_scene_numbering_issues"><small>[[#how_does_sonarr_handle_scene_numbering_issues|anchor]]</small></span><br>

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a ''black sheep'' and in this case there is a list of them.
** This is a list of the known shows and how/why they're problematic:
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokémon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking *dubbed* episodes. So if you want subbed episodes, you may be out of luck.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but dont count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), you are SOL & sonarr will never see them or find them. Right click > Save as on the torrent and add it manually is your <u>solution</u>. However here is the odd part, if you use tags and you add it to your client with a tag that Sonarr looks for, it will see the episodes and when they download it '''will''' automatically import them to S17. So it wont find S17 because it is mapped to S16 but it will import S17 to S17 even though it is mapped to S16. Cant explain it & never got an answer for it so enjoy the inconsistent logic as it will save you having to import it.
* '''Final thoughts:'''
** This may or may not happen on other shows but we have only tested it on this one. Main point, if you have any issues related to these shows you're kind of out of luck and just have to deal with it. It is something that is constantly being worked on and discussed as it is a pain for us as well as much as it is for you.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
<span id="why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x"><small>[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]]</small></span><br>

Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg ''CSI: Crime Scene Investigation'' as just ''CSI'' so Sonarr can’t match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. '''For anime, it will need to be added to [https://thexem.de thexem.de]''', for other series to request a new mapping see the steps below.

# Make sure it hasn’t already been requested. [https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0 Requested Mappings]
# Make a new request here: [https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform Scene Mapping Request Form]

''Typically these are added within 1-2 days.''

''Again, do not request a mapping for Anime; use XEM for that.'' Further information can be found with some of the XEM folks that hangout in our [https://discord.gg/an9rnEdWs5 <nowiki>#XEM</nowiki> discord channel].

== Sonarr grabbed a release, why can’t it import it? ==
<span id="sonarr_grabbed_a_release_why_cant_it_import_it"><small>[[#sonarr_grabbed_a_release_why_cant_it_import_it|anchor]]</small></span><br>

The reason it was able to grab the release in the first place was because the indexer returned the tv rage ID for the series and Sonarr was able to match it to that, but that ID is not available during import, so it fails.

== TVDB is updated why isn't Sonarr? ==
<span id="tvdb_is_updated_why_is_not_sonarr"><small>[[#tvdb_is_updated_why_is_not_sonarr|anchor]]</small></span><br>

TVDB has a 24 hour cache on their API. Skyhook has a much smaller few hour cache on top of that. Sonarr only runs the Refresh Series task every 12 hours. Thus it typically takes 24 to 48 hours for a TVDB update to make it into Sonarr.

If you know a TVDB update was made more than 48 hours ago, then please come discuss on our [https://discord.gg/M6BvZn5 Discord].
== I see that feature/bug X was fixed, why can’t I see it? ==
<span id="i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it"><small>[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it"|anchor]]</small></span><br>

Sonarr consists of two main branches of code, master and develop, master is released periodically, when the develop branch is stable and develop is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Sonarr_Settings#Updates|Release Branches]]. When a feature is marked as In Develop it will only be available to users running the develop branch, once it has been move to Live (in master) it is officially released.

== Episode Progress - How is it calculated? ==
<span id="episode_progress_-_how_is_it_calculated"><small>[[#episode_progress_-_how_is_it_calculated|anchor]]</small></span><br>

There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.

* Episode Count
** Episode has already aired AND is monitored OR
** Episode has a file
* Episode File Count
** Episode has a file

If a series has 10 episodes that have all aired and you don’t have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.

== How do I access Sonarr from another computer? ==
<span id="how_do_I_access_sonarr_from_another_computer"><small>[[#how_do_I_access_sonarr_from_another_computer|anchor]]</small></span><br>

By default Sonarr doesn’t listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).

== Why doesn’t Sonarr automatically search for missing episodes? ==
<span id="why_doesnt_sonarr_automatically_search_for_missing_episodes"><small>[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]]</small></span><br>

There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.

In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.

In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn’t there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.

== Why does Sonarr refresh series information so frequently? ==
<span id="why_does_sonarr_refresh_series_information_so_frequently"><small>[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]]</small></span><br>

* Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDB proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren’t airing are being updated with new information.
* The disk scan is less important, but is used to check for new files that weren’t sorted by Sonarr and detect deleted files.
* The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.

== Why is there a number next to Activity? ==
<span id="why_is_there_a_number_next_to_activity"><small>[[#why_is_there_a_number_next_to_activity|anchor]]</small></span><br>

* This number shows the count of episodes in your download client’s queue and the last 30 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
* You need to remove the item from your download client’s queue or history to remove them from Sonarr’s queue.

== I see log messages for shows I don’t have/don’t want ==
<span id="i_see_log_messages_for_shows_i_don_t_have_dont_want"><small>[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]]</small></span><br>

* These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you don’t want, in the event it is for a show you want, open up a support thread on the forums.

== Seeding torrents aren’t deleted automatically ==
<span id="seeding_torrents_arent_deleted_automatically"><small>[[#seeding_torrents_arent_deleted_automatically|anchor]]</small></span><br>

* When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and ''possible'') so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and ''look like it'' (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
* In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to ''pause'' or ''stop'' when they’re met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.

== Why can’t I add a new series? ==
<span id="why_cant_i_add_a_new_series"><small>[[#why_cant_i_add_a_new_series|anchor]]</small></span><br>

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by TheTVDB ID if you know what it is, the UI explains how to add it by an ID.

== Why can’t I add a new series when I know the TVDB ID? ==
<span id="why_cant_i_add_a_new_series_when_i_know_the_tvdb_id"><small>[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]]</small></span><br>

* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).

== Sonarr won't work on Big Sur ==
<span id="sonarr_wont_work_on_big_sur"><small>[[#sonarr_wont_work_on_big_sur|anchor]]</small></span><br>

Run <code>chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr</code>

== My Custom Script stopped working after upgrading from v2 ==
<span id="my_custom_script_stopped_working_after_upgrading_from_v2"><small>[[#my_custom_script_stopped_working_after_upgrading_from_v2|anchor]]</small></span><br>

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

{{FAQ|ARRNAME=Sonarr|ARRDISCORD=https://discord.gg/M6BvZn5|ARRPORT=8787}}

Definitions

2021-03-14T13:39:50Z

PhilxBefore: /* Video Qualities */

=== Download Protocols ===
* <code>Usenet</code> - (USEr NETwork) A public access network on the Internet that provides group discussions and group email. It is a giant, dispersed bulletin board that is maintained by volunteers who provide news and mail feeds to other nodes. All Usenet content is "NetNews," and a running collection of messages about a subject is a "newsgroup."
:'''Note:''' This is typically a paid service with a direct connection to the servers containing the data you're wishing to acquire. The connections can be quite fast and typically can saturate any home download connection. <br> For more information about Usenet and discussions about them we'd recommend you look at [https://www.reddit.com/r/usenet/ r/usenet]

* <code>Torrents</code> - In the BitTorrent file distribution system, a torrent file or meta-info file is a computer file that contains metadata about files and folders to be distributed, and usually also a list of the network locations of trackers, which are computers that help participants in the system find each other and form efficient distribution groups called swarms. A torrent file acts like a table of contents (index) that allows computers to find information through the use of a Bittorrent client. A torrent file gives addresses identifying computers that can send parts of the requested file.
:'''Note:''' Torrents in of them selves are completely innocuous and is simply a file sharing system. To share a file between two people is free. However, the service for finding the files (Trackers) and the computers that are hosting them can lead to a cost however there are may Trackers that are completely free to use. Torrent speeds are limited to the amount of seeders in a swarm. <br> For more information about Torrents and discussions about them we'd recommend you look at [https://www.reddit.com/r/torrents/ r/torrents]

=== Indexers/Trackers ===
==== Usenet ====
* <code>Indexers</code> - Usenet indexing sites allow you to search Usenet for specific posts. Some display the newsgroup and full subjects of each post matching the search criteria. Others allow you to download an NZB file which contains information about each post that your download client can use to automatically download the files. Indexes typically have a fee (usually to help cover server costs)that is typically paid yearly (some have an unlimited membership). <br> For more information about Indexers and discussions about them we'd recommend you look at [https://reddit.com/r/indexers r/indexers]

==== Torrents ====
* <code>Trackers</code> - Torrent trackers are servers that keep track of the peers who are available at the moment to offer you the requested files. These are a special type of servers that help in better communication between torrent clients and peers to speed up downloads.
** <code>Seeders</code> - Seeders are people who have a complete copy of the file. Seeders are only uploading because they already have the file finished, so there's no reason to download it.
** <code>Leechers</code> - Leechers are people with an incomplete copy of the file. Due to the nature of torrents, you are always sharing the part of the file that you have downloaded. So you are always uploading to others while you download the file yourself.
** <code>Ratio</code> - The ratio of what you have uploaded versus downloaded. Calculated as uploaded quantity / downloaded quantity.

=== Seedboxes ===

=== Common File Containers ===
*<code>MKV</code> - An MKV file is a video file saved in the Matroska multimedia container format. It supports several types of audio and video codecs and may include .SRT, .SSA, .USF (Universal Subtitle Format), or VobSub subtitles. MKV files are typically used for storing short video clips, TV shows, and movies.

*<code>MP4</code> - An MP4 file is a multimedia file commonly used to store a movie or video clip. It may also contain subtitles or images. MP4 is short for MPEG-4 Part 14, which is a container format based on the QuickTime File Format (QTFF) used by .MOV and .QT files

*<code>MP3</code> - An MP3 file is an audio file saved in a compressed audio format developed by the Moving Picture Experts Group (MPEG) that uses "Layer 3" audio compression (MP3). It is most commonly used to store music, but may also contain other types of audio content, such as a lecture, sermon, audiobook, or podcast.

*<code>AAC</code> - Compressed audio file similar to an .MP3 file, but offers several performance improvements; examples include a higher coding efficiency for both stationary and transient signals, a simpler filterbank, and better handling of frequencies above 16 kHz; maintains quality nearly indistinguishable from the original audio source.

*<code>OGG</code> - An OGG file is a compressed audio file that uses free, unpatented Ogg Vorbis audio compression. It is similar to an .MP3 file, but sounds better than an MP3 file of equal size, and may include song metadata, such as artist information and track data. OGG files are supported by many software music players and some portable music players.

*<code>FLAC</code> - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to an .MP3 file, but is compressed without any loss in quality or loss of any original audio data.

For a list of different video containers and its capabilities click [https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Video_coding_formats_support HERE]

For a list of different audio containers and its capabilities click
[https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Audio_coding_formats_support HERE]

=== Bitrates ===
<section begin=bitrates />
Bitrate, as the name implies, describes the rate at which bits are transferred from one location to another. In other words, it measures how much data is transmitted in a given amount of time. Bitrate is commonly measured in bits per second (bps), kilobits per second (Kbps), or megabits per second (Mbps). For example, a DSL connection may be able to download data at 768 kbps, while a Firewire 800 connection can transfer data up to 800 Mbps.

Bitrate can also describe the quality of an audio or video file. For example, an MP3 audio file that is compressed at 192 Kbps will have a greater dynamic range and may sound slightly more clear than the same audio file compressed at 128 Kbps. This is because more bits are used to represent the audio data for each second of playback. Similarly, a video file that is compressed at 3000 Kbps will look better than the same file compressed at 1000 Kbps. Just like the quality of an image is measured in resolution, the quality of an audio or video file is measured by the bitrate.
<section end=bitrates />

=== Scene Naming ===
<section begin=scene naming />
* <code>PROPER</code> - means there was a problem with the previous release. Downloads tagged as PROPER shows that the problems have been fixed in that release. This is done by a Group that did not release the original.
* <code>REPACK</code> - means there was a problem with the previous release and is corrected by the original Group. Downloads tagged as REPACK shows that the problems have been fixed in that release. This is done by a Group that did release the original.
<section end=scene naming />

=== Qualities ===
==== Video Qualities ====
<section begin=video-qualities />

<section begin=Unknown />*<code>Unknown</code> - Self Explanatory<section end=Unknown />

*<code>WORKPRINT</code> - A workprint of a film generally contains timecode and usually has watermarks from the studio involved in the production of the film. These "proxy" copies of a film often go between the editorial and visual effects departments of the film crew. A workprint may be of any resolution, but are generally lower quality versions of the film used to show progress on the editorial or post-production process. Therefore, these may not be at all the same as a theatrical version of the film, and may be missing many of the visual effects or audio that end up making it to the theatrical release.

*<code>CAM</code> - is a theater rip usually done with a digital video camera. A mini tripod is sometimes used, but a lot of the time this won't be feasible, so the camera may shake. Seating placement isn't always ideal, and it might be filmed from an awkward angle. If cropped properly, this is hard to tell unless there's text on the screen, but a lot of times these are left with triangular borders on the top and bottom of the screen. Sound is taken from the onboard microphone of the camera, and especially in comedies, laughter can often be heard during the film. Due to these factors picture and sound quality are usually quite poor, but sometimes we're lucky, and the theater will be fairly empty and a fairly clear signal will be heard.

*<code>TELESYNC</code> - is the same spec as a CAM except it uses an external audio source (most likely an audio jack in the chair for the disabled). A direct audio source does not guarantee good quality audio, as a lot of background noise can interfere. Sometimes a telesync is filmed in an empty cinema or from the projection booth with a professional camera, giving better picture quality. Quality ranges drastically. A high percentage of telesyncs are CAMs that have been mislabeled.

*<code>TELECINE</code> - A telecine machine copies the film digitally from the reels. Sound and picture should be very good, but due to the equipment and cost involved telecines are fairly uncommon. Generally, the film will be in correct aspect ratio, although 4:3 telecines have existed. TC should not be confused with TimeCode, which is a visible counter on screen throughout the film.

*<section begin=REGIONAL /><code>REGIONAL</code> - <--------------------- Needs definition<section end=REGIONAL />

*<code>DVDSCR</code> - A pre-release DVD often sent to awards judges and various other places for promotional use. A screener is supplied on a DVD or other large enough media. The main draw back is a “ticker” (a message that scrolls past at the bottom of the screen, with the copyright and anti-copy telephone number). Also, if the screener contains any serial numbers, or any other markings that could lead to the source of the tape, these will have to be blocked, usually with a black mark over the section. This is sometimes only for a few seconds, but unfortunately on some copies this will last for the entire film, and some can be quite big. Depending on the equipment used, screener quality can range from excellent to very poor. Usually transferred to SVCD, DivX/XviD, or MP4.

<section begin=SDTV />*<code>SDTV</code> - Post air rips from an analog source (usually cable television or OTA standard definition). The image quality is generally good (for the resolution) and they are usually encoded in DivX/XviD or MP4.<section end=SDTV />

<section begin=DVD />*<code>DVD</code> - A re-encode of the final released DVD9. If possible this is released PRE retail. It should be excellent quality (for the resolution). DVDrips are usually released in DivX/XviD or MP4.<section end=DVD />

*<code>DVD-R</code> - Same as DVD, but re-compressed to fit a single-layer DVD (generally reduces the original source bitrate by half, so the source material may have already been compressed from the original DVD copy and has been compressed a third time by the ripper).

<section begin=WEBDL-480p />*<code>WEBDL-480p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 480p (SD) quality. <section end=WEBDL-480p />

<section begin=WEBRip-480p />*<code>WEBRip-480p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 480p (SD) quality.<section end=WEBRip-480p />

<section begin=Bluray-480p />*<code>Bluray-480p</code> - A re-encode of the final released Blu-ray, downscaled to 480p resolution (720x480 @ 16:9, any other Aspect Ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to DivX, XviD, or AVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4, but some DivX/XviD are around as well which use AVI.<section end=Bluray-480p />

*<code>Bluray-576p</code> - Same as Bluray-480p, but in 576p (720x576). 576p is the standard PAL resolution for SDTV (although some manufacturers represent HDTV as anything above 480p, 576p offers barely any perceived quality increase over 480p). Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.

<section begin=HDTV-720p />*<code>HDTV-720p</code> - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1280x720 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4.<section end=HDTV-720p />

*<code>WEBDL-720p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 720p quality.

<section begin=WEBRip-720p />*<code>WEBRip-720p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 720p quality.<section end=WEBRip-720p />

<section begin=Bluray-720p />*<code>Bluray-720p</code> - A re-encode of the final released Blu-ray, downscaled to 720p resolution (1280x720 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-720p />

<section begin=HDTV-1080p />*<code>HDTV-1080p</code> - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4 container.<section end=HDTV-1080p />

<section begin=WEBDL-1080p />*<code>WEBDL-1080p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 1080p quality.<section end=WEBDL-1080p />

<section begin=WEBRip-1080p />*<code>WEBRip-1080p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 1080p quality.<section end=WEBRip-1080p />

<section begin=Bluray-1080p />*<code>Bluray-1080p</code> - A re-encode of the final released Blu-ray, at its native 1080p resolution (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality and the same resolution as the source. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while slightly reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-1080p />

<section begin=1080p Remux />*<code>Remux-1080p</code> - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 1080p quality.<section end=1080p Remux />

<section begin=HDTV-2160p />*<code>HDTV-2160p</code> - TVRip is a capture source from an capture card. HDTV stands for captured source from HD television. With an HDTV source, the quality can sometimes even surpass DVD. Movies in this format are starting to grow in popularity. Some advertisement and commercial banner can be seen on some releases during playback. This is at 2160p (4K) quality.<section end=HDTV-2160p />

<section begin=WEBDL-2160p />*<code>WEBDL-2160p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 2160p (4K) quality.<section end=WEBDL-2160p />

<section begin=WEBRip-2160p />*<code>WEBRip-2160p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 2160p (4k) quality.<section end=WEBRip-2160p />

<section begin=Bluray-2160p />*<code>Bluray-2160p</code> - A re-encode of the final released Blu-ray, at its native 2160p resolution (3840x2160 @ 16:9, any other aspect ratio may be a different resolution). 4K versions of films that are released in generally HEVC codec and could be either 8-bit or 10-bit color reproduction or from an HDR source. slightly reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-2160p />

<section begin=2160p-Remux />*<code>Remux-2160p</code> - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 2160p (4K) quality.<section end=2160p-Remux />

*<code>BR-DISK</code> - The original Blu-ray disc, with it's AVC/HEVC folder structure and no change in container format. Some media players are unable to deal with these, but they are generally used for archival purposes. The original Blu-ray disc content is unmodified. Most of the time, these have been run through an HDCP decryption process already via the ripper. Sometimes they are still encrypted.
<section end=video-qualities />

==== Audio Qualities ====
<section begin=audio-qualities />
*<code>AAC-192</code> - An AAC file with a 192 kbps bitrate
*<code>AAC-256</code> - An AAC file with a 256 kbps bitrate
*<code>AAC-320</code> - An AAC file with a 320 kbps bitrate
*<code>AAC-VBR</code> - An AAC file with a variable bitrate
*<code>ALAC</code> - Audio file created with the Apple Lossless Audio Codec (ALAC); used for storing digital music losslessly without losing any sound quality from the original audio data; differs from lossy audio codecs such as AAC.
*<code>APE</code> - Audio file compressed using Monkey's Audio lossless compression algorithm; includes error detection and support for tags that store information about audio files; sometimes created with .CUE files to comprise an audio CD image.
<section begin=FLAC />*<code>FLAC</code> - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to a .MP3 file, but is compressed without any loss in quality or loss of any original audio data.<section end=FLAC />
*<code>FLAC 24bit</code> - A FLAC file with 24-bit encoding, allowing a much wider dynamic range than CD, and sampling rates all the way up to 192kHz
*<code>MP3-8</code> - A MP3 file with a 8 kbps bitrate
*<code>MP3-16</code> - A MP3 file with a 16 kbps bitrate
*<code>MP3-24</code> - A MP3 file with a 24 kbps bitrate
*<code>MP3-32</code> - A MP3 file with a 32 kbps bitrate
*<code>MP3-40</code> - A MP3 file with a 40 kbps bitrate
*<code>MP3-48</code> - A MP3 file with a 48 kbps bitrate
*<code>MP3-56</code> - A MP3 file with a 56 kbps bitrate
*<code>MP3-64</code> - A MP3 file with a 64 kbps bitrate
*<code>MP3-80</code> - A MP3 file with a 80 kbps bitrate
*<code>MP3-96</code> - A MP3 file with a 96 kbps bitrate
*<code>MP3-112</code> - A MP3 file with a 112 kbps bitrate
*<code>MP3-128</code> - A MP3 file with a 128 kbps bitrate
*<code>MP3-160</code> - A MP3 file with a 160 kbps bitrate
*<code>MP3-192</code> - A MP3 file with a 192 kbps bitrate
*<code>MP3-224</code> - A MP3 file with a 224 kbps bitrate
*<code>MP3-256</code> - A MP3 file with a 256 kbps bitrate
<section begin=MP3-320 />*<code>MP3-320</code> - An MP3 file with a 320 kbps bitrate<section end=MP3-320 />
*<code>MP3-VBR-V0</code> - An MP3 file with a variable bitrate (version 0)
*<code>MP3-VBR-V2</code> - An MP3 file with a variable bitrate (version 2)
*<code>OGG Vorbis Q5</code> - An OOG file with an 160 kbps bitrate
*<code>OGG Vorbis Q6</code> - An OOG file with a 192 kbps bitrate
*<code>OGG Vorbis Q7</code> - An OOG file with a 224 kbps bitrate
*<code>OGG Vorbis Q8</code> - An OOG file with a 256 kbps bitrate
*<code>OGG Vorbis Q9</code> - An OOG file with a 320 kbps bitrate
*<code>OGG Vorbis Q10</code> - An OOG file with a 500 kbps bitrate
*<code>Unknown</code> - Self Explanatory
*<code>WavPack</code> - WavPack compresses high-quality audio to between thirty and seventy percent and supports both mono and stereo audio ranging from 8 to 32 bits. Typically these are audio files in an <code>.WV</code> container
*<code>WAV</code> - A WAV file is an audio file saved in the WAVE format, which is a standard digital audio file format utilized for storing waveform data. WAV files may contain audio recordings with different sampling rates and bitrates but are often saved in a 44.1 KHz, 16-bit, stereo format, which is the standard format used for CD audio.
*<code>WMA</code> - A WMA file is an audio file saved in the Advanced Systems Format (ASF) proprietary format developed by Microsoft. It contains Windows Media Audio and metadata objects such as the title, artist, album, and genre of the track. WMA files are similar to .MP3 files and primarily used for streaming music from the web.
<section end=audio-qualities />

==== eBook Qualities ====
<section begin=ebook-qualities />
*<code>Unknown</code> - Self Explanatory
*<code>PDF</code> - A PDF file is a multi-platform document created by Adobe Acrobat or another PDF application. The PDF format is commonly used for saving documents and publications in a standard format that can be viewed on multiple platforms. In many cases, PDF files are created from existing documents instead of from scratch. With that being said PDF isn't a book format it is originally designed as a printing format so a lot of features you'll find with other formats will not be available.
*<code>MOBI</code> - A MOBI file is an eBook saved in the MOBI format, a format originally used by the Mobipocket Reader but now supported by several different readers. It contains an eBook and may incorporate DRM copyright protection to prevent copying or unauthorized viewing. MOBI files are supported by various eReaders, tablets, PDAs, and desktop computer applications.
*<code>EPUB</code> - An EPUB file is a digital ebook saved in the EPUB format, an open XML-based format for digital books and publications. It provides a standard digital publication format for publishers and consumers. EPUB files can be viewed with supporting software programs and hardware devices, such as the Amazon Kindle and Barnes & Noble NOOK.
*<code>AZW3</code> - An AZW3 file is an eBook created in the Kindle Format 8 (KF8), Amazon's successor to the .AZW format. It supports newer features such as HTML5 and CSS3 support as well as many other formatting capabilities. AZW3 files often include DRM protection and are used as the download format for many Amazon eBooks.
<section end=ebook-qualities />

=== Indexer Flags ===

Torrent Indexers sometimes have torrents that, while they contain the same video, have other attributes that differentiate them. In Radarr, these are called Indexer Flags and you can do some cool stuff with them. See the table below, for a list of available flags and what they signify.

==== Uses ====

Indexer Flags can be used for multiple things in Radarr. Under Settings -> Indexers, you can e.g. specify that all releases with any indexer flag is preferred. This is useful, if you occasionally want to download a golden popcorn release over a normal encode.

If you want more control over indexer flags, there are two other options:

==== 1. Required Flags ====

In your indexer settings, you can specify, what exact flags are required, for a release to be downloaded for this indexer. This allows you to have a strict indexer only download freeleech torrents as an example. To require an indexer flag, look at the table below, take the flag name and put it in the corresponding field in your indexer’s settings.

==== 2. Custom Formats ====

'''(Radarr Only)'''
Indexer Flags can be used as Format Tags in a Custom Format. Check out the [[Radarr Settings#Custom Formats|Custom Formats]] section for more information.

==== Supported Flags ====

{| class="wikitable
!width="33%"| Flag Name
!width="33%"| Symbol
!width="33%"| Description
|-
| G_Freeleech
| ⬇⬇
| Sometimes, torrent sites set a torrent to be freeleech. This means, that the download of this torrent will not count towards your download quota or ratio. This is really useful, if you do not have the best ratio yet.
|-
| G_Halfleech
| ⇩⇩
| Similar to G_Freeleech, G_Halfleech signifies that only half of the size of this torrent will count towards your download quota or ratio.
|-
| G_DoubleUpload
| ⬆
| Similar to G_Freeleech, G_DoubleUpload signifies that any amount of data you upload via seeding is counted twice towards your upload quota and ratio. This is very useful, if you want to build up a ratio buffer.
|-
| PTP_Golden
| 🌟
| On PassThePopcorn, some torrents are given the Golden tag, when they meet certain encoding standards. These are usually the best encodes, with almost no perceptible quality loss. You can learn more on their wiki page.
|-
| PTP_Approved
| ✔
| On PassThePopcorn, some torrents are approved, when they meet the minimum standards for encoding (e.g. no low bitrates). See their wiki for more information.
|-
| HDB_Internal
| 🚪
| Releases on HDBits receive this tag, when the release was uploaded by one of the release groups of HDBits themselves.
|-
| G_Scene
| ☠
| This flag is applied to releases that are reported to be from a scene release group by your indexer.
|-
| G_Freeleech75
| ⇩⬇
| Similar to G_Freeleech, G_Freeleech75 signifies that only 25% of the size of this torrent will count towards your download quota or ratio.
|-
| G_Freeleech25
| ⇩
| Similar to G_Freeleech, G_Freeleech25 signifies that only 75% of the size of this torrent will count towards your download quota or ratio.
|}