View Full Version : madVR - high quality video renderer (GPU assisted)
Asmodian
27th April 2016, 02:02
If you don't want to get into it too deeply I suggest you set white point and brightness to native, tone curve to BT.1886. Black point compensation on for the first try, off if that calibration is not good near black.
This method doesn't try to fix the white point but white is relative for humans and without a lot of testing and doing it right HDTV calibrations are generally better without targeting a white point, IMO. You sacrifice too much to sort-of fix white.
I suggest you look at the Display Calibration (http://forum.doom9.org/showthread.php?t=172783) thread for continued discussion of this topic. There is some good information there and it is nice to avoid clogging up this thread with display calibrations.
Stereodude
27th April 2016, 04:25
hey people, about 3dlut calibration
tomorrow i gonna try again make a 3dlut, the last experience was bad... i got an old i1d2 and an lcd hdtv that donīt have rgb sliders or any colour controls...
what is the best config in dispcal gui?
should i set all to as measured and disable the interactive display adjustments? or should try using the rgb controls from intel cp?
and the tone curve? should i set as measured?
in profiling should i use black point compesation?
can somenone help me? the colorimetry is not mine and i donīhave much time for testing possible configurations..
ps: my tv donīt support full range, and the best config i found is set madvr to tv levels and intel to full range... there something i should do in dispcalgui to match this settings?
DisplayCAL is much better than it used to be. I generated 3D LUTs for my plasma and one of my LCD monitors in the past week. It now has a 3D LUT for madVR option on the main page. You don't need black point compensation. Don't mess with RGB sliders in the drivers.
The rest of your questions depend on what you're trying to do or are after. After you generate a profile of your display you can generate a 3D LUT over and over changing the options however you want. That only takes a few minutes per 3D LUT and doesn't require any remeasurement.
*Touche*
27th April 2016, 15:44
Can you produce test images? I have hard time noticing any difference when super-xbr or NNEDI3 is combined with SuperRes.
Don't have any saved, I just pause some movies and tv shows and compare. It's not that SR is important, actually, just sxbrAB25 ~ NNEDI3.
aufkrawall
27th April 2016, 16:09
It's a bit softer, though, which is corrected well by SR.
SR also corrects some of the bloating by super-xbr without A-B, but this is mainly limited to bloating of dark areas since SR in GL has kind of thinning effect for dark lines. The ringing/bloating of bright areas by super-xbr isn't corrected as good, that's where super-xbr A-B comes in.
pirlouy
27th April 2016, 17:56
I am using it with a DVB-T2 tuner in the UK with MPC-HC and channels broadcast both in h264 and mpeg2 streams, no matter what I get dropped frames, albeit very very occasionally.
I also had dropped frames. I've tried to disable deinterlacing, but I still also noted dropped frames, despite using bilinear basic filters. Maybe the problem is with hardware. I never took time to test with DVBViewer.
CarlosCaco
27th April 2016, 18:53
Guys i need help, i aways used madvr in tv levels and the gpu on full range... My tv cleary don't suports full range, all other aplications turn darker and saturated...
But i downloaded avschd patterns and when i play the black clipping pattern all the bar are flashing so i tried others
And the only that keep 16 black and 17 flashing is madvr 1-255 and gpu full
But how this is possible? If i can see cleary on other aplications that the tv don't support full range, also on madvr full range the movies are darker and oversaturated...i really don't know what is happening
Its possible to be a Intel driver bug?
huhn
27th April 2016, 19:57
are you getting a different result here?
https://www.youtube.com/watch?v=9TI9f1zxucw
+-1 level scaling can make more levels visiable.
is DXVA scaling used?
Dodgexander
27th April 2016, 21:04
I also had dropped frames. I've tried to disable deinterlacing, but I still also noted dropped frames, despite using bilinear basic filters. Maybe the problem is with hardware. I never took time to test with DVBViewer.
I've done some more testing using jriver with madVR. And I think I've narrowed it down to some kind of deinterlacing detection. It was most apparent when watching the Simpsons but I found madVR kept switching deinterlacing on and off, eg not detecting if it's needed from the stream or not.
This was more apparent because when I turned on forced deinterlacing in madVR or forced it off there's no dropped frames.
At first I thought it was video mode/film mode detection and that may be responsible from some dropped frames too but its best stuck to video only for TV.
It might help to understand how the auto detection works to try figure out why madVR keeps switching deinterlacing off/on.
Edit # further testing confirms the same behavior in mpc-hc. Never dropping frames with deinterlacing off. Keeping deinterlacing off in madvr and forcing it on in lav such as enabling yadif once again means the occasional dropped frames. The same occurs when using hardware deinterlacing in lav and forcing it on. How the hell can I work out how to solve this?
Sent from my Nexus 5 using Tapatalk
CarlosCaco
27th April 2016, 21:22
are you getting a different result here?
https://www.youtube.com/watch?v=9TI9f1zxucw
+-1 level scaling can make more levels visiable.
is DXVA scaling used?
No dxva, later i will try your link
Is Very strange if i set madvr to tv anda gpu to full 1 to 25 all flashes
Ir ser madvr full and gpu limited i get 19 to 25 flashing but with madvr full and gpu full almost the same happens... I found that madvr 1-255 and gpu limited works but i don't want Intel dithering...
Asmodian
27th April 2016, 23:53
No dxva, later i will try your link
Is Very strange if i set madvr to tv anda gpu to full 1 to 25 all flashes
Ir ser madvr full and gpu limited i get 19 to 25 flashing but with madvr full and gpu full almost the same happens... I found that madvr 1-255 and gpu limited works but i don't want Intel dithering...
What do you mean by "works"? 17 to 25 flashing is correct so it sounds like you have correct behavior using the recommended madVR full and GPU full setting. You simply have slight shadow crush which is very common on any consumer display that hasn't been calibrated. You can use custom levels in madvr to correct it or use different options when calibrating your display.
edit: btw your results are not strange at all, that is exactly what you would expect to happen. Picture information is 16-235, so when set to full madVR expands 16-235 to 0-255, clipping 0-15. If set to limited madVR outputs the untouched 0-255, which includes the blacker than black 1-15 bars which you incorrectly see. The GPU setting simply compresses 0-255 to 16-235 if set to limited and outputs the untouched 0-255 if set to full. The GPU always assumes it is 0-255 so if you set both the GPU and madVR to limited you get double compression.
CarlosCaco
28th April 2016, 00:35
What do you mean by "works"? 17 to 25 flashing is correct so it sounds like you have correct behavior using the recommended madVR full and GPU full setting. You simply have slight shadow crush which is very common on any consumer display that hasn't been calibrated. You can use custom levels in madvr to correct it or use different options when calibrating your display.
edit: btw your results are not strange at all, that is exactly what you would expect to happen. Picture information is 16-235, so when set to full madVR expands 16-235 to 0-255, clipping 0-15. If set to limited madVR outputs the untouched 0-255, which includes the blacker than black 1-15 bars which you incorrectly see. The GPU setting simply compresses 0-255 to 16-235 if set to limited and outputs the untouched 0-255 if set to full. The GPU always assumes it is 0-255 so if you set both the GPU and madVR to limited you get double compression.
Maybe i not explaned cleary english is not my native language
I aways used madvr on tv levels and gpu on full levels
But when i run the patterns the resulta are strange
Lets show you:
Madvr: 16-235 gpu: 0-255 = all bars 1 to 25 flashing similar to limited limited But with brackground more darker
Madvr: 0-255 gpu: 16-235 = 18 to 25 flashing
Madvr: 0-255 gpu: 0-255 = 19 to 25 flashing
If i set madvr 1-255 any range on gpu flashes 17-25
But my tv don t have hdmi black level option also don't have any levels
Options, and with gpu to full all colors on desktop and internet and everything else become Very darker without any shadow detail and oversaturated on reds...
I really don t know more what levels use...
With thats situation i tried 3dluts with all settings and only terrible results
Asmodian
28th April 2016, 01:40
Madvr: 16-235 gpu: 0-255 = all bars 1 to 25 flashing similar to limited limited But with brackground more darker
Madvr: 0-255 gpu: 16-235 = 18 to 25 flashing
Madvr: 0-255 gpu: 0-255 = 19 to 25 flashing
If i set madvr 1-255 any range on gpu flashes 17-25
Your first setting doesn't make sense given you report a clipped desktop if you have the GPU set to full range. How can you see bars 1-15 if you have crushed shadow detail on your desktop?
Options, and with gpu to full all colors on desktop and internet and everything else become Very darker without any shadow detail and oversaturated on reds...
I really don t know more what levels use...
With thats situation i tried 3dluts with all settings and only terrible results
Set madVR to 1-255 and the GPU to limited to fix the desktop, of course this has Intel's dithering.
The only other option is madVR 16-235 and the GPU full, but this clips your desktop.
These are the only two options if your TV does not support full range. But it sounds like your's does if you can see all the bars with madVR 16-235 and the GPU 0-255?
Maybe you can recalibrate your TV for full range input? I know some TVs I have calibrated did not have an option for blacklevel but I could change it by changing brightness and contrast.
Set madVR to 16-235, GPU to Full, usually you raise brightness to bring lower numbered bars visible and lower contrast to bring higher numbered bars visible. Sadly sometimes the manufacture has 'brightness' and 'contrast' change different aspects so these adjustments might not be right or even involved in the black or white level. You want to adjust until you can see 1 and 254. If you can adjust so all steps are visible you then change madVR to full range and you should only see 16 and 235 (and the desktop should look correct).
Warner306
28th April 2016, 03:59
When set to 0-255, madVR clips 0-15? This is news to me. What about 236-255? Also clipped?
CarlosCaco
28th April 2016, 04:55
Your first setting doesn't make sense given you report a clipped desktop if you have the GPU set to full range. How can you see bars 1-15 if you have crushed shadow detail on your desktop?
Set madVR to 1-255 and the GPU to limited to fix the desktop, of course this has Intel's dithering.
The only other option is madVR 16-235 and the GPU full, but this clips your desktop.
These are the only two options if your TV does not support full range. But it sounds like your's does if you can see all the bars with madVR 16-235 and the GPU 0-255?
Maybe you can recalibrate your TV for full range input? I know some TVs I have calibrated did not have an option for blacklevel but I could change it by changing brightness and contrast.
Set madVR to 16-235, GPU to Full, usually you raise brightness to bring lower numbered bars visible and lower contrast to bring higher numbered bars visible. Sadly sometimes the manufacture has 'brightness' and 'contrast' change different aspects so these adjustments might not be right or even involved in the black or white level. You want to adjust until you can see 1 and 254. If you can adjust so all steps are visible you then change madVR to full range and you should only see 16 and 235 (and the desktop should look correct).
asmodian i only have to say thank you very much for your patience and compreension, youīre right, i did what you said and really my tv support full range, yeah great great great more contrast, more color more real life look, thanks again man
and to the others in this thread sorry for bring an old topic discussion
huhn
28th April 2016, 06:54
When set to 0-255, madVR clips 0-15? This is news to me. What about 236-255? Also clipped?
both are clipped as it should be.
James Freeman
28th April 2016, 13:12
madshi can you please add DCI-P3 D65 to madVR?
zaemon
28th April 2016, 16:50
Just wanted to thank madshi and guys over at LAVfilters to help enable MVC playback. Just one thing: sometimes madVR does not switch to 3D stereoscopic mode and resolution when I play back an MVC video. That's a problem because I'm outputting at 4k and thus the video is played back in 2D at 4k. Maybe having some kind of 1080p23@3D display mode would do the trick. Right now I'm using two profiles, one with 4k resolutions and one with 1080p. Using 1080p display mode always ensure that 3D stereoscopic mode is activated. Using 4k display mode don't.
Sent from my iPhone using Tapatalk
Sunspark
28th April 2016, 17:49
In case anyone is curious to know, a 2-core Broadwell cpu with Intel HD 6000 can upscale 1280x720p to 2048x1152p using NNEDI3 16 neurons for chroma and Lanczos 4-tap with anti-ringing filter for luma without frame drops. Render time is about 20 ms on my computer. Picture quality is quite good for this combination. and noticeably superior to DXVA2.
NNEDI3-16 chroma however, cannot be selected to upscale 1920x1080p to 2048x1152p or just chroma upscaling by itself (normal size) without lots of dropped frames so you still need to use a different chroma upscaler like Mitchell-Netravali.
I am not sure why because I thought the jump from 1080p to 1152p would be less intensive than the jump from 720p to 1152p. Is there a mathematical pixel limit for the scaling or something else?
Warner306
28th April 2016, 18:15
In case anyone is curious to know, a 2-core Broadwell cpu with Intel HD 6000 can upscale 1280x720p to 2048x1152p using NNEDI3 16 neurons for chroma and Lanczos 4-tap with anti-ringing filter for luma without frame drops. Render time is about 20 ms on my computer. Picture quality is quite good for this combination. and noticeably superior to DXVA2.
NNEDI3-16 chroma however, cannot be selected to upscale 1920x1080p to 2048x1152p or just chroma upscaling by itself (normal size) without lots of dropped frames so you still need to use a different chroma upscaler like Mitchell-Netravali.
I am not sure why because I thought the jump from 1080p to 1152p would be less intensive than the jump from 720p to 1152p. Is there a mathematical pixel limit for the scaling or something else?
1080p sources have 1.5x more pixels to process. I'm curious, can an HD 6000 handle Jinc or super-xbr upscaling if Bicubic is used for chroma upscaling (NNEDI3 is a bit wasteful).
What about super-xbr100 + AR + Bicubic150 (downscaling) + SuperRes (1) for 720p sources?
Sunspark
28th April 2016, 19:26
1080p sources have 1.5x more pixels to process. I'm curious, can an HD 6000 handle Jinc or super-xbr upscaling if Bicubic is used for chroma upscaling (NNEDI3 is a bit wasteful).
What about super-xbr100 + AR + Bicubic150 (downscaling) + SuperRes (1) for 720p sources?
On 1080p sources it can handle jinc/jinc or superxbr/jinc no problem, 2-5ms. So it is a given that bicubic would be even easier. I'm sure 720p would be no problem either if it can handle NNEDI3-16 for chroma.
I never liked the "look" of jinc on luma though.
Didn't test the second combo, but I'm sure it would be fine as well.
Shiandow
28th April 2016, 20:27
1080p sources have 1.5x more pixels to process.
Actually it's 1080p is 1.5 bigger in both directions, so that would be 2.25x more pixels. For most upscaling algorithms this wouldn't affect computation time much, but NNEDI3 always doubles the image, so the computation time is proportional to input size.
Warner306
28th April 2016, 22:07
Actually it's 1080p is 1.5 bigger in both directions, so that would be 2.25x more pixels. For most upscaling algorithms this wouldn't affect computation time much, but NNEDI3 always doubles the image, so the computation time is proportional to input size.
Yes, 1.5x is the scaling factor. My mistake. But I think NNEDI3 was applied to chroma upscaling not image upscaling, so that shouldn't matter.
Magik Mark
29th April 2016, 00:30
What would be the ideal setting if you want the output to be as natural as possible? Considering the hardware under my signature.
Thanks
Asmodian
29th April 2016, 00:42
Natural? That is very subjective. I might suggest Jinc3+AR as low artifact and not too soft or sharp, I like Reconstruction soft for chroma upscaling too. Also maybe test how you like Mitchell-Netravali, Catmull-Rom and Bicubic 75. The defaults (maybe with all trade quality for performance options disabled) are a good starting point too.
Magik Mark
29th April 2016, 02:25
Natural? That is very subjective. I might suggest Jinc3+AR as low artifact and not too soft or sharp, I like Reconstruction soft for chroma upscaling too. Also maybe test how you like Mitchell-Netravali, Catmull-Rom and Bicubic 75. The defaults (maybe with all trade quality for performance options disabled) are a good starting point too.
Thanks for your thought! Natural in the context of ISF (Imaging Science Foundation). I would definitely try those settings. So far tried sxbr 100 with sr 1. Tried reconstruction as well. Setting SR 1 gives more ISF feel.
JarrettH
29th April 2016, 05:01
Is SuperRes at a value of 1 really worth it? I don't start to see the pop/feeling of depth until I put it at 2-3. I'm using it on 720p to 1080p. I also have a matte screen (maybe it's due to that) :D
What do you mean by ISF (Imaging Science Foundation) feel? I did quickly look it up, but I don't understand the reference
huhn
29th April 2016, 06:04
Yes, 1.5x is the scaling factor. My mistake. But I think NNEDI3 was applied to chroma upscaling not image upscaling, so that shouldn't matter.
360p chroma to 720p (720p source) is way easier than 540p chroma to 1080p (1080p source)
James Freeman
29th April 2016, 09:07
madshi, the 10,000 nit HDR setting will not respect my selection and clip the highlights.
It also exhibits random behavior when pausing the video or resizing the window.
There is some unstable interaction between the Metadata and the selected nit peak setting.
When I select 10,000 nit I need to see all the 64-940 range without madVR clipping, stretching, or compressing anything, even if above 1000 nit input (metadata peak, step 721) there is no content.
Happens with the official HDR demo videos or my videos.
EDIT:
It happens with all peak nit settings is madVR.
Just pause and unpause the video several times.
RyuzakiL
29th April 2016, 09:29
Hello currently i'm using Windows 8.1+MadVR+AMD Crimson 16.4.2, I previously use the last AMD Catalyst and so far it seems color reproduction was superb but now on AMD Crimson since the settings that control the video are not found/available in AMD Crimson, does MadVR ignores the hidden settings pre-defined by AMD Crimson?
Coz it seems using AMD Crimson colors aren't uniform as opposed to using AMD Catalyst since in I was able to turn off the unnecessary video settings in AMD Catalyst for MadVR.
And does MadVR still runs crap on Windows 10?
huhn
29th April 2016, 09:44
Hello currently i'm using Windows 8.1+MadVR+AMD Crimson 16.4.2, I previously use the last AMD Catalyst and so far it seems color reproduction was superb but now on AMD Crimson since the settings that control the video are not found/available in AMD Crimson, does MadVR ignores the hidden settings pre-defined by AMD Crimson?
Coz it seems using AMD Crimson colors aren't uniform as opposed to using AMD Catalyst since in I was able to turn off the unnecessary video settings in AMD Catalyst for MadVR.
And does MadVR still runs crap on Windows 10?
madVR is AFAIK only affected to the crimson video settings when using DXVA scaling or deinterlancing.
go to video select custom and set everything to off or 0. this should avoid if not all processing.
madVR works fine on windows 10.
Warner306
29th April 2016, 17:43
Is SuperRes at a value of 1 really worth it? I don't start to see the pop/feeling of depth until I put it at 2-3. I'm using it on 720p to 1080p. I also have a matte screen (maybe it's due to that) :D
What do you mean by ISF (Imaging Science Foundation) feel? I did quickly look it up, but I don't understand the reference
The idea is to take a 1080p source and downscale it to 720p. Then upscale the same image to 1080p. If you did this with image upscaling alone, the upscaled image would be too soft compared to the original 1080p source. In this case, image sharpening can be used to assist in resizing to add detail lost by upscaling.
Personally, I think SuperRes (1) at 720p -> 1080p is most faithful to the original image without being oversharpened, but this could vary based on the source and display. If want the image to be artificially sharp, use higher values of SuperRes.
Sunspark
29th April 2016, 18:04
Good practice to make sure the sharpness of the display itself is correct before looking to add sharpness in madvr. Lots of displays are oversharpened for some reason at default settings.
lagom.nl has a good sharpness pattern, it will look wrong in most browsers due to scaling just like the chroma test pattern in the first post of this thread, so just save the png image to a folder and open it in Paint instead where it will be correctly displayed at a pixel level. Then open the monitor's menu options and adjust the sharpness up and down until you can get it almost flat grey with your eyes slightly squinted. Of most value with VGA, but I do it with HDMI as well.
On madvr specifically, I noticed the other day that .90.17 is slower responding than .89.18 was in terms of stopping playback and then going to a black screen, or switching from fullscreen exclusive to windowed and back again.. there are longer delays with more visual artifacts (e.g. flickering seek bar, I have now disabled that as well or a momentary outline of the menus on the black background before being redrawn as black as well). I actually ended up having to uncheck the delay 3 seconds option which I didn't have to do before in .89.18.
Edit: I notice that hitting the space bar to start/pause playback when in FSE is showing a frame that has already played so you see a momentary flash of a previous frame before the regular stream continues. Not sure why it is momentarily showing a previous frame on unpausing. Flush settings for FSE are in order, flush, flush&wait (sleep), don't flush, don't flush. Should they be different? Or is this a bug?
MrBonk
30th April 2016, 02:08
What happened to the Mad VR settings explanation thread?
Warner306
30th April 2016, 03:09
What happened to the Mad VR settings explanation thread?
It was moved because of a lack of replies for an extended period of time. It still exists. I'll bump it now.
MrBonk
30th April 2016, 03:23
Oh well thanks. Why does it disappear completely though? Wouldn't it just be moved further down the list as it got less and less replies?
Since it's a resource of information for what does what. Seems like it would be a good idea to keep it visible no?
Patrik G
30th April 2016, 14:57
When I select 10,000 nit I need to see all the 64-940 range without madVR clipping, stretching, or compressing anything,
dont you need a tv with 10 bit panel to see steps above 255?
that panasonic plasma is only 8 bit right ?
sure it will be clipping.
get a 500M instead :)
true 10bit panel
Clammerz
30th April 2016, 16:05
Why does it disappear completely though?
Sorry for offtopic: look at the bottom of the sub-forum index page:
http://forum.doom9.org/forumdisplay.php?f=15
Take note of "from the" option (daysprune param.) Doesn't appear like you can change this in options. If you look at the sub-forum frequently maybe perhaps bookmark the page after setting the option you desire.
aufkrawall
30th April 2016, 16:29
Or just find it via Google.
Georgel
30th April 2016, 19:36
I was thinking of buying a laptop with desktop GPU GTX980. (Not 980M). My question regarding madVR, is: would an i7-6700K + GTX980 be able to run NNEDI at 256 Neurons and add edge sharpening + edge thinning + debanding + 4K upscaling with AR and sigmoidal light using Jinc ?
I am a bit curious if anyone tried, because I was thinking of getting a P870 from Clkevo, and while it is a power house of a laptop, I am afraid that for using madVR in these conditions, I should probably wait a bit more for the new generation of GPUs to appear. Especially that I will be always upscaling FHD to 4K.
sat4all
30th April 2016, 19:49
Any idea why madvr dxva image upscaling is clipping btb and wtw? gpu 0-255, madvr and tv 16-255.
I'm forced to dxva upscaling for 1080p24 > 2160p24 bcs of my intel nuc performances.
baii
30th April 2016, 19:52
I was thinking of buying a laptop with desktop GPU GTX980. (Not 980M). My question regarding madVR, is: would an i7-6700K + GTX980 be able to run NNEDI at 256 Neurons and add edge sharpening + edge thinning + debanding + 4K upscaling with AR and sigmoidal light using Jinc ?
I am a bit curious if anyone tried, because I was thinking of getting a P870 from Clkevo, and while it is a power house of a laptop, I am afraid that for using madVR in these conditions, I should probably wait a bit more for the new generation of GPUs to appear. Especially that I will be always upscaling FHD to 4K.
256 neuron luma nnedi3? No, let alone all the enhancement.
With no enhancement a 980ti / fury x can do 128 for 1080p while gimping everything else. Anyways, cramping all the option on doesn't always make it "look better".
Btw, if you push the gpu hard on laptop, the fan noise can be pretty annoying unless you have headphone on all time.
huhn
30th April 2016, 19:53
dont you need a tv with 10 bit panel to see steps above 255?
that panasonic plasma is only 8 bit right ?
sure it will be clipping.
get a 500M instead :)
true 10bit panel
plasma are technically 1 bit and noisy compared to LCD screens.
and of cause you don't need more bit deep to show steps higher than x that's not how this works.
aufkrawall
30th April 2016, 20:04
I was thinking of buying a laptop with desktop GPU GTX980. (Not 980M). My question regarding madVR, is: would an i7-6700K + GTX980 be able to run NNEDI at 256 Neurons and add edge sharpening + edge thinning + debanding + 4K upscaling with AR and sigmoidal light using Jinc ?
1080p NNEDI3 32 doubling already requires much performance, GTX 980 can do 1080p 30fps NNEDI3 64 doubling + some very lightweight postprocessing at most. When you output 4k resolution, deband with max quality isn't low on resources either and neither is sharpen edges.
Don't buy an expensive notebook now, probably already in June or July you can buy notebooks with Polaris 10 or GP104/106 GPU which will be a huge technology update in general over current GPUs (HEVC 10 bit, HDR, Display Port 1.3...).
Uoppi
30th April 2016, 20:15
The only other option is madVR 16-235 and the GPU full, but this clips your desktop.
This is the recommended combination if desktop colors are of no concern, right?
I'm getting confused once again because some on the other hand say to use madVR full and GPU full.
I have madVR limited, GPU full and HDMI black level "low" on my Samsung TV (can't remember if low meant full or limited but I'm guessing low = full). Can someone confirm if this is opimal? Black levels look alright on test clips at least.
baii
30th April 2016, 20:25
yet Another TV color range question, so confusing grr
Samsung TV hdmi in
Intel HD
I have full range gpu, pc mode tv (should be full IDK...), hdmi normal, madvr set to full, AVS hd709 black clipping flashing at 17+.
hdmi low with full on gpu will crush black. (no flash)
Does this sound right~?
And 1080p 59hz vs 60hz?
I hate TV...
seems like I am on the same boat like uoppi,lols.
edit
Going to go with this~~ from AVS zoyd
http://www.avsforum.com/forum/139-display-calibration/1966746-help-calibrating-samsung-tv-rgb-full-limited.html#post33427002
For me would be the second one.
trueunborn
30th April 2016, 21:58
Hi all, Got the 3D player working great with Latest LAV and Mavr but Reclock does not detect correctly the refresh rate that MAdVr is forcing. Reclock thinks it is 24hz while MAdvr forces 23hz (x2 in reality...)... the result is a lot of dropped frames. Tried a lot of things with no luck.Any idea?
BTW, I have an nvidia card with drivers 364,47.
JamPS
30th April 2016, 22:21
...Reclock thinks it is 24hz while MAdvr forces 23hz (x2 in reality...)... the result is a lot of dropped frames. Tried a lot of things with no luck.Any idea?
Try setting ReClock on manual fps.
Warner306
30th April 2016, 22:34
This is the recommended combination if desktop colors are of no concern, right?
I'm getting confused once again because some on the other hand say to use madVR full and GPU full.
I have madVR limited, GPU full and HDMI black level "low" on my Samsung TV (can't remember if low meant full or limited but I'm guessing low = full). Can someone confirm if this is opimal? Black levels look alright on test clips at least.
I'd set everything to full range so desktop levels remain accurate and the GPU doesn't have to do a range conversion for the display -- after madVR, the output is straight passthrough.
Your configuration is considered optimal because madVR doesn't clip anything and all output is passed-through as is to the display. But I doubt it has any real advantage over setting everything full range; especially when your desktop levels will be off and look distracting.
Can anyone claim superiority for setting madVR to 16-235?
Asmodian
30th April 2016, 23:12
Can anyone claim superiority for setting madVR to 16-235?
There is some banding introduced by expanding 16-235 to 0-255 but madVR's dithering prevents this being an issue (it results in extra dither noise instead of banding), at least on most displays.
Warner306
30th April 2016, 23:53
There is some banding introduced by expanding 16-235 to 0-255 but madVR's dithering prevents this being an issue (it results in extra dither noise instead of banding), at least on most displays.
If the display is set to 16-235, does it clip 0-15 or 236-255? I'm still editing this section in my own guide.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.