FAQ: How to correct luminance levels

[clsid]

The registry hacks don't work anymore with recent versions of the ATi drivers :(

Also, Haali renderer can't be used in Media Center. At least not without setting the merits of the other renderers to Do_NOT_USE, which might break things.

[sarastro]

The registry hacks don't work anymore with recent versions of the ATi drivers :(


I realized that.

But even if I managed to use the Haali renderer, MPC-HC requires EVR or EVR Custom as renderer. So would DXVA even work with Media Center with Haali as a renderer?

If not, I'd rather use coreavc although corecodec still hasn't come up with a x64 edition.

[clsid]

Nope, DXVA won't work with Haali.

You could try ffdshow and select ffmpeg-mt as H.264 decoder. That has decent performance on multi-core CPUs.

[sarastro]

Nope, DXVA won't work with Haali.

You could try ffdshow and select ffmpeg-mt as H.264 decoder. That has decent performance on multi-core CPUs.

That was already my previous setup.It worked fine, but I just wanted to take advantage of DXVA with Media Center like i do with MPC-HC.
Why? 1080p with ffdshow makes my CPU fan spin harder (temps go up a lot), it doesn't with DXVA.

But thanks anyway:thanks:

[clsid]

You can always spam ATI support to request a luminance option similar to what NVIDIA has.

[THX-UltraII]

All my movies have perfect luminance but with SOME (not all!) trailers the black is totally greyed out. Anyone knows if this is a trailer problem or some last things I m missing and might need to change?

thanks!

[clsid]

Something is obviously different about those files than your other files. Perhaps a different decoder is being used?

[Delerue]

Something is obviously different about those files than your other files. Perhaps a different decoder is being used?

