datahoarder
Who are we?
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
We are one. We are legion. And we're trying really hard not to forget.
-- 5-4-3-2-1-bang from this thread
view the rest of the comments
I'm sure plenty will disagree with me, but unless you have specific needs, I'd suggest spending more time sourcing your media rather than rely on transcoding. Most formats of popular stuff are available and Jellyfin will happily play it natively.
Also be aware that transcoding is VERY cpu intensive, unless you have a compatible gpu/transcoder. I run a ML110 with a 6-core Xeon (12 threads) and if Jellyfin needs to transcode something, it uses all of that and still stutters badly when seeking.
If you do need to transcode because you can't source the media in a compatible way - you may want to use something like Tdarr to transcode it before you try to play it, so it's ready when you are.
I'm running a Ryzen 7 2700X without any GPU acceleration and I can transcode any media just fine with Jellyfin.
An i7 gen 10 with QS can handle transcoding way better than a Xeon...