Tdarr

Tdarr copied to clipboard

**Describe the bug** I'm using latest docker image on Debian 11. Tdarr server and Tdarr_node. Created with docker-compose file. Device /dev/dri is not enabled on server container, but enabled on...

rchovan

**Is your feature request related to a problem? Please describe.** I would like to be able to cancel/ignore and move to next plugin if estimated target size produced by current...

ejalal

**Describe the bug** My setup looks like this: Server (Docker on Linux) Node-1 (Windows) - AMD GPU - AMD CPU Node-2 (Windows) - Nvidia GPU - Intel CPU For Node-1...

Seriox

Tdarr node process doesn't stop when closing terminal on Windows

2

**Describe the bug** When starting the node on a windows machine using the executable, a terminal is started. Closing the terminal doesn't kill the node process, meaning that the server...

savvasdalkitsis

Enhancement request: The only options for hardware encoding type in the Node config options are nvenc, qsv, vaapi and all. Please add an option for Apple's videotoolbox hardware encoding as...

MaSt3rGrIfF

Enhancement Request: Would like the ability to add in-line GPU up-scaling. https://github.com/k4yt3x/video2x provides many different solutions.

dsrtusr88

My Tdarr is not detecting Closed Captions anymore. I believe it may have something to do with this error message that I get on the media details: "closedCaptionRead":""Unable to run...

wsegatto

**Describe the bug** Under certain circumstances TDAR processing can 'skip' or 'bypass' a plugin if both CPU and GPU workers are enabled for the node. **To Reproduce** I have two...

Span24

The issue occurs when we are using long plugin lists and want one specific worker CPU or GPU to be the one getting started. (Meaning pulling the item from the...

tws101

**Describe the bug** I currently have all my libraries set to put the completed encodes to various output folders, so that none of my originals get deleted until after I...

FreelancerJay