PDA

View Full Version : VMRCCCSStatus trick for NV cards not working?


rahzel
11th August 2008, 03:46
i have a NV 7800GT and i was using older 169.xx drivers, and the VMRCCCSStatus trick worked. i updated to the newest 175.xx drivers, followed the instructions (created DWORD entry in 0000 for primary video device) but when i tried to make the value 0x3, it won't let me type an x in the value. i doubt this has anything to do with the driver, but i'm completely confused as to why its not working now but it did before.

on a somewhat related note, when i did get this trick working and was using VMR9 renderless mode in media player classic HC, when i took a screenshot of it running in VMR9 and System Default mode, it looked exactly the same. maybe because the video i was comparing was 1080p but my TV is 720p native (1366x768)?

Mangix
11th August 2008, 06:37
update to the newest 177.79 drivers. they let you configure the color range from the control panel. no registry tricks anymore!

rahzel
11th August 2008, 07:48
unfortunately for me, that driver doesn't seem to support the 7 series (which is BS). its not like the 7 series are ancient cards.

but thanks, that gives me hope that NV is on it and it will be in the next official release.

Leak
11th August 2008, 17:23
when i tried to make the value 0x3, it won't let me type an x in the value. i doubt this has anything to do with the driver, but i'm completely confused as to why its not working now but it did before.
FYI: "0x3" means 3 in base 16 (i.e. hexadecimal).

Just select "Hexadecimal" as base and enter just "3".

np: Proem - Live @ Amoda Austin 03-12-2002 (Merck Fragments)

Mangix
11th August 2008, 20:38
unfortunately for me, that driver doesn't seem to support the 7 series (which is BS). its not like the 7 series are ancient cards.

but thanks, that gives me hope that NV is on it and it will be in the next official release.

you could modify the inf file to get it to support the 7 series. don't ask me how to do that as i've never done it.

rahzel
11th August 2008, 20:45
FYI: "0x3" means 3 in base 16 (i.e. hexadecimal).

Just select "Hexadecimal" as base and enter just "3".

np: Proem - Live @ Amoda Austin 03-12-2002 (Merck Fragments)
ahhh... maybe last time, i thought i hit x, but i just typed "03" essentially making it a 3. its on hex. by default.

as for the driver, yeah i might do that sometime. thanks.

pitch.fr
11th August 2008, 21:25
this trick hasn't worked for a long long time.

I wish there was a way to output 16-235 in windows, but I think there isn't.

besides I got an ATI now :D

Kado
12th August 2008, 02:54
No tricks needed in 177.79 drivers, you just need to change the settings.
http://pwp.netcabo.pt/kado/dr.jpg

pitch.fr
12th August 2008, 09:45
yes but it's only for video, not the windows desktop.

"full range" w/o levels conversion in ffdshow gives the exact same result.

Kado
12th August 2008, 11:34
If you use MPC HC DXVA for h264, ffdshow is not an option although before we could use a shader to make the conversion.

rahzel
13th August 2008, 05:34
on this PC, i only have a 7800GT which does not support dxva. i have CoreAVC installed, so if i use ffdshow or MPC HC built in filter, won't it override CoreAVC? on my HTPC, i have a Gigabyte 780G (HD 3200) which does support it, so i will definitely be using MPC HC H264 (dxva).
i'm not going to bother modifying the inf... i'm in no hurry. i'm sure Nvidia will add this in their next release.

am i right in assuming ATI doesn't have this issue? i'm hoping i won't run into this problem once i get my motherboard back from RMA.

ranpha
13th August 2008, 08:08
on this PC, i only have a 7800GT which does not support dxva. i have CoreAVC installed, so if i use ffdshow or MPC HC built in filter, won't it override CoreAVC? on my HTPC, i have a Gigabyte 780G (HD 3200) which does support it, so i will definitely be using MPC HC H264 (dxva).
i'm not going to bother modifying the inf... i'm in no hurry. i'm sure Nvidia will add this in their next release.

am i right in assuming ATI doesn't have this issue? i'm hoping i won't run into this problem once i get my motherboard back from RMA.

If you turn on the ffmpeg DXVA filter in Internal Filter section, CoreAVC/ffdshow will not be used, unless you set them to Prefer in MPC-HC External Filters section.

Kado
13th August 2008, 15:13
@rahzel
am i right in assuming ATI doesn't have this issue?

ATI cards uses 0-255 for hd video and 16-235 for sd video, or maybe it's the other way around but still I prefer nvidia's way because you can choose the luma range yourself in the control panel.

wozio
14th August 2008, 22:08
ATI cards uses 0-255 for hd video and 16-235 for sd video, or maybe it's the other way around

You can apply registry fix to convert sd video to pc levels also and if you want to have video levels you can undo conversion via contrast/brightness settings in ccc.

