[HowTo] Guide to the Kodi whitelist function and related settings

Platforms: Vero 4K and 4K+, Raspberry Pi 2 and 3.
Applies to OSMC v18.x and 19.x

I would like to cover the Pi 4 as well, but I don’t possess one; if others would like to research it for me, feel free!


Introduction

This is a guide to the Kodi whitelist feature and some related settings, and how to use them to get the best possible image quality.

Feel free to post comments and suggestions below.

This is in question-and-answer format; click/tap on a section to expand it.

Notes

  • This is for users with a Vero 4K or 4K+, or a Raspberry Pi 2 or 3. I am not familiar with older Vero devices or the original Apple TV, so I can’t comment on them. As noted above, I also have no direct knowledge of the Raspberry Pi 4 - all references to “Pi” in here refer to the Pi 2 and 3, unless otherwise specified.

  • Any time the text refers to “Vero 4K” it also applies to the Vero 4K+.

  • The text generally assumes that you are using the default OSMC skin. I imagine that the same settings are available in other skins, but the icons and the structure of the menus may be different.

Questions and Answers

1) What is a whitelist?

The whitelist is the list of video modes (combinations of output resolution and refresh rate) that Kodi is allowed to switch to automatically when playing a video.

2) What happens if I don't set up a whitelist?

With all settings at stock/default values, Kodi runs at a fixed resolution and refresh rate: everything is scaled and/or frame-rate-converted to that one mode.

This has several disadvantages. The Kodi GUI isn’t optimised for 4K resolution, so you shouldn’t set Kodi to run at 4K; but if you set the GUI to run at 1080p then 4K videos will be downscaled. And frame-rate-conversion can reduce viewing quality.

To improve on this, go into Settings>Player>Videos and set the (misleadingly named!) “Adjust display refresh rate” setting to “On start/stop”. This allows Kodi to change its output refresh rate to match the frame rate of the video; it also allows Kodi to switch the resolution upwards, but not downwards; so, if the GUI is running at 1080p, that setting allows Kodi to change resolution to 4K (2160p) when playing a 4K video. (Obviously this doesn’t apply to a Raspberry Pi which is not capable of 4K playback).

Note: the recommendation is that all users should use these two settings (i.e. set “Adjust display refresh rate” to “On start/stop” and set the GUI to run at 1080p). If you aren’t using a whitelist, this is recommended; if you are using a whitelist, this is essential - without it, the whitelist won’t work correctly.

Tip: when Kodi switches output resolution or refresh rate, the screen will usually go black for a few seconds, which means you may miss a little bit of the video. You can prevent that by adding an automatic delay to playback when there’s a mode change. Under Settings / System / Display / General, there’s a setting called “Delay after change of refresh rate”. Set that to however long it takes for the picture to come back up, and you won’t miss anything.

3) How does using a whitelist help?

First, if you don’t use a whitelist, any video that has a resolution of less than 1080p (for example, DVD rips) will be upscaled to 1080p (assuming the Kodi GUI is running at that resolution). If you do use a whitelist then 720p, 576p/i and 480p/i videos can also be output at native resolution. (Section 4 explains why this is desirable).

Secondly, if you have set up a whitelist you get an extra menu in the OSD during playback. (In the default OSMC skin, this is launched from an icon on the far right hand side). This allows you to switch to any whitelisted mode on the fly (and thus override Kodi’s default choice if you don’t like it).

Thirdly, there are some situations where you might want to block Kodi from switching to a specific resolution or refresh rate while still allowing it to use others. The whitelist gives you fine-grained control over which modes Kodi can or can’t use.

Finally, without a whitelist, Kodi will only switch resolutions if the video dimensions exactly match an allowed output resolution. So, for example, if the video is 2560x1440, with no whitelist this will be downscaled to 1080p; with a whitelist active Kodi can upscale to 4K instead.

4) Why might outputting a video at native resolution improve image quality?

It means it is the TV, not the Vero 4K or the Pi, that does the upscaling.

Almost all TVs can upscale as well as the Vero 4K or Pi can, and most TVs can do it at least a little better.

In addition, if the TV screen is 4K resolution, then without a whitelist a low resolution video is scaled twice: once by Kodi to 1080p and once by the TV from 1080p to 4K. Doing all of the scaling in one step gives better image quality.

5) How do I set up a whitelist?

