Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54698 readers

371 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

[Request] Any Guides to FFMPEG, Transcoding, Codecs, and Metadata? (leminal.space)

submitted 6 months ago by [email protected] to c/[email protected]

29 comments fedilink hide all child comments

I have a collection of about ~110 4K Blu-Ray movies that I've ripped and I want to take the time to compress and store them for use on a future Jellyfin server.

I know some very basics about ffmpeg and general codec information, but I have a very specific set of goals in mind I'm hoping someone could point me in the right direction with:

Smaller file size (obviously)
Image quality good enough that I cannot spot the difference, even on a high-end TV or projector
Preserved audio
Preserved HDR metadata

In a perfect world, I would love to be able to convert the proprietary HDR into an open standard, and the Dolby Atmos audio into an open standard, but a good compromise is this.

Assuming that I have the hardware necessary to do the initial encoding, and my server will be powerful enough for transcoding in that format, any tips or pointers?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 6 months ago (1 children)

If you want to do an open codec, use AV1 codec and Opus for audio.

https://github.com/master-of-zen/Av1an and use aomenc for the av1 codec.

Ffmpeg doesn't have good av1 support.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago) (2 children)

With current hardware support I would advise against using AV1 or even H.265.

I'd recommend to experiment with H.264 and low CRF values to see what quality loss and file size OP is comfortable with: https://trac.ffmpeg.org/wiki/Encode/H.264

[–] [email protected] 12 points 6 months ago (2 children)

God no. X264 is way worse than x265 is way worse than av1 for quality by size.

Yes, everything made in the past 15 years can do x264, but that does not mean it is a good idea. Only do x264 if you have a specific device that needs it. Otherwise, x265 is a better choice for long term storage.

[–] [email protected] 5 points 6 months ago (1 children)

AV1 is definitely what I'd like to do. I'm not aiming for maximum compatibility; small file size and high quality encodes are my goal. I can transcode if needed.

[–] [email protected] 3 points 6 months ago

Keep in mind at least your server should be able to decode whatever you choose in hardware, so AV1 might still not be a good idea depending on your current hardware and upgrade plans.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

You're right, I forgot about the on-the-fly transcoding abilities of Jellyfin for a moment. But still, the server should be able to handle whatever codec they choose in hardware.

[–] [email protected] 3 points 6 months ago (1 children)

What hardware doesn't support H.265?

[–] [email protected] -1 points 6 months ago (1 children)

Old smartphones, old CPUs/GPUs, some SBCs.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

How many of those are you streaming video to, though?

Intel iGPUs have supported H265 since 7th gen, which is 8 years old now (released in 2016). Nvidia added support the same year, starting with the GTX1050. Even the Raspberry Pi 4 supports hardware-accelerated H265.