madVR - high quality video renderer (GPU assisted)

[THX-UltraII]

Hi,

Been using madVR from the start but decided a year ago to switch to a Dune player. This still does not satisfy me so I decided to switch back to HTPC.

After a clean install of my system and installing all lastest drivers, MPC-HC, ffDSHOW and madVR some first questions are here:

1.
what pixel format output do I pick at the ATI CCC settings?
yCbCr 4:4:4 Pixel Format
yCbCr 4:2:2 Pixel Format
RGB 4:4:4 Pixel Format Studio (Limited RGB)
RGB 4:4:4 Pixel Format PC Standard (Full RGB)

2.
the ATI CCC got some new function I see. There is 'Brighter Whites' which can be enabled/disabled. I can imagine this will be important to set this on or off. What to choose here?

3.
Dynamic range can be altered in the ATI CCC settings Just leave this off?

4.
PullDown detection and Smooth Video Playback in the ATI CCC. On or Off?

5.
FFdshow: only check output YV12?

6.
madVR. I see that madVR got decoding options! Check all and use ffmpeg software decoder? Or is ffdshow decoder still better to use?

7.
What are some good algorithms settings to use? Looking for some (basic) settings that can be used for all type of movies that do not cause too much artifacts.

8.
See a lot of new rendering options since the first versions of madVR. Is there a guide somewhere to find out what they do/which make quality better?

Maybe more questions will come but I think this is enough for now :)

Thanks!

EDIT: And of course my setup:
HTPC (w7 x64) with ATI 5450, Core2Quad Q9550 oc, 8gb DDR3 1333.
JVC RS25 projector

[nand chan]

1.
what pixel format output do I pick at the ATI CCC settings?
yCbCr 4:4:4 Pixel Format
yCbCr 4:2:2 Pixel Format
RGB 4:4:4 Pixel Format Studio (Limited RGB)
RGB 4:4:4 Pixel Format PC Standard (Full RGB)

Set it to full range RGB. Chances are, madVR is better at concerting the Y'CbCr than your TV's processor is.

And if you need a limited range display, you can set the display to limited range in madVR.

4.
PullDown detection and Smooth Video Playback in the ATI CCC. On or Off?

I'll assume off, madVR takes care of pulldown and it (+ reclock) attempt to take care of smooth video playback.

5.
FFdshow: only check output YV12?

Yes.

6.
madVR. I see that madVR got decoding options! Check all and use ffmpeg software decoder? Or is ffdshow decoder still better to use?

Check all and use ffmpeg. ffdshow's decoder is worse than the madVR internals. However, if you want the best, I recommend you use the LAV Filters for decoding - they are even better than the madVR internals.

7.
What are some good algorithms settings to use? Looking for some (basic) settings that can be used for all type of movies that do not cause too much artifacts.

I use Mitchell-Netravali for chroma upscaling and Spline (4 taps) for Luma upscaling.

I have found the other algorithms (other than Lanczos and Spline) don't produce a sharp enough result for luma upscaling, but softness is fine for chroma.

[QBhd]

Those "video" settings in AMD VISION Engine Control Center will have no affect on madVR. madVR behaves basically like a game.

QB

[namaiki]

My madVR is stuttering on my XPS 15 laptop.
It only stutters in D3D Fullscreen but it's fine in windowed mode.
My specs are:
i7 2630QM processor
Nvidia GT525M

Help?

You don't need to enable D3D Fullscreen in MPC-HC options to use exclusive mode in madVR, if that is what you have done.

[THX-UltraII]

Set it to full range RGB. Chances are, madVR is better at concerting the Y'CbCr than your TV's processor is.

And if you need a limited range display, you can set the display to limited range in madVR.



I'll assume off, madVR takes care of pulldown and it (+ reclock) attempt to take care of smooth video playback.



Yes.



Check all and use ffmpeg. ffdshow's decoder is worse than the madVR internals. However, if you want the best, I recommend you use the LAV Filters for decoding - they are even better than the madVR internals.



I use Mitchell-Netravali for chroma upscaling and Spline (4 taps) for Luma upscaling.

