Somebody save my CPU. made with Krita™

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (5 children)
  • [–] 2 points 1 year ago (3 children)

    I think FileFlows is better. I used tdarr for a few years, but I couldn't get back into it after I had an m.2 burn itself out and I didn't have good backups. I tired to set it back up and didn't have enough patience to get it working again, and FileFlows was a drop in replacement that required minimal setup to get everything running again.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (2 children)

    I haven't seen that one. Tdarr used to be more work to get going with classic plugins, but with Flows its really intuitive and I've codified my flows into the helm chart I deploy it with so I don't need to think about it. Its all in git and commented well.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago* (last edited 1 year ago) (1 child)

    Huh.. FileFlows does a lot more than video and music though... interesting.

    Eh there are a couple of things I dislike, though the UI is very nice looking and there are lots of features. Closed source, no lifetime option and tiered subs... that all puts me off a tool pretty quickly these days. I've lost the ability to trust anything that does not have open code due to the never ending and constant corporate enshittification and underhanded tracking.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    That's legit. I haven't needed more than just a single processing node and it does the job rather well, so I've been fine with it (if rather annoyed by the business model they went with). I may give tdarr another go and see if it's still pulling teeth to get my conversion pipeline reconfigured.

  • source
  • parent