diff --git a/README.md b/README.md index f14bd48..b4f3f1a 100644 --- a/README.md +++ b/README.md @@ -179,7 +179,208 @@ Once the Tdarr Server is running, install **Tdarr Node** (a separate listing). T
image
**Identify GPUs** by running: +
image
+> **Warning:** One entry might be your iGPU. Don’t assign your iGPU to a Tdarr node. + +**Tip:** Go to Plex → Settings → Transcoding. When you pick a GPU in Plex, the GPU order matches the order from `ls -la /dev/dri`. In the example below, `render129` is the iGPU, so I skip it and use `render130` for Node2 and `render131` for Node3. + +
image
+ +### Configuring Tdarr + +1. Go to `http://:8265`. +2. You should see your nodes listed: + +
image
+ +3. For each node, click it and set CPU/GPU worker counts based on your ARC card: + + - **ARC A310** + - Transcode: CPU (0), GPU (2–3) + - Health Check: CPU (2), GPU (0) + + - **ARC A380** + - Transcode: CPU (0), GPU (2–4) + - Health Check: CPU (2), GPU (0) + + - **ARC A500/A700** + - Transcode: CPU (0), GPU (2–5) + - Health Check: CPU (2), GPU (0) + +
image
+ +4. Click **Options**, scroll to the bottom, and enable “GPU Workers to do CPU Tasks,” then close. + +
image
+ +5. In the staging section, check **Auto-accept successful transcodes** so Tdarr replaces old files automatically. + +
image
+ +6. In **Status**, pick the queue order (e.g., largest files first). + +
image
+ +--- + +# Setting up the AV1 Tdarr Flow + +**Change Log** +- **v1:** Original AV1 flow +- **v2:** Removed B-frames +- **v3:** Improved quality +- **v4:** Removed images from files (failure rates ~25% → 1–2%) +- **v5:** Better quality, simpler flow + +**JSON Script:** [av1_flow_v5.json](av1_flow_v5.json) + +image + +## What is the AV1 Flow? + +The AV1 Flow is a prebuilt workflow that encodes your media to AV1 for huge storage savings, without requiring expert knowledge of encoding parameters. You must import it before creating your Tdarr libraries. + +## Importing the AV1 Flow in Tdarr + +1. In Tdarr, go to **Flows**. +2. Scroll down and click **Import**. +3. Paste the AV1 Flow JSON. +4. Apply it to your libraries. + +![Adding a New Flow in Tdarr](https://i.imgur.com/nLzQi1b.png) +![Scroll to Import Option](https://i.imgur.com/hmYNetQ.png) +![Pasting the JSON Content](https://i.imgur.com/Qe13kYg.png) + +--- + +# Optimizing AV1 Encoding Settings + +Within the AV1 flow, adjust **CRF** and **bitrate** to balance quality and size. Make sure you’ve enabled hardware acceleration so the GPU does the heavy lifting. In general: + +- **Higher CRF** → Lower quality, smaller files +- **Lower CRF** → Higher quality, larger files + +I’ve found the default settings in the AV1 Flow give an excellent quality-to-size ratio. If you want finer control, test small sets of files and tweak CRF/bitrate until you find your sweet spot. + +
image
+
image
+ +--- + +# Setting Up Tdarr Libraries + +Libraries let you specify locations and define how Tdarr processes them. For instance, you might have separate libraries for “tv” and “movies.” Adjust to your setup. + +1. Click **Libraries**: +
image
+ +2. Click **Library+**: +
image
+ +3. Name your new library (e.g., “TV,” “Movies,” etc.). +4. Under **Source**, point it to your media folder. Enable [Hourly] scanning to catch new content. + +
image
+
image
+ +5. Under **Transcode Cache**, set the path to `/temp` (or your chosen transcode folder). + +
image
+ +6. In **Filters**, add `AV1` to “Codecs to Skip,” so you never re-encode existing AV1 files. You can also skip small files if you like. + +
image
+ +7. In **Transcode Options**, uncheck “Classic Plugins,” go to the **Flows** tab, and pick the AV1 flow. (If you haven’t imported the flow yet, see the [Importing the AV1 Flow in Tdarr](#importing-the-av1-flow-in-tdarr) section first.) + +
image
+ +8. Repeat for all your libraries. +9. Perform a **Fresh New Scan** to apply changes. + +
image
+ +10. After scanning, the home page should show transcoding activity. If not, re-check your GPU assignments and node settings. + +
image
+ +11. If you see tons of errors, review your GPU configuration or flow settings. + +
image
+ +--- + +# SABNZBD Speed Control - Bonus + +You can also tie SABnzbd’s download speed to Plex streaming demand. By throttling SABnzbd when Plex is active, you minimize buffering. Check out Tautulli’s scripts or the SABnzbd API for ways to reduce speed during high stream loads. This is optional but can significantly improve user experience if you often saturate your internet bandwidth with downloads. + +--- + +# Tdarr Node Killer Script + +**Change Log** +- **v1:** Original script +- **v2:** Switched to Tautulli for simpler detection +- **v3:** Option to avoid killing Tdarr node on local-only transcodes +- **v4:** Added a threshold to kill the Tdarr container only if transcodes exceed (default) 3 sessions +- **v5:** Added Tautulli API connectivity check in logs at startup + +## Overview + +The Tdarr Node Killer script ensures Plex always has GPU priority. When Plex starts transcoding on the same GPU, the script stops Tdarr. Once Plex stops, it waits a short cooldown and restarts Tdarr. + +## Script Behavior + +- Stops the Tdarr Node container as soon as Plex begins GPU transcoding. +- Waits for Plex transcoding to end, then restarts Tdarr after a short cooldown (e.g., 3 minutes). + +**Script:** [tdarr_node_killer.sh](tdarr_node_killer.sh) + +Use **User Scripts** in Unraid to install this script, set it to run on array startup, and keep it running in the background. + +image + +## Step-by-Step Implementation for Unraid + +1. Confirm Tdarr Node [N1] is running when no one’s transcoding in Plex: +
image
+ +2. The script runs and waits for Plex transcoding activity: +
image
+ +3. A user begins transcoding in Plex: + + ![Plex User Starts Transcoding](https://i.imgur.com/AT6hCUV.png) + +4. The script detects transcoding and stops the Tdarr Node: + +
image
+
image
+ +5. Tdarr Node [N1] is now stopped: + +
image
+ +## Script Behavior After Plex Transcoding Stops + +When Plex finishes transcoding, the script waits a cooldown (e.g., 180 seconds) and then restarts Tdarr: + +1. You’ll see a countdown timer in the logs before it restarts the container. +2. Tdarr Node starts again after the countdown: + +
image
+
image
+ +3. Tdarr Node is fully online: + + ![Tdarr Node Online](https://i.imgur.com/M1M2vSL.png) + +## Troubleshooting Common Issues + +- **Plex Not Using GPU?** Re-check your Plex Docker template and transcoding settings. +- **Tdarr Not Restarting?** Make sure the script has the right container name, Tautulli API key, and is set to run in the background. +- **High CPU Usage?** Some features, like HDR tone mapping, can be CPU-intensive. Ensure your GPU and drivers support it. Update drivers if needed. ---