48
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Feb 2024
48 points (88.7% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54390 readers
475 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
That is how I encode (mostly SVT but a bit with NVEenc too). There is an av1 community here on lemmy but it isn't super active. Otherwise, you're limited to the handbrake forum or reddit.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !av1@lemmy.world
Good bot
Are you able to get HDR and HDR10+ to encode over properly? I'm having hell of time with it.
The general consensus in the AV1 community is that the SVT encoder implementation isn't ready for HDR(10+) yet. There are some other encoders of AV1 (including Netflix's proprietary implementation) that can do it well but basic SVT offered through the public repo is not ready for HDR yet.
Edit: I should add that I compress most of my library in 1080p with av1-svt. I only leave a couple of titles in 4k format and those I'm waiting to rip until SVT becomes mature enough to handle 4K.
So I should probably stick to H.256 right now for my HDR needs is what you're saying?
yup, that's what I'm saying.
Thanks for the help. I appreciate it.