It’s AV1. poggers

This is similar to your illya encode. Both are top quality! This is definitely a must-download ? The playback is perfect on my andriod phone too. Very smooth.

While I appreciate people like you being early adopters of AV1, if you're going to spend the time encoding in AV1, why not apply some filters to fix basic issues with the sources? Some Anti-Aliasing would have fixed this movies BDs biggest issue that is persistent across most scenes and easy to fix. Some comparisons to SAD and Asenshi-MTBB who both cleaned the aliasing https://slow.pics/c/fOKkiGzD Seriously though, AV1 is great(when you're not targeting transparent quality) it does a great job a reducing visible compression artifacts with its smoothing, making it great for "mini" sized encodes at a good enough quality level.

@nosebleeds Yeah I totally agree. I think about that a lot but the problem I have is I'd have to get real invested in rescaling for this which I didn't see toooo much an issue of and I haven't the time for that. Would be nice if someone just gave me the scripts lol.

For the third movie, I don't think you can rescale it, while I'm not 100% sure it's native 1080p, I wasn't able to get a decent guess at anything else. Here's my extremely basic Vapoursynth script for my v1. clip = core.lsmas.LWLibavSource(r"F:\enc\[BDMV] Made In Abyss - Fukaki Tamashii No Reimei (2020)\BDMV\STREAM\00004.m2ts") clip = taa.TAAmbk(clip, showmask=0, preaa=0, aatype='Eedi3', cycle=0, opencl=True, mtype=3, mthr=72, txtmask=224, dark=0, sharp=0, aarepair=0, postaa=False, stabilize=1) clip = core.fmtc.bitdepth (clip, bits=16) clip = havsfunc.SMDegrain(clip, tr=2, thSAD=88, contrasharp=True, RefineMotion=True, chroma=False, pel=1, plane=0) clip = core.knlm.KNLMeansCL(clip, d = 2, a = 1, h = 0.38, channels = 'UV', device_type="gpu") clip = core.f3kdb.Deband(clip, 12, grainc=0, grainy=22, y=32, cb=24, cr=24, output_depth=16) clip = core.fmtc.bitdepth (clip, bits=10) clip.set_output() TAAmbk is really good at cleaning aliasing, Eedi3 is really good for almost anything, but it's REALLY slow. In my v0 I used Nnedi3 with cycle=2 which cleaned the aliasing alright but was overly blurry in some frames and didn't handle small aliasing as well as Eedi3, but it was much faster. My scripts for v0 and v1 didn't change much other than that, but using Eedi3 instead of Nnedi3 with cycle 2 caused my encode time to change from about 6 hours to 17 hours on my 8700k / 1080ti. screens from my v0 here, nosebleeds used the same frames as what I used. https://slow.pics/c/0t4vViRL When encoding with AV1, I'm not sure degrain/denoising, debanding, and dithering are needed at all, pretty sure AV1 will just wipe that stuff in its denoising and smooth it itself.

@sorrow Thanks for the info. Also while it is true that AV1 does smooth noise (but it does keep static grain), it's mainly the quantizer and it does try to encode it (given enough bits/time), so degraining would actually reduce the file size even more. So it may actually be a good idea to.degrain/denoise it, and maybe do film grain synthesis, but it's hard for me to decide if re-adding the grain is worth it.

The problem is that this appears to be a 10bit encode. With AV1, we need 8bit because 10bit decodes too slowly, except possibly on ARM CPUs. This is not usable for playback.

@sorrow it is, in fact, native FHD. iirc the Marulk specials were not, but I'm unsure of what its native res is, since most tests I've seen are very inconsistent. Might be mixed or post-processed.

i played this by stream on my qled tv and its also perfect looking its always the case people who don't download this, or watch this have something critical to speak of if they prefer something else then get those instead of this. many people are happy with this lmao

A TV likely has an ARM CPU -- and so specially written accelerated code to play AV1 at 10 bit. Better to make a release which plays well on PCs also.

@Hifumi_I if you look at a lot of other AV1 releases, people say this kind of stuff all the time (assuming you're referring to the people criticizing/commenting on the encoding). AV1 is really new and people aren't as comfortable or as skilled with it as much as other codecs like HEVC or H.264. I personally like seeing the comments, as I'm a nerd and would also like to see the encodes improve as a whole. @Hoholedo the only TV's that can decode AV1 natively is LG's and Samsung's 2020 lineup. Most devices that can decode AV1 through hardware can do 10-bit fine (including the new NVIDIA and AMD GPU's, and Intel's Tiger-Lake CPU's). 10-bit also has the benefit of reducing banding and being able to hold more colors (which is important to HDR and since its a next gen codec most stuff in AV1 will be 4K with HDR). Content should remain in 10-bit imo as it just pushes 10-bit decoders to be made better, faster.

Thank you for your work and posting here.

I just looked at that slow.pics link and... wow, I am soooo glad I am not that autistic about extremely microscopic jaggies. Being neurotypical really is a blessing. Are there seriously people who sit so close to their monitors that they can see that shit? You'd basically have to be pixel-hunting frame by frame as well, not even watching the movie or paying attention to the subs/dialogue. Maybe switching to a recliner+TV combo really did me a favor to not get painfully obsessed with that kind of insipid crap. I know what VapourSynth is, I've even used it (once), and that experience half-convinced me that people only use it because they are expected to, as a streecred thing. Gatekeepey "scene" shit. The differences aren't worth it unless you are working with a heavily degraded/damaged source. This is a fine AV1 encoded indeed. You did nothing wrong, OP. There is absolutely nothing wrong with keeping your encodes transparent to the BDs. It's my personal philosophy that anti-aliasing and other things that destroy/munge the source image should be done by client-side shaders/filters like Anime4k.