Vero 4K+ EDID issues with Samsung 8 Series smart TV UE55MU8009


#1

Hi @ All,

I received my Vero 4K+ today and I have trouble with UHD (HDR) Files with more than 30 FPS.

As example the file “Samsung and RedBull See the Unexpected HDR UHD 4K Demo.ts” is a UHD HDR sample from Samsung with 59.949 FPS, you could easily find it in web. But it is only played back with 30 FPS HDR.

I figured out that the Vero has incorrect EDID from my TV (Samsung UE55MU8009 is directly connected, no AVR in between):

osmc@Vero4K:~$ cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz

But I’m pretty sure that this TV supports 2160p60 on all four HDMI inputs. I checked that (same port same HDMI cable) against my Desktop PC (Win10, GTX970) and 2160p60 works well and is also directly suggested by the Nvidia graphics driver.

I still also have an RaspberryPi 3 connected to the TV running OSMC (it should be replaced by the Vero), following output:

osmc@rpspi:~$ /opt/vc/bin/tvservice -d edid.dat
Written 256 bytes to edid.dat
osmc@rpspi:~$ /opt/vc/bin/edidparser edid.dat
Enabling fuzzy format match…
Parsing edid.dat…
HDMI:EDID version 1.3, 1 extensions, screen size 121x68 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 24-75 Hz, horizontal is 15-81 kHz, max pixel clock is 300 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is SAMSUNG
HDMI:EDID failed to find a matching detail format for 3840x2160p hfp:176 hs:88 hbp:296 vfp:8 vs:10 vbp:72 pixel clock:297 MHz
HDMI:EDID calculated refresh rate is 30 Hz
HDMI:EDID guessing the format to be 3840x2160p @30 Hz
HDMI:EDID found unknown detail timing format: 3840x2160p hfp:176 hs:88 hbp:296 vfp:8 vs:10 vbp:72 pixel clock:297 MHz
HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID established timing I/II bytes are BD EF 80
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II
HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x714F 81C0 8100 8180 9500 A9C0 B300 0101
HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 0
HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 1
HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 2
HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 3
HDMI:EDID found DMT format: code 47, 1440x900p @ 60 Hz (16:10) in standard timing 4
HDMI:EDID found DMT format: code 83, 1600x900p @ 60 Hz (16:9) in standard timing 5
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 6
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:0
HDMI:EDID found CEA detail timing format: 1920x1080i @ 50 Hz (20)
HDMI:EDID found DMT detail timing format: 1366x768p @ 60 Hz (81)
HDMI:EDID does not understand CEA format code 95
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz
HDMI:EDID found CEA format: code 32, 1920x1080p @ 24Hz
HDMI:EDID found CEA format: code 33, 1920x1080p @ 25Hz
HDMI:EDID found CEA format: code 34, 1920x1080p @ 30Hz
HDMI:EDID does not understand CEA format code 93
HDMI:EDID does not understand CEA format code 94
HDMI:EDID does not understand CEA format code 98
HDMI:EDID does not understand CEA format code 99
HDMI:EDID does not understand CEA format code 100
HDMI:EDID found CEA format: code 7, 1440x480i @ 60Hz
HDMI:EDID found CEA format: code 22, 1440x576i @ 50Hz
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: 16|20|24 bits
HDMI:EDID found audio format 6 channels AC3, sample rate: 32|44|48 kHz, bitrate: 640 kbps
HDMI:EDID found audio format 6 channels DTS, sample rate: 48 kHz, bitrate: 1536 kbps
HDMI:EDID found audio format 8 channels Dobly Digital+, sample rate: 32|44|48 kHz, codec define: 0
HDMI:EDID found Video Capability DB length 2
HDMI:EDID video capability: CE:3 IT:3 PT:0 QS:0
HDMI:EDID extended data block tag 0x05 length 3 not supported
HDMI:EDID found HDMI VSDB length 14
HDMI:EDID HDMI VSDB has physical address 4.0.0.0
HDMI:EDID HDMI VSDB supports AI:yes, dual link DVI:no
HDMI:EDID HDMI VSDB deep colour support - 48-bit:no 36-bit:yes 30-bit:yes DC_yuv444:yes
HDMI:EDID HDMI VSDB max TMDS clock 300 MHz
HDMI:EDID HDMI VSDB does not support content type
HDMI:EDID HDMI VSDB supports extended resolutions 1,2,3,4
HDMI:EDID extended data block tag 0x06 length 3 not supported
HDMI:EDID extended data block tag 0x0e length 5 not supported
HDMI:EDID adding mandatory support for CEA (1) 640x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (2) 720x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 61864)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 66472)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 135592)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 18432
HDMI:EDID best score mode is now CEA (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz (score 149416)
HDMI:EDID DMT mode (5) 640x480p @ 72 Hz with pixel clock 31 MHz has a score of 22118
HDMI:EDID DMT mode (6) 640x480p @ 75 Hz with pixel clock 31 MHz has a score of 23040
HDMI:EDID CEA mode (7) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 28800
HDMI:EDID DMT mode (10) 800x600p @ 72 Hz with pixel clock 50 MHz has a score of 34560
HDMI:EDID DMT mode (11) 800x600p @ 75 Hz with pixel clock 49 MHz has a score of 36000
HDMI:EDID best score mode is now CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz (score 5398248)
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 47185
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID DMT mode (17) 1024x768p @ 70 Hz with pixel clock 75 MHz has a score of 55050
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID DMT mode (18) 1024x768p @ 75 Hz with pixel clock 78 MHz has a score of 58982
HDMI:EDID CEA mode (19) 1280x720p @ 50 Hz with pixel clock 74 MHz has a score of 117160
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 4732360
HDMI:EDID DMT mode (21) 1152x864p @ 75 Hz with pixel clock 108 MHz has a score of 99649
HDMI:EDID CEA mode (22) 1440x576i @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (28) 1280x800p @ 60 Hz with pixel clock 83 MHz has a score of 86440
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 232360
HDMI:EDID CEA mode (32) 1920x1080p @ 24 Hz with pixel clock 74 MHz has a score of 124532
HDMI:EDID CEA mode (33) 1920x1080p @ 25 Hz with pixel clock 74 MHz has a score of 128680
HDMI:EDID CEA mode (34) 1920x1080p @ 30 Hz with pixel clock 74 MHz has a score of 149416
HDMI:EDID DMT mode (35) 1280x1024p @ 60 Hz with pixel clock 108 MHz has a score of 103643
HDMI:EDID DMT mode (36) 1280x1024p @ 75 Hz with pixel clock 135 MHz has a score of 98304
HDMI:EDID DMT mode (47) 1440x900p @ 60 Hz with pixel clock 106 MHz has a score of 102760
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 130840
HDMI:EDID DMT mode (81) 1366x768p @ 60 Hz with pixel clock 85 MHz has a score of 4062945
HDMI:EDID DMT mode (83) 1600x900p @ 60 Hz with pixel clock 108 MHz has a score of 111400
HDMI:EDID DMT mode (85) 1280x720p @ 60 Hz with pixel clock 74 MHz has a score of 80296
HDMI:EDID preferred mode remained as CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
osmc@rpspi:~$

For me it looks like both systems has a problem with the EDID data, maybe something OSMC specific? Any patch possible?
Are there any possibilities to tell the Vero manually which resolutions are supported by my TV ignoring any EDID data?

This is an major issue for me.

Best,
Bimbo385

Edit: When I reboot the Vero4K+ it comes back with 720p60 which results in a ugly overscanned picture…


#2

Hi,

We can definitely override EDID data. This is quite easy to do.
But first thing to check: can you give us the output of cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid

It’d be handy to know what EDID your TV is giving us; to see if it’s a parsing issue or a problem with what your TV is giving us.

Cheers

Sam


#3

Good Morning,

thanks for the fast answer, here it is:

osmc@Vero4K:~$ cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid
00ffffffffffff004c2dee0d000e0001011b0103807944780a23ada4544d99260f474abdef80714f81c0810081809500a9c0b300010104740030f2705a80b0588a00501d7400001e023a801871382d40582c4500501d7400001e000000fd00184b0f511e000a202020202020000000fc0053414d53554e470a2020202020013a020349f0535f101f041305142021225d5e626364071603122c0907071507503d04c057070083010000e2000fe30503016e030c001000b83c20008001020304e3060d01e50e60616566011d80d0721c1620102c2580501d7400009e662156aa51001e30468f3300501d7400001e00000000000000000000000000000000000069
osmc@Vero4K:~$

Best,
Bimbo385

Edit:

I just edited the format a little bit to get http://www.edidreader.com/ working:

0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00, 0x4c, 0x2d, 0xee, 0x0d, 0x00, 0x0e, 0x00, 0x01, 0x01, 0x1b, 0x01, 0x03, 0x80, 0x79, 0x44, 0x78, 0x0a, 0x23, 0xad, 0xa4, 0x54, 0x4d, 0x99, 0x26, 0x0f, 0x47, 0x4a, 0xbd, 0xef, 0x80, 0x71, 0x4f, 0x81, 0xc0, 0x81, 0x00, 0x81, 0x80, 0x95, 0x00, 0xa9, 0xc0, 0xb3, 0x00, 0x01, 0x01, 0x04, 0x74, 0x00, 0x30, 0xf2, 0x70, 0x5a, 0x80, 0xb0, 0x58, 0x8a, 0x00, 0x50, 0x1d, 0x74, 0x00, 0x00, 0x1e, 0x02, 0x3a, 0x80, 0x18, 0x71, 0x38, 0x2d, 0x40, 0x58, 0x2c, 0x45, 0x00, 0x50, 0x1d, 0x74, 0x00, 0x00, 0x1e, 0x00, 0x00, 0x00, 0xfd, 0x00, 0x18, 0x4b, 0x0f, 0x51, 0x1e, 0x00, 0x0a, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xfc, 0x00, 0x53, 0x41, 0x4d, 0x53, 0x55, 0x4e, 0x47, 0x0a, 0x20, 0x20, 0x20, 0x20, 0x20, 0x01, 0x3a, 0x02, 0x03, 0x49, 0xf0, 0x53, 0x5f, 0x10, 0x1f, 0x04, 0x13, 0x05, 0x14, 0x20, 0x21, 0x22, 0x5d, 0x5e, 0x62, 0x63, 0x64, 0x07, 0x16, 0x03, 0x12, 0x2c, 0x09, 0x07, 0x07, 0x15, 0x07, 0x50, 0x3d, 0x04, 0xc0, 0x57, 0x07, 0x00, 0x83, 0x01, 0x00, 0x00, 0xe2, 0x00, 0x0f, 0xe3, 0x05, 0x03, 0x01, 0x6e, 0x03, 0x0c, 0x00, 0x10, 0x00, 0xb8, 0x3c, 0x20, 0x00, 0x80, 0x01, 0x02, 0x03, 0x04, 0xe3, 0x06, 0x0d, 0x01, 0xe5, 0x0e, 0x60, 0x61, 0x65, 0x66, 0x01, 0x1d, 0x80, 0xd0, 0x72, 0x1c, 0x16, 0x20, 0x10, 0x2c, 0x25, 0x80, 0x50, 0x1d, 0x74, 0x00, 0x00, 0x9e, 0x66, 0x21, 0x56, 0xaa, 0x51, 0x00, 0x1e, 0x30, 0x46, 0x8f, 0x33, 0x00, 0x50, 0x1d, 0x74, 0x00, 0x00, 0x1e, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x69

And I found out something interesting. There is one “Video Data Block” within “Block 1” which contains the formats recognized by the Vero4K+ missing the 2160p/4K formats with higher frame rates. But there are a second “YCbCr 4:2:0 Video Data Block” within “Block 1” which only contains the missing UHD and 4K high frame rate resolutions.

My guess is that the Vero4K+ parses only the “Video Data Block” and doesn’t recognize the information in the additional “YCbCr 4:2:0 Video Data Block”.

Maybe it’s quiet unusual that Samsung split these information in two separate blocks to distinguish between the color formats but it looks like a bug in the EDID parser.

Best,
Bimbo385


#4

Thanks. This is useful


#5

Hey,

It’s good that my report is useful, but what happens next? Any bugfix in near future? How could I fake the EDID in the meantime?

I don’t want to sent the Vero back but this is not what I expected and without a solution I see no other way.

Best
Bimbo385


#6

You can put your own disp_cap in /home/osmc/.kodi/userdata with the resolutions you’d like supported. This will override EDID. You will need to restart Kodi after.


#7

Hi,

I copied the disp_cap from /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap and added lines with the correct resolutions I think (see below). But the only effect I can recognize is that the first line has something to to with the resolution which is set after a complete reboot.
But the kodi resolution is still 3840x2160p30 after reboot and 30hz is the highest framerate available in the menu. But now there a two times 3840x2160p available (maybe because I split the possible 2160p resolutions) and there are an additional 4096x2160 resolution with low frame rates which I haven’t expected at all.

Playback of a 59.9/60hz video file is still 30hz.

Is some kind of documentation available for the disp_cap file which string means which resolution in particular. Google found nothing on the first two pages. I see no logical optino to distinguish between fractional and non fractional refresh rates and between 4096x2160 and 3840x2160 which is both supported by my TV.

And there are other very annoing things with Vero and resolutions. When I set the Vero to 1920x1080p60 I get it but by default my TV does overscanning. Than I have an option to adapt the resolution to the screen. With Auto and Off I have overscan, it fits only with the On setting.
But when I connect my old Notebook (only HDMI 1.4) and select 1080p60 I haven’t any overscan and the option adapt to screen is grayed out on my TV. So there must be a difference between the Vero FullHD and the one from my Notebook.

osmc@Vero4K:~/.kodi/userdata$ cat /home/osmc/.kodi/userdata/disp_cap
2160p60hz
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p59hz
2160p50hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz


#8

With your notebook connected your TV probably switches to PC mode which normally automatically deactivates overscan (and also other image enhancement options for less input lag) on most TVs. That’s probably the difference…


#9

Hey,

I checked that against my RaspberryPi and it behaves exactly the same at 1080p60. So I think that’s ok.
But I still haven’t 2160p60. I’m going to play a little bit with the disp_cap file but I don’t have much hope.

Have someone 2160p60 working in the Kodi menus and library with the Vero4K+?

Best,
Bimbo385


#10

Yes — but we really don’t recommend doing this.

The scaler on your TV will be better. Instead you should set it to 1080p and enable adjust refresh rate for 4K auto switching


#11

Yes Okay,

but the option should be available and it should be working. But in my case 4k60p playback and menu isn’t working at all.

Edit:

I’ve selected 1080p60 as menu resolution and the result is that UHD content with 60hz is played as 1080p60 instead of 2160p60 or at least 2160p30.

I’m still looking for a reference for the disp_cap, my is now:

osmc@Vero4K:~$ cat /home/osmc/.kodi/userdata/disp_cap
480p60hz
576p50hz
720p60hz
720p50hz
1080i60hz
1080p60hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p60hz
2160p50hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz

Next Edit: I got it:

The trick is to add “420” behind the 2160p50/60hz resolutions in the disp_cap. I would guess this is for the YCbCr 4:2:0 color space. But how to know this… I found it out by chance while searching for the weird smpteXYhz resolutions. Here some peoples have posted their disp_cap with the 420 at the end and I just tried.

I still don’t know what the “*” is good for, maybe a mark for native or recommended resolution, but I haven’t recognized any effect.

Is there any action on the OSMC side to fix the obvious bug in the EDID parser?

I will keep my Vero4K+, because it works for me but I wasn’t happy with the support.

My custom disp_cap is now:

osmc@Vero4K:~$ cat /home/osmc/.kodi/userdata/disp_cap
480p60hz
576p50hz
720p60hz
720p50hz
1080i60hz
1080p60hz*
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p60hz420
2160p50hz420
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz


#12

Hello,

The asterisk (*) marks a preferred mode. Some TVs do not advertise one.

I’m very sorry to hear this and I hope we can meet your expectations. It sounds like you might have a quirky TV here. We’ll work towards improving things for you. Please send me a PM and I’m happy to take a phone call to discuss things with you.

With that said: we do not recommend running the GUI at 4K at all. Kodi skins are only at 1080p, so they are scaled. Your TV will likely do a better job at scaling than Kodi.

Your issue was reported on 2nd November, so it will need a bit of time to address this. With any luck we can get it included in the next monthly update (November). In future, for a more expedient response you can open a ticket via the ticketing system.

Cheers,

Sam


#15

I doubt there is anything wrong with the EDID parser. It looks to me like you are using an HDMI input on the TV that is set to a lower HDMI mode (there are various names for it but the maximum you will get is 4k50/60 4:2:0 at 8 bits). We have not been reading that resolution into disp_cap because most (all?) 4k60Hz material is HDR. If you play it at 8 bits you will get banding. Much better to play it at 1080p and 10 bits.

But if you set your HDMI input to ‘Ultra HD’, ‘HDMI mode 2’ or whatever Samsung call it, you should get the full range up to 4k60Hz 4:2:0.

HTH


#16

Hi graham,

How do you get this information? I can’t find any option on my TV to switch the type of the HDMI inputs.

But if I play UHD 60hz material which is HDR the TV shows me a little HDR logo next to the resolution info when pressing the info button. When I play UHD 60hz material which is non HDR this logo didn’t appear. I can’t see any banding on my HDR test clips.

Best,
Bimbo385


#17

Page 120 of your manual has some information.
http://downloadcenter.samsung.com/content/UM/201801/20180123103332177/ENG_KTMDVBEUL-3.0.7_180111.1.pdf

I can’t immediately find a menu tree to see where you set ‘UHD Color’.


#18

Oh shit… you’re absolutely right.

The whole thing seems to be my fault, I only can say sorry for the trouble. RTFM…

I found the menu but to find it is like playing hide and seek. Its hidden under “Allgemein -> Externe Geräteverwaltung” (German language) and not under “Bild” (Picture) where all other color and image options are.

Now also the EDID parser offers 2160p60 by default without any custom disp_cap. Beside the resolution another string (something like UHD color) appears now.

I think we can close this discussion and many thanks for your help. But maybe this information are very useful for all the other Samsung users out there and could be a tip in the WiKi.

If I could support OSMC somehow, please let me know.

Best,
Bimbo385


#19

https://osmc.tv/about/#donate :wink:


#20

done