Too dark picture. Vero 4K+

Help and Support
23

Odd. My Panny tells me if I press the info (i) button.

Sounds like your best bet is to force RGB on vero and full-range so everything is speaking the same language. But you won’t be able to watch 4k50/60fps HDR video.

24

Thanks, I don’t need a 4k output but would be nice if I didn’t have to fiddle with the TV every time I switch to/from the vero. Blu-ray/firestick and pvr are all ok through amp with tv set to full. No matter whether I set RGB to on or off and limited or full. Now I can’t seem to get a decent pcture at all with YCbCr and the only nice option is RGB limited (with tv set to normal). It’s annoying that the TV has an auto option which doesn’t seem to work.

25

Hi,
after 5 yrs of this thread opened, I’m still facing with too dark picture on vero4k / 4k+ too.
I have a LG55B7V Oled screen with native HDR, and Dolby Vision support.
The source files are normal 2160p HDR content but 1080p content are also too dark on my TV.
When I watch Netflix, MAX, ShowTime…any other streaming apps, the picture is decent.
Is there any tweak / extra settings on vero that would help?

26

This thread is five years old. It would be good to know what content you are playing on your device and some logs.

1 Like
27

Sure Sam,

Here is my log.
https://paste.osmc.tv/matumiwosa.xml
The file I was trying to play is:
Silo.S02E02.Order.2160p.ATVP.WEB-DL.DDP5.1.DV.HDR.H.265-NTb.mkv

Info:
—GENERAL----
Size…: 7.19 GiB
Container…: Matroska
Duration…: 00:41:24.566

—VIDEO----
Codec…: HEVC, Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible, PQ
Resolution…: 3840x1606
Bit rate…: 24.1 Mb/s
Frame rate…: 23.976 fps

—AUDIO----
Format…: Dolby Digital Plus with Dolby Atmos
Channels…: 6 channels
Sample rate…: 48.0 kHz
Bit rate…: 768 kb/s
Language…: English

But honestly any file I try to play is very dark).
My Tv is LG OLED 55B7V
Any help would be appreciated.

28

These aren’t full logs, so unfortunately my guess is as good as yours.

29

Thanks Sam.
How long should be the log file? Should I open debug logging, than play some videos and go back to log screen and switch debug log off? Or just upload the whole log file I got back to some days?

30

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image960×539 41.4 KB

31

I am so sorry about forgot this method. I did not have any problem with my vero4k, so that’s why I forgot how to do the proper upload.

Here it is my latest log from my device.
https://paste.osmc.tv/elodoreyud

32

I wonder if it’s just the HDR fallback layer that is dark. Can you try a non Dolby Vision clip?

33 
Use limited colour range (16-235): false

Turn this setting on and see if it gets better. There’s no reason not to use limited colour range unless you are watching on a PC monitor.

34

I tried but other sources are dark too, I mean much darker than on my pc monitors.
(DELL U215H 1440p, LENP24H-20).

But as I said before Netflix or Disney 4K Dolby Vision movies are just fine on my TV, so it shouldn’t be the tv itself I guess.

35

It could be - because the fallback layer won’t be used on your TV, the DV track will be.

Can you try a non DV clip as a test?

36

I set up this settings and applied the october update. Since than, all of my nfs share are unaccessable.
I’ll post it to another thread, logs:
https://paste.osmc.tv/elodoreyud


2024-12-03 09:34:13.595 T:3012    error <general>: NFS: Failed to mount nfs share: / (mount_cb: command timed out)
2024-12-03 09:34:13.597 T:3012  warning <general>: Process directory 'nfs://192.168.17.14/volumeUSB1/usbshare/tv series - usb/Severance/' does not exist - skipping scan.

192.168.1.x allowed to access

2024-12-03 09_49_29-ESOX_NAS - Synology DiskStation
2024-12-03 09_49_29-ESOX_NAS - Synology DiskStation1052×726 223 KB

37

Please open new thread to not pollute this thread.
But initial question what is sitting between 192.168.1.0/24 and 192.168.17.0/24?

38

0/24 means every number from 0…255

39

Really? Wasn’t aware of that :speak_no_evil:

40

8 bits dedicated to IPs

Which means 2^8 = 255
Two IPs are lost (broadcast address and gateway address), giving 253 usable/routable IPs.

I can do CIDR and calculations for v4 but when it gets to v6 it gets a bit :face_with_diagonal_mouth:

Try a ping first to check access.

1 Like
41

This is definitely did the “trick”. Thank you.

2 Likes