this post was submitted on 29 Aug 2023
47 points (96.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54424 readers
401 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I prefer x264 since all my devices can play it, though x265 is great for file sizes.
This. I actually went the opposite route to OP, replaced everything 265 to 264 to avoid playback issues. My content is played on many different devices so 265 simply won't cut it.
For me the math worked out that it was cheaper to get a nuc with quick sync than to pay for the extra storage h264 uses, it's less than half the bitrate (usually ~2Mbit for 1080 compared to 8+), I have 23TB of content and my Intel nuc power efficiently transcodes to h264 on demand if the device needs it.
What kind of devices won't play x265? I've got some rather old hardware and it seems to work just fine on everything.
I sometimes stream from my 2014 ultrabook to my TV... never had a problem with x264, but some x265 encodings cut out/freeze/lag during scenes where a lot is happening (motionwise)
Same, laptop from '15, TV from '09. If you're on linux what did you use to reencode, ffmpeg? Never even occurred to me I could do that lol.
I've been using Handbrake for a while now - albeit on Windows. It is available for Linux but I can't guarantee it's the exact same experience.