I have an 8tb drive and barely have half of it full, so no. That said, if you want to do good encodes look at what settings others use. Many uploaders on nyaa specify theirs and you can use ffprobe to get a general picture of how something was encoded.
AV1 is god-tier, but hardly practical unless you have powerful enough hardware. HEVC is perfectly fine and miles better than H.264.
From what i understand, Mpeg4 is half the size of Mpeg 2. x265 (HEVC) is about 30% smaller than Mpeg4, and AV1 is 30% smaller than x265. So AV1 you should have close to half the bitrate to match it than mpeg4.
But seriously dropping keyframes to a longer period will save you a lot more than anything else. Some encodings i've done i got about the same size as the original video. Then just by extending key frames to 200-300 frames away and the video size dropped by like a third!
Yeah seeking is a little slower, and some players will just jump to the closest keyframe, but that is the price i pay for tiny files.
As for the amount of time it takes. That really depends on how much processing you want AV1 to do.
-preset 10 is a default i believe; while 12 is the fastest. But identifying duplicates and really getting better compression you need to go under 7.
I started doing 5 for everything, but i've changed that to 3. I don't care if it takes a day or three to encode in the background, i'm not watching it. Then again i have an OCD on efficiency where i try to use all my resources at full if i can.
Though, newer generation of video cards soon will support AV1 encoding. They probably won't be as space efficient as software, but would be decent for streaming or initial capturing.
As for CRF levels... I would treat 20 as basically lossless, 30-32 is great for general viewing, and i would even go up to 35 (
which i use for adult videos). Go above 35 and artifacts and errors start to become noticeable, while 30-32 they are unnoticeable unless you are looking really closely for them.
Your brain is really good at fixing errors and filling in gaps in videos. Paused screens, then all the errors in a single frame jumps out at you.
MKV is a container format, the codecs used for encoding the videos/audio streams could be anything <snip>
It sounded like the player on the TV didn't support subtitles at all. Or like on mine where i sideloaded VLC, some subtitles tend to come up so light it's impossible to read. The DVD-style hard coded subtitles (
images with transparency of the text) sounds like it may work but those aren't really supported unless you make it a VOB, and if you do that I'm not sure you can use Mpeg4. Quite confusing.
Then there's the case where some Mpeg4 refuses to play because it was DivX and they didn't want to pay a license, but a tiny tool to change the codec ID to FourCC and it was happy to do playback. (
with Project Mayo, 3vix, and DivX and the early Mpeg4, they took a few parts of Mpeg4 and used that primarily, much like how Jpeg files are JFIF which is a sub-format of Jpeg but was easy to implement and did almost everything halfway decently, then none of the other Jpeg formats caught on).
In my experience ASS and SRT subtitles work find in MP4 files, and most codecs and audio works too. If you merely want to change containers, you can attempt and experiment.
Code:
ffmpeg -i inputfile -map 0 -c copy outputfile
Though some subtitle formats and some audio formats aren't 'officially supported', if you get that error, add
-strict experimental which will allow it to do it anyways and then it may or may not work for you, though PC players are more lenient.
I found AV1 to be terribly slow for encoding it myself, I wanna save space, but I also want to save electricity lol. But whenever I see anime on Nyaa that is encoded with AV1 already, then i always download that one.
I notice a lot of the AV1s encoded on Nyaa amount to be effectively lossless. Good for long term storage, but not for general viewing, especially on smart TV's in the last 5 years unless you go the expensive top line Samsung or something. But yeah i do the same and go for AV1 when it's there.