this post was submitted on 05 Jan 2026
146 points (99.3% liked)

Hardware

7453 readers
111 users here now

All things related to technology hardware, with a focus on computing hardware.


Some other hardware communities across Lemmy:


Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. If posting an archived version of the article, please include a URL link to the original article in the body of the post.


Icon by "icon lauk" under CC BY 3.0

founded 3 years ago
MODERATORS
 

Major releases still coming out, and enthusiasts collecting discs.

you are viewing a single comment's thread
view the rest of the comments
[–] Eheran@lemmy.world 1 points 4 months ago (1 children)

The jump was/is the same: Same quality with halve the bitrate.

[–] Rekall_Incorporated@piefed.social 3 points 4 months ago* (last edited 4 months ago) (1 children)

Got to disagree with you on that one. It was universally true for the move from ASP/H263 to AVC/H264. It's not the case with H264 to H265 on a universal basis.

You can forget about such results if you're dealing with grain (and preserving it). Things are a bit better with "complex" content (oceans, snow storms etc), but you'll be struggling to get 50% space savings (more so with pre 2005 content).

The general bitrate level is also a massive factor.

Low bitrates, sure, even more than 50%. But you'll still be dealing with artifacts.

Medium to high bitrates (i.e. targeting a "near transparent" encode), you often won't be able to replicate a H264 encode at 12 Mbps (1080p 24 FPS) with a 6 Mbps H265 encode. Sometimes it works, but often it doesn't; I find you often need to go with 9-10 Mbps.

Haven't tried H266/VVC. For AV1 the x4 increase in encode times didn't seem to be worth it at high bitrates. Although for low bitrates AV1 seems to be modestly better than H265 (for far worse encore times).

This is all for CPU encodes at the "VerySlow" preset (1/2 for AV1 if I remember correctly).