Video | Audio #1 | Subtitles #1 | Scans |
---|---|---|---|
Codec: AV1 | Codec: WavPack | Codec: ASS | Codec: JXL |
Format: YUV420P10LE | Profile: Hybrid | Compression: zlib | Profile: Lossless JPG Transcode |
Frame Size: 1920x1080 | Channel Layout: Stereo | Source: DmonHiro | — |
Framerate: 23.976fps | Bitrate: 220kbps | Contents: Dialogue, Signs, Songs | — |
Aspect Ratio: 16:9 | Language: JPN | Language: ENG | — |
Encoder: aomenc 3.5.0-575-g32ed2d8ac | Encoder: WavPack 5.6.0 x64 | — | Encoder: JPEG XL encoder v0.8.0 6a891d6 |
First Season and Extras, Second Season and Extras, Subtitles
AniDB: Season 01, Season 02
MediaInfo: Episodes and Menus, Mitsudomofes
Finally, Mitsudomoe is done. The encoding process was quite alright, though I did had more problems than I would like to admit on the muxing step. Either way, it is done now, and I hope you like it.
This series did hit way harder on the encoder than the previous one, and even after reducing the quality a little bit, it still ended up with a larger file size for the video track than expected. I could had reduced the quality more, but it would be entering uncomfortable territory as this series have a lot of moments with grain and coarse imagery.
I’m testing quite a lot of things now, one of them being the change to using a table scheme for the quick info, and dropping some text because I do type a lot. How does it look, should I add something to, or remove something from it?
Another thing is the tags on the names of my releases, as I think things are too long. Considering I mark my releases as English translated and always include chapters and extras that are present in the sources, I think I can drop those. How do you prefer the title tags, more information like before, or less information like now?
I couldn’t find the other Audio CDs for this, so I was considering not including the ones present on the second season source, but I ended up including them anyway. They are inside the second season extras folder.
My releases are meant to be watched using mpv. It probably works with other players, but that is beyond me.
I’m always accepting suggestions, principally of loli and/or DVD material to encode.
I already have plans for the next encodes and am already working on one of them. The next one will be an experimental release, so wait for it!
Comments - 6
f00f
AV1 and JXL, nice
AndyAlex91
please tell me whats the point of your encodes? because I don’t understand, other groups re-encodes anime releases to make smaller sizes what about your releases are they make to be compatible with more devices or something if not for smaller sizes?
Stultus
Pointless as it’s not the smallest edition and without “(polished)” subs totally pointless.
ScarletNeko (uploader)
@AndyAlex91 biggest point is the audio, as I really hate how the 128kbps OPUS and AAC became the standard. I don’t like how they sound, and although I would still rather have higher bitrates for my own audio tracks, 2.0bps is already a world better. then there’s both the av1 and jpegxl codecs which I am a fan of, I think it’s already way past time we get more stuff encoded in it. another important thing to me is to encode DVDs and old media in general, or controversial things, though that is not a hard coded rule and I do encode as well things that I like (such as Monster Musume and Ishuzoku Reviewers for example).
device/hardware compatibility was never really a concern, I always made it clear that my stuff was meant to be watched using mpv, and hinting that I meant the PC version, though even my ancient android smartphone have no problems playing these videos.
indeed there is the intention is to reduce file sizes taking advantage of the av1 codec, but I never had the intention to make the smallest files available. I want to keep the quality high and the sizes low, but I am biased towards quality and there is a point I will not sacrifice any more quality just for the sake of “having the smallest files around”.
About the subs, unfortunately that is the hardest part for me as I can’t really figure out subtitles, so I will use subtitles from things I already have downloaded or from a known source to me. to whoever doesn’t like the subs included on my releases, by all means feel free to use a different one, it’s not like I demand you watch them with the subs I included.
chrnodroid
Ooooh! Finally Mitsudomoe! Thanks as always, perfect release also this time!
File size is fine, quality is totally good, and I’m starting to appreciate Wavpack more (still not for Anime though).
I started using Wavpack to heavily compress my Hi-Res FLAC huge collection, but I don’t know how to properly use that "WAVPACK Hybrid Lossless Audio Compressor Win64 Version 5.6.0"
so I’m using the built-in Foobar2000 wavpack encoder, 128 kbps, Extra High 6x.
And don’t worry for compatibility, the only issue is the JXL format for the masses, but mpv can read everything.
For the video should be ok also mpc-be and mpc-hc, and obiously also vlc. (I use always mpv because is the best, especially for its upscales, like FSR, NIS and FSRCNNX, so your DVD releases looks like BD remasters)
ScarletNeko (uploader)
For images, I use and recommend IrfanView on Windows, it does have a jpegxl plugin and it works like a charm. There is also a plugin, I don’t really remember for what/where, but it makes the explorer generate thumbnails for jpegxl images as well.
For the WavPack, I use the standalone command line encoder as usual. It is pretty easy. If you want lossless, -h -x4 is what I usually use (high, extra processing x4). If you want lossy, you can add -b(number), where you can use values between 2.0 and 23.9 and it will recognize as bits per sample, or 24 to 9600 and it will recognize as kbps.
So, for a lossless encode,
wavpack -h -x4 -m input.wav
. The -m is for it to calculate and store the audio md5 hash.For a lossy encode,
wavpack -h -x4 -b'2.0' input.wav
for a 2.0bps file, orwavpack -h -x4 -b'384' input.wav
for a 384kbps file, for example.If you want to create a correction file, so you can use the lossy file normally but be able to restore it to it’s original form at a later date, add -c and it will also create a wvc file.
For example,
wavpack -h -x4 -b'384' -c input.wav
will generate a lossy, playable .wv file at 384kbps and a separate .wvc file with the remaining information which you can use with wvunpack later to restore the full lossless input.Edit to break some lines and make it easier to read