fatboy93

Dang, you’re Moneyball’ing your kid?

Sounds awesome!

ThinkPad T450s (my old laptop)

OS: Arch Linux DE: Plasma

Services: Arr stack for gluetun, sonarr, radar and jackets Jellyfin for videos Gonic for audio

All 3 of them are run using docker compose

This has the same energy as my spouse yelling at me because jellyfin went down

Funny story, we are moving out of our apartment to another in the same city, because that is close to $300 cheaper.

We had an issue in the bathroom and the maintenence guy comes and we make small talk. I find that he lives in another apartment complex, the property managers live in another apartment complex, because the ones I live in is expensive and the housing in our city is expensive that none of us can afford to buy one.

I use gonic with sonixd on my laptops, but probably might move to supersonic from sonixd.

On my phone, Tempo is really awesome!

Not sure if this would be useful, but my university uses ThinLinc. We can use the desktop and other stuff in the browser.

Its really good in North America given that it is from Cornell. Gets probably a bird or two wrong out of hundreds

When I’m in India, its a kinda of a swing and a miss, but they’re constantly improving it.

Not necessarily, generally the defaults for most of the tools tend to be sane, but when you have a swiss army knife with dozens of attachments, you’d still need a manual to figure what is what.

Note that many tools use ffmpeg under the hood so users are generally never exposed to the various options. But sometime if they need to, cheatsheets like these are really useful.

It would be great if you can post the compose and comfigs!

Are there any minimum requirements?

Absolutely! Sometimes its just easier for me to keep jobs in a single list and run them on a big fat node rather than array submit and block half the queue!

Love posts like this, because I can plug a tool that I revently found!

Its called ParaFly and i use it a lot on HPCs. Doesn’t really have a multi-node support, but it also offers logging and resuming of jobs.

So your point 3 is essentially this: ParaFly -c commands.txt -CPU N where N is the number of jobs you want to run in parallel