![](https://img.2222.moe/images/2020/05/14/euphonium_movie_finale_800v2.jpg)
Gekijouban Hibike! Euphonium Chikai no Finale BDRip
劇場版 響け! ユーフォニアム ~誓いのフィナーレ~ BDRip
10-bit 1080p HEVC + FLAC, MKV format. Movie ~ 5.5 GB.
Embedded official JPN PGS.
MKA contains FLAC 5.1 and DTS Headphone:X.
Thanks to **Airota** for elaborating Chinese subtitles.
The Blu-ray of Gekijouban Hibike! Chikai no Finale has outstanding image quality, upholding the same high standard as we have seen in Liz to Aoi Tori. There are hardly any noticeable artifacts. Many scenes are pleasantly overlaid with fine grains, complemented with clean, smooth lines and rich textures. Therefore, we applied only the most conservative de-banding and de-ringing to retain as many of those grains as possible. We then applied very mind texture enhancement in advance to offset the loss in perceived sharpness, as encoding would subsequently blur the lines. Given the stunning visuals of this anime, the encoding parameters were also chosen to be high-quality.
***
Thanks to our participating members:
Script: 静流的抱枕
Encode: 某位粳米组员
Collate: 百江なぎさ
QC: ANLOF
Upload: Tom
Seed: Seeding members of VCB-Studio CDN (refer to our website for full list)
Thanks to all resource providers:
CD: sagisawafumika@TSDM, MessIAН@TSDM, あおば@TSDM[https://www.tsdm.live/forum.php?mod=viewthread&tid=940012], TSDM合购区
BDBOX Scan: Mizore@Voice Memories
***
Please refer to https://vcb-s.com/archives/7949 if you have trouble viewing WebP images.
***
Comparison (right click on the image and open it in a new tab to see the full-size one)
Source________________________________________________Encode
[![](https://img.2222.moe/images/2020/05/13/14692s.png)](https://img.2222.moe/images/2020/05/13/14692.png) [![](https://img.2222.moe/images/2020/05/13/14692s.png)](https://img.2222.moe/images/2020/05/13/14692v.png)
[![](https://img.2222.moe/images/2020/05/13/21094s.png)](https://img.2222.moe/images/2020/05/13/21094.png) [![](https://img.2222.moe/images/2020/05/13/21094s.png)](https://img.2222.moe/images/2020/05/13/21094v.png)
[![](https://img.2222.moe/images/2020/05/13/28545s.png)](https://img.2222.moe/images/2020/05/13/28545.png) [![](https://img.2222.moe/images/2020/05/13/28545s.png)](https://img.2222.moe/images/2020/05/13/28545v.png)
[![](https://img.2222.moe/images/2020/05/13/50899s.png)](https://img.2222.moe/images/2020/05/13/50899.png) [![](https://img.2222.moe/images/2020/05/13/50899s.png)](https://img.2222.moe/images/2020/05/13/50899v.png)
[![](https://img.2222.moe/images/2020/05/13/62725s.png)](https://img.2222.moe/images/2020/05/13/62725.png) [![](https://img.2222.moe/images/2020/05/13/62725s.png)](https://img.2222.moe/images/2020/05/13/62725v.png)
[![](https://img.2222.moe/images/2020/05/13/66851s.png)](https://img.2222.moe/images/2020/05/13/66851.png) [![](https://img.2222.moe/images/2020/05/13/66851s.png)](https://img.2222.moe/images/2020/05/13/66851v.png)
[![](https://img.2222.moe/images/2020/05/13/73425s.png)](https://img.2222.moe/images/2020/05/13/73425.png) [![](https://img.2222.moe/images/2020/05/13/73425s.png)](https://img.2222.moe/images/2020/05/13/73425v.png)
[![](https://img.2222.moe/images/2020/05/13/83900s.png)](https://img.2222.moe/images/2020/05/13/83900.png) [![](https://img.2222.moe/images/2020/05/13/83900s.png)](https://img.2222.moe/images/2020/05/13/83900v.png)
[![](https://img.2222.moe/images/2020/05/13/120584s.png)](https://img.2222.moe/images/2020/05/13/120584.png) [![](https://img.2222.moe/images/2020/05/13/120584s.png)](https://img.2222.moe/images/2020/05/13/120584v.png)
[![](https://img.2222.moe/images/2020/05/13/122788s.png)](https://img.2222.moe/images/2020/05/13/122788.png) [![](https://img.2222.moe/images/2020/05/13/122788s.png)](https://img.2222.moe/images/2020/05/13/122788v.png)
@Trxsh
The answer is "slower" if you ask, but of course we tweak many other parameters individually based on our research (just like any experienced encoders would do), and right now it's actually somewhere between "slower" and "veryslow".
Just throw one of our encode into MediaInfo and you will see all the encoding parameters used.
Ok, also, thanks for the release! I was just asking because I think you guys are a good group for x265, and I am trying to encode stuff with this encoder, but I don't really know what preset with what CRF should I use to get a good quality (as yours). Thank you really much!
@Trxsh
No problem.
Official presets are good to try out first if you don't know much about all those little options, and they should give you decent results. However it's worth noting that "--tune animation" is NOT really suitable for most modern anime. It's actually designed for "cartoons" which have strong edges and smooth planar areas with little to no texture.
Also keep in mind the end result depends not only on the encoding parameters, but more importantly, also on the preprocessing script, where all of those anti-aliasing, debanding filters etc. take place. Also for example, we often intentionally enhance the grain in the source a little bit in our script to precompensate the smoothing effect of the encoder. So while of course you can copy the x265 parameters from us or other good encoders, be aware those are only part of the equation.
@vikrant9760
We've almost completed our transition from AVC to HEVC and about 95% of our new releases are now using 10-bit HEVC encoding. One of the few occasions we would use AVC is when making portable versions i.e. in MP4 format.
Comments - 13
Asakura
Trxsh
VCB-Studio (uploader)
Trxsh
VCB-Studio (uploader)
Trxsh
Tanteiouji
SomaHeir
kumikooooo
vikrant9760
VCB-Studio (uploader)
Campyfire
Anh9000