Not necessarily they use different codecs. For example, Nvidia Cascade Demo Video (http://us.download.nvidia.com/downloads/nZone/videos/nzm_Cascades_tech.wmv) uses the same codec as Nvidia GeForce 8800 Demo Reel (http://us.download.nvidia.com/downloads/videos/GF8800Demoreel_High_8000.wmv) and Nvidia Pure Video Demo (http://download.nvidia.com/downloads/nZone/videos/PureVideo_1080p.wmv), but the first one has correct luminance (i.e.: black is really black), and the second and third haven't. I think Nvidia encoded these videos with different luminance settings, which is really bad. :(

[mark0077]

Yeah alot of those nvidia demos show greyish blacks when I have played them in the past. They probably use full range 0-255 values so something like ffdshow's rgb conversion will let you watch them the way they should (by using its rgb conversion, with input set to 0-255 instead of the default 16-235). But I doubt there is a way to automatically detect what range of values its using. Isn't there a way for developers to have a flag in there to say what range of values is used for colors, rec 601 vs rec 709 etc. Software like video card drivers, ffdshow on auto, all seem to try to guess this, guessing the rec 601 / rec 709 based on the resolution.

[LoRd_MuldeR]

ForeWare 186.18 WHQL:
http://www.nvidia.com/object/winxp64_186.18_whql.html

First impression: Does remember "luminace range" across system reboot :D

[73ChargerFan]

But I doubt there is a way to automatically detect what range of values its using.

We 'assume' that properly encoded files are video range

As the video is displayed, check the range of R G B values
If r,g or b values are <16 or >235, change to full range

Black is going to be a very prevalent color, and it would appear in the first frame of every film, so those would adjust correctly. For videos, again we assume most will be video range, so on occasion you'll get what looks like a "auto-contrast" adjustment a second or two into playback.

I, too, would like to see the video range / gamut included as standard meta-data in video files. There is no reason to not add it matroska containers. Then if a compliant player determines the video is "full range" it can add the tag to the file for future reference, or to an internal list of file names.

[mark0077]

We 'assume' that properly encoded files are video range

As the video is displayed, check the range of R G B values
If r,g or b values are <16 or >235, change to full range

Black is going to be a very prevalent color, and it would appear in the first frame of every film, so those would adjust correctly. For videos, again we assume most will be video range, so on occasion you'll get what looks like a "auto-contrast" adjustment a second or two into playback.

I, too, would like to see the video range / gamut included as standard meta-data in video files. There is no reason to not add it matroska containers. Then if a compliant player determines the video is "full range" it can add the tag to the file for future reference, or to an internal list of file names.

Yea that sounds good. I think ffdshow or is it avisynth that has a method to detect <16 or >235, but havn't heard of alot using it. Encoding the files with some sort of flag should be the way to go though as you suggest. How would one / us all come up with a way of flagging videos that may become a standard that all players can look at.

[Shakey_Jake33]

ForeWare 186.18 WHQL:
http://www.nvidia.com/object/winxp64_186.18_whql.html

First impression: Does remember "luminace range" across system reboot :D

I've not tried the desktop drivers, but the notebook drivers have never had a problem with this.

[chros]

ForeWare 186.18 WHQL:
http://www.nvidia.com/object/winxp64_186.18_whql.html

First impression: Does remember "luminace range" across system reboot :D
On both head of the graphic card?
Can you try it?

Because of the previously linked beta driver only remembers on the primary head ... :(

Thanks

[LoRd_MuldeR]

On both head of the graphic card?
Can you try it?

Because of the previously linked beta driver only remembers on the primary head ... :(

Thanks

Head? :confused:

Well, I have two screens (VGA and DVI) and it remembers the setting for both of my screens. If that is what you asked for...

[Leak]

Head? :confused:
Well, "head" as in "dual-head graphics card", i.e. 2 output connectors for connecting 2 screens...

np: Jackie Leven & The Celtic Soulmen - Deep Choking Wooded Death Fix (The Haunted Year: Spring - Man Bleeds In Glasgow)

[LoRd_MuldeR]

Well, "head" as in "dual-head graphics card", i.e. 2 output connectors for connecting 2 screens...

That's what I assumed. Hence my answer :)

[chros]

ForeWare 186.18 WHQL:
http://www.nvidia.com/object/winxp64_186.18_whql.html

First impression: Does remember "luminace range" across system reboot :D
Well, I have tried the 32bit version, and it forgot them, again ... :(

[LoRd_MuldeR]

Well, I have tried the 32bit version, and it forgot them, again ... :(

Odd...

[THX-UltraII]

I would like to talk about something I posted in this thread a few months ago. I had some question about the black levels and enhanced/normal setting on my projector. I solved everything (with the help of you guys!) by changing the ATI CCC Pixel Format option to RGB:Full and putting my projector on ENHANCED. What I also did (on the advise of someone users here) was installing FFdshow and ONLY checked the 'RGB32' and 'HIGH QUALITY YV12 to RGB conversion' boxes in the 'Output' setting of ffdshow. In the upper 'Codecs' setting of ffdshow I only check 'Raw video' and set this to 'all supported'.

So I had to do a full HD format of my PC last night (had some other, non-related video, problems with my PC) and while installing everything it got my thinking about something:

Isn t my setup I used the last months (which seems ok by the way!) a 'double' setting and isn t it so that one of the two things I do (OR the ffdshow settings OR the ATI CCC pixel format setting) can be skipped? If so I would like to skip FFdshow HQ RGB because this eats some CPU.

So I tried playing some content last night WITHOUT ffdshow and with only the correct ATI CCC setting (also not use any shader or something like that in MPC-HC). Everything seems ok but I would like to know if I m correct in all things I ve put here.

IS it not needed to use FFdshow in my case and DOES it have no benefits (for my setup) at all to use it.

I ask this because I would like to have a HTPC as simple as possible and skipping ffdshow also saves CPU.

But maybe you guys have other suggestions to set it up different.


My hardware:
- Core2Quad Q6600
- 4GB internal mem
- Asus P5B-V motherboard
- Asus 4350 ati card with a native HDMI output going directly to my JVC HD100 projector (projector set to ENHANCED video)

And software:
- XP SP3 with .NET Framework 1.1, 2.0 and 3.0 installed
- MPC-HC latest version with EVR Custom as output
- Reclock
- CoreAVC 1.9.5 (only comes in when running .mkv files, not with my .wmv files)
- Haali Media Splitter
- ATI display driver and CCC 9.6
- march2009 release of DirectX 9


Thanks for all help and sorry for the clumsy English.

Cheers.

[fastplayer]

@THX-UltraII:
8) No cross posting. Post your message once, to the appropriate forum and nowhere else or it will be locked or deleted without warning.

How many times do we have to remind you about cross-posting (http://forum.doom9.org/showthread.php?t=148024)?

[THX-UltraII]

I will close the other topic.

[mark0077]

I would like to talk about something I posted in this thread a few months ago. I had some question about the black levels and enhanced/normal setting on my projector. I solved everything (with the help of you guys!) by changing the ATI CCC Pixel Format option to RGB:Full and putting my projector on ENHANCED. What I also did (on the advise of someone users here) was installing FFdshow and ONLY checked the 'RGB32' and 'HIGH QUALITY YV12 to RGB conversion' boxes in the 'Output' setting of ffdshow. In the upper 'Codecs' setting of ffdshow I only check 'Raw video' and set this to 'all supported'.

So I had to do a full HD format of my PC last night (had some other, non-related video, problems with my PC) and while installing everything it got my thinking about something:

Isn t my setup I used the last months (which seems ok by the way!) a 'double' setting and isn t it so that one of the two things I do (OR the ffdshow settings OR the ATI CCC pixel format setting) can be skipped? If so I would like to skip FFdshow HQ RGB because this eats some CPU.

So I tried playing some content last night WITHOUT ffdshow and with only the correct ATI CCC setting (also not use any shader or something like that in MPC-HC). Everything seems ok but I would like to know if I m correct in all things I ve put here.

IS it not needed to use FFdshow in my case and DOES it have no benefits (for my setup) at all to use it.

I ask this because I would like to have a HTPC as simple as possible and skipping ffdshow also saves CPU.

But maybe you guys have other suggestions to set it up different.


My hardware:
- Core2Quad Q6600
- 4GB internal mem
- Asus P5B-V motherboard
- Asus 4350 ati card with a native HDMI output going directly to my JVC HD100 projector (projector set to ENHANCED video)

And software:
- XP SP3 with .NET Framework 1.1, 2.0 and 3.0 installed
- MPC-HC latest version with EVR Custom as output
- Reclock
- CoreAVC 1.9.5 (only comes in when running .mkv files, not with my .wmv files)
- Haali Media Splitter
- ATI display driver and CCC 9.6
- march2009 release of DirectX 9


Thanks for all help and sorry for the clumsy English.

Cheers.

Well your right when you say that the ATI drivers might be doing exactly what ffdshow does when its in the chain, ie detecting the width / height of the video, and based on that deciding whether it is Rec 601 or Rec 709.

You will have to decide a few things when choosing whether you want ffdshow or your gfx card to do the conversion to RGB. Here are my feelings.

ATI / NVidia: I have mostly got experience with nvidia lately, and have found many colorspaces that it does an absolutely terrible job at converting to RGB. This is obviously ati / nvidia dependent, and I have seen different driver versions fix / break this conversion. For this reason, I never ever want to trust the drivers. I prefer to trust the ffdshow developers.

Also recently, ffdshow has introduced high quality dithering, and internally represents values in 10-12 bits. I am not sure if ATI or NVidia do dithering, but I don't think either does higher than 10 bits. MadVR is now doing 16bits and in comparisons even this is producing higher quality conversion than ATI / Nvidia / FFdshow.

I choose to use ffdshow, with ditering on, and high quality RGB32 checked.

The only real disadvantage is, that you can't use hardward de-interlacing if you output rgb from ffdshow, but thats a price I am willing to pay to have consistent output from all colorspaces.

[THX-UltraII]

Well your right when you say that the ATI drivers might be doing exactly what ffdshow does when its in the chain, ie detecting the width / height of the video, and based on that deciding whether it is Rec 601 or Rec 709.

You will have to decide a few things when choosing whether you want ffdshow or your gfx card to do the conversion to RGB. Here are my feelings.

ATI / NVidia: I have mostly got experience with nvidia lately, and have found many colorspaces that it does an absolutely terrible job at converting to RGB. This is obviously ati / nvidia dependent, and I have seen different driver versions fix / break this conversion. For this reason, I never ever want to trust the drivers. I prefer to trust the ffdshow developers.

Also recently, ffdshow has introduced high quality dithering, and internally represents values in 10-12 bits. I am not sure if ATI or NVidia do dithering, but I don't think either does higher than 10 bits. MadVR is now doing 16bits and in comparisons even this is producing higher quality conversion than ATI / Nvidia / FFdshow.

I choose to use ffdshow, with ditering on, and high quality RGB32 checked.

The only real disadvantage is, that you can't use hardward de-interlacing if you output rgb from ffdshow, but thats a price I am willing to pay to have consistent output from all colorspaces.

Thanks for your reply Mark.

So if I want to be sure that it is done right, it is best to keep using ffdshow. At least, that gives me the best trust in it.

But when using ffdshow, isn t a 'double' process done in this case? I mean, when I use FFdshow and change the ATI Pixel Shader to eg. 4:4:4 limited the colors get washed out so this means that ATI is still doing SOMETHING with the signal. So that s why I thought FFdshow could only do more harm because of the 'double' effect. (Also the beginning of this topics tells that there are more ways to do it and it is not mentioned what 2 methods at the same time do).

[mark0077]

No, the graphics card doesn't do any fiddling with the "signal" when you give it RGB (which is what it gets if you force ffdshow to output rgb). If ffdshow converts to RGB, the graphics drivers say... oh rgb, and send straight to screen. If its like yv12 or whatever, then graphics card does its own conversion. So no you shouldn't get a double conversion in this situation.

[THX-UltraII]

No, the graphics card doesn't do any fiddling with the "signal" when you give it RGB (which is what it gets if you force ffdshow to output rgb). If ffdshow converts to RGB, the graphics drivers say... oh rgb, and send straight to screen. If its like yv12 or whatever, then graphics card does its own conversion. So no you shouldn't get a double conversion in this situation.


thxz! You talked about 'high quality dithering' with ffdshow. Can you tell me what this is (compared to what I do now) and how to config this properly?

thxz!

[THX-UltraII]

here is a reply on the avs forum by the way. Totally different opinion. The guy who says it (Jong) is also supposed to be a HTPC guru:

http://www.avsforum.com/avs-vb/showthread.php?t=1126479

[mark0077]

here is a reply on the avs forum by the way. Totally different opinion. The guy who says it (Jong) is also supposed to be a HTPC guru:

http://www.avsforum.com/avs-vb/showthread.php?t=1126479

Everyone has the right to their own opinion, but if ffdshow is doing slightly higher bit depth conversion internally, it will give better results than ati or nvidia who i believe (not sure) use 10-bit.

Check out the madvr thread for screenshots comparing madvr, vs ffdshow vs drivers. The dithering brings this 10-12 bit representation down to 8-bit (your displays bit depth for each color) in a nicer way than just chopping off the 2-4 bits. My experience has told me to never rely on graphics cards / drivers anyways and madVR is too buggy for me to use.

[clsid]

Does anyone have more details on this: "ATI CCC Pixel Format option RGB:Full"? Is that a new option that was added, similar to the option NVIDIA has?

[THX-UltraII]

Does anyone have more details on this: "ATI CCC Pixel Format option RGB:Full"? Is that a new option that was added, similar to the option NVIDIA has?


It s been there far some time now. It seems to work but tonight I m going to try the FFdshow dither option to see how the quality is.

[THX-UltraII]

Does anyone have more details on this: "ATI CCC Pixel Format option RGB:Full"? Is that a new option that was added, similar to the option NVIDIA has?


And can you tell me how to config it correctly?

Is this the best FFdshow version to use for it? http://sourceforge.net/project/showfiles.php?group_id=173941&package_id=214245

And what about the setup?

Picture 1:
Is it correct that I only need to check RGB32 and high quality YV12 to RGB conversion?
And what about the setting
- set closest matching colorspace
- set pixel aspect ratio in output media type
- set interlace flag in output media type
Leave them all on standard like it is in the picture or change somethings here?

http://img230.imageshack.us/img230/5316/ffdshow1.jpg (http://img230.imageshack.us/i/ffdshow1.jpg/)

Picture 2:
- YCbCr: Auto, BT.601 or BT.709?
- Can I choose Progressive at method for the best result(because I only watch full-hd content and standard def. dvds)?
- input levels and output levels, leave it that way?

http://img141.imageshack.us/img141/4851/ffdshow2.jpg (http://img141.imageshack.us/i/ffdshow2.jpg/)

thanks

[clsid]

Leave everything at defaults and just enable the RGB and high quality options.

[mark0077]

Does anyone have more details on this: "ATI CCC Pixel Format option RGB:Full"? Is that a new option that was added, similar to the option NVIDIA has?

The nvidia option only controls the output of video, not the entire desktop. In my case, the nvidia drivers incorrectly detect my TV as limited range TV, and when I then use the option (0-255 for video output), it all becomes a mess.

NVidia need something like ATI's option, something that controls the entire desktop and video content, not just video content. In my case I need to do an EDID override to get the nvidia drivers to send the entire desktop in full range, then its own 0-255 setting does a fairly good job of outputting video at the correct levels.

So as far as I believe, ATI's option controls the entire desktop = :D

[LoRd_MuldeR]

So as far as I believe, ATI's option controls the entire desktop = :D

What options? The last time I used CCC (back at the time I still had an ATI card), there was no such option :confused:

[tetsuo55]

Does anyone have more details on this: "ATI CCC Pixel Format option RGB:Full"? Is that a new option that was added, similar to the option NVIDIA has?

It's basically the same output you get when connecting a pc monitor over DVI

4:4:4 0-255, expansion is still a seperate option.

The good news is that ATI users can have an almost perfect set-up (assuming the dvi-hdmi dongle)

-ATI driver set to RGB:FULL
-Renderer (or sooner YUY to RGB conversion setting) should expand video content to 0-255 (unless the content already is 0-255)

Preferably the expanding part has a dynamic gamma that deals with blacker than black and whiter than white (i don't believe any of them do)

[tetsuo55]

clsid, maybe you could update the first post with some more technical information.

although it might confuse things a little more:

Actually all displays use 0-255 (electrically), the only difference is the exact point of "reference black" and "reference white"

PC > Reference black is on 0, reference white is at 255 (RGB)
Video > Reference black is on 16 for YCrCb and reference white is at Y 16-235 and CrCb 16-240

Now video can actually put data in 0-15 and 236-255 (some numbers are reserved and cannot be used). This extra data is used on analoge displays to intensify or darken parts of the screen, when the image is too dark or too bright.

Things like a bright flashlight in an extremely dark scene.

To simulate this effect, these values have to be taken into account by the YCrCb to RGB converter, probably most accurately by bending the Gamma curve, realtime, only when these extra values are availabe.

RGB for several reasons does not show this behaviour.

[Leak]

What options? The last time I used CCC (back at the time I still had an ATI card), there was no such option :confused:
I don't have it either, but that's because it's only available for displays connected via HDMI...

Here (http://img7.imageshack.us/img7/2720/pixelcolor.jpg) is a screenshot I found via Google image search...

np: Baxendale - I Built This City (Michael Mayer Mix) (Kompakt Total 6 (Disc 1))

[honai]

No, the graphics card doesn't do any fiddling with the "signal" when you give it RGB (which is what it gets if you force ffdshow to output rgb). If ffdshow converts to RGB, the graphics drivers say... oh rgb, and send straight to screen. If its like yv12 or whatever, then graphics card does its own conversion. So no you shouldn't get a double conversion in this situation.

Not true. When you choose anything like VMR or EVR as output renderer then indeed the GPU driver will apply all sort of "tweaks" to the image to "improve" quality. This cannot be prevented for those renderers, even with RGB output.

The only way to evade this is by using a custom renderer like HR (which has its own problems, btw) or madVR (perfect but development has stalled for a while).

[mark0077]

Not true. When you choose anything like VMR or EVR as output renderer then indeed the GPU driver will apply all sort of "tweaks" to the image to "improve" quality. This cannot be prevented for those renderers, even with RGB output.

The only way to evade this is by using a custom renderer like HR (which has its own problems, btw) or madVR (perfect but development has stalled for a while).

Well with the nvidia drivers at least, by default there is none of these "tweaks". Any of the hqv test results will show this. And I am referring to luminance anyways, and I can say when being fed RGB, the nvidia drivers don't touch luminance. Unfortunately after months of madVR development, it cant even play a DVD from my hard drive without giving macrovision errors.... for me at least, the only way to go is EVR-CP, and feed the drivers RGB from ffdshow.

[honai]

Any of the hqv test results will show this.

Well, no. The HQV tests don't actually measure if the rendered output is faithful to the source.

[diman1982]

I was very much confused with all this levels stuff for a long time. Honestly, converted levels test clip from this thread(TV_LEVELS_TEST_CLIPS.zip) confused me even more.
But then i found a great calibrating thread http://www.avsforum.com/avs-vb/showthread.php?t=948496
I downloaded test patterns(mp4 variant), started tweaking my nvidia 9500 output and adjusting my lcd tv and everything became clear for me.

[Polcius]

I don't fully understand the levels stuff.

I have a PC running Win7, hooked up to a Samsung HDTV via VGA (Nvidia 9500GT graphics card). Mainly, I use it to watch DVD's and some TV shows in .mkv.

In the TV, I can't select between "Auto" or "Native" colour spaces because they are greyed out.

In MPC-HC, in renderer settings, I can select to output 0-255 or 16-235. But in the Nvidia Control panel I ALSO can select between 0-255 or 16-235.

My question is wich way should I set it up, because the levels can be changed in many settings.

Thanks, and sorry for my English...

PD: Nvidia settings off.

In MPC HC. "View-> Renderer Settings-> Output Range". I'm using EVR Custom.

With 0-255, I see 2 bars.

With 16-235, I see 3 bars.

My problem is that when using 0-255 (blacks/whites) clipped, the colors look good & vivid, but the whites seem to "pop out" a lot. And when using 16-235, the white/black level is fine, but the colors seem washed out.

PD: I posted this to the MPC HC thread, but someone said I should post it in here.

[XadoX]

At the moment I am also trying to get real black bars on DVDs in Vista Media Center. Changing the Dynamic from 16-235 to 0-255 aso did not work (Nvidia 8600GT).

So I had to change the contrast and brightness also?

At the moment I am realy confused :confused:

[juGGaKNot]

off the bat when i do not use PC.601 in avs the color is washed out

if i add it all is k

if i set fullrange in the gfx card the black is too black

kmplayer and mpc-hc

[Polcius]

I want to use ffdshow as mark077 but I don't know if I'm doing it right.

First I set all the "output" settings (rgb32, high quality conversion...). Then I disable all the codecs on ffdshow, and set RAW Video to "all supported".

Now there's a step I don't know. I'm supposed to do something in MPC HC about "External filters", but I dunno.

[THX-UltraII]

guys, im back with some new questions involving output ranges etc.:

I had some changes in my config and don t know what to do now anymore for getting the right output ranges/luminance levels.

Here is my config:

1. Windows7

2. ATI HD4350 with the first question:
I can choose 4 options here. Is the last one still the best to pick nowdays?:
- ycbcr 4:4:4 pixel format
- ycbcr 4:2:2 pixel format
- rgb 4:4:4 pixel format studio (limited rgb)
- rbg 4:4:4 pixel format pc standard (full rgb)

3. Next the is a setting in MPC-HC which I didnt notice until yesterday:
when you right-click in mpc-hc and choose renderer settings you can select 2 different output ranges: 0-255 and 16-235. Which one do I need?

4. Coreavc:
I have 3 options @input levels and 3 @output levels:
- tv (16-235)
- pc (0-255)
- auto detect
Should I pick auto detect @ both in and output?

5. My JVC RS2 projector setting: leave it on enhanced?

For the info (and I think this was important): I use EVR Custom for output in MPC-HC

Thanks for all input

cheers

[Mercury_22]

Just my two C
You have to set all the components of your chain TV/Monitor/Projector, Graphics Card and player to use the same range
Since RGB (http://en.wikipedia.org/wiki/RGB) data has a range of 0-255 and YCbCr (http://en.wikipedia.org/wiki/Ycbcr) data has a range of 16-235 everything can be reduced to what you can use: RGB or YCbCr
So if you use VGA (http://en.wikipedia.org/wiki/VGA_connector) connection set everything to RGB = 0-255 but for DVI (http://en.wikipedia.org/wiki/Digital_Visual_Interface), HDMI (http://en.wikipedia.org/wiki/High-Definition_Multimedia_Interface), S-Video (http://en.wikipedia.org/wiki/S-Video), Composite video (http://en.wikipedia.org/wiki/Composite_video), Component video (http://en.wikipedia.org/wiki/Component_video), ... you should check what your TV, Monitor or Projector it's using RGB or YCbCr since most of the modern Graphics card can output both when you are using this types of connection.

So, again, if you use RGB set everything to 0-255 if you use YCbCr (http://en.wikipedia.org/wiki/Ycbcr) set everything to 16-235 !

P.S. A good place to start if you don't use VGA connection is in your Graphics card Pixel Format settings

[73ChargerFan]

4. Coreavc:
I have 3 options @input levels and 3 @output levels:
- tv (16-235)
- pc (0-255)
- auto detect
Should I pick auto detect @ both in and output?

I think input auto detect, since sources could be either.
Output pc levels.

[ears1991]

Hey guys this has been driving me nuts for ages
running win 7 x64 with an ati 4850

Ok so WMC always displays blacks as greys etc. but that is easily fixed using the NominalRange reg tweak

However, in powerdvd9 ultra, dvds display correctly but blu rays have the problem wmc did have with the blacks being shown as grey

If anyone could tell me how to fix this i would be soooo grateful!

I tried the bt601csc tweak but it didnt seem to do anything, i am using ati driver 9.9 (latest)
Havnt installed catalyst control center but when i have done it didnt seem to make any difference.

Any help would be greatly appreciated!

[mark0077]

You could try media player classic. If it doesn't give you black blacks you can use the well talked about ffdshow rgb32 conversion in tandem with mpc hc and your sorted.