This has the same energy as my spouse yelling at me because jellyfin went down
This has the same energy as my spouse yelling at me because jellyfin went down
For $10M, I might just retire, buy a house and raise my kid.
Sure beats having to struggle at work.
This. They just need you for a follow-up visits, since they get graded on how mow complete the procedure was done.
Unfortunately, dental works are of those kinds where everything takes multiple sittings.
While I really get what you’re saying, the unfortunate situation is that they are always a secondary fiddle to money
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.
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
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