shbr

Sounds really cool. Perhaps it would be better if we work on merging this feature into the main source? If you would be open to it sure. I’ll try to get started on a PR in the near future. Will reach out to you if I have any questions.

So this is super useful but my backlog is going to take far too long. I solved this by running unmanic docker containers for unmanic on multiple machines, and using the unRAID instance as the primary that tells other containers what to encode (I now have 6 computers to churn through my files). Just wanted to share in case others find this useful: Sorry this isn't setup as an unraid package and is going to require some technical skills, if anyone wants to help out with that I'd welcome it but that's not part of my normal workflow. To use: git clone https://github.com/shaenchen/unmanic-distributed to your /mnt/cache/appdata folder. install your unmanic containers on other machines and ensure that /library/tv and /library/movies are bound to the same paths (I use linux, windows, and Mac as sources so I know it can be done anywhere) IMPORTANT: all unmanic instances need to be using tag 0.0.5 version. This version exposed a route to get current status that no longer exists. All sub instances should have library scanning/watching turned off. edit ./src/config.js so that primary is your unraid unmanic instance, and there is an entry for each secondary you have run ./docker_up.sh script on unraid and this will start the container you can browse to http://unraidip:49163 to see the status of all containers What it does: it reads the queue from the main unraid instance, checks all your sub-instances and sends queue items to the others if they aren't busy. They can process it exactly as the main instance would (or differently if you want them to take advantage of hw encoding etc.) but only run files when told to by this application. I'll admit this code is a bit hacky, but I've been running it for a month without issue. @Josh.5 please let me know if you'd like me to take this discussion elsewhere. (and thank you for your work on providing this, it's super useful)