this post was submitted on 01 Apr 2025
37 points (97.4% liked)

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

59718 readers
264 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):

🏴‍☠️ Other communities

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

For those of you that torrent video files this question is geared toward you. I'm looking for a sweet spot between quality, size & speed for HEVC encoding. I'm using FastFlix and seem to be getting really wide and varying speeds.

I'm not really literate on all this video lingo but I can, at least, get it going. Most files take anywhere from 5-17 mins for a 30-40 mins clip. I have a AMD Radeon RX 470 graphics card but when I try and use the VCEEnc it won't let me use CRF which I've heard it the best way.

Anyway, if you're willing to share knowledge or what settings you use when you convert video to HEVC that might help me speed up my processing, I would be eternally grateful.

you are viewing a single comment's thread
view the rest of the comments
[–] fakeplastic@lemmy.dbzer0.com 11 points 2 days ago (12 children)

you'll do nothing but bloat the file size

That's very wrong. Going from h.264 to h.265 cuts file size down to 25-50% of the original. That's what the HE is for in HEVC.

[–] ragebutt@lemmy.dbzer0.com 0 points 1 day ago (5 children)

You’re correct that it will reduce file size but encoding lossy to lossy is foolish. You will introduce compression artifacts and have an objectively worse quality image, the encode will take much longer than if you used a proper lossless source, and if you don’t set your configs right you’ll strip out subtitles, tags, chapters, etc

Additionally if the h264 was already compressed by a lot h265 won’t save all that much space, giving you all the downsides with basically no upside

Only dummies encode lossy>lossy. The debate about lossy>h265 is one thing (h265 is not for archival) but h264>h265 will result in visible distortion

[–] fakeplastic@lemmy.dbzer0.com 6 points 1 day ago (3 children)

I also went through the phase where I thought I was an audiophile/videophile and everything I collected needed to be in ultra high quality. Eventually I realized it was stupid and now I spend a third as much money on storage and still have perfectly fine media that I have no issues with in practice despite the flaws I'm supposed to see in theory.

[–] ragebutt@lemmy.dbzer0.com 2 points 1 day ago (1 children)

I don’t understand what you are arguing?

If you’re arguing that downloading remuxes and only flac is foolish then yeah, 99.8% of the time h264 and 320 mp3 are going to be indistinguishable on most setups with most content. H265 will be the same on like 99.5% of setups with slightly less content and will save tons of space. Sure. But this assumes the lossy encodes were done properly from a lossless master

if you encode lossy to lossy it will result in visible and audible distortion of the image and audio. Sometimes it’s minimal, sometimes it’s quite bad, sometimes it’s masked by your equipment, but it’s always there. Further, you’d spend more money on electricity running your cpu on full blast encoding terabytes of video files when you could simply just redownload your library in whatever format by someone who knows what they’re doing (if you’re so concerned about space and don’t care about quality go av1)

But you do you

[–] rice@lemmy.org 3 points 1 day ago (1 children)

it will result in visible and audible distortion

This is completely wrong, it "might" be visible is accurate. The actual answer is "that depends"

[–] ragebutt@lemmy.dbzer0.com 2 points 1 day ago

That’s correct, I misspoke, I clarified that with the rest of my post though

load more comments (1 replies)
load more comments (2 replies)
load more comments (8 replies)