this post was submitted on 24 Aug 2023
4 points (100.0% liked)

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

54500 readers
695 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
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

Hi all!

I'm working on re-encoding a bunch of TV shows from H264 to H265 as well as making the metadata more uniform (especially between seasons).

As I've completed a couple of shows, I would like to possibly give back to the community by shareing it so that more people could benefit from it.

What would be the best way for this? Since I download most of it from torrent, I am thinking of having it on torrent as well. How to make sure it gets the exposure it needs (i.e. seeding)?

top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago (2 children)

You're going from a source of an encoded x264 and reencoding (the already encoded file) as x265?? What are the results like?

Most people encode from a high quality source like a remux, rather than an encode

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah, a lot of private travelers will not accept doubly-lossy encoded files as a rule. So you can't just go from 264 to 265. You need the original lossless file.

To OP, yeah, you want a seed box. Both to pin the file up and host it for a while, and to preserve your anonymity (the original seeder is under particular scrutiny.)

[–] [email protected] 0 points 1 year ago (2 children)

a lot of private travelers

What's a "private traveler" out of interest?

[–] [email protected] 1 points 1 year ago

It's a typo, supposed to say "private tracker"

[–] [email protected] 1 points 1 year ago (1 children)

Auto correct typo of private tracker. Sorry.

[–] [email protected] 1 points 1 year ago

Ah I see, thanks for clarifying.

[–] [email protected] 0 points 1 year ago (1 children)

Looks good to me... I'd be happy to take some feedback tho

[–] [email protected] 1 points 1 year ago (1 children)

It will depend a lot on hardware and/or software but I'd bet users would see some artefacting, ghosting, and general noise when they play your x265 file

As another comment pointed out, an encode of an encode is banned on a lot of trackers... Or at least an encode of an already pretty lossy encode (x264) won't be allowed

Does the filesize change much?

[–] [email protected] 1 points 1 year ago

I was able to shrink down the whole thing from about 120GB to 90GB