Look under Settings>System>Display. (You will need to set “Settings level” to “Expert” for the setting to be visible).

When editing the list, Kodi gives you a list of all possible video modes, and you can choose to make each one active or not. Active modes are highlighted; click on one to select or deselect it. (In the standard OSMC skin, with the default colour scheme, active modes are coloured blue, inactive ones are grey).

When you’ve finished editing the list, remember to select “OK” at the bottom of the screen, otherwise the change won’t be saved.

Important: there are some other settings you may need to change, in the Settings>Player>Videos section.

  • Set “Adjust display refresh rate” to “On start/stop”.

  • Make sure “Sync playback to display” is NOT selected.

  • You also need to set “Display 4:3 videos as” correctly. Vero 4K users should usually set this to “Use HDMI AVI signalling”, but there are a few exceptions. Pi users running Kodi v19 should usually select “Stretch 16:9”. For Pi users running Kodi v18, it’s more complicated. See the next section (section 6) for more information.

If you are using Kodi v19, please also see section 20 of this guide - there are two new settings.

6) What do the different options for the 'Display 4:3 videos as' setting do?

There are three options for this setting that could make sense.

Option 1: "Normal"

Behaviour on the Pi in Kodi v19

I will freely admit that I don’t entirely understand what this option does on the Pi in Kodi v19, but whatever it’s doing, it definitely isn’t right! On a 4:3 SD video, it seems to shrink the picture in both dimensions.

Behaviour on the Vero 4K or on the Pi in Kodi v18

With this option, Kodi manages aspect ratio by scaling videos differently. 16:9 videos are scaled to fill the screen horizontally; 4:3 videos are scaled to fill three quarters of the screen horizontally, with the rest of the screen filled in black. Kodi always tells the TV that the aspect ratio is 16:9.

This approach works well if the output resolution is 720p or higher. If the output resolution is 576p or 480p, 16:9 videos still look good, but 4:3 videos are horizontally downscaled from 720 pixels wide to 540, and the rest of the screen filled in black. The aspect ratio that you see on the TV is correct, because the TV is still in 16:9 mode and stretches the video back to its correct size; but because the video is downscaled before it is sent to the TV, you lose horizontal resolution in the image, which significantly harms the image quality.

Summary: definitely a bad idea for Pi users under Kodi v19. On the Pi under v18 or on the Vero: good for HD videos; 16:9 SD videos are fine; 4:3 SD videos upscaled to HD are okay; SD 4:3 output at native resolution has the correct aspect ratio, but looks significantly worse because of downscaling. May be the best option for Pi users running Kodi v18. (See under “The Best Option” below).

Option 2: "Use HDMI AVI Signalling"

This option is only available on the Vero 4K and not on the Pi.

For HD videos, it works the same way as the “Normal” setting - controlling aspect ratio by scaling. For SD output at native resolution, the video is always output without any downscaling, and the Vero signals the TV to switch aspect ratio between 16:9 and 4:3 as needed.

Assuming your TV (or other equipment) does what it is supposed to do, this is the best option; every type of video is played with the correct aspect ratio automatically, and nothing suffers from resolution loss.

But there are some TVs and AVRs which don’t behave the way they’re supposed to - they may not correctly respond to the signal to switch aspect ratio, or they may misbehave in other ways (e.g. by adding undefeatable overscan when the aspect ratio is 4:3). In this case you may need to use another option.

Summary: the best option for most Vero 4K users, but some TVs don’t behave the way they should. Not available on the Pi (but Kodi 19 Pi users can select “Normal” and get the same behaviour).

Option 3: "Stretch 16:9"

Behaviour on the Pi in Kodi v19

Under Kodi v19, this option (on the Pi) has become much more useful. It now exactly mirrors the behaviour of the “Use HDMI AVI Signalling” option on the Vero 4K (see previous sub-section) and produces optimal behaviour in nearly all situations.

Behaviour on the Vero 4K or on the Pi in Kodi v18

The name of this option is misleading: what it does on the Vero 4K (and on the Pi in Kodi v18) is scale all videos horizontally to fit the full width of the screen. If the output mode is 720x576, or 720x480, the effect is the same - the video always fills the full width of the screen. This applies to HD and SD videos.

With this option, the player does not send any signal to the TV to switch aspect ratio, and also doesn’t scale videos to get the aspect ratio correct.

