<inputclass="md-option"data-md-color-media="(prefers-color-scheme: dark)"data-md-color-scheme="slate"data-md-color-primary="indigo"data-md-color-accent="blue"aria-label="Switch to light mode"type="radio"name="__palette"id="__palette_0">
<inputclass="md-option"data-md-color-media="(prefers-color-scheme: light)"data-md-color-scheme="default"data-md-color-primary="indigo"data-md-color-accent="blue"aria-label="Switch to dark mode"type="radio"name="__palette"id="__palette_1">
<ahref="https://github.com/TRaSH-Guides/Guides/edit/master/docs/Radarr/radarr-setup-quality-profiles.md"title="Edit this page"class="md-content__button md-icon">
<ahref="https://github.com/TRaSH-Guides/Guides/raw/master/docs/Radarr/radarr-setup-quality-profiles.md"title="View source of this page"class="md-content__button md-icon">
<h1id="how-to-set-up-quality-profiles">How to set up Quality Profiles<aclass="headerlink"href="#how-to-set-up-quality-profiles"title="Permanent link"></a></h1>
<p><em>aka How to set up Custom Formats</em><br><br>
So what's the best way to set up the Custom Formats and which ones to use with which scores to set up your quality profiles?</p>
<p>There isn't a "best" setup, it depends on your media setup (hardware devices) and your personal preferences.</p>
<p>After you've added the Custom Formats, as explained in <ahref="/Radarr/Radarr-import-custom-formats/"rel="noopener noreferrer"target="_blank">How to import Custom Formats</a>.
You will need to set it up in the quality Profile you want to use/prefer to make use of the Custom Formats.</p>
<li>Keep upgrading Custom Format until this score is reached. (setting this to <code>0</code> means no upgrades will happen based on Custom Formats)</li>
<li>Your preferred language profile for your releases. (Original is recommended)</li>
<p>These screenshots are just examples to show you how it should look and where you need to place the data that you need to add, they aren't always a 100% reflection of the actual data and not always 100% up to date with the actual data you need to add.</p>
<ul>
<li>Always follow the data described in the guide.</li>
<p>Custom formats are controlled by Quality Profiles.</p>
<ul>
<li>The Upgrade Until score prevents upgrading once a release with this desired score has been downloaded.</li>
<li>A score of 0 results in the custom format being informational only.</li>
<li>The Minimum score requires releases to reach this threshold otherwise they will be rejected.</li>
<li>Custom formats that match with undesirable attributes should be given a negative score to lower their appeal.</li>
<li>Outright rejections should be given a negative score low enough that even if all of the other formats with positive scores were added, the score would still fall below the minimum.</li>
<p>The Current logic on how downloads are compared is <strong>Quality Trumps All</strong><imgalt="‼"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/203c.svg"title=":bangbang:"/></p>
<p><ahref="https://wiki.servarr.com/radarr/faq#how-are-possible-downloads-compared"rel="noopener noreferrer"target="_blank">Source: Wiki Servarr</a></p>
<p>REPACKS and PROPERs are v2 of Qualities and thus rank above a non-repack of the same quality.</p>
<p><code>Settings</code> =><code>Media Management</code> =><code>File Management</code> =><code>Proper & Repacks</code> Change to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper"rel="noopener noreferrer"target="_blank">Repack/Proper Custom Format</a></p>
<h2id="which-quality-profile-should-you-choose">Which Quality Profile should you choose<aclass="headerlink"href="#which-quality-profile-should-you-choose"title="Permanent link"></a></h2>
<p>The following Quality Profiles can be combined into a single Quality Profile if you, for example, want to be able to upgrade from 1080p to 4K/2160p.</p>
<p>All the used scores and combination of Custom Formats in this Guide are tested to get the desired results and prevent download loops as much as possible.</p>
<p>From experience most of the time when people change scores or leave out certain CF that work together they end up with undesired results.</p>
<p>If you're unsure or have questions do not hesitate to ask for help on Discord</p>
<p>IMAX Enhanced: Get More Picture Instead of Black Bars.</p>
<p>IMAX Enhanced exclusive expanded aspect ratio is 1:90:1, which offers up to 26% more picture for select sequences, meaning more of the action is visible on screen.</p>
<p>If you don't prefer <code>IMAX Enhanced</code> then don't add it or use a score of <code>0</code></p>
<p>I also suggest to change the Propers and Repacks settings in Radarr</p>
<p><code>Media Management</code> =><code>File Management</code> to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper">Repack/Proper</a> Custom Format.</p>
<li><strong>BR-DISK :</strong> 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.</li>
<li><strong>LQ:</strong> A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality or other reasons.</li>
<li><strong>LQ (Release Title):</strong> A collection of terms seen in the titles of Low Quality releases that are not captured by using a release group name.</li>
<p><strong>x265 (HD):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<td><ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a><imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></td>
<li><strong>Bad Dual Groups:</strong> [<em>Optional</em>] These groups take the original release and add their own language track (e.g. AAC 2.0 Portuguese) as the first track. Afterward, FFprobe would determine that the media file is Portuguese. It's a common rule that you only add the best audio as the main track.
Also they often even rename the release name into Portuguese.</li>
<li><strong>EVO (no WEBDL):</strong> This group is often banned for low-quality Blu-ray releases, but their WEB-DLs are okay.</li>
<li><strong>No-RlsGroup:</strong> [<em>Optional</em>] Some indexers strip out the release group which could result in LQ groups being scored incorrectly. For example, a lot of EVO releases end up with a stripped group name. These releases would appear as "upgrades" and could end up getting a decent score after other CFs are scored.</li>
<li><strong>Obfuscated:</strong> [<em>Optional</em>] Use these only if you wish to avoid renamed releases.</li>
<li><strong>Retags:</strong> [<em>Optional</em>] Use this if you want to avoid retagged releases. Retagged releases often are not consistent with the quality of the original group's release.</li>
<li><strong>Scene:</strong> [<em>Optional</em>] Use this only if you want to avoid SCENE releases.</li>
<li>
<p><strong>x265 (no HDR/DV):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<p><strong>But it will allow x265 releases if they have HDR and/or DV</strong></p>
<p><em>Being that some NF releases won't be released as 4k, but you want to have DV/HDR releases.</em></p>
<p>In your quality profile use the following score for this Custom Format: <code>-10000</code></p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd">x265 (HD)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<li>The reason why these Custom Formats have a score of <code>0</code> is because they are mainly used for the naming scheme and other variables should decide for movies if a certain release if preferred.</li>
<li><code>BCore</code>, <code>CRiT</code> and <code>MA</code> are the only ones with a score because of their better source material, or higher bitrate and quality compared to other streaming services.</li>
<p>I decided not to add <code>Audio Advanced</code> Custom Formats to the encodes profile. You will hardly find HD audio with HD Bluray Encodes. When downloading HD Bluray Encodes, I suggest going for quality. If you want HD audio formats, I would suggest going with a Remux or UHD Encode.</p>
<p>The order listed in the profile matters even if a quality is not checked, for example if you have a 1080p version but wanted the SD version, Radarr will reject all SD results because 1080p is listed higher than SD even though 1080p was not checked.</p>
<p>Qualities at the top of the list will appear first in manual searches.</p>
<ul>
<li>Qualities higher in the list are more preferred even if not checked.</li>
<li>Qualities within the same group are equal.</li>
<li>Only checked qualities are wanted.</li>
</ul>
<p>This is why it's recommended to move the selected quality to the top of the list.</p>
<p><ahref="https://wiki.servarr.com/en/radarr/settings#quality-profiles"rel="noopener noreferrer"target="_blank">Source: Wiki Servarr</a></p>
<p>All the used scores and combination of Custom Formats in this Guide are tested to get the desired results and prevent download loops as much as possible.</p>
<p>From experience most of the time when people change scores or leave out certain CF that work together they end up with undesired results.</p>
<p>If you're unsure or have questions do not hesitate to ask for help on Discord</p>
<li>Passthrough: The preferred method if you have an audio setup (AVR/Soundbar). This mode will send the audio signals without any alteration or processing.</li>
<li>Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server simply sends the media file as-is to the client. This uses very little CPU power.</li>
<li>Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.</li>
<li>Decodes: Decompresses the audio before sending it to your AVR/Soundbar.</li>
<p><em>partial used source: <ahref="https://support.firecore.com/hc/en-us/articles/217735707-Audio-Options-tvOS#h_01HE1Z5XNJZK5YTF1SVTPS0MTR"rel="noopener noreferrer"target="_blank">Infuse FAQ</a></em></p>
</details>
<detailsclass="info">
<summary>Am I losing any quality by using LPCM? - [Click to show/hide]</summary>
<ul>
<li>No. Since LPCM is a lossless format, using it will result in no loss of quality. What your ears hear will be exactly the same. The only difference is your receiver will recognize the audio stream as PCM instead of Dolby/DTS.</li>
<li>LPCM will discard object and spatial metadata. (TrueHD Atmos, DTS-X)</li>
<summary>Should I block certain audio formats because something in my setup doesn't support it? - [Click to show/hide]</summary>
<p>If you have chosen a profile that includes Audio Formats, it's somewhat pointless to lower the scores or block certain audio formats since 95% of the Remuxes and UHD Encodes provide HD audio formats such as TrueHD Atmos, TrueHD, and DTS-X.</p>
<p>So you have 2 options.</p>
<ol>
<li>Choose another quality profile that doesn't include audio formats such as <code>HD Bluray + WEB</code> or <code>2160p WEB-DL</code>.</li>
<li>Accept the limitations of your audio setup (AVR/Soundbar) and/or your hardware media player device.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/which-audio-formats-should-i-choose.md -->
<p>You have a 4K/2160p TV and a hardware media player device (such as Roku, AppleTV, Shield, SmartTV App, etc.) that supports several HDR formats (such as Dolby Vision, HDR10, HDR10+, etc.).</p>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
</div>
<!-- END INCLUDE -->
</li>
<li>
<p>You've chosen a profile that includes 4K/2160p releases. You must use all the HDR formats with 4k/2160p profiles.</p>
</li>
<li>You must add <strong>ALL</strong> the HDR formats - don't leave any of them out!</li>
</ul>
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-green-purple.md -->
<detailsclass="info">
<summary>Why am I getting purple or green colors? - [Click to show/hide]</summary>
<p>Why am I getting purple or green colors?</p>
<p>There are several possible reasons why your TV would show purple or green colors when playing Dolby Vision content.</p>
<ol>
<li>
<p><strong>Unsupported Hardware</strong>: Your TV or hardware media player device (Roku, AppleTV, etc) doesn't support Dolby Vision or your hardware media player device doesn't support all the Dolby Vision Profiles. As a result, the device might struggle to produce accurate colors, leading to a purple or green tint.</p>
</li>
<li>
<p><strong>Incorrect Display Settings</strong>: Dolby Vision content often requires specific settings to be enabled on your TV or display device in order to deliver the intended visual experience. If these settings are not configured properly, it can result in the device showing distorted colors (including purple or green hues).</p>
</li>
<li>
<p><strong>HDMI Compatibility Issues</strong>: Sometimes, HDMI cables or ports may not be fully compatible with Dolby Vision. If the media player device is not recognizing the Dolby Vision signal properly, it may fail to process the content correctly, resulting in abnormal color rendering.</p>
</li>
</ol>
<p>To resolve the purple or green color issues when playing Dolby Vision content, you can try the following troubleshooting steps:</p>
<ol>
<li>Ensure your TV or hardware media player device is Dolby Vision compatible and up-to-date with the latest firmware.</li>
<li>Verify that your TV or display device is set up correctly and has the necessary Dolby Vision settings enabled.</li>
<li>Check the HDMI cables and ensure they are capable of transmitting Dolby Vision signals.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-profiles.md -->
<detailsclass="info">
<summary>Dolby Vision Profiles - [Click to show/hide]</summary>
<p>Dolby Vision Profiles</p>
<ul>
<li><strong>Profile 5</strong><sup>(<em>1</em>)</sup> - This is what comes with WEB-DL Dolby Vision releases without HDR10 fallback.<br>(<em>Incompatible devices will playback with blown out pinks and greens</em>)</li>
<li><strong>Profile 7</strong><sup>(<em>2</em>)</sup> - This is what comes with UHD Bluray Remuxes and UHD BluRay releases.<br><em>These files will play on an Nvidia Shield Pro (2019), but on most other players will revert to the HDR10 fallback.</em></li>
<li><strong>Profile 8</strong><sup>(<em>3</em>)</sup> - This is what comes with (Hybrid) WEB-DL (HULU), Hybrid UHD Remux, and UHD BluRay releases (all of which have HDR10 fallback).<br><em>This works with several mainstream media players.</em><br></li>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
<li><sup>(<em>3</em>) <em>On PLEX for AppleTV it won't deliver real Dolby Vision with Profile 8, and will only play the HDR10 fallback if CM2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“although your TV will incorrectly say that it is playing DV”</em></strong>.<br><em>With infuse it will convert it on the fly to Profile 5, and deliver real Dolby Vision if CMv2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“Make sure you set the Extended Dolby Vision settings to Limited (prefer accuracy), Convert P8 to P5 (when possible), and play other P8 as HDR (output will switch to either DoVi or HDR depending on the video)”</em></strong></sup></li>
<summary>Dolby Vision Versions - CMv2.9 and CMv4.0 - [Click to show/hide]</summary>
<divclass="admonition bug">
<pclass="admonition-title">It is too technical to explain in detail, so I'll keep it short with tested facts: <br>PLEX for AppleTV and Plex with Infuse only support CMv2.9.</p>
<p>There are two versions of Dolby Vision, namely CMv2.9 and CMv4.0. CMv4.0 uses an improved algorithm and a superior tone curve that allows for better mapping and more controls during the Dolby Vision trim pass process.</p>
<p>More info about the different Dolby Vision Versions: <ahref="https://professionalsupport.dolby.com/s/article/When-should-I-use-CM-v2-9-or-CM-v4-0-and-can-I-convert-between-them?language=en_US">Dolby Vision Versions - CMv2.9 vs. CMv4.0</a></p>
<pclass="admonition-title">If you use this Custom Format then 99% of the time you also need to add the following Custom Format <code>DV (WEBDL)</code> with a score of <code>-10000</code></p>
<p>IMAX Enhanced: Get More Picture Instead of Black Bars.</p>
<p>IMAX Enhanced exclusive expanded aspect ratio is 1:90:1, which offers up to 26% more picture for select sequences, meaning more of the action is visible on screen.</p>
<p>If you don't prefer <code>IMAX Enhanced</code> then don't add it or use a score of <code>0</code></p>
<p>I also suggest to change the Propers and Repacks settings in Radarr</p>
<p><code>Media Management</code> =><code>File Management</code> to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper">Repack/Proper</a> Custom Format.</p>
<li><strong>BR-DISK :</strong> 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.</li>
<li><strong>LQ:</strong> A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality or other reasons.</li>
<li><strong>LQ (Release Title):</strong> A collection of terms seen in the titles of Low Quality releases that are not captured by using a release group name.</li>
<p><strong>x265 (HD):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<td><ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a><imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></td>
<li><strong>Bad Dual Groups:</strong> [<em>Optional</em>] These groups take the original release and add their own language track (e.g. AAC 2.0 Portuguese) as the first track. Afterward, FFprobe would determine that the media file is Portuguese. It's a common rule that you only add the best audio as the main track.
Also they often even rename the release name into Portuguese.</li>
<li><strong>EVO (no WEBDL):</strong> This group is often banned for low-quality Blu-ray releases, but their WEB-DLs are okay.</li>
<li><strong>No-RlsGroup:</strong> [<em>Optional</em>] Some indexers strip out the release group which could result in LQ groups being scored incorrectly. For example, a lot of EVO releases end up with a stripped group name. These releases would appear as "upgrades" and could end up getting a decent score after other CFs are scored.</li>
<li><strong>Obfuscated:</strong> [<em>Optional</em>] Use these only if you wish to avoid renamed releases.</li>
<li><strong>Retags:</strong> [<em>Optional</em>] Use this if you want to avoid retagged releases. Retagged releases often are not consistent with the quality of the original group's release.</li>
<li><strong>Scene:</strong> [<em>Optional</em>] Use this only if you want to avoid SCENE releases.</li>
<li>
<p><strong>x265 (no HDR/DV):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<p><strong>But it will allow x265 releases if they have HDR and/or DV</strong></p>
<p><em>Being that some NF releases won't be released as 4k, but you want to have DV/HDR releases.</em></p>
<p>In your quality profile use the following score for this Custom Format: <code>-10000</code></p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd">x265 (HD)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<li>The reason why these Custom Formats have a score of <code>0</code> is because they are mainly used for the naming scheme and other variables should decide for movies if a certain release if preferred.</li>
<li><code>BCore</code>, <code>CRiT</code> and <code>MA</code> are the only ones with a score because of their better source material, or higher bitrate and quality compared to other streaming services.</li>
<p>The order listed in the profile matters even if a quality is not checked, for example if you have a 1080p version but wanted the SD version, Radarr will reject all SD results because 1080p is listed higher than SD even though 1080p was not checked.</p>
<p>Qualities at the top of the list will appear first in manual searches.</p>
<ul>
<li>Qualities higher in the list are more preferred even if not checked.</li>
<li>Qualities within the same group are equal.</li>
<li>Only checked qualities are wanted.</li>
</ul>
<p>This is why it's recommended to move the selected quality to the top of the list.</p>
<p><ahref="https://wiki.servarr.com/en/radarr/settings#quality-profiles"rel="noopener noreferrer"target="_blank">Source: Wiki Servarr</a></p>
<p>All the used scores and combination of Custom Formats in this Guide are tested to get the desired results and prevent download loops as much as possible.</p>
<p>From experience most of the time when people change scores or leave out certain CF that work together they end up with undesired results.</p>
<p>If you're unsure or have questions do not hesitate to ask for help on Discord</p>
<li>Passthrough: The preferred method if you have an audio setup (AVR/Soundbar). This mode will send the audio signals without any alteration or processing.</li>
<li>Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server simply sends the media file as-is to the client. This uses very little CPU power.</li>
<li>Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.</li>
<li>Decodes: Decompresses the audio before sending it to your AVR/Soundbar.</li>
<p><em>partial used source: <ahref="https://support.firecore.com/hc/en-us/articles/217735707-Audio-Options-tvOS#h_01HE1Z5XNJZK5YTF1SVTPS0MTR"rel="noopener noreferrer"target="_blank">Infuse FAQ</a></em></p>
</details>
<detailsclass="info">
<summary>Am I losing any quality by using LPCM? - [Click to show/hide]</summary>
<ul>
<li>No. Since LPCM is a lossless format, using it will result in no loss of quality. What your ears hear will be exactly the same. The only difference is your receiver will recognize the audio stream as PCM instead of Dolby/DTS.</li>
<li>LPCM will discard object and spatial metadata. (TrueHD Atmos, DTS-X)</li>
<summary>Should I block certain audio formats because something in my setup doesn't support it? - [Click to show/hide]</summary>
<p>If you have chosen a profile that includes Audio Formats, it's somewhat pointless to lower the scores or block certain audio formats since 95% of the Remuxes and UHD Encodes provide HD audio formats such as TrueHD Atmos, TrueHD, and DTS-X.</p>
<p>So you have 2 options.</p>
<ol>
<li>Choose another quality profile that doesn't include audio formats such as <code>HD Bluray + WEB</code> or <code>2160p WEB-DL</code>.</li>
<li>Accept the limitations of your audio setup (AVR/Soundbar) and/or your hardware media player device.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/which-audio-formats-should-i-choose.md -->
<p>IMAX Enhanced: Get More Picture Instead of Black Bars.</p>
<p>IMAX Enhanced exclusive expanded aspect ratio is 1:90:1, which offers up to 26% more picture for select sequences, meaning more of the action is visible on screen.</p>
<p>If you don't prefer <code>IMAX Enhanced</code> then don't add it or use a score of <code>0</code></p>
<p>I also suggest to change the Propers and Repacks settings in Radarr</p>
<p><code>Media Management</code> =><code>File Management</code> to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper">Repack/Proper</a> Custom Format.</p>
<li><strong>BR-DISK :</strong> 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.</li>
<li><strong>LQ:</strong> A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality or other reasons.</li>
<li><strong>LQ (Release Title):</strong> A collection of terms seen in the titles of Low Quality releases that are not captured by using a release group name.</li>
<p><strong>x265 (HD):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<td><ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a><imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></td>
<li><strong>Bad Dual Groups:</strong> [<em>Optional</em>] These groups take the original release and add their own language track (e.g. AAC 2.0 Portuguese) as the first track. Afterward, FFprobe would determine that the media file is Portuguese. It's a common rule that you only add the best audio as the main track.
Also they often even rename the release name into Portuguese.</li>
<li><strong>EVO (no WEBDL):</strong> This group is often banned for low-quality Blu-ray releases, but their WEB-DLs are okay.</li>
<li><strong>No-RlsGroup:</strong> [<em>Optional</em>] Some indexers strip out the release group which could result in LQ groups being scored incorrectly. For example, a lot of EVO releases end up with a stripped group name. These releases would appear as "upgrades" and could end up getting a decent score after other CFs are scored.</li>
<li><strong>Obfuscated:</strong> [<em>Optional</em>] Use these only if you wish to avoid renamed releases.</li>
<li><strong>Retags:</strong> [<em>Optional</em>] Use this if you want to avoid retagged releases. Retagged releases often are not consistent with the quality of the original group's release.</li>
<li><strong>Scene:</strong> [<em>Optional</em>] Use this only if you want to avoid SCENE releases.</li>
<li>
<p><strong>x265 (no HDR/DV):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<p><strong>But it will allow x265 releases if they have HDR and/or DV</strong></p>
<p><em>Being that some NF releases won't be released as 4k, but you want to have DV/HDR releases.</em></p>
<p>In your quality profile use the following score for this Custom Format: <code>-10000</code></p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd">x265 (HD)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<li>The reason why these Custom Formats have a score of <code>0</code> is because they are mainly used for the naming scheme and other variables should decide for movies if a certain release if preferred.</li>
<li><code>BCore</code>, <code>CRiT</code> and <code>MA</code> are the only ones with a score because of their better source material, or higher bitrate and quality compared to other streaming services.</li>
<p><aclass="glightbox"href="../images/qp-remux-webdl-1080p.png"data-type="image"data-width="100%"data-height="auto"data-desc-position="bottom"><imgalt="Remux + WEB 1080p"src="../images/qp-remux-webdl-1080p.png"/></a></p>
<p>The order listed in the profile matters even if a quality is not checked, for example if you have a 1080p version but wanted the SD version, Radarr will reject all SD results because 1080p is listed higher than SD even though 1080p was not checked.</p>
<p>Qualities at the top of the list will appear first in manual searches.</p>
<ul>
<li>Qualities higher in the list are more preferred even if not checked.</li>
<li>Qualities within the same group are equal.</li>
<li>Only checked qualities are wanted.</li>
</ul>
<p>This is why it's recommended to move the selected quality to the top of the list.</p>
<p><ahref="https://wiki.servarr.com/en/radarr/settings#quality-profiles"rel="noopener noreferrer"target="_blank">Source: Wiki Servarr</a></p>
<p>All the used scores and combination of Custom Formats in this Guide are tested to get the desired results and prevent download loops as much as possible.</p>
<p>From experience most of the time when people change scores or leave out certain CF that work together they end up with undesired results.</p>
<p>If you're unsure or have questions do not hesitate to ask for help on Discord</p>
<li>Passthrough: The preferred method if you have an audio setup (AVR/Soundbar). This mode will send the audio signals without any alteration or processing.</li>
<li>Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server simply sends the media file as-is to the client. This uses very little CPU power.</li>
<li>Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.</li>
<li>Decodes: Decompresses the audio before sending it to your AVR/Soundbar.</li>
<p><em>partial used source: <ahref="https://support.firecore.com/hc/en-us/articles/217735707-Audio-Options-tvOS#h_01HE1Z5XNJZK5YTF1SVTPS0MTR"rel="noopener noreferrer"target="_blank">Infuse FAQ</a></em></p>
</details>
<detailsclass="info">
<summary>Am I losing any quality by using LPCM? - [Click to show/hide]</summary>
<ul>
<li>No. Since LPCM is a lossless format, using it will result in no loss of quality. What your ears hear will be exactly the same. The only difference is your receiver will recognize the audio stream as PCM instead of Dolby/DTS.</li>
<li>LPCM will discard object and spatial metadata. (TrueHD Atmos, DTS-X)</li>
<summary>Should I block certain audio formats because something in my setup doesn't support it? - [Click to show/hide]</summary>
<p>If you have chosen a profile that includes Audio Formats, it's somewhat pointless to lower the scores or block certain audio formats since 95% of the Remuxes and UHD Encodes provide HD audio formats such as TrueHD Atmos, TrueHD, and DTS-X.</p>
<p>So you have 2 options.</p>
<ol>
<li>Choose another quality profile that doesn't include audio formats such as <code>HD Bluray + WEB</code> or <code>2160p WEB-DL</code>.</li>
<li>Accept the limitations of your audio setup (AVR/Soundbar) and/or your hardware media player device.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/which-audio-formats-should-i-choose.md -->
<p><strong>Why would I choose All HDR formats?</strong></p>
<ul>
<li>
<p>You have a 4K/2160p TV and a hardware media player device (such as Roku, AppleTV, Shield, SmartTV App, etc.) that supports several HDR formats (such as Dolby Vision, HDR10, HDR10+, etc.).</p>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
</div>
<!-- END INCLUDE -->
</li>
<li>
<p>You've chosen a profile that includes 4K/2160p releases. You must use all the HDR formats with 4k/2160p profiles.</p>
</li>
<li>You must add <strong>ALL</strong> the HDR formats - don't leave any of them out!</li>
</ul>
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-green-purple.md -->
<detailsclass="info">
<summary>Why am I getting purple or green colors? - [Click to show/hide]</summary>
<p>Why am I getting purple or green colors?</p>
<p>There are several possible reasons why your TV would show purple or green colors when playing Dolby Vision content.</p>
<ol>
<li>
<p><strong>Unsupported Hardware</strong>: Your TV or hardware media player device (Roku, AppleTV, etc) doesn't support Dolby Vision or your hardware media player device doesn't support all the Dolby Vision Profiles. As a result, the device might struggle to produce accurate colors, leading to a purple or green tint.</p>
</li>
<li>
<p><strong>Incorrect Display Settings</strong>: Dolby Vision content often requires specific settings to be enabled on your TV or display device in order to deliver the intended visual experience. If these settings are not configured properly, it can result in the device showing distorted colors (including purple or green hues).</p>
</li>
<li>
<p><strong>HDMI Compatibility Issues</strong>: Sometimes, HDMI cables or ports may not be fully compatible with Dolby Vision. If the media player device is not recognizing the Dolby Vision signal properly, it may fail to process the content correctly, resulting in abnormal color rendering.</p>
</li>
</ol>
<p>To resolve the purple or green color issues when playing Dolby Vision content, you can try the following troubleshooting steps:</p>
<ol>
<li>Ensure your TV or hardware media player device is Dolby Vision compatible and up-to-date with the latest firmware.</li>
<li>Verify that your TV or display device is set up correctly and has the necessary Dolby Vision settings enabled.</li>
<li>Check the HDMI cables and ensure they are capable of transmitting Dolby Vision signals.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-profiles.md -->
<detailsclass="info">
<summary>Dolby Vision Profiles - [Click to show/hide]</summary>
<li><strong>Profile 5</strong><sup>(<em>1</em>)</sup> - This is what comes with WEB-DL Dolby Vision releases without HDR10 fallback.<br>(<em>Incompatible devices will playback with blown out pinks and greens</em>)</li>
<li><strong>Profile 7</strong><sup>(<em>2</em>)</sup> - This is what comes with UHD Bluray Remuxes and UHD BluRay releases.<br><em>These files will play on an Nvidia Shield Pro (2019), but on most other players will revert to the HDR10 fallback.</em></li>
<li><strong>Profile 8</strong><sup>(<em>3</em>)</sup> - This is what comes with (Hybrid) WEB-DL (HULU), Hybrid UHD Remux, and UHD BluRay releases (all of which have HDR10 fallback).<br><em>This works with several mainstream media players.</em><br></li>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
<li><sup>(<em>3</em>) <em>On PLEX for AppleTV it won't deliver real Dolby Vision with Profile 8, and will only play the HDR10 fallback if CM2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“although your TV will incorrectly say that it is playing DV”</em></strong>.<br><em>With infuse it will convert it on the fly to Profile 5, and deliver real Dolby Vision if CMv2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“Make sure you set the Extended Dolby Vision settings to Limited (prefer accuracy), Convert P8 to P5 (when possible), and play other P8 as HDR (output will switch to either DoVi or HDR depending on the video)”</em></strong></sup></li>
<summary>Dolby Vision Versions - CMv2.9 and CMv4.0 - [Click to show/hide]</summary>
<divclass="admonition bug">
<pclass="admonition-title">It is too technical to explain in detail, so I'll keep it short with tested facts: <br>PLEX for AppleTV and Plex with Infuse only support CMv2.9.</p>
<p>There are two versions of Dolby Vision, namely CMv2.9 and CMv4.0. CMv4.0 uses an improved algorithm and a superior tone curve that allows for better mapping and more controls during the Dolby Vision trim pass process.</p>
<p>More info about the different Dolby Vision Versions: <ahref="https://professionalsupport.dolby.com/s/article/When-should-I-use-CM-v2-9-or-CM-v4-0-and-can-I-convert-between-them?language=en_US">Dolby Vision Versions - CMv2.9 vs. CMv4.0</a></p>
<pclass="admonition-title">If you use this Custom Format then 99% of the time you also need to add the following Custom Format <code>DV (WEBDL)</code> with a score of <code>-10000</code></p>
<p>IMAX Enhanced: Get More Picture Instead of Black Bars.</p>
<p>IMAX Enhanced exclusive expanded aspect ratio is 1:90:1, which offers up to 26% more picture for select sequences, meaning more of the action is visible on screen.</p>
<p>If you don't prefer <code>IMAX Enhanced</code> then don't add it or use a score of <code>0</code></p>
<p>I also suggest to change the Propers and Repacks settings in Radarr</p>
<p><code>Media Management</code> =><code>File Management</code> to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper">Repack/Proper</a> Custom Format.</p>
<li><strong>BR-DISK :</strong> 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.</li>
<li><strong>LQ:</strong> A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality or other reasons.</li>
<li><strong>LQ (Release Title):</strong> A collection of terms seen in the titles of Low Quality releases that are not captured by using a release group name.</li>
<p><strong>x265 (HD):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<td><ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a><imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></td>
<li><strong>Bad Dual Groups:</strong> [<em>Optional</em>] These groups take the original release and add their own language track (e.g. AAC 2.0 Portuguese) as the first track. Afterward, FFprobe would determine that the media file is Portuguese. It's a common rule that you only add the best audio as the main track.
Also they often even rename the release name into Portuguese.</li>
<li><strong>EVO (no WEBDL):</strong> This group is often banned for low-quality Blu-ray releases, but their WEB-DLs are okay.</li>
<li><strong>No-RlsGroup:</strong> [<em>Optional</em>] Some indexers strip out the release group which could result in LQ groups being scored incorrectly. For example, a lot of EVO releases end up with a stripped group name. These releases would appear as "upgrades" and could end up getting a decent score after other CFs are scored.</li>
<li><strong>Obfuscated:</strong> [<em>Optional</em>] Use these only if you wish to avoid renamed releases.</li>
<li><strong>Retags:</strong> [<em>Optional</em>] Use this if you want to avoid retagged releases. Retagged releases often are not consistent with the quality of the original group's release.</li>
<li><strong>Scene:</strong> [<em>Optional</em>] Use this only if you want to avoid SCENE releases.</li>
<li>
<p><strong>x265 (no HDR/DV):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<p><strong>But it will allow x265 releases if they have HDR and/or DV</strong></p>
<p><em>Being that some NF releases won't be released as 4k, but you want to have DV/HDR releases.</em></p>
<p>In your quality profile use the following score for this Custom Format: <code>-10000</code></p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd">x265 (HD)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<li>The reason why these Custom Formats have a score of <code>0</code> is because they are mainly used for the naming scheme and other variables should decide for movies if a certain release if preferred.</li>
<li><code>BCore</code>, <code>CRiT</code> and <code>MA</code> are the only ones with a score because of their better source material, or higher bitrate and quality compared to other streaming services.</li>
<p><aclass="glightbox"href="../images/qp-remux-webdl-2160p.png"data-type="image"data-width="100%"data-height="auto"data-desc-position="bottom"><imgalt="Remux + WEB 2160p"src="../images/qp-remux-webdl-2160p.png"/></a></p>
<p>The order listed in the profile matters even if a quality is not checked, for example if you have a 1080p version but wanted the SD version, Radarr will reject all SD results because 1080p is listed higher than SD even though 1080p was not checked.</p>
<p>Qualities at the top of the list will appear first in manual searches.</p>
<ul>
<li>Qualities higher in the list are more preferred even if not checked.</li>
<li>Qualities within the same group are equal.</li>
<li>Only checked qualities are wanted.</li>
</ul>
<p>This is why it's recommended to move the selected quality to the top of the list.</p>
<p><ahref="https://wiki.servarr.com/en/radarr/settings#quality-profiles"rel="noopener noreferrer"target="_blank">Source: Wiki Servarr</a></p>
<p>Because I'm too lazy to calculate the maximum for every Quality Profile I use, and I want it to be upgraded to the highest possible score anyway.</p>
<h2id="custom-format-groups">Custom Format Groups<aclass="headerlink"href="#custom-format-groups"title="Permanent link"></a></h2>
<p>The following custom format groups should be combined with the Quality Profiles above. Users will need to choose which options and custom formats they prefer.</p>
<p><em>The reason that I score lossy Atmos higher than lossless DTS-HD MA is that I prefer having the object metadata (Atmos) over lossless audio.</em></p>
<li>Passthrough: The preferred method if you have an audio setup (AVR/Soundbar). This mode will send the audio signals without any alteration or processing.</li>
<li>Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server simply sends the media file as-is to the client. This uses very little CPU power.</li>
<li>Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.</li>
<li>Decodes: Decompresses the audio before sending it to your AVR/Soundbar.</li>
<p><em>partial used source: <ahref="https://support.firecore.com/hc/en-us/articles/217735707-Audio-Options-tvOS#h_01HE1Z5XNJZK5YTF1SVTPS0MTR"rel="noopener noreferrer"target="_blank">Infuse FAQ</a></em></p>
</details>
<detailsclass="info">
<summary>Am I losing any quality by using LPCM? - [Click to show/hide]</summary>
<ul>
<li>No. Since LPCM is a lossless format, using it will result in no loss of quality. What your ears hear will be exactly the same. The only difference is your receiver will recognize the audio stream as PCM instead of Dolby/DTS.</li>
<li>LPCM will discard object and spatial metadata. (TrueHD Atmos, DTS-X)</li>
<summary>Should I block certain audio formats because something in my setup doesn't support it? - [Click to show/hide]</summary>
<p>If you have chosen a profile that includes Audio Formats, it's somewhat pointless to lower the scores or block certain audio formats since 95% of the Remuxes and UHD Encodes provide HD audio formats such as TrueHD Atmos, TrueHD, and DTS-X.</p>
<p>So you have 2 options.</p>
<ol>
<li>Choose another quality profile that doesn't include audio formats such as <code>HD Bluray + WEB</code> or <code>2160p WEB-DL</code>.</li>
<li>Accept the limitations of your audio setup (AVR/Soundbar) and/or your hardware media player device.</li>
</ol>
</details>
<!-- END INCLUDE -->
<!-- BEGIN INCLUDE ../../includes/cf/which-audio-formats-should-i-choose.md -->
<li>You have a 4K TV and a hardware media player device (such as Roku, AppleTV, Shield, SmartTV App, etc.) that supports several HDR formats (such as Dolby Vision, HDR10, HDR10+, etc.).</li>
<p>You have a 4K/2160p TV and a hardware media player device (such as Roku, AppleTV, Shield, SmartTV App, etc.) that supports several HDR formats (such as Dolby Vision, HDR10, HDR10+, etc.).</p>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
<p>You've chosen a profile that includes 4K/2160p releases. You must use all the HDR formats with 4k/2160p profiles.</p>
</li>
<li>You must add <strong>ALL</strong> the HDR formats - don't leave any of them out!</li>
</ul>
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-green-purple.md -->
<detailsclass="info">
<summary>Why am I getting purple or green colors? - [Click to show/hide]</summary>
<p>Why am I getting purple or green colors?</p>
<p>There are several possible reasons why your TV would show purple or green colors when playing Dolby Vision content.</p>
<ol>
<li>
<p><strong>Unsupported Hardware</strong>: Your TV or hardware media player device (Roku, AppleTV, etc) doesn't support Dolby Vision or your hardware media player device doesn't support all the Dolby Vision Profiles. As a result, the device might struggle to produce accurate colors, leading to a purple or green tint.</p>
</li>
<li>
<p><strong>Incorrect Display Settings</strong>: Dolby Vision content often requires specific settings to be enabled on your TV or display device in order to deliver the intended visual experience. If these settings are not configured properly, it can result in the device showing distorted colors (including purple or green hues).</p>
</li>
<li>
<p><strong>HDMI Compatibility Issues</strong>: Sometimes, HDMI cables or ports may not be fully compatible with Dolby Vision. If the media player device is not recognizing the Dolby Vision signal properly, it may fail to process the content correctly, resulting in abnormal color rendering.</p>
</li>
</ol>
<p>To resolve the purple or green color issues when playing Dolby Vision content, you can try the following troubleshooting steps:</p>
<ol>
<li>Ensure your TV or hardware media player device is Dolby Vision compatible and up-to-date with the latest firmware.</li>
<li>Verify that your TV or display device is set up correctly and has the necessary Dolby Vision settings enabled.</li>
<li>Check the HDMI cables and ensure they are capable of transmitting Dolby Vision signals.</li>
<li><strong>Profile 5</strong><sup>(<em>1</em>)</sup> - This is what comes with WEB-DL Dolby Vision releases without HDR10 fallback.<br>(<em>Incompatible devices will playback with blown out pinks and greens</em>)</li>
<li><strong>Profile 7</strong><sup>(<em>2</em>)</sup> - This is what comes with UHD Bluray Remuxes and UHD BluRay releases.<br><em>These files will play on an Nvidia Shield Pro (2019), but on most other players will revert to the HDR10 fallback.</em></li>
<li><strong>Profile 8</strong><sup>(<em>3</em>)</sup> - This is what comes with (Hybrid) WEB-DL (HULU), Hybrid UHD Remux, and UHD BluRay releases (all of which have HDR10 fallback).<br><em>This works with several mainstream media players.</em><br></li>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
<li><sup>(<em>3</em>) <em>On PLEX for AppleTV it won't deliver real Dolby Vision with Profile 8, and will only play the HDR10 fallback if CM2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“although your TV will incorrectly say that it is playing DV”</em></strong>.<br><em>With infuse it will convert it on the fly to Profile 5, and deliver real Dolby Vision if CMv2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“Make sure you set the Extended Dolby Vision settings to Limited (prefer accuracy), Convert P8 to P5 (when possible), and play other P8 as HDR (output will switch to either DoVi or HDR depending on the video)”</em></strong></sup></li>
<summary>Dolby Vision Versions - CMv2.9 and CMv4.0 - [Click to show/hide]</summary>
<divclass="admonition bug">
<pclass="admonition-title">It is too technical to explain in detail, so I'll keep it short with tested facts: <br>PLEX for AppleTV and Plex with Infuse only support CMv2.9.</p>
<p>There are two versions of Dolby Vision, namely CMv2.9 and CMv4.0. CMv4.0 uses an improved algorithm and a superior tone curve that allows for better mapping and more controls during the Dolby Vision trim pass process.</p>
<p>More info about the different Dolby Vision Versions: <ahref="https://professionalsupport.dolby.com/s/article/When-should-I-use-CM-v2-9-or-CM-v4-0-and-can-I-convert-between-them?language=en_US">Dolby Vision Versions - CMv2.9 vs. CMv4.0</a></p>
<pclass="admonition-title">If you use this Custom Format then 99% of the time you also need to add the following Custom Format <code>DV (WEBDL)</code> with a score of <code>-10000</code></p>
<p>I also suggest that you change the Propers and Repacks settings in Radarr</p>
<p><code>Media Management</code> =><code>File Management</code> to <code>Do Not Prefer</code> and use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#repackproper">Repack/Proper</a> Custom Format.</p>
<p>This way you make sure the Custom Format preferences will be used instead.</p>
</details>
<h3id="custom-formats-to-avoid-certain-releases">Custom Formats to avoid certain releases<aclass="headerlink"href="#custom-formats-to-avoid-certain-releases"title="Permanent link"></a></h3>
When you add your preferred Custom Format and set it to something like <code>+10</code>, it's possible that, for example, the <code>BR-DISK</code> will be downloaded - (-10)+(+10)=0 - if your <code>Minimum Custom Format Score</code> is set at <code>0</code>.</p>
<li><strong>BR-DISK :</strong> 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.</li>
<li><strong>LQ:</strong> A collection of known Low Quality groups that are often banned from the the top trackers because the lack of quality or other reasons.</li>
<li><strong>LQ (Release Title):</strong> A collection of terms seen in the titles of Low Quality releases that are not captured by using a release group name.</li>
<p><strong>x265 (HD):</strong> This blocks 720/1080p (HD) releases that are encoded in x265. - More info <ahref="/Misc/x265-4k/"rel="noopener noreferrer"target="_blank">HERE</a>.</p>
<pclass="admonition-title">Don't use this together with <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-no-hdrdv">x265 (no HDR/DV)</a>, Only ever include one of them <imgalt="⚠"class="twemoji"src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/26a0.svg"title=":warning:"/></p>
<h3id="custom-formats-with-a-score-of-0">Custom Formats with a score of 0<aclass="headerlink"href="#custom-formats-with-a-score-of-0"title="Permanent link"></a></h3>
<p>Elsewhere in the guide, you will find a separate group of custom formats called <code>Audio Channels</code>. These will match the number of audio channels in a release, for example, 2.0 (stereo) or 5.1/7.1 (surround sound). Personally, I wouldn't add the audio channels Custom Formats as you could limit yourself in the amount of releases you're able to get. Only use them if you have a specific need for them.</p>
<p>Using this with any kind of Remux Quality Profile is useless, in my opinion, being that 99% of all Remuxes are multi-audio anyway. You can get better scores just by using the <code>Audio Advanced</code> Custom Formats.</p>
<h3id="avoid-using-the-x264x265-custom-format">Avoid using the x264/x265 Custom Format<aclass="headerlink"href="#avoid-using-the-x264x265-custom-format"title="Permanent link"></a></h3>
<p>Avoid using the x264/x265 Custom Format with a score if possible, it's smarter to use the <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd"rel="noopener noreferrer"target="_blank">x265 (HD)</a> Custom Format.</p>
<p>Something like 95% of video files are x264 and have much better direct play support. If you have more than a of couple users, you will notice much more transcoding.</p>
<p>Use x265 only for 4k releases and the <ahref="/Radarr/Radarr-collection-of-custom-formats/#x265-hd"rel="noopener noreferrer"target="_blank">x265 (HD)</a> makes sure you still get the x265 releases.</p>
<h3id="why-am-i-getting-purple-or-green-colors">Why am I getting purple or green colors<aclass="headerlink"href="#why-am-i-getting-purple-or-green-colors"title="Permanent link"></a></h3>
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-green-purple.md -->
<detailsclass="info">
<summary>Why am I getting purple or green colors? - [Click to show/hide]</summary>
<p>Why am I getting purple or green colors?</p>
<p>There are several possible reasons why your TV would show purple or green colors when playing Dolby Vision content.</p>
<ol>
<li>
<p><strong>Unsupported Hardware</strong>: Your TV or hardware media player device (Roku, AppleTV, etc) doesn't support Dolby Vision or your hardware media player device doesn't support all the Dolby Vision Profiles. As a result, the device might struggle to produce accurate colors, leading to a purple or green tint.</p>
</li>
<li>
<p><strong>Incorrect Display Settings</strong>: Dolby Vision content often requires specific settings to be enabled on your TV or display device in order to deliver the intended visual experience. If these settings are not configured properly, it can result in the device showing distorted colors (including purple or green hues).</p>
</li>
<li>
<p><strong>HDMI Compatibility Issues</strong>: Sometimes, HDMI cables or ports may not be fully compatible with Dolby Vision. If the media player device is not recognizing the Dolby Vision signal properly, it may fail to process the content correctly, resulting in abnormal color rendering.</p>
</li>
</ol>
<p>To resolve the purple or green color issues when playing Dolby Vision content, you can try the following troubleshooting steps:</p>
<ol>
<li>Ensure your TV or hardware media player device is Dolby Vision compatible and up-to-date with the latest firmware.</li>
<li>Verify that your TV or display device is set up correctly and has the necessary Dolby Vision settings enabled.</li>
<li>Check the HDMI cables and ensure they are capable of transmitting Dolby Vision signals.</li>
<!-- BEGIN INCLUDE ../../includes/cf/dv-info-profiles.md -->
<detailsclass="info">
<summary>Dolby Vision Profiles - [Click to show/hide]</summary>
<p>Dolby Vision Profiles</p>
<ul>
<li><strong>Profile 5</strong><sup>(<em>1</em>)</sup> - This is what comes with WEB-DL Dolby Vision releases without HDR10 fallback.<br>(<em>Incompatible devices will playback with blown out pinks and greens</em>)</li>
<li><strong>Profile 7</strong><sup>(<em>2</em>)</sup> - This is what comes with UHD Bluray Remuxes and UHD BluRay releases.<br><em>These files will play on an Nvidia Shield Pro (2019), but on most other players will revert to the HDR10 fallback.</em></li>
<li><strong>Profile 8</strong><sup>(<em>3</em>)</sup> - This is what comes with (Hybrid) WEB-DL (HULU), Hybrid UHD Remux, and UHD BluRay releases (all of which have HDR10 fallback).<br><em>This works with several mainstream media players.</em><br></li>
</ul>
<hr/>
<!-- BEGIN INCLUDE ../../includes/cf/dv-limitations-atv.md -->
<divclass="admonition bug">
<pclass="admonition-title">Plex for Apple TV and Plex with Infuse is only capable of playing Dolby Vision profiles 5 and 8 correctly if CMv2.9 is being used.<br>This is something that cannot be determined beforehand.<br>So whether you are using an Apple TV, with or without Infuse, it will always be hit or miss whether the content is compatible.<br>Additionally, it is uncertain whether the Dolby Vision layer will play, fall back to HDR10, or encounter a black screen.</p>
</div>
<!-- END INCLUDE -->
<ul>
<li><sup>(<em>1</em>) <em>PLEX for AppleTV and Plex with Infuse will only play profile 5 correctly if CMv2.9 is used</em></sup></li>
<li><sup>(<em>2</em>) <em>Neither Infuse nor PLEX for AppleTV will deliver real Dolby Vision with Profile 7.</em></sup></li>
<li><sup>(<em>3</em>) <em>On PLEX for AppleTV it won't deliver real Dolby Vision with Profile 8, and will only play the HDR10 fallback if CM2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“although your TV will incorrectly say that it is playing DV”</em></strong>.<br><em>With infuse it will convert it on the fly to Profile 5, and deliver real Dolby Vision if CMv2.9 is used, otherwise you will end up with a black screen</em><br><strong><em>“Make sure you set the Extended Dolby Vision settings to Limited (prefer accuracy), Convert P8 to P5 (when possible), and play other P8 as HDR (output will switch to either DoVi or HDR depending on the video)”</em></strong></sup></li>
</ul>
</details>
<detailsclass="info">
<summary>Dolby Vision Versions - CMv2.9 and CMv4.0 - [Click to show/hide]</summary>
<divclass="admonition bug">
<pclass="admonition-title">It is too technical to explain in detail, so I'll keep it short with tested facts: <br>PLEX for AppleTV and Plex with Infuse only support CMv2.9.</p>
</div>
<p>There are two versions of Dolby Vision, namely CMv2.9 and CMv4.0. CMv4.0 uses an improved algorithm and a superior tone curve that allows for better mapping and more controls during the Dolby Vision trim pass process.</p>
<p>More info about the different Dolby Vision Versions: <ahref="https://professionalsupport.dolby.com/s/article/When-should-I-use-CM-v2-9-or-CM-v4-0-and-can-I-convert-between-them?language=en_US">Dolby Vision Versions - CMv2.9 vs. CMv4.0</a></p>
<pclass="admonition-title">Questions or Suggestions?</p>
<p>If you have questions or suggestions click the chat badge to join the Discord Support Channel where you can ask your questions directly and get live support.</p>
<scriptid="__config"type="application/json">{"base":"../..","features":["navigation.instant","navigation.tabs","navigation.top","content.code.copy","content.action.edit","content.action.view"],"search":"../../assets/javascripts/workers/search.b8dbb3d2.min.js","translations":{"clipboard.copied":"Copied to clipboard","clipboard.copy":"Copy to clipboard","search.result.more.one":"1 more on this page","search.result.more.other":"# more on this page","search.result.none":"No matching documents","search.result.one":"1 matching document","search.result.other":"# matching documents","search.result.placeholder":"Type to start searching","search.result.term.missing":"Missing","select.version":"Select version"}}</script>
