Tdarr

Tdarr copied to clipboard

Describe the bug

You cannot have two libraries pointing to the same folder and have them both process the folder as expected. Only a single library will process the folder and the other one will ignore it.

To Reproduce

1. Set up a working Tdarr instance with a working library that is being processed (no delete, copy to output folder).
2. Add a second library with different filters/transcode pipeline and point it to the same folder with a different output folder.

Expected behavior

Multiple libraries should be able to process the same folder. Example use case is that many people keep 4K content separate from HD content. So, one library filters on 4K content and transcodes then outputs to the 4K folder. The other library filters on HD content and transcodes then outputs to the HD folder.

Please provide the following information:

• OS: Linux
• Version: 2.00.18

This is intentional so that a file can only be in the Tdarr database once instead of in multiple different libraries which could cause issues between nodes, plugin stacks etc. The primary way for Tdarr to be used is for replacing the original file so it's designed around that if that makes sense.

Then how would one apply rules based on conditions like if/else? The plugin stack stops if a condition isn't met.

for example: different settings depending on cpu or gpu node, resolution, bit depth, source bitrate, etc. Currently I'm trying to downscale 4k to 1080p, but not change the resolution of 1080p or lower content. This isn't possible currently outside of making a custom plugin.

@Codel1417 in a custom plugin you can use process.env.nodeName (or process.env.nodedID if before 2.00.19) to add if/else conditions depending on node. Or can check the host os using const os = require('os'); and os.platform(). Obviously not ideal but working on some things to make it a bit easier.