This is a bad choice for HD videos with a 4:3 aspect ratio (e.g. 960x720 or 1440x1080) because these will be horizontally stretched. (You can fix that on a case-by-case basis by going into the OSD during playback, going into the Video Settings menu, and setting the View Mode to Stretch 4:3 for that specific video).

This can be a good option for Standard Definition videos: you’ll always see all of the available picture detail. But for SD videos you will need to change the aspect ratio between 4:3 and 16:9 using the TV’s controls.

Summary: Usually the best option for Pi users under Kodi v19. Under v18 or on the Vero 4K you need to set aspect ratio manually, and use different approaches for SD and HD videos; but if you’re willing to do that, image quality is always optimal.

The Best Choice

Vero 4K Users

On the Vero 4K, most users should choose “Use HDMI AVI Signalling”. So long as the equipment you’re connecting to responds the way it should, everything is optimised. But you may need a different option if the TV misbehaves.

Pi Users on Kodi v19

On the Pi under Kodi v19, most users should select “Stretch 16:9”, which now works the same way as “Use HDMI AVI Signalling” does on the Vero 4K.

Pi Users on Kodi v18

On the Pi under Kodi v18, “Stretch 16:9” will give you great picture quality for all videos, but only if you are willing to control the aspect ratio manually, and to do that in completely different ways for SD and HD videos. (Not “family friendly”!) Using “Normal” with 480p and 576p whitelisted works well for HD and for 16:9 SD, but 4:3 SD will look significantly worse because of downscaling. “Normal” with 480p and 576p not whitelisted may also be worth considering: this prevents Kodi from downscaling 4:3 SD, but it means all SD videos will be upscaled by Kodi instead of by the TV, which eliminates much of the benefit of using a whitelist.

7) When editing the whitelist, why are some of the modes listed twice?

This is a bug in Kodi. For now, just select both versions of each mode you want to whitelist.

8) Will Kodi let me whitelist resolutions that my TV doesn't actually support?

Normally Kodi pulls the list of supported modes from the TV or AVR, and only offers you those; so you shouldn’t be offered modes the TV can’t handle.

If you are being offered invalid modes, it could be that an AVR is not returning the correct EDID data from the TV; it could also be due to the presence of an incorrect .kodi/userdata/disp_cap file. On a Raspberry Pi, the presence of an incorrect override RPi config.txt with hdmi_edid_file=1 can also cause this.

9) Which resolutions should I whitelist?

You should usually whitelist every mode your TV supports, with the following exceptions:

  • Most users will want to de-whitelist all 25Hz, 29.97Hz and 30Hz modes. See section 19 for an explanation.

  • Some users may not want to whitelist 1280x720p/59.94 or 1280x720p/60 (see section 10 for more info). N.B. 1280x720p/50 should be whitelisted if it’s available.

  • Most users will want to whitelist 720x480p/59.94, but a few might not - see section 11 for more info.

  • Some Pi users on Kodi v18 may want to de-whitelist 480p and 576p - see section 6, under the “The Best Choice”.(On Kodi v19 you should whitelist them).

10) Why might I not want to whitelist 720p/60 and 720p/59.94?

720p/24 or 720p/23.98 videos are quite common, but 720p/24 and 720p/23.98 are HDMI modes that are not supported. (Even if the TV could support them, the Vero 4K and Pi can’t output those modes).

So, if a video is 720p/23.98, you have to choose between preserving the original refresh rate (by playing at 1080p/23.98) and preserving the original resolution (by playing at 720p/59.94).

Converting from 23.98Hz to 59.94Hz introduces 3:2 pulldown judder, and the majority of users will prefer to avoid judder, even if it means Kodi doing the upscaling. If you whitelist 720p/59.94 and the video is 720p/23.98 then Kodi will play the video at 720p/59.94. So it’s usually better not to whitelist this.

Of course, if you actually watch a lot of 720p/59.94 videos - and PVR users in America may well do that - and especially if you also don’t watch 720p/23.98 (or you do but you are not sensitive to 3:2 judder), then by all means do whitelist 720p/59.94.

Similarly, it is usually best not to whitelist 720p/60 - otherwise Kodi will use that mode to play 720p/24 videos. But if you actually watch a lot of 720p/60, then go ahead and whitelist it.

