this post was submitted on 28 Jun 2023
269 points (95.6% liked)

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

54424 readers
363 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
 

Hello just making a poll, which one do you prefer? personally I prefer x265 but since the rarbg falldown i've seen that almost all 1080p rips are in x264, what do you think about that, and do you recommend any place to find more x265 content beside those in the megathread?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 year ago (1 children)

I'm using a pi4 as a media center so 265 as it can cope with 2160p

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

Wait, does the pi4 support 265 now? I meddled around with it a few years ago, and it always had to transcode 265 to 264.

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

yeah, it plays 2160p x265 media nicely. Doesn't do Dolby Vision tho, play smooth but colour is off.

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

Not sure of your use case but shouldn't it only matter what your client (Roku, Fire stick, etc) is capable of playing or are you using the Pi as a client? If the former, the Pi should just act as a file server regardless of the format (provided it's all compatible with the client) while the latter will cause the media to be converted if it can't be played directly.

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

~~It might have been an issue with my set-up. I was trying to use the Jellyfin web version from my computer, which probably was not serving the files correctly. I'll have to test again soon to see whether fixes were made in the last 2 years for it :)~~

Never mind. It's because I was using Firefox, which doesn't support x265 due to licensing issues.