I was trying to catch up on my 1080P movie backlog on my laptop recently, only to discover that Jellyfin would transcode the movie since the 5.1 audio track apparently won't work on modern Firefox on my modern Macbook (grr, why? )
Rather than just watching on my nVidia Shield (which plays everything I throw at it), I instead spent about 6 hours (I never even got to watch the movie!) adding Tdarr to our platform, with a mind to having a 2-channel audio track added to my existing media.
So, we now have Tdarr available! It works as advertised, although it turns out to be quite tricky to configure, and even trickier to make work with the Quick Sync Video hardware transcoding support in our 9th-gen Intel nodes.
A few peculiarities to our implementation:
- While Tdarr can support multiple, distributed worker nodes, we just use one worker node, paired with the Tdarr server, for easy resource isolation, and because our transcoding "scratch" volume is actually a 200Gb ephemeral NVMe-backed disk, which only exists for as long as the pod does.
- We don't actually want to significantly increase our CPU usage across the platform - rather, we want to leverage Tdarr for spare capacity on hardware-based transcoding. Each Tdarr pod has minimal CPU, and enough RAM to run the server, plus one hardware transcode, but will crash and restart if trying to do more than one transcode in parallel (because mooar transcodes requires mooar RAM)
I've pre-configured a working Tdarr setup, so you won't be starting from scratch when configuring it, and I've added more specifics to the app page.
Get your 24h trial / subscription at the store!