Dolby Vision now possible through MP4 Mux.

[DaMacFunkin]

Got it to work very strange behavior indeed

Hi, how did you get it to work, attached my edid on a previous post.

[shawnc22]

Like I said, the guy who tested my C9 edid said the LG was requesting LLDV from the Zidoo / Shield, don't know why it is different on the B9, the B9 and C9 don't have the same processor so might have different firmware.Attach-edid0003.zip
Anybody want a try?

There's an easy way to just test this on your own. Play some DV content on your Shield, and then open up the HDMI diagnostics menu on your C9 and check what kind of signal it's receiving. No need to worry about what anyone else's HDFury is reporting when you can get it directly from your TV.

[zxaura1]

Hello guys,
I only have a LG OLED E6 (2016) which plays some (not all) DV mp4 and TS files, but not any mkv files as Dolby Vision. I wonder if any of you knows a proper way to convert mkvs created with the latest MakeMKV, to DV .ts files (latest TSMuxer doesn't work for me, it creates a ts file that plays in HDR).
Maybe you @yusesope ?
Thanks in advance

[pete19]

Hello,

I have a LG CX and Oppo 203 and want to know if the DV signal displayed by the LG CX is tv-led or player-led.

How can I get that info ?

Thx.

[DaMacFunkin]

Hello,

I have a LG CX and Oppo 203 and want to know if the DV signal displayed by the LG CX is tv-led or player-led.

How can I get that info ?

Thx.

The Oppo can be set to player led or tv led for Dolby vision in the hdr settings.

[pete19]

The Oppo can be set to player led or tv led for Dolby vision in the hdr settings.

yes, I know that. But I want to leave on AUTO and see what DV type (tv-led or player-led) it sends depending on the media it plays back

is there any way to get that info ?

[TickTock]

I believe the furtherest we have got with the seeking issue, is that it is somehow related to the length of the file.

Interestingly, different formats, whilst they don’t support DV, supposedly allow seeking to work with long duration.

I haven’t got my player yet to investigate myself, but I think that’s all we know at the moment. Duration seems to be a factor but not necessarily the only factor at play.

Can’t help with the subtitle sync issue though, maybe someone else can.

Thanks for your response and for the information. I'm going to try an experiment with some files in the hope I can help narrow down/confirm the cause.

I believe the furtherest we have got with the seeking issue, is that it is somehow related to the length of the file.

I'm not sure of that anymore ...
The Lord of the rings trilogy all failed to FF/RW.
same for the first 2 Hobbit.

but somehow the Hobbit 3 has no issue with FF/RW even though it's a 2h40 movie. I'm sure I had issues with title shorter than that.

Last night I watched The Lord of the Rings The Fellowship of the Ring and I was able to fast forward. I used the latest version of tsMuxer and muxed both parts to individual m2ts files.

[RESET_9999]

Last night I watched The Lord of the Rings The Fellowship of the Ring and I was able to fast forward. I used the latest version of tsMuxer and muxed both parts to individual m2ts files.

I merged mine in a single TS file.
So if FF works for each individual part, that pretty much confirms the issue is related to the length of the movie.
thank you

[magnetoeric]

Still RGB 8bit here on my B9. Latest 5.0 firmware on the TV and 8.2.1 on the Shield experience. Tested with both UHD disk backup DV and Netflix DV.

Could you tell me how to access this menu on my CX?

[RayDawGGG]

ive been thinking this over and it makes sense...
Your CX is internally processing HDR via its app correctly, correct colours, correct tone map and as such it looks good.
Dolby Vision from the shield is being processed by the shield (player led LLDV) and as such looks a little darker, you also have the incorrect color to deal with.
For some reason the LG’s even though they can do TV led processing of Dolby Vision, request player led by default.
If you have an Oppo or Oppo clone you can force TV led processing (RGB 8 bit tunnelling) and it looks brighter than selecting player led ( 12 bit LLDV).

Not sure where you're getting this from, but LG's do not force the Shield to default to LLDV. At least on my B9, RGB tunneling is the default DV mode. Unless this changed in the new X-generation of TV's, you can only get LLDV from the Shield into an LG Oled via HDFury EDID spoofing.

I appreciate the feedback and knowledge. So the Shield still has color issues.. and the LG CX does a great job with HDR. I am now going to invest in a 4K UHD player(to support the 4K disc market). While I enjoy having the ability to play backups and save shelf space, I want to get the best picture on my CX. As the technology improves, maybe one day the Shield will be a great alternative. I'm going to remux to m2ts to see if DV logo shows in the CX plex app & check for visual differences.

[shawnc22]

Could you tell me how to access this menu on my CX?

http://ltroyalshrimp.com/how-to-get-int ... tics-menu/

[PlatypusW]

Last night I watched The Lord of the Rings The Fellowship of the Ring and I was able to fast forward. I used the latest version of tsMuxer and muxed both parts to individual m2ts files.

I merged mine in a single TS file.
So if FF works for each individual part, that pretty much confirms the issue is related to the length of the movie.
thank you

Yes but that isn't enough for me

I still haven't got myself a x700 yet, but I dug out my old x800. It can't do dolby vision, but I had some time today and figured it should be close enough to see whats going on (they should be very similar internal players if not the same).

Started with the second hobbit film. The raw m2ts and the tsmuxer file both wouldn't seek. 'Operation not permitted'.

Tried cutting the file with tsmuxer to 2 hours and 45 minutes. Seek worked.

Then I went for 2 hours 50 minutes. Seek didn't work.

Something in tsmuxer caught my eye: "--cut-end=10200000ms"

To me that seemed like such a specific round number. I have now tested both hobbit 1 and 2...

If the file is 2 hours, 46 minutes and 39 seconds or shorter. The file will allow seeking.
If the file is 2 hours, 46 minutes and 40 seconds or longer. The file will not allow seeking.

Turns out in milliseconds that is:

9999000ms: Seeks
10000000ms: Does not seek

From all this, I believe that if the file is greater than (or equal to) 10 million millisconds then seeking will not work. Anything below seems to work fine.

Does this align with what you have experienced on the x700? Know any titles that might be under this 10 million ms 'limit' that don't allow seeking?

Note: For me, on the latest tsmuxer nightly, the resulting file was always 1 second less than what I put into the 'end'. So if anyone tries this, take this into account if you are trying to be precise.

Why there might be such a limit I'm not sure - maybe someone else might know that

Never seen something related to length in ms, at least 10 million...doesn't really strike me as a number that would normally cause issues in the computing world

[RESET_9999]

↑↑ very interesting...

[Exovitae]

Does the Zidoo Z9X plays the new mkv dolby vision files more accurately than the Shield 2019 regarding colors? I keep reading about Shield and the problems with DV so i was thinking to try a Zidoo.

[pete19]

Last night I watched The Lord of the Rings The Fellowship of the Ring and I was able to fast forward. I used the latest version of tsMuxer and muxed both parts to individual m2ts files.

Did you happen to freeze frame compare the resulting m2ts file with the original movie ?

As per my earlier post, I also remuxed LOTR UHD DV to m2ts file via latest tsmuxer (one for each disc), and the resulting m2ts is slightly less bright in the highlights than the original UHD disc.

Both played back on Oppo 203 tv-led to LG CX.

see here for comparison: https://screenshotcomparison.com/comparison/8739

(ignore blown out highlights, this is a camera setting issue)

Would be interesting to hear your results.