If 720p/50 is available, that should be whitelisted.

Kodi v19 users: there is a new option which may sometimes help - but it’s not always as useful as you might think. Under Settings>System>Display, in the Whitelist section, there is a new checkbox called “Allow 3:2 pulldown refresh rates”. If you uncheck that then you can safely whitelist 720p/59.94 and 720p/60, and Kodi will still output 720p/24 as 1080p/24. However, unchecking this also means that 480p/24 will be upscaled to 1080p/24 instead of being output as 480p/60, which may not be desirable.

11) Why might I not want to whitelist 480p/59.94?

For the same reasons as with 720p (see section 10), if you watch a lot of 480p/23.98 videos, and you never watch 480p/59.94, or 720p/59.94, you may want to de-whitelist 720x480p/59.94 as well as 1280x720p/59.94.

However, 480p/59.94 video is much more common than 720p/59.94 or 720p/60, and you can always manually switch the output to 1080p/23.98 during playback if you want to; so my standard recommendation is to whitelist 480p/59.94 and switch manually if needed.

12) If the whitelist is active, how does OSMC choose which resolution to switch to?

It checks for the following things, in this order.

  • First it looks for a whitelisted mode whose resolution and refresh rate are an exact match to the video resolution and frame-rate.

  • If it can’t find one, then it looks for a mode where the resolution matches the video, and the refresh rate is a multiple of the video frame-rate. For example, if the video is 1080p/25 but 1080p/25 is not a whitelisted mode, it will check to see if 1080p/50 is available. (Note that, annoyingly, a “multiple” includes a refresh rate that is 2.5x the video frame rate, so a refresh rate of 60Hz is an acceptable match to a frame rate of 24fps.)

Kodi v19 users: there are two new options which allow extra control. Under Settings>System>Display, in the Whitelist section, there is a new checkbox called “Allow 3:2 pulldown refresh rates” and another called “Allow double refresh rates”. The first, if unchecked, prevents Kodi from converting 24Hz to 60Hz (or 23.98 to 59.94); the second, if unchecked, prevents Kodi from converting 25Hz to 50Hz, or 30Hz to 60Hz.

  • If it still hasn’t found a match, it then looks for a higher resolution with the correct refresh rate. So, if the video is 1080p/25 and neither 1080p/25 nor 1080p/50 is available, it will check to see if 2160p/25 is an option.

  • Then it will look for a higher resolution mode whose refresh rate is a multiple of the video frame rate. (Again, 2.5x is acceptable, unless blocked under Kodi v19).

  • If that fails, it will use the Kodi desktop resolution, matching the refresh rate to the video frame rate if possible, or just using the default refresh rate if not.

(In Kodi v18, searching for a higher resolution with an appropriate refresh rate is a feature that is specific to OSMC - generic Kodi Leia doesn’t do this. But in Kodi v19 standard Kodi also does this.)

13) What if I don't like the mode Kodi switches to?

Either change the resolution manually from the OSD during playback (in the default OSMC skin it’s the icon on the far right of the OSD) or, if Kodi is consistently doing something you don’t like, consider de-whitelisting the resolution it keeps switching to.

14) Is there any type of video where whitelisting can cause problems?

See sections 10, 11 and 19 for some possible examples.

In Kodi v18 there is another type of video that can cause problems (although happily this has been fixed in Kodi v19): if the video resolution is Standard Definition or less, and it has a pixel ratio of 1:1 (i.e. the pixels are square, not rectangular) - for example, a video that is 720x540/25Hz, or 640x480/59.94Hz. If you try to play one of these in Kodi v18 with the output mode set to 480p or 576p, Kodi will probably mess up the aspect ratio; so you’re better off switching to a higher resolution for those.

However, videos like this are quite rare - and even even when you do come across files with those dimensions, they tend to have 24 or 23.98Hz frame rates. So, if you ever watch 720x480 or 720x576 videos (e.g. DVD remuxes) then it’s probably worth whitelisting 576p and 480p anyway and switching resolution by manually if needed.

And, as noted above, this issue is fixed in Kodi v19, so you don’t need to worry about it there.

15) If the video dimensions don't match any whitelisted mode, can you still stop Kodi from scaling?

You can, but you may not want to.