I have found the other algorithms (other than Lanczos and Spline) don't produce a sharp enough result for luma upscaling, but softness is fine for chroma.

thxz!
How do I set madVR to Limited range and why exactly should I do that?

Are those LAV filters new? Never heard from them. Where can I get them and is there a guide somewhere how to use them?

[nand chan]

thxz!
How do I set madVR to Limited range and why exactly should I do that?

If your TV is limited range instead of full range (PC monitors are full range), you can set it as such in madVR's settings -> devices -> <your TV> -> properties.

Are those LAV filters new? Never heard from them. Where can I get them and is there a guide somewhere how to use them?

https://forum.doom9.org/showthread.php?t=156191&page=289

Just run the installer, it *should* take care of everything.

[pirlouy]

Are those LAV filters new? Never heard from them.
It's the new reference decoder for quite all popular codec (my opinion).

[THX-UltraII]

If your TV is limited range instead of full range (PC monitors are full range), you can set it as such in madVR's settings -> devices -> <your TV> -> properties.



https://forum.doom9.org/showthread.php?t=156191&page=289

Just run the installer, it *should* take care of everything.

you mean set it to TV levels? With this settings the colours are grey and washed out.

What about the LAV Output Formats setting? Check only RGB? Athe RGB Output Levls? Is it best to set it on 'untouched' (as input)?

[nand chan]

you mean set it to TV levels? With this settings the colours are grey and washed out.

Well then you have a full range monitor.....

What about the LAV Output Formats setting? Check only RGB? Athe RGB Output Levls? Is it best to set it on 'untouched' (as input)?

Good heavens no, check all formats. You should *always* output a format similar to the source. If your source is a YV12 frame, you should output YV12 as well.

As for the RGB output, just use full range.

[naoan]

Slightly off topic here but, what is the thing that made madvr decoder and lav decoder to be better than ffdshow? I used ffdshow for ages and the only crashing I get are the avisynth related one.

[nand chan]

Slightly off topic here but, what is the thing that made madvr decoder and lav decoder to be better than ffdshow? I used ffdshow for ages and the only crashing I get are the avisynth related one.

The LAV Decoder has a lot better performance than the madVR decoder, and the madVR decoder has a lot better performance than the ffdshow decoder.

In addition, both LAV and madVR support 10-bit properly, while ffdshow doesn't - it only supports 8 bit formats, so the decoder dithers the input down when playing a Hi10P file. Normally, this wouldn't be a problem, but it doesn't dither correctly either, so you'll get image artifacts.

It's mainly a quality and performance issue, not an issue of crashing.

[naoan]

I see, I never have problem with performance and there's hacked ffdshow 10 bit build available so I don't have that problem as well, thanks for clarifying.

[nand chan]

I see, I never have problem with performance and there's hacked ffdshow 10 bit build available so I don't have that problem as well, thanks for clarifying.

That's the build I was referring to. It doesn't actually support 10 bit textures.

[naoan]

The one on CCCP? well, that suck. It's the only way to use advanced debanding like flash3kyuu_deband on the fly afaik. :(

[nand chan]

The one on CCCP? well, that suck. It's the only way to use advanced debanding like flash3kyuu_deband on the fly afaik. :(

I know. Then again, flash3kyuu_deband doesn't even support 10-bit either way so there's no point. Btw, what you want to do is:

1. Use LAV Video decoder to decode and dither down to 8-bit (it does this properly unlike ffdshow)
2. Use the ffdshow *raw* video filter to host avisynth scripts

That way you can use flash3kyuu in realtime. You won't have 10-bit textures but the difference will be very minimal. Just make sure you dither back down to 8-bit using proper levels in avisynth (don't let ffdshow take care of *any* dithering).

Set the ffdshow video decoder to “block” and the raw video decoder (aka raw filter) as “prefer”.

[THX-UltraII]

I know. Then again, flash3kyuu_deband doesn't even support 10-bit either way so there's no point. Btw, what you want to do is:

1. Use LAV Video decoder to decode and dither down to 8-bit (it does this properly unlike ffdshow)
2. Use the ffdshow *raw* video filter to host avisynth scripts

