(2024-11-11, 09:29 PM)TheDreadPirate Wrote: Tdarr can automate re-encoding your media.

(2024-11-25, 02:03 PM)TheDreadPirate Wrote: Running Jellyfin in docker makes managing its data easier.  Makes backups and migration easier as well.  Definitely recommend learning Docker (it's not that hard) and starting with Jellyfin in Docker.

I've never used Tdarr so I can't help with specifics.  I just use ffmpeg, directly, to re-encode.

As for compatibility and file size, that is personal preference and depends on what clients you have and how many clients you have.  My reason for re-encoding, to AV1 video + OPUS audio specifically, is to maximize quality per bit since I don't have a lot of upload bandwidth (40Mbps).  This also results in direct play on near all my clients, soon to be ALL my clients once I finish swapping one more.  My phones, Pixel 6a's and my wife and I's primary remote client, can direct play both codecs and is the primary beneficiary of using more efficient codecs.  The reduced cellular usage and storage efficiency are huge benefits as well.

What codecs YOU choose depends on your client capabilities, whether your clients are all local or some are remote, what your available upload bandwidth is.  If you and/or your users have old clients that don't support AV1, or even HEVC, and you don't want to be transcoding constantly then you should target H264 + AAC.  Especially if you have 5+ users.  If you only have a couple users with capable devices, HEVC (your iGPU can encode to that) and AAC or OPUS audio since HEVC is much more efficient.

(2024-11-25, 02:54 PM)TheDreadPirate Wrote: Which ASRock A380 did you get?  The Challenger?  And are you trying to find the OPROM code or data?

(2024-11-25, 04:28 PM)TheDreadPirate Wrote: I posted on the tech powerup forum post asking for clarification regarding the low profile variant and which OPROM data it uses.

(2024-11-25, 04:52 PM)Magg66 Wrote: Thank you 

(2024-11-25, 04:28 PM)TheDreadPirate Wrote: I posted on the tech powerup forum post asking for clarification regarding the low profile variant and which OPROM data it uses.

(2024-11-27, 02:12 PM)TheDreadPirate Wrote: The TechPowerUp forum OP indicated that the low profile cards simply have not received an OPROM data update since release.  And that is why it isn't on his matrix.

Run this command and compare the output with my Challenger card.

Code:

sudo ./igsc oprom-data version --device /dev/mei2

Replace the device path with yours, if it is different.  The output for mine is "14 00 2C 04 00 00 00 00".  If it matches, you can just go ahead and update the rest of your firmware and skip the oprom-data since it is already the latest.  The OPROM code and data don't get frequent updates anyway.

(2024-11-28, 06:24 PM)TheDreadPirate Wrote: Ok.  Based on what the TechPowerUp dude said, your card probably hasn't receive an update for OPROM data.  Since their source grabs all the available files.  Update whatever components have an available update for.  Skip OPROM data.