[M41K] Dragon Ball Super - Super Hero (2022) [Tint Fix - UHD 2160p BluRay DV+HDR10, Dolby TrueHD 7.1 Atmos] :: Nyaa ISS

[M41K] Dragon Ball Super - Super Hero (2022) [Tint Fix - UHD 2160p BluRay DV+HDR10, Dolby TrueHD 7.1 Atmos]

Category:
Date:
2022-12-19 02:35 UTC
Submitter:
Anonymous
Seeders:
4
Information:
No information.
Leechers:
1
File size:
19.3 GiB
Completed:
950
Info hash:
3f78ecd13219d82b9e1d86d5c653a4500b0a07b2
**[Notes]** - UHD BluRay losslessly encoded with the green tint issue fixed using a DCI-P3 to D65 white point adaptation and SMPT2084 gamma. Then re-encoded with a Constant Rate Factor of 4; - This release was aimed to be extremely close in quality to the BluRay without breaking hardware decoders compliance and also not making the final encode huge (You can check some comparisons here: https://slow.pics/c/6RbK07wy); - Audio and subtitles untouched; - Dolby Vision layer with a fallback to standard HDR. **[Mediainfo]** General Unique ID: 202269947775462485081543983381421876902 (0x982BC6619E57F9D5118AF79F3721E6A6) Complete name: Dragon.Ball.Super.Super.Hero.2022.JAPANESE.2160p.BDRip.x265.DV.HDR10.TrueHD.7.1.Atmos.Tint.Fix-M41K.mkv Format: Matroska Format version: Version 4 File size: 19.3 GiB Duration: 1 h 39 min Overall bit rate mode: Variable Overall bit rate: 27.7 Mb/s Movie name: Dragon.Ball.Super.Super.Hero.2022.JAPANESE.2160p.BDRip.x265.DV.HDR10.TrueHD.7.1.Atmos.Tint.Fix-M41K Attachments: PTSANSTIGHT-BOLD.TTF / PTSANSTIGHT-BOLDITALIC.TTF Video ID: 1 Format: HEVC Format/Info: High Efficiency Video Coding Format profile: Main [email protected]@Main HDR format: Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible Codec ID: V_MPEGH/ISO/HEVC Duration: 1 h 39 min Bit rate: 21.8 Mb/s Width: 3 840 pixels Height: 2 160 pixels Display aspect ratio: 16:9 Frame rate mode: Constant Frame rate: 23.976 (24000/1001) FPS Color space: YUV Chroma subsampling: 4:2:0 (Type 2) Bit depth: 10 bits Stream size: 15.2 GiB (79%) Color range: Limited Color primaries: BT.2020 Transfer characteristics: PQ Matrix coefficients: BT.2020 non-constant Mastering display color primaries: BT.2020 Mastering display luminance: min: 0.0001 cd/m2, max: 1000 cd/m2 Maximum Content Light Level: 996 cd/m2 Maximum Frame-Average Light Level: 996 cd/m2 Audio #1 ID: 2 Format: MLP FBA 16-ch Format/Info: Meridian Lossless Packing FBA with 16-channel presentation Commercial name: Dolby TrueHD with Dolby Atmos Codec ID: A_TRUEHD Duration: 1 h 39 min Bit rate mode: Variable Bit rate: 5 173 kb/s Maximum bit rate: 9 492 kb/s Channel(s): 8 channels Channel layout: L R C LFE Ls Rs Lb Rb Sampling rate: 48.0 kHz Compression mode: Lossless Stream size: 3.61 GiB (19%) Title: Japanese - Dolby TrueHD Atmos 7.1 (+15 objects) Language: Japanese Default: Yes Forced: No Number of dynamic objects: 15 Bed channel count: 1 channel Bed channel configuration: LFE Audio #2 ID: 3 Format: AC-3 Format/Info: Audio Coding 3 Commercial name: Dolby Digital Codec ID: A_AC3 Duration: 1 h 39 min Bit rate mode: Constant Bit rate: 640 kb/s Channel(s): 6 channels Channel layout: L R C LFE Ls Rs Sampling rate: 48.0 kHz Frame rate: 31.250 FPS (1536 SPF) Compression mode: Lossy Stream size: 457 MiB (2%) Title: Japanese - Dolby Digital 5.1 (Compatibility Track) Language: Japanese Service kind: Complete Main Default: No Forced: No Text #1 ID: 4 Format: UTF-8 Codec ID: S_TEXT/UTF8 Codec ID/Info: UTF-8 Plain Text Duration: 1 h 39 min Bit rate: 56 b/s Count of elements: 1150 Stream size: 40.9 KiB (0%) Title: English (SRT) Language: English Default: Yes Forced: No Text #2 ID: 5 Format: PGS Muxing mode: zlib Codec ID: S_HDMV/PGS Codec ID/Info: Picture based subtitle format used on BDs/HD-DVDs Duration: 1 h 39 min Bit rate: 106 kb/s Count of elements: 5534 Stream size: 75.6 MiB (0%) Title: Japanese (PGS) Language: Japanese Default: No Forced: No Menu 00:00:00.000: en:Chapter 01 00:05:04.763: en:Chapter 02 00:13:12.208: en:Chapter 03 00:18:26.605: en:Chapter 04 00:21:45.804: en:Chapter 05 00:28:48.894: en:Chapter 06 00:34:41.705: en:Chapter 07 00:38:37.482: en:Chapter 08 00:43:00.828: en:Chapter 09 00:48:36.247: en:Chapter 10 00:53:31.750: en:Chapter 11 00:58:08.777: en:Chapter 12 01:02:04.888: en:Chapter 13 01:07:59.200: en:Chapter 14 01:15:56.427: en:Chapter 15 01:20:40.044: en:Chapter 16 01:25:02.889: en:Chapter 17 01:28:27.052: en:Chapter 18 01:34:05.723: en:Chapter 19 01:38:05.963: en:Chapter 20

File list

  • Dragon.Ball.Super.Super.Hero.2022.JAPANESE.2160p.BDRip.x265.DV.HDR10.TrueHD.7.1.Atmos.Tint.Fix-M41K.mkv (19.3 GiB)
Is the Dolby Vision also fixed?

NFP

Trusted
Encoder's note: I don't have a Dolby Vision compatible device myself, but using the XML metadata Resolve tonemapped it properly, so I assume it's working as intended.
:-( Nope. The DV is god awfull on this disc and needs to be edited.
Can you shsre the Japanese subtitle, please? Thanks

NFP

Trusted
@Diogo_23 https://files.catbox.moe/ag324v.mks
@NFP: shouldn't it be a PGS file?

NFP

Trusted
@Diogo_23 .mks is just Matroska containing subtitles only, the PGS is stored there and will work the same. Also, I don't think ".pgs" is a thing, the raw format would be ".sup" (https://files.catbox.moe/bpkzyo.sup).
Thanks! Afterwards i just realized i just need to extract the sup file from the mks
Where is the sub from? Is it PotatoHeads or ripped from CAMrip or some other source?

NFP

Trusted
@SamirParvez According to the encoder: From WaLKAFaLKA's REMUX.
this movie is MEL DV (EL Layer is only 35.7MB), it's purely RPU. Checked the DV presentation of this already after the HDR layer has been adjusted for the green tint. DV presentation for this is fine. Colors remain clean. Checked it on a Calibrated G2 played via Zidoo and Oppo after converting this to m2ts. Thanks for the fix.
Lol, what do you mean, presentation is fine? Colors are overly aggressive. Also, full disc was FEL. ;-)
this encode is only MEL. color on the HDR10 layer vs HDR10 + RPU (MEL DV) no color change from HDR10 layer. Only certain scenes are brighter.
True, but by an insaaaaane amount. ;-)
hmmm could be your tv onboard dynamic tone mapping curve for just HDR cut off point being early? because at 0:36 mark on video measured the bright highlight on same panel same location was only 21nit difference between DV presentation of it vs HDR10
I had a friend check it out with a totally different TV, and he noticed the same thing. So it looks watchable to you, then? For instance, in this shot: https://images2.imgbox.com/15/f4/HZvQsN33_o.png The red isn't overly bright? And in this shot: https://images2.imgbox.com/17/ac/IOw45jpm_o.png The brightness of the yellow is totally over the top for us. Eye-rape. And in this one: https://images2.imgbox.com/de/42/Wg609XkR_o.png The sky appears almost white to us. It isn't like that for you? Unfortunately, said friend is the only person I know who has DV, so you're actually only the 3rd person I'm able to discuss this with. I think the one thing my friend and I have in common is that we both watched it on a Nvidia Shield TV, although he watches through Plex, and I watch through Kodinerds. So if it looks OK to you, it might be that. But every other DV movie I have plays just fine... Would love to get in contact with as much people that have DV as possible to see how it looks to them, so anyone who has DV, please leave your thoughts on how the DV looks to you.
Nvidia Shield doesn't play FEL. And from my knowledge there is no device on market new or old that plays FEL as an mkv with dolby vision and trueHD. And there are some FEL when played with the EL layer ignored (like what the Nvidia Shield does and also my Zidoo does this), causes weird stuff to happen. Example of this is Saving Private Ryan, Dune and Total Recall from top of my head. Saving Private Ryan and Dune you will see the sky flicker. Total Recall you will see the sky artifact.That's why I had to break this BL+EL+RPU back into dual layer and TSmuxer it back into BDMV or m2ts for the Oppo to do FEL and noticed that the EL layer is only 35.7MB which is means it's a MEL encode with only RPU metadata. And from MEL there should be no color data at all. So the color from base HDR10 layer to DV hasn't changed. And also there has always been an issue with Nvidia Shield and Red balance on DV output. Does it fine in SDR and HDR but DV Red on Nvidia Shield is wrong.
So, do those scenes look good to you? You didn't really answer my question lol.
https://images2.imgbox.com/de/42/Wg609XkR_o.png This is mine from that scene. More distinct color separation and shadow details. https://imgbox.com/eOa0NSu4 Think I'll download your ISO and rip the FEL layer from that.
https://imgbox.com/SxModlEv Bottom Image is this encode, BL + RPU ( MEL). Or how most devices will play FEL releases and ignores the EL layer. Top Image is BL layer from this encode + FEL from your ISO. Playing as Full BL+EL+RPU. Color slightly lifted compared to BL+RPU. Most noteable is the shadows in the cliffs.
I get this. The yellow on the third screen is really offensive, this picture doesn't really capture how bad it is. It's even worse in real life. The grass on the last screen is also more aggressive than it appears on this picture. https://images2.imgbox.com/65/b9/xiCHBoVo_o.jpg https://images2.imgbox.com/6b/e0/dEtwakoA_o.jpg https://images2.imgbox.com/05/66/sQVKGZYT_o.jpg https://images2.imgbox.com/8f/72/U5Yy4RbT_o.jpg https://images2.imgbox.com/6b/45/oic2G00t_o.jpg https://images2.imgbox.com/80/5a/2WGKxNui_o.jpg I think the BL and FEL need to be encoded with the exact same frame types in the same order. So your Encoded BL+FEL+RPU might not work properly. I checked the color of the FEL on a black frame and the RGB was 165 165 165, so at least we know the FEL doesn't need color fixing, which is good, as encoding FEL removes details, so if we can manage to encode the BL with predefined frame types/order, we can make a perfect, BD compliant fix. But if you watch the movie in DV, it's mostly fine? That is somewhat good news, I guess, aside from the fact I now might have to upgrade my DV setup lol.
also another thing i noticed the MCLL of this encode BL compared to original BDMW/ISO is lower.
Yeah, the HDR metadata doesn't take the increased brightness into account. I think the metadata of the SiMPLE encode is more accurate.