That way you can use flash3kyuu in realtime. You won't have 10-bit textures but the difference will be very minimal. Just make sure you dither back down to 8-bit using proper levels in avisynth (don't let ffdshow take care of *any* dithering).

Set the ffdshow video decoder to “block” and the raw video decoder (aka raw filter) as “prefer”.

This is out of league :)
Can I use MPC-HC, madVR and LAV filters for the best PQ?

[nand chan]

This is out of league :)
Can I use MPC-HC, madVR and LAV filters for the best PQ?

Yeah, it'll be good enough. Avisynth scripts are just needed for the absolute control freaks. :)

You'll need a very strong CPU to do color space conversions, gamut mapping, debanding, dithering etc. in realtime, but if you can handle it then by all means skip madVR and just output RGB32 from your avisynth chain.

[THX-UltraII]

As for the RGB output, just use full range.

I don t have that option listed in LAV. I can only choose TV, PC or Untouched

[naoan]

I know. Then again, flash3kyuu_deband doesn't even support 10-bit either way so there's no point. Btw, what you want to do is:

1. Use LAV Video decoder to decode and dither down to 8-bit (it does this properly unlike ffdshow)
2. Use the ffdshow *raw* video filter to host avisynth scripts

That way you can use flash3kyuu in realtime. You won't have 10-bit textures but the difference will be very minimal. Just make sure you dither back down to 8-bit using proper levels in avisynth (don't let ffdshow take care of *any* dithering).

Set the ffdshow video decoder to “block” and the raw video decoder (aka raw filter) as “prefer”.

I actually usually do this before for 8 bit video, but used coreavc to take care of the decoding since it is faster than ffdshow. But thanks for the info about the wrong dithering on ffdshow, I'd be oblivious otherwise.

Now if madvr has avisynth support my dream media setup is complete, but that's asking a bit too much I guess. :o

[THX-UltraII]

I use Mitchell-Netravali for chroma upscaling and Spline (4 taps) for Luma upscaling.

I have found the other algorithms (other than Lanczos and Spline) don't produce a sharp enough result for luma upscaling, but softness is fine for chroma.

And what do you use for Luma DOWNscaling?

[THX-UltraII]

And another strange thing that I just noticed:

When I choose RGB Full in the ATI ccc my computer (ATI ccc) is switching back automatically to YCbCr 4:4:4 Pixel Format after 30 seconds or so......

EDIT: Switches back to 4:2:2 and not 4:4:4

[nand chan]

I don t have that option listed in LAV. I can only choose TV, PC or Untouched

PC = Full range

I actually usually do this before for 8 bit video, but used coreavc to take care of the decoding since it is faster than ffdshow. But thanks for the info about the wrong dithering on ffdshow, I'd be oblivious otherwise.

Well, CoreAVC only decodes 8-bit either way so there's no issue here :P

And for 10-bit, LAV Video is *faster* than CoreAVC. In fact, LAV is faster than CoreAVC for 8-bit as well if you have a CUDA graphics card.

Now if madvr has avisynth support my dream media setup is complete, but that's asking a bit too much I guess. :o

Instead of adding avisynth support to madVR, it's better to just create a separate DirectShow filter for avisynth. Like, y'know, the ffdshow raw video host.

There's no point either way until the next version of avisynth comes out which will support higher-than-8-bit textures. For now, ffdshow raw is no different than what you'd get from adding it to madVR.

I don't exactly see the point in that suggestion, maybe I'm missing something?

And what do you use for Luma DOWNscaling?

I don't downscale luma.

[pirlouy]

As for the RGB output, just use full range.
From what Madshi said in this thread, if you use MadVR, you can choose "untouched" (in LAV video 0.36+) and let MadVR deals with it.

[naoan]

Coreavc 3.0 does support proper 10 bit afaik (madvr report so at least).

I just like to have fewer filter chain and decrease the risk of something screwing up along the line (and hopefully, speed thing up). Also, isn't 10 bit support depend entirely on avisynth plugins and there are some that support higher than 8-bit (up to 16 bit).

