Your ROOT_URL in app.ini is https://git.cloudchain.link/ but you are visiting https://dash.bss.nz/open-source-guides/TRaSH-Guides/blame/commit/9fd17618d76cca3bc4a7ea3ed2d6c03faa39ab28/docs/Misc/x265-4k.md You should set ROOT_URL correctly, otherwise the web may not work correctly.
TRaSH-Guides/docs/Misc/x265-4k.md

22 lines
1.1 KiB

# x265-4k
## x265
{! include-markdown "../../includes/docker/x265.md" !}
<!-- --8<-- "includes/docker/x265.md" -->
### How to accomplish the Golden Rule
- For Sonarr check [HERE](/Sonarr/Sonarr-Release-Profile-RegEx/#golden-rule){:target="_blank" rel="noopener noreferrer"}
- For Radarr check [HERE](/Radarr/Radarr-collection-of-custom-formats/#x265-hd){:target="_blank" rel="noopener noreferrer"}
## 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){:target="_blank" rel="noopener noreferrer"} - Plex.tv
1. Dont bother transcoding 4k
4 years ago
1. If you cannot direct play 4k, then perhaps you should not even be collecting 4k.
1. If you dont 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.
1. This may of course mean that you keep a 4k copy and a 1080/720 copy, but if you are collecting 4k content then you should not be worried about storage space, should you?