Boot time screen resolution

[osmcb]

Hi,

the OSMC boot logo looks quite ugly (with jagged lines) and based on other forum entries it is related to the preferred screen resolution the TV reports during boot.

cat /proc/cmdline

initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 revision=4kplus androidboot.selinux=permissive logo=osd1,loaded,0x7f800000,720p60hz maxcpus=4 vout=720p60hz,enable hdmimode=720p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 pq= androidboot.firstboot=0 jtag=apao androidboot.hardware=amlogic mac=90:0e:b3:07:87:d5 androidboot.mac=90:0e:b3:07:87:d5 androidboot.slot_suffix=normal androidboot.rpmb_state=0 root=/dev/vero-nand/root rootfstype=ext4 quiet console=tty0 osmcdev=vero3

cat /sys/class/amhdmitx/amhdmitx0/disp_cap

480p60hz
576p50hz
720p50hz
720p60hz
1080p24hz
1080p30hz
1080i50hz
1080p50hz
1080i60hz
1080p60hz
2160p30hz
2160p24hz
2160p25hz
2160p30hz
2160p50hz
2160p60hz*
smpte24hz
smpte50hz
smpte60hz

Why has OSMC chosen 720p instead of 2160p? The preferred resolution is correct.

[grahamh]

I don’t think we can probe EDID in the bootloader so have to use a resolution that works on nearly all displays to avoid those ‘out of range’ messages.

[osmcb]

This discussion suggests that it should be possible.

Resolution of the boot image

No, I don’t believe so. It seems that U-Boot believes the preferred video mode of your device is 720p50. It would be good if you could run the following commands to confirm whether the kernel also believes this: cat /sys/class/amhdmitx/amhdmitx0/edid cat /sys/class/amhdmitx/amhdmitx0/disp_cap If you have an AVR, you may wish to connect directly to the TV temporarily. It’s possible it’s giving the device the incorrect EDID. Sam

Resolution of the boot image

There should be an asterisk beside one of the modes on the output of the second command next to the TV’s preferred mode. Your TV is not reporting a native/preferred mode. Because of this we default to 720p. This doesn’t stop you selecting 1080p in Kodi however, so it only affects the resolution of the boot screen. The program that displays the boot screen does not do high quality scaling so any boot resolution besides 1080p will cause the word OSMC to look a bit jaggy.

[grahamh]

OK, can you grab logs, then?

[osmcb]

https://paste.osmc.tv/tipoxawala

[darwindesign]

@osmcb

the OSMC boot logo looks quite ugly (with jagged lines) and based on other forum entries it is related to the preferred screen resolution the TV reports during boot.

The program that displays that image has a very poor scaler. If the couple seconds it displays bothers you that much the path of least resistance is to simply rescale the image on a PC to match the resolution your TV is at during boot. Alternatively you could replace it with a solid color or gradient that would not be sensitive to scaling artifacts.

Better boot logo and sad face

This is a bit of an understatement. If this really bothers you and you want to fix it then you have to figure out the resolution of your TV during boot. On my TV I can press the “info” button on the remote and it shows this information (mine is 1366x768 during boot). Download the image below (this is NOT the same as what comes with OSMC) and resize it to your boot display resolution if your display is something other than 1920x1080. https://drive.google.com/file/d/1eLJI8jVTQ4WBEyTy2hFaNybpQswi…

[osmcb]

Sorry for the harsh “quite ugly” statement. This thing is far away from being a problem I have replaced the splash.png with a 2160p png, but the jagged lines are still there. During boot my TV reports 720p as screen resolution and that most likely is the root cause for the jagged lines because of the needed scaling. The remaining question is if technically the Vero 4k+ is able to use a 2160p resolution during boot…

[grahamh]

I’m just checking if there’s a reason we can’t.

[sam_nazarko]

@osmcb

The remaining question is if technically the Vero 4k+ is able to use a 2160p resolution during boot…

You can force a resolution using fw_setenv.
Beware if you move it to another TV, you’ll need to swap this back.

[darwindesign]

@osmcb

I have replaced the splash.png with a 2160p png

You saw that jaggies with it scaling the stock 1920x1080px image to 1280x720px so it would only stand to reason that it scaling an even larger image would not provide a superior result. My point was to replace the image with one of the same resolution as your TV during the boot which your saying is 1280x720px. This will obviously be softer than a higher resolution image but the jaggedness your seeing should not be there as the program will no longer be scaling it.

[osmcb]

Good point. I have tried Sam’s fw_setenv suggestion and it has fixed the problem. Your approach has the advantage that it works even if i switch to a non 4K TV. Let me try that too…

[osmcb]

That works too. The scaler of the TV works much better than the Vero scaler. I will use the fw_setenv hdmimode 2160p60hz setting because it looks even better in the native resolution and it avoids another resolution switch after the boot sequence. Thanks for all your hints.

[sam_nazarko]

@osmcb

The scaler of the TV works much better than the Vero scaler

Just FYI - the issue is not the Vero scaler. The hardware video scaler is not used to display this image. If it was, and this was an issue, you wouldn’t be able to play lower resolution formats without issue.

The issue is that the specific splash screen application which scales the images doesn’t have a good scaler.