CMIIW. ;)

[THX-UltraII]

I don't downscale luma.but I have to choose SOMETHING in madVR for this right?

[THX-UltraII]

And another strange thing that I just noticed:

When I choose RGB Full in the ATI ccc my computer (ATI ccc) is switching back automatically to YCbCr 4:4:4 Pixel Format after 30 seconds or so......

EDIT: Switches back to 4:2:2 and not 4:4:4you guys have any idea about this problem? What are the downsides of having 4:2:2 yCbCr Pixel Format?

[nand chan]

but I have to choose SOMETHING in madVR for this right?

Set it to nearest neighbor if you really want to. It doesn't matter one bit if your monitor is 1080p (or higher). The only people that need to care about luma downscaling are those on 720p monitors or lower.

I personally have it set to Bicubic.

Coreavc 3.0 does support proper 10 bit afaik (madvr report so at least).

Yes, it supports 10-bit software decoding. However, it's a lot slower than LAV Video (and still slower than ffdshow). It also artifacts on very high bitrates.

The only good software decoder in CoreAVC is that of version 2, for 8-bit video - which is still slightly faster than LAV Video.

I just like to have fewer filter chain and decrease the risk of something screwing up along the line (and hopefully, speed thing up).

A raw video filter set to “prefer” will always have something to connect to. The only exception is when you're using the madVR internal decoders.

If you're planning on doing that then I can see why you'd want native avisynth support. However, I don't see a situation in which you'd *want* to use the internals either way.

Also, isn't 10 bit support depend entirely on avisynth plugins and there are some that support higher than 8-bit (up to 16 bit).

The avisynth filter itself only supports 8-bit pixel format inputs / outputs, so even if some plugins support higher bit depths they always need to go back down to 8-bit at some point. This is why, if you want to go with avisynth, you need to go all the way (do all color conversions and dither back down to 8-bit in RGB32 space at the very end in avisynth).

Also, flash3kyuu itself only supports YV12 input which is 8-bit only, so the point is moot. It does 8 -> 16 bit debanding.

And don't the custom “16-bit” avisynth formats just do some hacking where they save the low bits and high bits side by side?

you guys have any idea about this problem? What are the downsides of having 4:2:2 yCbCr Pixel Format?

If you really had 4:2:0 YCbCr pixel format (and your monitor accepted RGB) you probably wouldn't even be able to read this, all colors would be ridiculously messed up.

[THX-UltraII]

[QUOTE

If you really had 4:2:0 YCbCr pixel format (and your monitor accepted RGB) you probably wouldn't even be able to read this, all colors would be ridiculously messed up.[/QUOTE]
I don t understand what you mean here :(
You told me to use 4:4:4 Full RGB but my ATI CCC keeps reverting to 4:2:2 Pixel Format. This is not what is supposed to happen and not good right?

[SamuriHL]

It possibly means your AVR and/or TV don't support RGB.

[naoan]

@nand-chan
I'm working with coreavc on 720p lossless h.264 videos (one of them being 58MB/s 60FPS) and see no artifact at all. I can't comment on the speed (not sure how to do proper benchmark for 10 bit), but the cpu consumption seems about the same. Actually, seeking seems to be faster on coreavc.

By screwing up I mean something like that dither problem on ffdshow you explained earlier, though yeah, maybe the decoder like ffdshow is a better place for it to be. :)

I dunno about the detail but flash3kyuu readme specify that it could feed 16 bit output to x264 (to be dithered there to 10 bit), haven't tried it yet though.

btw, do you have another alternative for debanding 10 bit video without first converting it to 8 bit?

[nand chan]

@nand-chan
I'm working with coreavc on 720p lossless h.264 videos (one of them being 58MB/s 60FPS) and see no artifact at all. I can't comment on the speed (not sure how to do proper benchmark for 10 bit), but the cpu consumption seems about the same. Actually, seeking seems to be faster on coreavc.

http://img683.imageshack.us/img683/7264/faildwz.png

I'm not sure at what bitrate the issue occurred but multiple people have been experiencing it. I think it was like 30 Mbps for 24 Hz.

Either way, maybe it's fixed already?

By screwing up I mean something like that dither problem on ffdshow you explained earlier, though yeah, maybe the decoder like ffdshow is a better place for it to be. :)