Let’s say you’re playing a video that is 960x540/24Hz. Kodi will play that at 1080p/24. In the OSD, in the Video Settings menu, you can change the View Mode to “Original Size” - the video will then be displayed without any scaling. But of course this means the video doesn’t fill the screen - it is displayed in a 960x540 window with a huge black border round it.

Also, subtitles look odd in this mode, as they will still be upscaled to full screen even though the video itself is not. (IMO this is a bug in Kodi, but no one seems to want to fix it). You can partly work around it by temporarily setting the subtitle position to “bottom of video” and reducing the font size.

Note that you shouldn’t do this with 720x480 videos that have a 4:3 aspect ratio. For some reason Kodi horizontally downscales those to 640x480!

16) Is there anything that can cause Kodi still to do some scaling even when the video is being output at native resolution?

Yes: using Kodi to correct for overscan (in the Video Calibration settings) will cause it do some scaling. If at all possible you should correct overscan using the TV controls instead. (The setting will have different names on different TVs - “1:1” and “Just Scan” are possibilities, but there are others). Leave both overscan settings at the default value - i.e. (0,0) - and leave the Pixel ratio setting set to 1.000.

17) Are there any situations where you CAN output a video at native resolution, but you shouldn't?

See sections 10 and 11 for some examples - matching refresh rate to the video frame rate may be more important than matching resolution.

Additionally, if a video is a 480p/59.94Hz DVD rip, and the material was originally shot on film (as opposed to captured on a TV camera in a studio), then outputting 1080p/23.98 or 2160p/23.98 may look quite good. (But it also may not).

18) Can you summarise the list of recommended settings?

The following is what I would suggest for most users. But I strongly recommend that you read sections 6, 10 and 11 (and Kodi v19 users should also check section 20); these sections go into detail about why these settings might not always be the best choices.

All users, regardless of whether they use a whitelist or not:

  • Make sure Settings level is set to “Expert” or you won’t be able to access all the settings you need.

Under Settings>System>Display:

  • Set “Resolution” to 1920x1080.
  • Set “Refresh Rate” to 60Hz. (This is a matter of personal preference, so if you want to set it to a different value - to avoid some mode changes, for example - then go ahead: either 59.94Hz or 50Hz will also work fine. But higher refresh rates make the system look and feel more responsive, so I definitely don’t recommend setting the refresh rate lower than 50.)
  • When Kodi switches output resolution or refresh rate, the screen will usually go black for a few seconds. Set “Delay after change of refresh rate” to however long it takes for the picture to come back up again.

Under Settings>Player>Videos:

  • Set “Adjust display refresh rate” to “On start/stop”.

  • Make sure “Sync playback to display” is NOT selected.

Vero 4K and 4K+ users who want to use a whitelist:

ALL OF THE STANDARD SETTINGS IN THE LIST ABOVE, plus:

Under Settings>Player>Videos:

  • Set “Display 4:3 videos as” to “Use HDMI AVI signalling”. (Right for most users, but see section 6).

Under Settings>System>Display:

  • Edit the whitelist. Enable every mode that your TV supports, except that you probably want to de-whitelist all 25Hz, 29.97Hz, and 30Hz modes - see section 19 for the reasons why - and many users will also want to de-whitelist 1280x720p/59.94Hz and 1280x720p/60Hz (see sections 10 and 11 for discussion - Kodi v19 users also see section 20). Remember to select “OK” to save your changes!

  • Kodi v19 users should consider checking “Allow 3:2 pulldown refresh rates” (see section 20), and definitely check “Allow double refresh rates”. (These settings don’t exist in Kodi 18).

Under Settings>System>Display>Video calibration…

  • The default values in here are fine. You can change Subtitle positioning if you want, but it’s important that you leave all the other settings set to the default (overscan settings to (0,0) and Pixel ratio adjustment to 1.000).

Raspberry Pi users who want to use a whitelist:

  • The same settings as for the Vero 4K except that if you are running Kodi v19 you should set “Display 4:3 videos as” to “Stretch 16:9”. Pi users running Kodi v18 should set this either to “Normal” or to “Stretch 16:9” - see section 6 to understand the trade-offs.
19) Why might I not want to whitelist 25Hz, 29.97Hz and 30Hz modes?

This is related to some bugs in Kodi and the way it handles deinterlacing.

