Kodi DSPlayer – DirectShow Player for Windows
(2015-10-16, 00:08)Warner306 Wrote:
(2015-10-15, 22:46)Doom10 Wrote:
(2015-10-15, 15:13)gotham_x Wrote: In general, the size and color of the graphics card how to set it? I have these default values in Display -> Change resolution.

Desktop 32-bit color depth =

Intensity of color 'output = 8 bpc - or (12 bpc)

Color format of 'output = RGB - or (YCbCr422 / YCbCr444)

Dynamic range of the output = Limited - or (Maximum)

http://www.avsforum.com/forum/139-displa...st37130802

I think it is a mistake to feed the TV Full Range RGB unless it has been tested to show those levels accurately. Many TVs have a PC mode, but not all show whiter-than-white and blacker-than-black correctly. Some only offer Full Range RGB for calibration purposes but are meant to display Limited 16-235. So I disagree strongly with that post.

Regardless, I use the first option. The tradeoff involves adding extra dithering to the image, but I can't see any difference with my eyes. Also, other computer applications maintain correct levels. I don't feel like I'm cheating myself at all. Further, my TV isn't forced to use its PC mode, where the original 16-235 source is being upscaled for display by the TV.

madshi, madvr developer:

Quote:My recommendation is always to set configure your display so that it expects PC levels (full range). This has 2 important benefits: (1) Levels will be correct for everything, including games, photos, applications and video playback. (2) There should be no problem with image quality.

If your display can't do PC levels, or if you have good reasons for not using this solution, then you have 2 alternative solutions:

(a) Either set the GPU to limited range and madVR to PC levels. This means madVR will render to PC levels and the GPU will afterwards stretch the madVR output (and desktop, games, applications, photos etc) to limited range. Using this approach still has the benefit of having correct levels everywhere. But image quality might suffer because the GPU usually uses a rather bad stretching algorithm, which can introduce banding artifacts.

(b) Or set the GPU to fullrange and madVR to TV levels. This will result in good image quality (no artifacts) and correct levels for video playback. However, desktop, games, applications and photos will have wrong levels

http://forum.doom9.org/showpost.php?p=16...ount=19433

nevcairiel, LAV filters developer:

Quote:madVR handles the input levels automatically, you don't need options or anything for them. You can override it on a per-file basis, but its only useful if madVR detects the wrong input level. The input level is defined by the file, not any setup in your display chain.

For the level settings, there is basically 3 combinations of settings:

(1) TV accepts PC/Full levels: Set madVR to PC/Full, set GPU to PC/Full - This is usually considered the better option, if your TV can do it.

(2) TV accepts only TV/Limited levels:
(a) Set GPU to PC/Full and set madVR to TV/Limited
(b) Set GPU to TV/Limited and set madVR to PC/Full
In the second case, both a and b have small drawbacks.
With (a), you get crushed black/white on the desktop, but everything is perfect in madVR.
With (b), you get proper colors everywhere, except that the GPU is doing the PC range -> TV range conversion, which may not be the highest quality and end up in banding.

NEVER set both madVR to TV/Limited AND GPU to TV/Limited, you get double range compression.

Because of these drawbacks with either a or b, its usually recommended to use (1) if your TV accepts it. Its only "downside" is that BTB/WTW are lost, but its arguable if those are even worth keeping. If you insist on WTW/BTB, the 2a setting is probably the next best for video quality, if you can live with crushed black/white on the Desktop.

However you set it up, the test patterns should only show 16-235 after calibration.

http://forum.doom9.org/showthread.php?p=...ost1678269
Reply


Messages In This Thread
Lockup on STOP issue resolved! - by MKANET - 2015-04-11, 21:59
RE: 4G aware patch - by MagikMark - 2015-09-08, 03:27
RE: Kodi DSPlayer – DirectShow Player for Windows - by Doom10 - 2015-10-16, 12:10
Alt-F4 no longer quits - by JeffA - 2015-10-31, 20:38
H265 playback - by rew88 - 2017-11-04, 00:41
RE: H265 playback - by ashlar - 2017-11-04, 16:21
RE: H265 playback - by rew88 - 2017-11-05, 01:34
RE: H265 playback - by ashlar - 2017-11-05, 16:48
RE: H265 playback - by rew88 - 2017-11-05, 23:08
RE: H265 playback - by ashlar - 2017-11-06, 12:00
Leia 18 - by terpsarlington - 2017-11-21, 03:51
RE: Leia 18 - by spencerjford - 2017-11-21, 06:24
Display Modes / Refresh Rates - by goofer69 - 2019-09-20, 00:19
RE: Display Modes / Refresh Rates - by ashlar - 2019-09-20, 00:39
RE: Display Modes / Refresh Rates - by ashlar - 2019-09-20, 19:35
DSPlayer 23.810 to 23.976 - by Runakanta - 2018-05-09, 03:24
RE: DSPlayer 23.810 to 23.976 - by Warner306 - 2018-05-10, 01:32
Logout Mark Read Team Forum Stats Members Help
Kodi DSPlayer – DirectShow Player for Windows47