My personal remux of Saving Private Ryan was made with MakeMKV 1.5.3 back on 2020-11-26. That’s the first MakeMKV version to merge EL and BL. So I don’t think it’s necessarily an issue with early versions of MakeMKV.
1 Like
I don’t have that personally but if you are talking about the “hybrid” version it is known to cause issues. Plenty of talk about it’s CMv4.0 version on other forums and test samples as well.
No, i was talking about the cinephiles group version.
Greetings,
well I tried to do the try the FEL test today, but I cannot log in to my Vero V either by PowerShell or Putty, I get “connection refused” on both methods. SSH is checked in the settings.
is there another way?
Have you validated that you use the correct IP via the OSMC Settings status?
Yes, their hybrid version. That’s what I was talking about too.
They have a non-hybrid version as well.
People having issues with the hybrid on the AM6Bs on AVSF.
How do I know if it was hybrid? It didn’t say so in the title.
I’ve some insights about the cause of failing remuxes in the workflow (MakeMKV → MKVToolnix).
EDIT: After further investigation and a little help from AI to generate a script, the problem is a desync on RPU and BL in all the cases, which affect both MEL and FEL, that’s why it only happens when seeking or skipping to chapters. Those cases are concentrated in prior versions of MKVToolnix to 81, when the tool added support to read dual-layer Dolby Vision with both the base and enhancement layers in the same track from Annex B bitstream.
The script uses mkvextract to demux the raw HEVC bitstream, then pipes it through dovi_tool to extract the RPU NAL units into a binary file and read its frame count. That count is compared against the video frame count stored in the container’s track statistics tags. If the difference exceeds a two-frame tolerance the file is flagged as desynced, indicating that the RPU metadata is not properly aligned with the base layer.
The results match with the manual testing of the affected files by skipping to chapters, so it works.
The AI hypothesis:
In a Profile 7 file, the RPU is not a separate layer — it is embedded within the HEVC bitstream itself as NAL units of type 62 (Unspecified). These are interleaved between the regular video NAL units, one per frame, in strict order. The synchronization between the RPU and the BL depends entirely on that sequence remaining intact and in order.
When MKVToolNix prior to v81 remuxed an MKV, it had to parse the HEVC NAL units in order to correctly build the Matroska container structures — clusters, blocks, keyframe flags. The problem is that older versions did not recognize type 62 NAL units as part of the DV stream. To them, they were simply unknown NAL units.
1 Like
yes
Ok than it is odd. You could try to uninstall/install or you can follow the access via local console.
Details regarding how to access the command line interface can be found here on our Wiki: Accessing the command line - General - OSMC
ok, thank you
Just in case there’s a really simple solution vince48, I had myself in knots trying to figure out why Putty had stopped working, but then realised I’d been experimenting with a VPN and forgotten to turn it off…
thank you for the “reminder” but no VPN, but thanks for chiming in.
1 Like
Currently, colours on the osd (and throughout kodi) are overly saturated while playing a DV file. Is this something that can be addressed?
It is a known thing for the OSMC team, though one of the issues is, when playing a DV file, the OSD acts differently on different TVs and hard to fix it for all TVs at once.
They are experimenting with ways to change it.
1 Like
I’m happy that the team is trying taking their time and meeting these issues before realease. Why to go team!
Watched ‘Star Trek TMP, Director Edition’ UHD, iso backup, supposedly FEL. Supposedly using TV Led but Kodi does show me that display support TV Led and LLDV.
Main issue: Audio is trailing video by half a second or more. Repeated effect with a few other DV UHD, same effect. When disabling DV (force HDR10 playback) no audio latency. Also of course no-DV UHD discs.
Played around with various parameters, no change - passthrough, 24fps vs. 60fps display, sync video to display or now, playback from m2ts (browse into), playlist file. I think i managed sometimes to get very little latency when converting to 2.0 PCM, but given how that’s an irrelevant output (obviously i want my DTS audio)…
Secondary issues:
Is there really no reboot option in OSMC skin ? I looked long but had to change skin to reboot. Hiding well if it’s there.
It’s kinda non-intuitive that forcing EDID to HDR10 only does not disable use of DV. If you want to keep it this way, at least make a note of it in the explanation text on the bottom IMHO (“changing EDID does not disable DV processing…”).
No way to see if DV is FEL or not nor whether DV TV Led or LLDV is being used playing back (i guess this is planned - let’s see i can really see that info from the OSMC remote info key or the like…).
1 Like
If anyone else reported that I’ve missed it. Is it only with ISOs?
Power->Reboot just like on every other skin.
I don’t know what you mean. You can’t change the EDID with the GUI. You can force HDR10 output, but DV profile 5 will still be watchable as HDR10. Otherwise, DV is ‘disabled’.
Yes. FEL/MEL will be indicated with Kodi v22. We never output LLDV so no point in adding that.
1 Like
Thanks, Graham,
ISO: Hah. Right now i did everything from ISO (sorry for leaving this out), but as said either by browsing into and finding the m2ts file, or from the play menu using a playlist file or lastly blu ray menu (which has non-DV performance issues). And it works fine (no delay) when not decoding DV or having a file that doesn’t even have DV.
I should be able to continue testing in ca. 2 weeks with a different AVR / projector. Lets see if that makes a difference - if i am the only one reporting audio lag. And then i can also extract the m2ts. But if i am the only one with the problems i would rather bet it’s the AVR (VSX-S520). Lets see.
power/reboot - i must be getting blind… will check, thanks. But there was actually some crazy missing stuff in menus after the firmware upgrade. I had to go to the standard Kodi skin before passthrough options showed up, and then i could change over to OSMC skin to see them there. Maybe power option is also victim of that.
EDID = “force HDR10” : I agree that converting IPTQc2 to “normal” HDR10 signal (RGB color space), is completely logically when you say “force HDR10”. But then equally the setting should also force HDR10 signal for Profile 7 input (aka: play back only HDR10 base layer). Which it doesn’t. granted, this is only a logical/usability concern, not a functional one, given how i can force HDR10 output in a different menu. But it seems inconsistent to me.
TV-Led vs. LLDV: The HDMI output info in OSMC shows that my display supports TV-Led and LLDV. You could similarily argue that showing LLDV support serves no functional benefit given how the Vero V will never use that format. But i very much like the diagnostics. Likewise i think its nice to explicitly say that “TV Led” is being used, even if there is no alternative implemented. Again just a useability nitpick.
What makes you say that? Last time I looked you don’t get the FEL layer. At least if you change the settings not while playing a video.
Oh? Which one? Ah! I see what you mean. In the Display menu you can add capabilities to the EDID but it doesn’t remove capabilities like DV or HDR10+. In the Player-Video menu you can effectively take away such capabilities. Nothing to do with EDID, just bypasses DV processing.
Hugely beneficial to us when users complain they are not getting DV output.