[TESTING] Vero V: Dolby Vision TV led support

Testing
26

Thanks for the update, works perfect :ok_hand:

1 Like
27

Could you clarify this passage?
Vero V will output DV only on TV-led capable TV sets? Is that what you mean?

28

Yes. We donā€™t plan to implement player led. Some older TVs only support LLDV but this should not be an issue for modern displays.

We are not using the VS10 engine which can be used to sort of ā€˜upscaleā€™ content to DV.

29

Ok, thanks for clarifying. I own a tv-led capable set, I wasnā€™t asking for myself.
VS10 is not too much of a deal for the majority of cases, I think.

Hats off for pulling off all of this. Really surprising and a first in the tech world, I think.

1 Like
30

I thought Iā€™d come back this morning and say that the Dolby Vision content I have looks absolutely stunning on my Sony TV. All the DV content I have is from disc rips (that I own), so Iā€™ve only ever been able to test Profile 7. All my streaming is done from an AppleTV 4K, and Iā€™d say what Iā€™m getting from the Vero V is on par with what I get from the AppleTV 4K.

Many thanks to the OSMC team for their work on this.

As an aside, if you have local media with Dolby Vision that Kodi is saying is HDR, you just need to rescan the item and your library will update to say Dolby Vision. Recognition of DV content was only added in Kodi 21, so stuff scanned with older versions had the HDR tag. Someone related, ATMOS still isnā€™t recognized for tagging purposes (it passes through fine), but I believe Kodi 22 will add that, so youā€™ll be able to tell what you have that has Dolby Vision and ATMOS sound once the new version of Kodi is released (no, I have no idea when that will be).

1 Like
31

Confirming that DV content from Kodi samples plays as DV in my TV. Looks quite good, impressive stuff. Kudos to Sam and team!

1 Like
32

Hi Sam. Tried the Power Rangers sample from Kodi page and the text is showing as grey, not white. Also, woman does not appear at 80s on DV FEL All Layers Test.

Also, on my TV, LG C1, should I get a notification that DV is active or just the generic HDR one?

33

So, no LLDV? Thatā€™s a pity. Unfortunately, my display doesnā€™t support TV-led. Is there any plan to support it in the future?

34

FEL is not supported as outlined in the post.

Unfortunately not.

35

So when you say ā€˜Software is available which can merge a FEL into the base layer to produce a Profile 8.1 video.ā€™ you are not talking about software decoding done by the V?

36

Weā€™re talking about DoviBaker. But I donā€™t know exactly what it does with the FEL.

I donā€™t know. You can check with cat /sys/class/amhdmitx/amhdmitx0/dv_cap. If you see DV_RGB_444_8BIT you are good.

1 Like
37

Hey there - I just downloaded and tried and there are some issues. Unfortunately I am not up for going through the testing process as it is so shouldnā€™t have done it. My bad.

Just to summarize, the remote stopped working upon reboot but now works intermittently. The time on the Vero V is off by 5 hours. And every so often the 4k videos will freeze for about 30 seconds and then resume. Probably after about 10 minute or so of playing.

These would require probably multiple attempts at logs in order for the intermittent nature of them to show up. I just canā€™t do that at this time.

At this point Iā€™d just like to go back to the way it was. Iā€™m assuming if I take out apt.osmc.tv bullseye-devel main from the sources list and then force an update it should go back to before. Please let me know if Iā€™m wrong.

And thanks for the continuing work on this. Iā€™m sure once it is all figured out it will be great.

Paul

38

Hi Paul

You will need to reinstall OSMC from the Download page to get things back to where they were.

We havenā€™t had other reports of this and without logs, itā€™s hard to tell what the issue is.

Sam

39

But if you just post logs anyway, we can check if there was a problem with the update. First thoughts:

  • remote: could be to do with interference from a USB3 device
  • clock: known issue which I thought had been resolved. Just go into Region settings and it will sort itself out.
  • playback issues: could again be a USB3 problem if you are using WiFi. If you are not using WiFi, best to disable it.

I donā€™t know how you could downgrade except by reinstalling.

40

I am possibly thinking this ā€“ as OP was previously using Vero V as a server if I recall and had a number of disks attached.

Also agree because if using as a server he probably didnā€™t update to Kodi v21 for some time until now.

41

Interestingly, the clock thing happened to me during early testing of the DV stuff (one of the last builds). It did, in fact, sort itself out once I went to the region settings, so I didnā€™t think anything about it and didnā€™t report it. So thereā€™s apparently one holdout gremlin somewhere screwing with the clock randomly.

1 Like
42

Useful to know, Iā€™ll see if I can reproduce.

43

Here are the logs:

https://paste.osmc.tv/jinatedive.xml

I couldnā€™t reproduce the remote situation. Right now it seems to be working.

The time situation resolved itself once I simply went into the regional settings on the Vero. I donā€™t think I even changed anything - just looked to see that it had the proper timezone on the page. Next thing I knew, it was updated properly.

I couldnā€™t reproduce the freezing. I let it play (I believe) for about 10 minutes or so.

One thing I should note is that the 4k image using DV seems to be less contrast and with over-saturation. I had my TV setup for the standard HDR and so I will have to adjust this. Reinstalling is just way too much work since, as Sam correctly stated (good memory!), this is the server with many attached hard drives.

Instead of reinstalling, is there a way to simply turn off the DV right now on the Vero until Iā€™m ready to adjust the picture for DV so it resorts to HDR (what I refer - probably incorrectly - to standard HDR)?

Thanks!

44

Try Settings->Player->Videos->HDR processing->Force HDR.

Linux osmc 4.9.269-59-osmc #1 SMP PREEMPT Sun Aug 11 20:11:54 UTC 2024 aarch64 GNU/Linux

Check sources and try updating again. But WAIT! That log is for a Vero 4k :thinking:

45

Hey Graham - the Vero Iā€™m using is a Vero V. Thatā€™s what the label says. Any idea whatā€™s going on here?