this post was submitted on 24 Feb 2024
0 points (NaN% liked)

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

53843 readers
572 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


💰 Please help cover server costs.

Ko-FiLiberapay


founded 1 year ago
MODERATORS
 

Nearing the filling of my 14.5TB hard drive and wanting to wait a bit longer before shelling out for a 60TB raid array, I've been trying to replace as many x264 releases in my collection with x265 releases of equivalent quality. While popular movies are usually available in x265, less popular ones and TV shows usually have fewer x265 options available, with low quality MeGusta encodes often being the only x265 option.

While x265 playback is more demanding than x264 playback, its compatibility is much closer to x264 than the new x266 codec. Is there a reason many release groups still opt for x264 over x265?

top 6 comments
sorted by: hot top controversial new old
[–] Shimitar@feddit.it 0 points 6 months ago (1 children)

Some notes: Don't use GPU to reencode you will lose quality.

Don't worry for long encoding times, specially if the objective is long term storage.

Power consumption might be significant. I run mine what the sun shine and my photovoltaic picks up the tab.

And go AV1, open source and seems pretty committed to by the big players. Much more than h265.

[–] pastermil@sh.itjust.works 0 points 6 months ago (2 children)

Why is the GPU reencoding bad for the quality? Any source for this?

[–] Kissaki@feddit.de 0 points 6 months ago

GPU encoding means it's using the encoder the GPU and driver provides. Which can be worse than software encoders. For software encoders they exist for encoding. On a GPU it's one feature of many, and doesn't necessarily seek out the same high bar.

[–] cuppaconcrete@aussie.zone 0 points 6 months ago (1 children)

Yeah that caught my eye too, seems odd. Most compression/encoding schemes benefit from a large dictionary but I don't think it would be constrained by the sometimes lesser total RAM on a GPU than the main system - in most cases that would make the dictionary larger than the video file. I'm curious.

[–] db2@lemmy.world 1 points 6 months ago

The way it was explained to me once is that the asic in the gpu makes assumptions that are baked in to the chip. It made sense because they can't reasonably "hardcode" for every possible variation of input the chip will get.

The great thing though is if you're transcoding you can use the gpu to do the decoding part which will work fine and free up more cpu for the encoding half.

[–] ChaoticNeutralCzech@feddit.de 0 points 6 months ago

x265 playback is more demanding than x264 playback

By a factor of 2 with the same bitrate. But you only need half the bitrate for the same quality (SNR) so it really isn't.

However, encoding is about 10x more demanding in terms of bitrate, or 5x for the same quality. This may be worth it for long-term storage or wide distribution over limited bandwidth (torrenting), but not for one-time personal use.