If a video is 1080i/50 and flagged as progressive, i.e. it should be deinterlaced in film-mode (weaving) rather than video-mode (motion-adaptive), Kodi may select 1080p/25 as its output mode rather than 1080p/50. This would be optimal if the deinterlacing were done correctly; but unfortunately Kodi will deinterlace it wrongly (using video-mode rather than film-mode); and converting the result of doing that to 1080p/25 gives jerky playback.

If you de-whitelist 1080p/25, this forces 1080p/50 output, which fixes the jerkiness.

You may experience the same issue with 1080i/59.94 material - if it’s output as 1080p/29.97, the result is jerky.

20) What are the changes in Kodi v19?

For Pi users, much of what is discussed in section 19 ceases to be relevant, as the Pi 2 and 3 are currently not capable of playing 1080i material reliably under Kodi 19.

For all users, there are two additional settings under Settings>System>Display, in the Whitelist section. The first is “Allow 3:2 pulldown refresh rates”, and the second is “Allow double refresh rates”.

If you are using a whitelist, the second (“double”) setting will allow Kodi to output (say) 1080p/25 video as 1080p/50, or 1080p/29.97 as 1080p/59.94. The first (“pulldown”) setting allows 23.98fps video to be output as 59.94Hz, or 24fps as 60Hz.

Pretty much all users will want to check the “double” setting.

The “pulldown” setting is more complex. Leaving it unchecked allows you to whitelist 720p/59.94Hz and 720p/60Hz modes but still have 720p/24fps videos output as 1080p/24Hz. That’s probably a good thing. But it also means that 480p/24fps videos will be output as 1080p/24 instead of 480p/60, and that doesn’t look so good. Generally my recommendation is to check this box but de-whitelist 720p/59.94 and 720p/60 modes. However, if you watch a lot of native 720p/60 material (e.g. live TV in the U.S.) you’re better off whitelisting those modes; in that case you may want to uncheck the box, depending on whether you watch more 720p/24 or more 480p/24 material.

Finally, for Pi users, the “Stretch 16:9” option for “Settings / Player / Videos / Display 4:3 videos as” has become much more useful than it was in v18, and should be the default for nearly all Pi users - see section 6 for details. Also, the “Normal” option for that setting has changed its function - what it now does is a little unclear, but it’s definitely not helpful!

