Nyaa archive 1662684

[MiniMTBB] Oshi no Ko - 02 (1080p)

Saved on 2023-07-29 04:50:02. This copy includes the description and comments available at capture.

Submitter
motbob
Category
Anime - English-translated
Published
2023-04-20 04:45:34
Size
196.3 MiB
Info hash
8945f75c0a04728abedb8e92dec019602de6fe7d
Information
https://discord.gg/r9gyPwJeqW
Source flags
Trusted

Description

This is a smaller and lower quality version of [MTBB] Oshi no Ko - 02 (1080p).

Still looks better than HIDIVE despite being smaller... (This comp is from episode 1, but it's still true.)

Since these videos are 10-bit AV1, you should make sure you have a fully updated version of your video player to avoid playback issues, whether it's MPC-HC, mpv, or VLC.

To avoid image quality problems in dark scenes, you may want to watch this encode in mpv with profile=gpu-hq and deband=no added to the conf file, or in MPC-HC with madVR installed.

Comments 20

Thanks a lot. Saved 5 minutes grabbing the subs and attachments from AnimeTosho to mux with an existing AV1 encode.
Also, request to add the OP and ED too.

Tell me which existing AV1 encode you used so I can make a comp showing how badly I blew it out of the water.

@white_rabbbit your toaster PC struggle to read av1 codec, Soon MTBB gonna replace Judas & Anime Time the King Mini® av1

My encode is also AV1, and it does not have those "playback issues" causing magic banding in animetosho's screenshots. Would you stop being biased for a sec?

That is a bug in AnimeTosho's screenshot function. I've reported it to the admin of AnimeTosho before and they don't seem interested in fixing it. The scene is at 11:57 if you want to confirm. The banding is not present in MPC with madVR (but it is faintly present in VLC, presumably because VLC doesn't dither properly).

I still don't know which encode that guy used, so I can't make a comp. But since you're so feisty, I can comp against yours if you want.

As background, media players don't always handle low-bitrate 10-bit encodes that well. That's because the simplest way to get something from 10-bit YUV to 8-bit RGB is to simply round to the nearest value. But this causes banding (though not nearly as bad as the banding in that animetosho screenshot), so it's better for a media player to use some sort of dithering instead, where the media player won't always round to the nearest value but will rather choose one of several close values.

mpv with gpu-hq dithers properly, and so does MPC with madVR.

Of course, one way to deal with this quirk of media players is to add grain to your encodes.

I mean, I agree with this, but since I now know you didn't use grain synth, next time enable --photon-noise 1 or 2 in av1an. It won't add any visible grain but will dither the encode itself anyway.
Because in this state, the issue is present with stock MPV which most MPV users will unfortunately be using, meaning that only recommending people to use these media players might not be enough.

next time enable --photon-noise 1 or 2 in av1an. It won’t add any visible grain but will dither the encode itself anyway.

Thank you for the advice. --enable-dnl-denoising=0 --denoise-noise-level=2 took care of the banding in VLC, but it added a bit of filesize and increased the CPU usage by 40%-100% (per ffmpeg benchmarks). I have to decide whether that's worth it or not, but I'm leaning towards yes.

It's true that --enable-dnl-denoising=0 --denoise-noise-level=2 can help with banding but it's using aomenc noise generation which attempts to replicate existing grain in the source which can be slow and inaccurate. av1an -i input.mkv --photon-noise 2 --chroma-noise will add a photon noise layer that will help with banding and has a 0 hit to encoding speed.

Thank you for the advice. I did not understand that --photon-noise was a feature of av1an rather than an encoder. --photon-noise 1 --chroma-noise seems good. It's too bad it didn't improve the decode speed.

Yes, for some reason I will never understand, CR video streams all have BT709 metadata and NF ones don't. Since it's the only NF show I'm doing this season, I added BT709 metadata that shouldn't have been there by mistake. Since I noticed it while posting these screenshots, it will be fixed from next week onward and in the batch. Now about the goatraping part, you're just being ridiculous...