The decoder shouldn't touch video at all, imo - video processing should be in a processing filter. Otherwise you're gonna get issues later on. (eg. what if you view a video file that doesn't get decoded by ffdshow, how do you get avisynth scripts for that?)

That's why it's important to distinguish between the ffdshow /decoder/ and the ffdshow /filter/. The decoder should never do anything, and you should never enable any post-processing in the decoder either.

All post processing should be done in the raw filter, including avisynth, because it works for everything.

I dunno about the detail but flash3kyuu readme specify that it could feed 16 bit output to x264 (to be dithered there to 10 bit), haven't tried it yet though.

Oh, neat. I guess you could use the standalone version of flash3kyuu independently of avisynth as well (it's open source after all).

btw, do you have another alternative for debanding 10 bit video without first converting it to 8 bit?

I'm not really a video encoder, so no.

[TheShadowRunner]

In fact, LAV is faster than CoreAVC for 8-bit as well if you have a CUDA graphics card.

It's not the case.
For 8-bit, CoreAVC w/CUDA is actually faster than LAV w/CUDA.

[naoan]

http://img683.imageshack.us/img683/7264/faildwz.png

I'm not sure at what bitrate the issue occurred but multiple people have been experiencing it. I think it was like 30 Mbps for 24 Hz.

Either way, maybe it's fixed already?


Seems so, they're quick to release 3.0.1.



The decoder shouldn't touch video at all, imo - video processing should be in a processing filter. Otherwise you're gonna get issues later on. (eg. what if you view a video file that doesn't get decoded by ffdshow, how do you get avisynth scripts for that?)

That's why it's important to distinguish between the ffdshow /decoder/ and the ffdshow /filter/. The decoder should never do anything, and you should never enable any post-processing in the decoder either.

All post processing should be done in the raw filter, including avisynth, because it works for everything.


The problem is, there really is no raw filter that could avisynth post processing beside ffdshow and I'd like more option beside it. But ideally, if a decoder is able to do compressed video it should be able to do post processing on raw video too, though then we'd just get another ffdshow. :p




Oh, neat. I guess you could use the standalone version of flash3kyuu independently of avisynth as well (it's open source after all).


Uh no, flash3kyuu exclusively avisynth filter, to my knowledge there is no way to call it without going through avisynth. Doesn't this mean that avisynth is able to output 16 bit video?


I'm not really a video encoder, so no.

Then the ideal solution should be for the madvr to have flash3kyuu_deband or other high profile debanding filter built in imho :o.

[nevcairiel]

It's not the case.
For 8-bit, CoreAVC w/CUDA is actually faster than LAV w/CUDA.

I suppose that may depend on the samples used, but i have a full set of h264 and vc1 tests that put lav video in cuvid mode about 1-2% above CoreAVC.

Its never a really big difference, i would be fine with calling them equally fast, as its really the hardware doing the decoding. :p

[TheShadowRunner]

I suppose that may depend on the samples used, but i have a full set of h264 and vc1 tests that put lav video in cuvid mode about 1-2% above CoreAVC.

I guess it must depend on the sample used (http://forum.doom9.org/showthread.php?p=1529461#post1529461), indeed ^^;

i would be fine with calling them equally fast, as its really the hardware doing the decoding. :p

That would make sense to me too! but..

[nevcairiel]

I guess it must depend on the sample used (http://forum.doom9.org/showthread.php?p=1529461#post1529461), indeed ^^;


You realize that the rendering time madVR shows has absolutely nothing to do with the performance of the decoder, right? :)
BTW, LAV is still faster on that sample for me.

Benchmark your sample with GraphStudio, that will get you the actual performance of the video decoder. (I dont remember if you tried that already)
If there is a big difference, then thats another thing.

Since i cannot reproduce your problem, thats rather problematic.
If you want, head over to the LAV thread and post your exact madVR settings, maybe its a combination of special settings that causes this weird interaction. No reason to keep spamming this in here. :)

[TheShadowRunner]

You realize that the rendering time madVR shows has absolutely nothing to do with the performance of the decoder, right? :)

True, what I don't get really is why madVR seem to be struggling almost twice more with LAV's output versus Core's.
Since they both go through CUDA, I'd expect exactly similar outputs to madVR.
If this is the case and madVR receives the same, the difference has to be due to the decoder. (since it's the only change in the graph)

But yes, I took for granted that madVR gets the same output, am I wrong on this?

Benchmark your sample with GraphStudio, that will get you the actual performance of the video decoder. (I dont remember if you tried that already)
If there is a big difference, then thats another thing.

GraphStudio crashes all the time in haali's splitter.ax.
I have to postpone the test, thanks for the suggestion ;)

[nand chan]

Uh no, flash3kyuu exclusively avisynth filter, to my knowledge there is no way to call it without going through avisynth. Doesn't this mean that avisynth is able to output 16 bit video?

No, what I mean is take the actual algorithm out of the source code and wrap it inside your own directshow filter / shader / renderer / decoder / whatever.

It's written in C, not avisynth script. (And even if it were, it's trivial to just translate it)

Then the ideal solution should be for the madvr to have flash3kyuu_deband or other high profile debanding filter built in imho :o.

This would probably be the best solution, yeah.

[naoan]

Ah sorry for the misunderstanding, Can we agree for debanding filter on madvr as a feature request? :D

Though at this point I'd consider it a bonus as madvr is already goddamn awesome as it is. :D

@nevcairiel
I remember about graphstudio after you mentioned it, and for the heck of it benchmarked lavfilter against coreavc with the lossless h.264. Surprisingly (for me) Lav is actually about 14 FPS faster (98 vs 112) than coreavc, strangely though it is noticeably slower at seeking the video when you're actually playing it via media player (used mpc-hc).

[nevcairiel]

Seeking performance greatly depends on where you actually seek. If you manage to seek directly on a keyframe (or shortly after it), seeking will be fast. If you seek in the middle between two keyframes, it'll probably take a while to recover. Due to that behaviour, truely objective comparisons are really hard, unless you use fixed time seek points, and not random clicking in the movie. :)

From my own tests, i can't really say that CoreAVC is faster, and from what i know about DirectShow, its not really in the decoders power to influence seeking speed all that much. If the seek request is at a bad position, and the file is encoded with very few key frames, it will just take a while to recover.
I still think people are far too obsessed with seeking, though. Watch the movie already! :)

[naoan]

Humm, you're right, it seems to be largely based on luck of the draw, I guess coreavc was just lucky on those two occasions (different launch).

[nand chan]

Ah sorry for the misunderstanding, Can we agree for debanding filter on madvr as a feature request? :D

Though at this point I'd consider it as a bonus as madvr is already goddamn awesome as it is. :D

@nevcairiel
I remember about graphstudio after you mentioned it, and for the heck of it benchmarked lavfilter against coreavc with the lossless h.264. Surprisingly (for me) Lav is actually about 14 FPS faster (98 vs 112) than coreavc, strangely though it is noticeably slower at seeking the video when you're actually playing it via media player (used mpc-hc).

Keyframe seeking enabled or not?

[ryrynz]

Then the ideal solution should be for the madvr to have flash3kyuu_deband or other high profile debanding filter built in imho :o.

Would love to see that.

[naoan]

Keyframe seeking enabled or not?

Does the decoder have option to disable it? My encoder setting have it specified though if that what you mean.

After some testing it looks like lav video is indeed the fastest 10 bit decoder around, reigning a whole 79FPS on one realistic test files I tried (you should really advertise this), but 8 bit video still is coreavc territory, though not by much (27 FPS faster on 1080p 24FPS video).

This is really off topic though, maybe not by much if you consider it as educative info for choosing madvr best pairing. :p

[Andy o]

And another strange thing that I just noticed:

When I choose RGB Full in the ATI ccc my computer (ATI ccc) is switching back automatically to YCbCr 4:4:4 Pixel Format after 30 seconds or so......

EDIT: Switches back to 4:2:2 and not 4:4:4

When you switch formats, IIRC there's a dialog that will ask you if you can see it correctly and confirm, if not it will revert after a certain amount of seconds. When you switch to RGB Full, does your screen blink (resync) and you can see everything OK?

Which AVR do you have?

Ideally you'd set Full RGB output and madVR to PC levels. Your display might have relevant input options for its HDMI inputs, see if it can take in RGB Full.

A quick test would be a test like the ones in the first page of this thread. Only with RGB Full/PC levels would you not get banding with the white/black gradient, and have all levels (madVR and the rest of Windows) as they should be.

As an aside, your 5450 might just be too slow for madVR, is it working fine?

[nand chan]

Does the decoder have option to disable it? My encoder setting have it specified though if that what you mean.

After some testing it looks like lav video is indeed the fastest 10 bit decoder around, reigning a whole 79FPS on one realistic test files I tried (you should really advertise this), but 8 bit video still is coreavc territory, though not by much (27 FPS faster on 1080p 24FPS video).

This is really off topic though, maybe not by much if you consider it as educative info for choosing madvr best pairing. :p

I meant in the MPC-HC settings, Tweaks -> Fast seek (on keyframe)

Does turning it on help?

And yeah, I was aware LAV Video has the fastest 10-bit decoder available, especially after the last patch which added another 2-5%.

[jmone]

Noob Q for nvidia users .... how do you adjust Contrast, Brightness and the Range for Video Playback & make it apply to the various refresh rates (Win 7 64-Bit Dirver 280.26 using HDMI at 1080p) so I can do an initial basic callibration.
Thanks
Nathan

Edit, I have std 1920x1080 at 50,59,60hz but I had to add a custom res to get 23 and 24hz. The contrast and brigtness is different between the std and custom res.
Edit2: Nevcairiel has posted previously of creating a custom res for all the major freq so he can manage the range but how do you do this as I get an error saying it already exists.

[Andy o]

Do you need the custom res? I haven't bothered at all cause I'm using ReClock and decoding everything. I'm done worrying about perfect refresh. I even do all 23-24 stuff at "24.002" or so.

[jmone]

FYI, I'm also a decoder and use "VideoClock" in MC16 to keep audio and video in sync but I need to add a custom res for 24hz as my EDID from the TV is not being passed from the Receiver (long story!). The issue is the Display Range is different for a Custom Res (my 24hz) to the nvidia predefined res (my 50 / 60hz).

Anyway - I've now worked out how to add a custom resolution for ones that already were predefined (in the Create Custom Resolution Panel, open up timing, select Standard = Manual and just change the reported refresh rate slightly eg to say "50.001" etc. Don't worry these do not actually change anything and are even reported as 50hz etc once saved). I now have all my refresh rates defined as a Custom Resolution so the same video output range is being applied to all. So far it appears that "TV Levels" (16-235) is the go, as I can tweak the Brightness and Contrast video slightly in the nvidia Desktop to get the correct levels according to the AVSForum Test pattern and they are now consistent as I change refresh rates between 23/24, 50, 59/60hz. I can not tune it in with "PC Levels" (0-255) selected in madVR unless there is another setting in nvidia's panel somewhere I missed for custom res! Anyway happy boy today.

[THX-UltraII]

I ve managed to get Full RGB Pixel Format work and my JVC RS25 accepts it. It s a bug in the ATI CCC. A temp. solution I found on the AMD forum: set it to RGB Full and immediately restart PC. This way it DOES get remembered by ATI and there will be no switching back anymore.

So I found out that with this setting my blacks looked good but I had the feeling that in dark scenes it was too dark. So I looked up the manual of my JVS and switched a HDMI setting to ENHANCED instead of AUTO (STANDARD was also an option but this resulted in the same as AUTO). Is this ENHANCED setting the right to use you guys think?

Also again about the ATI CCC settings. Some say that it does not affect madVR at all but others say it does indeed and I would have to set 0-255 manually in the ATI settings and that also the WHITE option in the CCC has effect on madVR. Could someone tell me what is right? Maybe madshi?