14 Likes
Kodi video settings for optimal quality (LG C9 OLED)
Unable to play smooth any kind of video
Vero4k Vero4k+ BURNT OUT
Resolution sticks to 4k
Video stops but audio carries on
Cannot get 3D MVC MKVs to play in 3D
Setting up 4K system for first time
Which resolutions whitelist?
Audio video settings questions - New user
[TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +
Stuttering / frame rate with older content
Resolution question
Setting the Display Resolution
No audio on Vero 4k+, fine on Rpi3B
[TESTING] Kodi v19 builds for Vero 4K / 4K +
Another stuttering thread
Vero 4K+ - Black screen when skipping video forward
Vero 4K+ v19 - Many Problems
1080i/50 playback (Vero 4K, August release)
Youtube audio stutter after upgrade to osmc 2021.08-1 running kodi 19.1
Best Vero Settings?
Confused over settings to play 4K videos
HLG UHD Rec 2020 playback
TV power and volume
VERO 4K+ crashes with 4K uncompressed movies
Vero 4k - keeps buffering, videos unwatchable :(
Issue with Vero4k and raw 4K MTS files?
Vero 4+ & Benq Projector: No 4k
Changing resolution
Vero 4K - Not working after March 20, 2020 build update
Video and sound cutting out after 30 to 45 secs
Not getting proper 25 fps playback
Vero 4+ doesnt wake up when connected to soundbar
Vero4K+, after idle, blank screen and no response (have to reboot via ssh or power cord)
Grey bars when watching video that doesn't match screen size when "use limited color range" setting is disabled
Vero 4k + Blank Screen & Doesn't Boot
Extern USB-Drive as Network Drive
Can't play .mkv from one day to the next
Playing MPEG 2 content plays at the wrong frame rate
Playing MPEG 2 content plays at the wrong frame rate
3D Frame Packed output
[TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +
Vero 4k+ wont play files after some time, rebooting fixes the issue
[BUG REPORT] Crash at same spot in the video
OSMC changing resolution by itself?
Pixel ratio (auto saved?)
OSMC changing resolution by itself?
Vero4k+ stop playing movies after a few seconds
KODI keep restarting when browsing my library
Is it unreliable or is it me?
Codec Supported by Vero4K
Bandwidth is really poor using wifi
Audio dropping/cutting out in movies via VERO4K/OSMC
Vero 4K+ Audio drop-outs
Best calibration/resolution/refresh rate settings?
Whats the best picture and sound settings for me?
Vero4k - after starting a file (movie or tvshow), it stops after a 1-2 seconds
Disable upscaling doesn't work
Vero 4k+ crashes seemingly randomly
2160@120Hz
DTS-HD MA doesn't work
Aspect ratio, lowres
Generally poor user experience; slow response, fickle remote(s), and network oddities
Vero4k+ only shows black screen for all 4k options
UI struggles at 1080 imageres in panelview
Problems with sound and pic after set up
Image Quality Issue
No voices on movies with AAC audio
Vero4k frequently hangs after longer idle periods
Disabling HDMI pass through
New user, observations and one more question
News feed is not displayed
Strange Resolution...3838x1920 won't play in 4K, 3840x1920 will
Vero 4K+ lightly stuttering without refresh rate adjustement
Vero 4k+ TVHeadEnd UK Freeview playback jerky
Some (or more precisely many) of my video files cannot play - resulting sad face
Use limited color range yes or no
UHD films now buffering
Loading Media Information From Files hangs at 0%
Any way to force resolution (fw_setenv) using the GUI
Force resolution change on certain files
Config for HDR?
Dark HDR Videos - Non HDR are perfect
AAC stream fade-in fade-out constantly
Vero 4k+ problem with fast forward and rewind
Osmc crashes everytime I am on 4k60
HDMI dropping (Vero4k)
New Vero 4k plus cannot sync audio and video for certain videos
Can’t Play 3D ISO
Vero 4K - no playback (overnight) - Audio problem, no ALSA sink?
Vero 4K + crashes more and more and doesn’t boot for some time
Audio stutter for 1 second every 27 seconds
Av receiver and vero 4k
Unable to play 2160p24 HEVC HDR10 File
Vero 4k update + TV Mosaic max 30fps
KODI crashes on latest osmc for raspi4
HD HEVC videos not playing on OSMC August 2021 update
Epson TW9300 and vero 4K
Display resolution
Display resolution
Live TV stuttering on 4k monitor
Stuttering audio playback after the last update
[TESTING] Kodi v19 builds for Vero 4K / 4K +

This is great work, thanks! Just a couple of remarks.

Yes there is: VIC 60. Probably rarely supported though.

Note under question 12, I think you have it right but OSMC uses a different scheme than standard Kodi, and Kodi v19 will be different again, allowing more fine-grained selection.

Wording changed.

You mean my four steps are correct, but I should change it to “How does OSMC decide…” rather than “How does Kodi decide…”?

It’s just bullet points 3 and 4. You might like to put at the end of bullet 4 ‘(this search for higher resolutions is unique to OSMC)’

Of course bullet 4 is not final - the final step is it gives up if it fails all the above and reverts to the desktop (GUI) resolution.

Also (picky) ‘exact multiple’ actually includes 2.5x the source framerate so 24fps can play at 60.

Very nice work indeed! :+1:t2:

As an idea: May be worth thinking about splitting this into single posts with a first post acting as a table of contents like I did with the audio wiki article: Audio hardware and software configuration The main advantage of this: We can always link to certain parts of the wiki article with said post structure. Might be useful to follow this structure with this article as well - not all users may want to read everything or it’s sufficient to just point them to one piece of information. :thinking:

That is currently beyond my editing abilities, but if you mods want to do it for me, knock yourselves out. :grin:

And I may add here: There can be severe disadvantages of doing this although using whitelisting.
A good example for this is my setup. Two reasons why:

  • The first being that my AVR doesn’t listen to the AVI signalling at all - all SD resolutions are handled as 4:3 and if the scaler is set to 16:9 (it can only either be set to 16:9 or 4:3 - don’t ask me why and how that makes any sense) it will then take the 4:3 content and stretch it to 16:9. I’ve even asked the Denon support and their reply was: all SD content is 4:3. Yeah, no. They only seem to look at resolution, nothing else. :rofl:
  • The second reason being how my TV handles 4:3 content. It listens to the AVI signalling properly, but it doesn’t offer any way of disabling overscan with its 4:3 mode, unfortunately.

As my AVR is a fairly recent Denon and my TV is a Panasonic plasma not that uncommon even today (not sure how newer Panas handle 4:3), it might be good to include warnings as to what the issues might be with properly signalled 4:3 SD output. With my setup it’s a better compromise IMHO to output 4:3 SD content pillarboxed (yes, it’s a loss of horizontal resolution) as neither my TV nor my AVR’s scaler can properly handle it the way you’d want them to.

That I could do once there’s time. Only issue: If I’d do this, I’d have to create a new thread with new posts thus loosing your authorship - but I’d surely mention that the original write-up was yours! :slightly_smiling_face:

I’ve redrafted that section a bit - see what you think.

1 Like

I’m not quite sure how to incorporate that. I mean, I can add a note to the effect that “if the equipment you’re connecting to is completely f*cked then this might not work properly” but that’s true of almost anything - it kind of goes without saying.

I suppose I could say a little more than I do about what the setting does, and what effect the other options have.

I agree. Just wanted to bring this up as it could lead to confusion when advocating this setting without more context. From what my equipment does with the signalling, I guess, lots of user equipment will handle this in funny ways. So, further explanation for the other settings might be just what’s needed here - that could include a remark about none of these settings being perfect in every scenario, depending on your setup (goes without saying, but some things can’t be said often enough) :slightly_smiling_face:

Explain how to test and if it fails then point them to the RPi recommend. Add a link to chillbo’s post alternatively?

So basically you want me to take the blame for everything in it but not have the power to edit it? :rofl:

No, if you want to do that, I’m fine with it. :slightly_smiling_face: I put this together as a result of a conversation with @darwindesign in which I was wondering why you guys don’t mention the whitelist and the “Use HDMI AVI Signalling” setting as standard. He said it was partly because there wasn’t actually much documentation about whitelisting, but that if someone were to write some it could maybe be linked to from the bottom of the standard info drop. So I thought I’d have a go at it.

But the purpose of this is to make people more aware of some features that may improve their viewing experience. If the best way for the information to be more widely disseminated is for me to relinquish authorial control, that’s not a problem.

1 Like

I promise I will give that some thought.

I don’t know if you are aware of what Kodi has been doing (slowly) with whitelists. IMHO they never wrote a specification for what they wanted to acheive either back when it started or when they decided it needed improving. I think they have a tendency to just think of kodi running on a PC with lots of grunt to handle a high-res display and a display with very few modes compared to a TV. I suspect whatever they do with v19 we will end up modding it.

Any chance you could mod the existing version a little more? :smiling_imp:

It has never made any sense to me that 720p/23.98 should default to 720p/59.94 instead of 1080p/23.98. And a case could be made for 480p/23.98 defaulting to 1080p/23.98 too, although that’s not quite so clearcut.

Either matching refresh-rate should take precedence over matching resolution (rather than vice versa) or 3:2 pulldown multiples of frame rates shouldn’t be regarded as matching the base frame rate at all.

Well maybe you should get stuck into the conversation at github if what they are proposing doesn’t do what you are after. I think they’ve got some kind of control over the ‘pull-up’ modes.

Then the wider Kodi community might benefit.

What consequences are there (if any) of setting this to 50 Hz? Most European/UK users would probably expect 50 Hz to be the correct setting …

None at all in my experience.

The GUI framerate should be a thing of user preference - while the resolution should typically be 1080p. :+1:t2:

I always avoid 50fps as most Panasonic plasma TVs are not perfect at playing 50fps content (50Hz bug). Whether you set 59.94fps or 60fps is really up to you, I’d say. Have switched to 59.94fps for a while now and it’s quite handy when playing US YT videos a lot - it avoids a framerate switch from GUI to video in these cases. I don’t watch 25fps or 50fps content a lot and setting the GUI to a 24p framerate is quite laggy, so a framerate switch for 24p is more or less unavoidable.

1 Like

The faster the GUI refresh rate is, the more responsive OSMC looks and feels. Slower refresh rates extend the time between when you push a button on the remote and when you actually see the screen update as a result.

The difference between 60Hz and 50Hz isn’t huge, of course, but it’s detectable.

EDIT: Added a note to section 17 saying this is a matter of personal preference.

1 Like