it will outsync when the audio have offset.
#SUBLER OFFSET TV#
So basically mp4muxer has more compatibility in my internal tv player, except that doesnt have delay audio offset. I definitely suggest subler muxer for any Apple devices, may including ATV perhaps, not tested on that.
#SUBLER OFFSET MP4#
My android hisense tv works with mp4muxer mp4 pc / m4v subler mac for p5 p7 p8.1, it support atmos too.Įxcept playing p7 fel single layer (somehow jitter.), and lazy cannot play subtitle inside mp4/m4vĪny p7 double layer fel that converted to p8.1 will downgraded to HDR10 with DVtool.Īny TSmuxer converted will have sync issue, may the subtitles hdv alone, or out of sync audio. If I can find time I'll try reencoding the pattern with my suggestions. So you can use latest version for the Shield, or tsmuxer. I think the latest version of mp4muxer doesn't work only on LG TV internal player? As for L9 i dont know.Ĭorrect me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and -dv-bl-compatible-id 1 doesnt work. I'll match the color primaries for the 2nd clip but i doubt it will make any difference. It defaults to chroma type 1 as well, i dont think we can change that. Resolve automatically calculated a new maxcll/fall at delivery, same for L6. The spears and munsill pattern is encoded with maxcll/fall 1000/400 but resolve and madvr measure it 10 000nits MakeMKV shouldn't be doing anything different, as the source isn't modified.Īlso, these MP4 files are missing the proper compatibility ID for 8.1. Those should obviously be matched first before jumping to conclusions. I doubt L11 makes a difference unless the display supports CM v4.x.įinally, Resolve doesn't support shot based metadata, so every frame carries "scene_refresh_flag": 1. Other: DCI-P3 mastering display, 1000/400 CLL, chroma location top-left.Īnd in the RPU, L6 and L9 are different (Resolve matches BT.2020 primaries, dovi_tool uses DCI-P3 by default). Resolve: BT.2020 mastering display, 10000/256 CLL, chroma location center. Strange though that only the Shield seem to be affected. So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!! We discovered something else, something quite big.
#SUBLER OFFSET MOVIE#
Now in this particular example, if the movie is only available in HDR10 (like Batman v Superman) MadVR DV would help alot as it will allow your TV work to its best potential and it will exclude that one 10000 nits frame from everything else in the content.
Thankfully most of those fucked up movies come with Dolby Vision. It also scales up MaxFALL value so it messess up all the tone mapping in the film. Warner brothers does the same stupid shit, when their logo is about 900 nits bright and the entire movie is 150-200 nits MaxFALL.įamously, new Spider-Man has MaxCLL of 10000 nits even though it was graded on Sony OLED with maximum brightness of 1000 nits. So 500 nits image will be presented in 350 nits.
And if it goes above your TV's maximum brightness it will skew the EOTF target and increase brightness roll off.
#SUBLER OFFSET FULL#
Not everybody fills full static metadata, some are using incorrect metadata that ruins tone mapping for OLED tvs without good DTM (LG)įor example, iTunes, ATV and Disney content (including disks) contains MaxCLL value way above what you can actually see in the actual movie. For movies with neither a Dolby Vision track nor HDR10+ metadata to convert, how much of a difference am I likely to notice on an LG C1 between auto-generating shot-by-shot metadata versus just playing it back with static metadata? Is it more likely to make a difference in a brighter room (so Dolby Vision IQ can do its thing) than a fully dark room?
0 kommentar(er)
