Change HDMI RGB range on Vero

Help and Support Vero
1

Hi!

I have had some issues with the latest software updates on my Vero. Some of the packages always failed to install. So a couple of days ago I decided to do a clean install and went ahead and downloaded the Vero image and re-flashed the SD card. Now the updating works fine, but after the clean install (or the latest September update) I got a new problem with the HDMI RGB setting. The picture is very dark and blacks are crushed. So I suspect it got something to do with the RGB range setting. I have my TV set to normal RGB range (16-235) and when changing to full (0-255) the picture looks fine. I then however get issues with my other devices (IPTV box etc.) which requires the “normal” setting (all devices are connected through my AV receiver to one input on the TV).

So the long story short: Is there a way I can change the HDMI range setting on Vero? Can this be done in the uEnv.txt file for instance?

2

Interesting… I’ve been noticing the same condition on my Vero, as well. I thought it was just my less than stellar HDMI cable since a screen grab of the same video on both the RPi2 and the Vero looked identical. Now that someone else is experiencing the same thing, there must be something Vero setting specific?

Duke

3

Hi

The default settings towards RGB quant range have indeed changed. Full range is now automatically used if the TV supports it. You can try adding to this to the end of /boot/uEnv.txt:

mxc_hdmi.rgb_quant_range=limited

Then reboot

Sam

4

Thanks for that, Sam. I will try that tonight when I get home.

Just so I have enough information to be dangerous, :smiley: the options for that argument are “limited” and “full”, yes? Are these also applied in the same manner for the RPi/RPi2?

Thanks again, Sam.

Duke

5

Your options are

limited
full
auto
default

This commandline setting is only available on the Vero.

Sam

6

Cool. Thanks again, Sam. Is there any way to adjust this on the Pi side?

Duke

7

Hi

hdmi_pixel_encoding can be used in config.txt. 1 is Limited, which is what Vero would have used before the last update, and 2 is Full, which is what Vero users now.

@popcornmix may be able to offer some additional insight here

8

Hi!

I tried adding “mxc.rgb_quant_range=“limited”” to uEnv.txt, but unfourtantely that didn´t solve the problem.

My uEnv.txt file now look like this:

mmcargs=setenv bootargs console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 mxc.rgb_quant_range=“limited” dmfc=3 consoleblank=0 loglevel=2 osmcdev=vero

Any other ideas? Can I post some log to help with the debugging?

9

Hi

Did you put “limited” in quotation marks? You shouldn’t do that. I have updated my original post to make this clearer. My apologies.

Sam

10

Ok, I tried that as well, but still no luck. I then did a google search of the command you posted and found this:

mxc_hdmi.rgb_quant_range=*

Added “mxc_hdmi.rgb_quant_range=limited” to /boot/uEnv.txt and that did the trick. So the “hdmi” part were missing it seems. Problem solved!

Thanks for your help Sam!

11

Yes… that will work! Sorry!

Glad it has fixed it though

Sam