2024-08-11 10:29:10 -04:00
2024-08-11 09:13:26 -04:00
2024-08-11 10:29:10 -04:00
2024-08-11 09:46:24 -04:00

Tdarr Scripts

AV1 Flow and Tdarr Node Killer Script Guide

This guide provides an overview of the AV1 encoding flow and explains how the Tdarr Node Killer Script works to manage GPU resources between Plex and Tdarr.


AV1 Encoding Flow (Compatible with Intel ARC GPUs)

AV1 Flow

What is the AV1 Flow?

The AV1 encoding flow is a process that converts video data into the AV1 format, known for its high efficiency and excellent compression. The flow involves:

  1. Source: Your original video file.
  2. Input Processing: Preparing the video by adjusting resolution, color space, and more.
  3. Encoding: The AV1 encoder compresses the video data, making the file smaller without losing too much quality.
  4. Output: The final, compressed AV1 video file is ready for streaming or storage.

Note: This flow should work on any operating system that has an Intel ARC GPU card. You just need to ensure that the ARC GPU is exposed in your Tdarr Docker container.


Tdarr Node Killer Script Overview (Designed for Unraid, Works on Any OS)

This section explains how the Tdarr Node Killer Script works to manage your GPU resources, ensuring that Plex can have dedicated access when needed.

Note: While this script is designed to work seamlessly on Unraid, it can technically work on any operating system as long as you create a service. An experimental service script for Ubuntu is provided at the end of this guide.

Step 1: Tdarr Node Running, No Plex Transcoding

Tdarr Node Running, No Plex Transcoding

Explanation: The Tdarr node is running, and Plex is not currently transcoding any videos. This means Tdarr is using the GPU resources for video processing tasks.

Step 2: Script Monitoring for Plex Transcoding

Script Monitoring, No Transcoding Detected

Explanation: The script continuously checks if Plex is transcoding. At this point, no transcoding is detected, so Tdarr continues using the GPU.

Step 3: Plex User Starts Transcoding

Plex User Starts Transcoding

Explanation: A Plex user starts watching a video, causing Plex to begin transcoding. This might happen if the video is in a format like AV1, H.264, or H.265, which requires transcoding for older devices or specific user settings.

Step 4: Script Detects Plex Transcoding, Stops Tdarr Node

Script Detects Plex Transcoding, Stops Tdarr Node

Explanation: The script detects that Plex is transcoding and stops the Tdarr node. This action frees up the Intel ARC GPU so that Plex can use it exclusively for transcoding.

Step 5: Tdarr Node Is Stopped

Tdarr Node Stopped

Explanation: Inside Tdarr, you can see that the node has been stopped by the script. This ensures that Plex has full access to the GPU for efficient transcoding.

Step 6: Tdarr Node Dead

Tdarr Node Dead

Explanation: The Tdarr node is completely stopped, ensuring that Plex has exclusive access to the GPU.


Script Behavior After Plex Transcoding Stops

The script doesn't immediately restart the Tdarr node after Plex stops transcoding. Instead, it checks every 5 seconds for 5 minutes to ensure that Plex isn't going to start transcoding again. This prevents the Tdarr node from constantly stopping and starting, which could be inefficient.

Step 7: Countdown Before Restarting Tdarr Node

Countdown Before Restarting Tdarr Node

Explanation: The script is counting down, checking every 5 seconds to see if Plex starts transcoding again. If Plex does start, the timer resets, ensuring that the Tdarr node stays off as long as Plex needs the GPU.

Step 8: Tdarr Node Restarted After 5 Minutes

Tdarr Node Restarted

Explanation: After 5 minutes with no Plex transcoding detected, the script restarts the Tdarr node. The process then continues to check if Plex starts transcoding, so the node can be stopped again if needed.

Step 9: Tdarr Node Coming Back Online

Tdarr Node Coming Back Online

Explanation: Inside Tdarr, you can see that the node is coming back online after being restarted by the script.

Step 10: Tdarr Node Fully Online

Tdarr Node Fully Online

Explanation: The Tdarr node is now fully operational and visible on the dashboard. The script will continue to monitor Plex and manage the node as needed.


Experimental: Running the Script as a Service on Ubuntu

If you're using a different operating system like Ubuntu, you can run this script as a service. Below is an experimental service script to help you set it up.

Creating the Service

  1. Save the Script: Save your Tdarr Node Killer Script as tdarr_node_killer.sh in /usr/local/bin/.

    sudo nano /usr/local/bin/tdarr_node_killer.sh
    
  2. Create a Service File: Create a service file for the script:

    sudo nano /etc/systemd/system/tdarr_node_killer.service
    
  3. Add the Following Content:

    [Unit]
    Description=Tdarr Node Killer Script
    After=network.target
    
    [Service]
    Type=simple
    ExecStart=/bin/bash /usr/local/bin/tdarr_node_killer.sh
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target
    
  4. Reload Systemd:

    sudo systemctl daemon-reload
    
  5. Start and Enable the Service:

    sudo systemctl start tdarr_node_killer.service
    sudo systemctl enable tdarr_node_killer.service
    

This will allow the script to run automatically on startup and ensure that it stays active in the background, just like it would on Unraid.


Summary

The Tdarr Node Killer Script is designed to intelligently manage GPU resources between Plex and Tdarr. By monitoring Plex transcoding activity and controlling the Tdarr node, the script ensures that your Intel ARC GPU is used efficiently. This guide provides a visual walkthrough of the process, making it easy for beginners to understand how the script works and how to configure it for their own use.

Description
Unraid - Comprehensive Guide to Enabling AV1 Encoding, Plex Deployment & GPU Management with Tdarr on Unraid 7.0+
Readme GPL-3.0 356 KiB
Languages
Shell 100%