home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
My guide to elminating juddering/stuttering play back (plus an upscale guide!)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Scythe42" data-source="post: 876240" data-attributes="member: 95833"><p>The Eye One is very good for calibrating displays. I can highly recommend it.</p><p> </p><p>You can't use hardware de-interlacing and then apply ffdshow filter afterwards.</p><p> </p><p>Before doing scaling and other stuff the picture has to be de-intetrlaced. So either the codec you use does it, meaning it uses the GPU for it, or if the codec can't do it then ffdshow has do to it by software, so it can apply its post-processing properly.</p><p> </p><p>Using hardware deinterlacing only means: do not touch the video at all, mark it at interlaced and send it this way to the video renderer. The renderer then usually let the GPU do it. With this method, you can't use ffdshow postprocessing. ffdshow passes the postprocessed video to the video renderer! If you post-process interlaced frames without deinterlacing first the result will be bad.</p><p> </p><p>It's in the profiles as a pre-caution, so that the picture doesn't get ruined incase a codec doesn't do GPU based de-interlacing. If frames are already marked as progressive then the ffdshow Deinterlacing does nothing.</p><p> </p><p>Various options only show up in GPU drivers based on the connection type or only have effect on some connections. So it can be different based on how your display is connected what is available and what not.</p><p> </p><p>The Color Fromat Setting is a general setting. It is either right for your TV or not. You will see a difference right away on the Desktop. Colors should be more "vibrant" instantly.</p><p> </p><p>When you send the color information in RGB and you TV's video processor doesn't handle it correctly, everything will be washed out (black becomes a bit more grey). So either RGB or YcBrCr is right for your display to stop it from tampering with the color range on its own.</p><p> </p><p>It is just HOW the GPU sends the color information to the display. It doesn't alter the colors! So no danger here for games or other stuff. Just try what is right for your display. Usually with YCbCr the display's video processor doesn't try to change the color range on its own or do other post processing stuff. No difference between the settings: stay with the default.</p><p> </p><p>The Dynamic Color Range need to be adjusted in the same manner. If your display doesn't like the full RGB range you will either see washed out picture or crushed blacks. But always try to set the Color Format from RGB to YcBrCr first as this solves most issues. Afterwards give the color range a try, too. But only if the picture is still washed out or if you have crushed blacks. No difference? Stay with the default. The color range can be application specific. So if you need to use 16-235 for videos it is a good idea to put it into a profile.</p><p> </p><p>Usually YCbCr and 0-255 is the correct combination for telling mist TVs: "Leave my colors alone, dude!.</p><p> </p><p>For my Samsung and my onboard Nvidia I need to do the following:</p><p>- Color Format: YCbCr or I have a washed out pictures, meaning blacks are not black and whites are too white.</p><p>- Color Range for Media Portal: 16-235 or I have crushed blacks (meaning black is too black) on MPEG2 streams (codec thingy...)</p></blockquote><p></p>
[QUOTE="Scythe42, post: 876240, member: 95833"] The Eye One is very good for calibrating displays. I can highly recommend it. You can't use hardware de-interlacing and then apply ffdshow filter afterwards. Before doing scaling and other stuff the picture has to be de-intetrlaced. So either the codec you use does it, meaning it uses the GPU for it, or if the codec can't do it then ffdshow has do to it by software, so it can apply its post-processing properly. Using hardware deinterlacing only means: do not touch the video at all, mark it at interlaced and send it this way to the video renderer. The renderer then usually let the GPU do it. With this method, you can't use ffdshow postprocessing. ffdshow passes the postprocessed video to the video renderer! If you post-process interlaced frames without deinterlacing first the result will be bad. It's in the profiles as a pre-caution, so that the picture doesn't get ruined incase a codec doesn't do GPU based de-interlacing. If frames are already marked as progressive then the ffdshow Deinterlacing does nothing. Various options only show up in GPU drivers based on the connection type or only have effect on some connections. So it can be different based on how your display is connected what is available and what not. The Color Fromat Setting is a general setting. It is either right for your TV or not. You will see a difference right away on the Desktop. Colors should be more "vibrant" instantly. When you send the color information in RGB and you TV's video processor doesn't handle it correctly, everything will be washed out (black becomes a bit more grey). So either RGB or YcBrCr is right for your display to stop it from tampering with the color range on its own. It is just HOW the GPU sends the color information to the display. It doesn't alter the colors! So no danger here for games or other stuff. Just try what is right for your display. Usually with YCbCr the display's video processor doesn't try to change the color range on its own or do other post processing stuff. No difference between the settings: stay with the default. The Dynamic Color Range need to be adjusted in the same manner. If your display doesn't like the full RGB range you will either see washed out picture or crushed blacks. But always try to set the Color Format from RGB to YcBrCr first as this solves most issues. Afterwards give the color range a try, too. But only if the picture is still washed out or if you have crushed blacks. No difference? Stay with the default. The color range can be application specific. So if you need to use 16-235 for videos it is a good idea to put it into a profile. Usually YCbCr and 0-255 is the correct combination for telling mist TVs: "Leave my colors alone, dude!. For my Samsung and my onboard Nvidia I need to do the following: - Color Format: YCbCr or I have a washed out pictures, meaning blacks are not black and whites are too white. - Color Range for Media Portal: 16-235 or I have crushed blacks (meaning black is too black) on MPEG2 streams (codec thingy...) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
My guide to elminating juddering/stuttering play back (plus an upscale guide!)
Contact us
RSS
Top
Bottom