Demi9OD
14th August 2008, 22:39
What is the final verdict on the 177 NV drivers? Does the control panel setting correctly set 0-255 levels for all video, including embedded internet videos? I tried 175 drivers till I discovered the VMR reg trick was not working, and dropped back down to 169.

NanoBot
15th August 2008, 06:29
Hi,

Adjusting the PC / TV levels works fine here with both the 177.79 beta and the 177.83 WHQL drivers, no matter if the content is SD or HD. And in a dual monitor configuration it is even possible to adjust the levels seperately for each monitor.

Nevertheless I did not check the levels when playing back embedded internet videos, simply because I do not care about correct levels on those material. I only checked content received by DVB and played back from optical disks and files, and with that sources everthing is fine.

C.U. NanoBot

rahzel
15th August 2008, 08:44
ended up getting 177.83 drivers with a modified inf, and it does in fact fix the problem setting it to 0-255 in the CP.

Sharktooth
15th August 2008, 15:23
177.89 with opengl 3 (http://www.tcmagazine.com/comments.php?shownews=21308&catid=3) for winxp/vista 32/64 supporting geforce 6+ series cards. warning for gamers: no physix driver included. if you need it you can dowload it here (http://www.toomanydownloads.com/index.php?option=com_mtree&task=viewlink&link_id=165&Itemid=54) though.

rahzel
16th August 2008, 20:17
now that i got my NV card fixed, and now that i got my 780G/ATI HD3200 motherboard back, i'm having a problem with VMR9 being too bright again (but with my ATI IGP).... this time, 720p videos are too bright, but 1080p appears to be fine. i haven't tried any other resolutions yet.
edit: 640x480 also too bright. so it seems like <720 is too bright, 1080p is fine.
is there any fix for ATI cards?

ranpha
16th August 2008, 20:32
now that i got my NV card fixed, and now that i got my 780G/ATI HD3200 motherboard back, i'm having a problem with VMR9 being too bright again (but with my ATI IGP).... this time, 720p videos are too bright, but 1080p appears to be fine. i haven't tried any other resolutions yet.
edit: 640x480 also too bright. so it seems like <720 is too bright, 1080p is fine.
is there any fix for ATI cards?

You probably need to apply the "UseBT601CSC" registry fix available at http://www.avsforum.com/avs-vb/showpost.php?p=11659897&postcount=2121

rahzel
16th August 2008, 21:01
thanks.
so do i make a DWORD value of UseBT601CSC and make the value 1? i tried it but it didn't seem to work.
edit: tried making them as a string instead of dword, but still no go.

pitch.fr
16th August 2008, 22:54
http://exdeus.home.comcast.net/~exdeus/ati-hd2x00/

but you should only output RGB32HQ from ffdshow anyway, the ATI drivers are borked :
http://forum.doom9.org/showpost.php?p=1137196&postcount=1868

rahzel
16th August 2008, 23:06
i ran the vbs file, and i guess i did do it right before... it just didnt work. do you have to have CCC installed or something? because i don't.

i'm using XP Pro SP3 with 8.475 drivers btw.

ranpha
17th August 2008, 07:33
If the vbs file did not do the trick, download DXVA Checker at http://cid-94cc264fce430b66.skydrive.live.com/self.aspx/Public/tutorial/DXVAChecker|_1810.zip, unzip it, run the executable (in admin mode if you use Vista), right-click on any of the values such as ModeMPEG2_IDCT, select Driver Settings.

In the pop-up window, scroll to UseBT601CSC, click on it, set the value to 1, press OK, exit the DXVA Checker utility and reboot the computer.

rahzel
17th August 2008, 09:09
thanks.
i did all that, and it is indeed checked. actually, i don't know if its VMR9 or what. if i use CoreAVC with VMR9, it looks ok. but when i use the internal H264 (DXVA) filter in MPC HC with VMR9, it looks brighter and washed out. and upon further examination, its not just <720p videos, but 1080p as well.

i'm having so many problems with filters and reg fixes lately. =\

ranpha
17th August 2008, 09:53
thanks.
i did all that, and it is indeed checked. actually, i don't know if its VMR9 or what. if i use CoreAVC with VMR9, it looks ok. but when i use the internal H264 (DXVA) filter in MPC HC with VMR9, it looks brighter and washed out. and upon further examination, its not just <720p videos, but 1080p as well.

i'm having so many problems with filters and reg fixes lately. =\

Well, if you are using MPC-HC exclusively, then enable the 16-235 --> 0-255 pixel shader operation then.

rahzel
17th August 2008, 11:51
so i installed CCC and it seems to be working now. so either DXVA checker made it work somehow, or you need CCC installed in order for this to work. 1080p videos still seem a little brighter than using coreavc, though.