Reply to thread

Message: <blockquote data-quote="Scythe42" data-source="post: 876440" data-attributes="member: 95833">If you use a regular monitor it should be RGB/0-255. Only TVs might require YCbCr and/or 16-235. And this is general for the TV when it can't handle RGB/0-255 correctly. It is just what your display's video processor can handle. If it is only with some codecs and the rest is fine, you do adjustments inside the codec. The RGB32 conversion in ffdshow just makes sure that the full RGB range is send to the renderer and nothing gets lost during what the GPU renderer does. This is just a precaution, so that nothing gets cut of before the picture is send to the renderer. The NV12 in/output you usually get from MediaPortal is fine for the renderer, too. I just like to be sure I always send the same stuff to the GPU to avoid any potential issues with some codecs. Especially on my development machine where I do experiments now and then. With RGB32 I provide the full color range of a video to the video renderer. Nothing will be cut of, nothing will be added. The rest is up to the GPU. But as said NV12 is fine, too. Not going into explaining the differences of the color formats here. So consider the to RGB32 setting an optional step. It doesn't change the colors, only the format. And from experience all GPUs I ever came across like RGB32 the most. But as said, consider this setting optional to avoid issues. The GPU driver decides after the renderer has rendered the picture based on the display settings if it should send the colors in RGB or YCbCr format and/or limit the color output if necessary. This happens AFTER the renderer and just defined the capabilities of the display itself. It is just what your display can handle. First: Color Format. And if you still have issues adjust the Color Range. You would have the same problems with games, desktop apps and other stuff with washed out colors or crushed blacks. It is just what your display likes. Has nothing do to with MediaPortal. If the settings are wrong they are wrong for everything! But most people only notice it during videos and not applications or games because they know how the colors look on their DVD player. And they often try to fix stuff in games with some gamma correction. If you ever needed to touch some brightness/constrast/gamma stuff for games, you have a general problem that display is not properly configured or the setup of the display is completely screwed. It should never be necessary unless for CRTs or a display that is miles way from the correct color representation (some people actually set their computer monitors to unbelievable crap...) To sum it up again:<ul> <li data-xf-list-type="ul">Computer Monitor are designed for RGB/0-255</li> <li data-xf-list-type="ul">TV are designed for YCbCr/16-235. Where some do 0-255 to 16-235 automatically when needed. You need to check if 16-235 is necessary for your display.</li> <li data-xf-list-type="ul">If you have a problem only in video playback check the codec settings in regards to color output</li> <li data-xf-list-type="ul">Some TV can handle RGB/0-255 correctly</li> <li data-xf-list-type="ul">Some Receivers do all the stuff when connected over HDMI as they see the color format/range and what every component likes most and convert it on the fly.</li> </ul>You can blame Nvidia and ATI here. There drivers don't really talk over HDMI to the display or they would know what the display really likes to display correct colors! But they don't. Same problem with 23,976Hz. No GPU I every came across does this 100% stable and exact. Not a biggie though. In the end it all depends on your display. You need to try it out. It just take a few seconds to see it on the desktop with the default win wallpaper right away.<ol> <li data-xf-list-type="ol">Try to use YCbCr output instead of RGB if you have washed out colors</li> <li data-xf-list-type="ol">If you still have problems (washed out colors or crushed blacks) change the color range from 0-255 to 16-235</li> <li data-xf-list-type="ol">If this doesn't help try the RGB/16-235 combination as a last resort.</li> <li data-xf-list-type="ol">If it is only in video playback or some videos > use codec setting to adjust colors</li> </ol>And as said this is depended on your display, unless something else is screwed up on the computer in general that effects stuff. It might also be possible that your display has different kind of inputs to automatically correct color formats and range. Check if you can switch with them as well. Again depends on the software on the TV. But usually doing this on the HTPC is easier and quicker. Games, Desktop, Web Browsing will suffer from the same color problems as Media Portal. Either your display can handle RGB/0-255 input right or it can't. There is no "only in this application" (unless the application screws with the color range on its own - but never saw that). Your display's video processor doesn't change magically because you are running a different kind of software. Some Media Players might be the exception to the rule as they might override GPU settings. Especially if they use an own renderer. But MP does this not as it doesn't have any kind of post processing at the moment built-in. And it relies on your codec installation and settings. No special/hidden configs here. You once setup your display right - you are done. Afterwards make sure the codecs don't play around with it again. And you will have the correct colors for you display everywhere. If this is not the case it is something other in your setup. The thing "bar goes through character" sounds like a de-interlacing artifact. I know this from the first seasons of my South Park DVDs. A line is present in one of the interlaced frame but not the other. Happens for me when I let the GPU do deinterlacing/scaling (meaning no postprocessing) on my box. But I need the video stream and the direct show graph to reproduce it and tell you what it is.</blockquote>

Verification