# Collection of Custom Formats for Radarr V3 Here I will try to collect a collection of the most needed and commonly used Custom Formats. These have been collected from either discussions on discord or that I created with help from others. Special thanks to [rg9400](https://github.com/rg9400){:target="_blank"}, [bakerboy448](https://github.com/bakerboy448){:target="_blank"} and Team Radarr. !!! warning "Important" Keep in mind Custom Formats are made to fine tune your Quality Profile **Quality Profile trumps Custom Formats** With Radarr V3, Custom Formats are much more advanced/powerful than with v0.2, although this also means a Custom Format is much more complicated to setup. After requesting at Team Radarr we now have the options to import/export the Custom Formats in a JSON format that we can use here what makes it easier to share the different kind of Custom Formats. I also made a [Guide](How-to-importexport-Custom-Formats-and-truly-make-use-of-it.md) on how to import/export the Custom Formats and how to truly make use of it. ------ ## INDEX | Audio | Audio Channels | Audio Advanced | Video | Video Advanced | Misc | | :--------------------------------------- | ---------------------------- | --------------------------------------------- | --------------------------------------------------------- | --------------------------------------------- | --------------------------------------------- | | [Dolby TrueHD/ATMOS](#dolby-truehdatmos) | [1.0 Mono](#10-mono) | [ATMOS (indeterminate)](#atmos-indeterminate) | [3D](#3d) | [Remaster](#remaster) | [BR-DISK](#br-disk) | | [DTS-HD/DTS:X](#dts-hddtsx) | [2.0 Stereo](#20-stereo) | [Basic Dolby Digital](#basic-dolby-digital) | [x264](#x264) | [4K Remaster](#4k-remaster) | [EVO except WEB-DL](#evo-except-web-dl) | | [Surround Sounds](#surround-sounds) | [3.0 Sound](#30-sound) | [Basic DTS](#basic-dts) | [x265](#x265) | [Criterion Collection](#criterion-collection) | [Low Quality Releases](#low-quality-releases) | | | [4.0 Sound](#40-sound) | [DD+ ATMOS (lossy)](#dd-atmos-lossy) | [Dolby Vision](#dolby-vision) | [Theatrical Cut](#theatrical-cut) | [Repack/Proper](#repack-proper) | | [AAC](#aac) | [5.1 Surround](#51-surround) | [Dolby Digital Plus](#dolby-digital-plus) | [Dolby Vision (Single Layer)](#dolby-vision-single-layer) | [Special Editions](#special-edition) | [Anime Dual Audio](#anime-dual-audio) | | [FLAC](#flac) | [6.1 Surround](#61-surround) | [DTS X](#dts-x) | [HDR](#hdr) | | [Hybrid](#hybrid) | | [MP3](#mp3) | [7.1 Surround](#71-surround) | [DTS-ES](#dts-es) | [10 Bit](#10-bit) | [Streaming Services](#streaming-services) | [Multi](#multi) | | [PCM](#pcm) | [9.1 Surround](#91-surround) | [DTS-HD HRA](#dts-hd-hra) | [MPEG2](#mpeg2) | [Dutch Groups](#dutch-groups) | [FreeLeech](#freeleech) | | [Opus](#opus) | | [DTS-HD MA](#dts-hd-ma) | | [HQ-P2P](#hq-p2p) | [720/1080p no x265](#7201080p-no-x265) | | | | [TrueHD (not ATMOS)](#truehd-not-atmos) | | | | | | | [TrueHD ATMOS](#truehd-atmos) | | | | ------ ## BR-DISK This is a custom format to help Radarr recognize & ignore BR-DISK (ISO's and Blu-ray folder structure) in addition to the standard BR-DISK quality. You will need to add the following to your new Custom Format when created in your Quality Profile (`Setting` => `Profiles`) and then set the score to `-1000` ??? example "json" ```json { "name": "BR-DISK", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "avc|vc-1|hevc", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "avc|vc-1|hevc" } }, { "name": "Remux", "implementation": "QualityModifierSpecification", "negate": true, "required": false, "fields": { "value": 5 } }, { "name": "WEBDL", "implementation": "SourceSpecification", "negate": true, "required": false, "fields": { "value": 7 } }, { "name": "^((?!x265).)*$", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "^((?!x265).)*$" } } ] } ``` !!! note Depending on your renaming scheme it could happen that Radarr will match renamed files after they are downloaded and imported as `BR-DISK`, This is a cosmetic annoyance till I come up for another way to solve this, being that this Custom Format is used to not download BR-DISK it does its purpose as intended. Several reasons why this is happening: - Blame the often wrongly used naming of x265 encodes. - Radarr v3 uses dynamic custom formats. ------ ## Dolby TrueHD/ATMOS If you prefer TrueHD|Atmos audio tracks. !!! warning Don't use this Custom Format in combination with the `Audio Advanced` CF if you want to fine tune your audio formats or else it will add up the scores. ??? example "json" ```json { "name": "Dolby TrueHD/ATMOS", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "truehd|atmos", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "truehd|atmos" } }] } ``` ------ ## DTS-HD/DTS:X If you prefer DTS-HD/DTS:X audio tracks. !!! warning Don't use this Custom Format in combination with the `Audio Advanced` CF if you want to fine tune your audio formats or else it will add up the scores. ??? example "json" ```json { "name": "DTS-HD/DTS:X", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "dts.?(hd|es|x(?!\\d))", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "dts.?(hd|es|x(?!\\d))" } }] } ``` ------ ## Dolby Vision (Single Layer) Custom Format for Single Layer Dolby Vision releases. !!! note This seems the preferred option for PLeX with a Shield 2019 model that supports DV. But keep in mind it also depends on how the releaser names the files! Shield can play any Single Layer DV in a .ts container via Plex natively. It can also play most Single Layer in .mkv but only via PlexForKodi with a modded version of exoplayer. An incompatible variant should still play as HDR10 in most clients. **UPDATE:** DV is part of the MKV spec now and ExoPlayer added native support so hopefully coming soon. ??? example "json" ```json { "name": "Dolby Vision (Single Layer)", "includeCustomFormatWhenRenaming": true, "specifications": [{ "name": "Dolby Vision (Single Layer)", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "sl.?dv|single.?layer.?dovi" } }, { "name": "Remux", "implementation": "QualityModifierSpecification", "negate": false, "required": true, "fields": { "value": 5 } } ] } ``` ------ ## Special Edition Custom format for several Special Editions - The Director's Cut is the version edited by the Director, usually for additional home media releases. - An Extended Cut is usually any version of the film which is longer than the theatrical cut (though in very rare cases, its shorter). ??? example "json" ```json { "name": "Special Edition", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "Special Edition ", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "(? x264 - 2160p/4k => x265 > If you want to make use of the Golden Rule you could make use of the following Custom Format [720/1080p no x265](#7201080p-no-x265) Some extra info about 4K/X265 [4k, transcoding, and you - aka the rules of 4k - a FAQ](https://forums.plex.tv/t/plex-4k-transcoding-and-you-aka-the-rules-of-4k-a-faq/378203) - Plex.tv 1. Don’t bother transcoding 4k 1. If you cannot direct play 4k, then perhaps you should not even be collecting 4k. 1. If you don’t have the storage space for a copy of both 4k and 1080/720, then perhaps you should not even be collecting 4k. 1. To avoid transcoding for remote and non-4k clients, keep your 4k content in separate plex libraries. ??? example "json" ```json { "name": "x265", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "x265", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "[xh]\\.?265|\\bHEVC(\\b|\\d)" } }, { "name": "Remux", "implementation": "QualityModifierSpecification", "negate": true, "required": true, "fields": { "value": 5 } } ] } ``` ------ ## Low Quality Releases A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality. !!! note You might want to add the following also [EVO except WEB-DL](#evo-except-web-dl) - BLOCK1 = Low-Quality Releases (often banned groups) - BLOCK2 = Another Small list of often banned groups. - BLOCK3 = And Another list. - BLOCK4 = Rips from Scene and quick-to-release P2P groups while adequate, are not considered high quality. ??? example "json" ```json { "name": "Low Quality Releases", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "[BLOCK1]", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "-aXXo|-CrEwSaDe|-DEViSE|-FaNGDiNG0|-FLAWL3SS|-FZHD|-FRDS|-HDTime|-IMAGINE|-iPlanet|-KingBen|-KiNGDOM|-KLAXXON|-Leffe|-LTRG|-mHD|-mSD|-NhaNc3|-nHD|-nikt0|-nSD|-PrisM|-PRODJi|-Rx|-RDN|-SANTi|-ViSION|-WAF|-WHiiZz|-x0r|\\bYIFY\\b|\\bYTS\\b|-STUTTERSHIT" } }, { "name": "[BLOCK2]", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "-CDDHD|-EuReKA|-DDR|-DNL|-BARC0DE" } }, { "name": "[BLOCK3]", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "\\bRARBG\\b|-FGT|-BReWeRS|-Grym|-LiGaS|-Zeus|-Tigole" } }, { "name": "[BLOCK4]", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "-beAst|-CHD|-HDWinG|-MTeam|-MySiLU|-WiKi" } } ] } ``` ------ ## EVO except WEB-DL This group is often banned for the low quality Blu-ray releases, but their WEB-DL are okay. You will need to add the following to your new Custom Format when created in your Quality Profile (`Setting` => `Profiles`) and then set the score to `-1000` ??? example "json" ```json { "name": "EVO (except WEB-DL)", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "EVO", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "\\bEVO\\b" } }, { "name": "WEBDL", "implementation": "SourceSpecification", "negate": true, "required": false, "fields": { "value": 7 } } ] } ``` ------ ## 3D If you prefer or not prefer 3D. You can use Custom Format or use Restrictions (`Settings` => `Indexers` => `Restrictions`) what ever you prefer. ??? example "json" ```json { "name": "3D", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "3d|sbs|half-ou", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "3d|sbs|half.?ou" } }] } ``` ------ ## 4K Remaster A remastered or mastered in 4K should give you usually the best picture and audio currently for the movie. Both are just names to describe the best possible currently for the movie. To be clear, the final digital films on the Mastered in 4K Blu-rays still only have the same 1920 x 1080 pixels of actual resolution as normal Blu-rays. But the argument goes that because these full HD files were derived from higher-resolution masters, their images will be more precise, with better colours, less noise, and enhanced sharpness and detail. Not least because the higher-resolution mastering process will provide more detail from the original print for the Blu-ray masters to draw on when going through their (hopefully…) frame-by-frame compression process. Another important element of the Mastered in 4K discs is that they’re all mastered with ‘x.v.YCC’ colour specification. This delivers an expanded colour range closer to that contained in original source material. ??? example "json" ```json { "name": "4K Remaster", "includeCustomFormatWhenRenaming": true, "specifications": [{ "name": "Remaster", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "Remaster" } }, { "name": "4K", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "4k" } }, { "name": "Not 4K Resolution", "implementation": "ResolutionSpecification", "negate": true, "required": true, "fields": { "value": 2160 } } ] } ``` ------ ## Anime Dual Audio ??? example "json" ```json { "name": "Anime Dual Audio", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "Dual Audio", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "dual\\.audio" } }, { "name": "BluDragon", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "bludragon" } }, { "name": "EN+JA", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "EN\\+JA|JA\\+EN" } }, { "name": "ZR", "implementation": "ReleaseTitleSpecification", "negate": false, "required": false, "fields": { "value": "\\bZR\\b" } }, { "name": "Japanese Language", "implementation": "LanguageSpecification", "negate": false, "required": true, "fields": { "value": 8 } } ] } ``` ------ ## ATMOS (indeterminate) Handles cases where only Atmos is specified in title but not DD+ or TrueHD (Where it is not specified if it is Lossy or Lossless) Give this the same score as Lossy Atmos, and then on import, it will get changed to either lossy or lossless based on mediainfo. ??? example "json" ```json { "name": "ATMOS (indeterminate)", "includeCustomFormatWhenRenaming": false, "specifications": [{ "name": "Dolby Digital Plus", "implementation": "ReleaseTitleSpecification", "negate": true, "required": true, "fields": { "value": "dd[p+]|eac3" } }, { "name": "ATMOS", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "\\bATMOS(\\b|\\d)" } }, { "name": "Not TrueHD", "implementation": "ReleaseTitleSpecification", "negate": true, "required": true, "fields": { "value": "TrueHD" } }, { "name": "Not DTS", "implementation": "ReleaseTitleSpecification", "negate": true, "required": true, "fields": { "value": "\\bDTS(\\b|\\d)" } }, { "name": "Not Basic Dolby Digital ", "implementation": "ReleaseTitleSpecification", "negate": true, "required": true, "fields": { "value": "(? `Profiles`) and then set the score to `-1000` !!! quote x265 is good for for 4k stuff or 1080p if they used the the remuxes as source. If the media isn't source quality/remux, then there will be a loss of quality every time. Also, once you go x265, typically that file is done. It can't be changed to something else without a huge loss of quality. Something like 95% of video files are x264 and have much better direct play support. If you have more than a couple users, you will notice much more transcoding. Just depends on your priorities. So basically if you are storage poor and just need to save space, use x265. The catch is if you want best quality x265, you need source quality files, so you still have huge file sizes. If you want maximum compatibility and the option to change your files to something else later, then x264. It's all really dependent on specific situations for different people It's a shame that most x265 groups microsize the releases or use the x264 as source what results in low quality releases. And the few groups that do use the correct source suffer from it. So I created my own golden rule. - 720/1080p => x264 - 2160p/4k => x265 ??? example "json" ```json { "name": "720/1080p != x265", "includeCustomFormatWhenRenaming": false, "specifications": [ { "name": "720p", "implementation": "ResolutionSpecification", "negate": false, "required": false, "fields": { "value": 720 } }, { "name": "1080p", "implementation": "ResolutionSpecification", "negate": false, "required": false, "fields": { "value": 1080 } }, { "name": "x265/HEVC", "implementation": "ReleaseTitleSpecification", "negate": false, "required": true, "fields": { "value": "[xh]\\.?265|\\bHEVC(\\b|\\d)" } } ] } ```