Should I start converting my movies and porn to AV1 to save space on my 1tb external or should I just buy a new external
>>106448899why downgrade when you can upgrade
>>106448899Loser. kys
>>106448899Depends on the AV1 encoder. If you're talking about the NVENC AV1 GPU encoder then it's going to depend how bad the H264 encodes were. If you're using a CPU AV1 encoder then it's unlikely you'll want to retain the H264 rip after passing quality validation.
>>106448899I would convert all low bitrate stuff, you aren't losing much quality and depending on how many videos you convert the savings can be substantial.be careful of videos with variable bitrate, preserve the birate curve (crf option), if you see bitstarved scenes you'll have to edit it manually and/or do a two-pass encode, it's usually something to care about for 4K BDMV rip or high quality remuxes, all the shitty reencodes you'll find on the internet are already of low quality and usually with fixed bitrate.be careful of HDR10+ or dolby vision as your encoder needs to support them if you want to keep them, i've read that svt-av1-psy encoder can do it, forget about any hw-accelerated encoder though, none support dynamic HDR of any kind
>>106448899https://desuarchive.org/g/thread/106322158
>>106448899use AV2 instead, it has been worked on for like 4 years nowhttps://gitlab.com/AOMediaCodec/avm
>>106449032this isn't supposed to be a social media site, it's the technology board, fuck off
>>106448899yes
>>106448899>Should I start converting my movies and porn to AV1 to save space on my 1tb externalnot unless you're encoding from a remux and jack the quality settings all the way up, or don't mind everything looking terrible>>106448899>should I just buy a new externalyes
>>106448899
>>106448899no. the power in requires to re encode cost more money than extra storage. unless you're distributing that video to millions, it's not worth it.
>>106450149Maybe it is worth it. There are trade-offs with everything...
>>106449836How can there be meaningful improvements for an AV2 already??
>>106450341AV1 was released stillborn
>>106449836this, av2 will likely fix all the issues with av1, but as others have said, hw support for encoding is limited. doing sw encode for av1 is extremely long, i got 0.2fps encoding on a 16-core@3.5GHz. If you have 1TB of ~5Mb/s h264 (or around 4000 hrs of videos) if would take 5 times as long to encode it all, which would probably require in the ~200kW/h range (given a 100W TDP), that said it's probably cheaper to buy a new hard drive/ssd than do sw encoding
>>106450341av2 had improvements like months after av1 was standardized
>>106448899Don't do this faggot, only encode from highest source quality like original Blu-Ray to AV1, if you encode H.264 to AV1, you're just making things worse because lossy to lossy encode
>>106451008That's like $10 of electricity.
>>106451404>lossy to lossy encodeBesides this I fully support the OP.
>>106451008what? First off thanks to Vulkan Video hw support is a non-issue, just write new shaders for the new codec. In fact, from what I've read about AVM/AV2, they're actually designing it in such a way to make use of AV1 hw acceleration with or without GPU assistance.As for sw encode I recently passed some 5-10Mb/s h264 pr0n through SVT-AV1 to reduce space and with a 5950X the encoder processed it at x5-x10 speed. The encoding speeds you're describing are what you'd get from the reference encoder 5 years ago.
>>106451439I messed up calculations, I looked at svt-av1 benchmark and it can perform as good as ~25 fps on consumer cpu (e.g drawing between 80-150W). For 4,000 hours of media, that would take ~4,000 to encode (assuming 25 fps if it's low quality tv/web dl, 24fps for blu-ray/dvd etc..), which would consume 100 * 4,000 / 1,000 = 400kWh, which would cost you about $40 at 0.10 $/kWh. That said it doesn't take into account that your computer will be in an unusable state for 6 month during which it'll be using 100% of the cpu for encoding only.
>>106451788what was the original bitrate?from svt-av1's website, you can see that consumer-grade cpu aren't that fast at encoding av1:openbenchmarking.org/test/pts/svt-av1also, that's assuming you only need to perform a single pass encode and you don't want to preserve special features, like dynamic hdr or 10bit color depth. When you start adding up those, the encode takes way longer.
>>106451804>cpu video transcoding
>>106451829No ASIC or SIMD (GPU) for it?
>>106451909>>106451881hw encoding exists, but it only supports a limited set of presets and formats. Given that you do transcoding, you also need a hardware decoder for the source format that supports the features you want/have to deal with. even the latests nvidia cards don't support hw decoding (let alone encoding) for all formats, they usually only implement the most commonly used ones. for that reason, doing software encode is the most viable option
