View Full Version : madVR - high quality video renderer (GPU assisted)
pie1394
15th March 2013, 04:54
Hi, I figured out what was wrong.
In order Nvidia high speed processor to be used at Jinc, the laptop must be charging. Not possible to nvidia to handle Jinc whilst laptop is on battery, even at simple tv rips of 720p I experience constant frame drops.
Sorry I didn't figure it out sooner. Kind of odd though as it can handle with ease Bicubic and Lanczos on battery.
Can anyone confirm that? Is there a workaround?
How about creating a 3D profile for media player (which uses madVR) application ?
Set it to "performance" + "VSync ON", and disable all other AA / texture filtering options, etc...
The recent nVidia GPU driver since 304.xx adaptively controls the GPU's frequency depending on measured loading. The driver does not 100% honor the OS power management settings any more. This behavior is described in the driver's release note.
To be honest, I cannot tell the difference between Lanczos3_AR and Jinc3_AR on 1280x720 anime content with 1920x1080 10-bit output signal to Sony 65HX920. (with super-resolution 50% , SBR on)
leeperry
15th March 2013, 05:38
Aside form all its prowess, it uses 145 Watts for a 25" monitor; Thats a lot.
Weren't we all told that OLED TV's/Monitors would use little energy?
Yeah and the manual mentions a fan too :/
Anyway, you can get OLED for a grand right here right now and it natively supports 720p@24Hz too: http://www.avsforum.com/t/1426822/ :cool:
6233638
15th March 2013, 14:17
Yeah and the manual mentions a fan too :/It's a high end broadcast monitor, not a consumer-grade display.
Anyway, you can get OLED for a grand right here right now and it natively supports 720p@24Hz too: http://www.avsforum.com/t/1426822/ :cool:These are terrible - the only thing they do well is 3D, and they require modification to be comfortable.
Niyawa
15th March 2013, 20:18
Good to know you figured out the issue artios, turned out to be more simple than we thought. I have one more question for everyone, this I'm really lost since I have no idea what could cause it.
"I cant seem to get the "CUVID Hardware/GPU Deinterlacing" to work. I set it to "Enable Adaptive HW Deinterlacing" and set it to the "50p/60p (Video)" option as well as enabled "high-Quality Processing". I'm running a Nvidia 670 so i know it is not a horsepower issue. I more want to just see if the video playback is smoother since it ups the videos to 60fps. Anyone know how to get this working?"
I know any sort of hardware acceleration won't work with 10-bit, but it doesn't really seem to be the case there, so I'm also asking for directions in that one. Any help is appreciated as always. Oh- I also did a search in the forum and around Google before asking, so I'm fairly confident this is a "new" issue. Both of them are using KCP pack which has madVR (0.86.1), LAV Filters (0.55.3), and MPC-HC lite.
oddball
16th March 2013, 04:48
Anyone able to save images in MPC-HC with this version of MadVR? I am using latest LAV filters too. All I get is a blank image. I have to switch to EVR to cap a still. Overlay is unticked btw (read back a bit).
Nvidia latest drivers and GTX560Ti
hevulo
16th March 2013, 05:45
Anyone able to save images in MPC-HC with this version of MadVR? I am using latest LAV filters too. All I get is a blank image. I have to switch to EVR to cap a still. Overlay is unticked btw (read back a bit).
That happens when you have smooth motion turned on and view the video with no scaling (100% zoom). Resizing the player window or turning off smooth motion should allow you to take screenshots until this bug is fixed.
corporalgator
16th March 2013, 06:04
I saw there was a discussion a few pages back about the most power friendly setup for madvr, but what about lav set to intel quicksync while using a discrete graphics card to handle the upscaling?
I ask because the stupid intel integrated graphics causes blue screens a lot if I turn off my tv since the dummy monitor then takes over and doesn't know what to do when I turn the tv on. This has been an ongoing issue through several drivers, different versions of windows installs and several clean ones at that.
If using dxva is better, then I may just turn off the integrated graphics altogether. Does anyone know?
pie1394
16th March 2013, 06:06
"I cant seem to get the "CUVID Hardware/GPU Deinterlacing" to work. I set it to "Enable Adaptive HW Deinterlacing" and set it to the "50p/60p (Video)" option as well as enabled "high-Quality Processing". I'm running a Nvidia 670 so i know it is not a horsepower issue. I more want to just see if the video playback is smoother since it ups the videos to 60fps. Anyone know how to get this working?"
I know any sort of hardware acceleration won't work with 10-bit, but it doesn't really seem to be the case there, so I'm also asking for directions in that one.
With the DXVA-compatible MPEG-2 / H.264 interlaced streams, everything just works fine on my mini-pc server's ION chipset. (Win7x64, GeForce 314.07, LavFilter 0.55.3, madVR 0.86.1, MPC-BE 1.1.0.1b2172)
Although it is not HW limitation, I don't think the CUDA deinterlacing function can be independently used while CUDA video decoder is NOT used. Just curious if nVidia CUDA SDK actually allows it or not...
Niyawa
16th March 2013, 07:05
With the DXVA-compatible MPEG-2 / H.264 interlaced streams, everything just works fine on my mini-pc server's ION chipset. (Win7x64, GeForce 314.07, LavFilter 0.55.3, madVR 0.86.1, MPC-BE 1.1.0.1b2172)
Although it is not HW limitation, I don't think the CUDA deinterlacing function can be independently used while CUDA video decoder is NOT used. Just curious if nVidia CUDA SDK actually allows it or not...
Hmm. I guess that would make sense for a certain perspective. Thanks for input.
DragonQ
16th March 2013, 11:53
I saw there was a discussion a few pages back about the most power friendly setup for madvr, but what about lav set to intel quicksync while using a discrete graphics card to handle the upscaling?
I can't imagine running 2 GPUs being power efficient.
huhn
16th March 2013, 12:01
I can't imagine running 2 GPUs being power efficient.
this makes sense for really powerfull gpu using dxva on an 680 gtx resultants in a high power state while normal madvr scailing is not that demanding and the gpu stays a a lower powerstate.
the igpu is allways very low even under full load.
6233638
16th March 2013, 12:43
this makes sense for really powerfull gpu using dxva on an 680 gtx resultants in a high power state while normal madvr scailing is not that demanding and the gpu stays a a lower powerstate.CUVID will do this, DXVA should not. (note: you should use copy-back, not native DXVA)
nevcairiel
16th March 2013, 12:53
DXVA forces the GPU into (at least) medium power state, iirc.
Might be GPU dependent.
kasper93
16th March 2013, 13:54
I would love option to lock my GPU on medium power state. It works great with DXVA, but I don't want to use DXVA... and without it GPU runs in full power which is highly power consuming ;|
DragonQ
16th March 2013, 14:55
You can do that using nVidia Inspector I think (if you have an nVidia card of course). My GT430 isn't powerful enough for HD playback using CUDA unless it's in the highest power state though so it was useless for me. I use DXVA2 Native now anyway.
huhn
16th March 2013, 15:21
u can create for amd a profile with max clock people use this to force the max power state u can use this to force medium power state.
this does not work with every card my 6770 stays always at medium power state as long as dxva is in use. i don't know about other cards with the same "problem".
6233638
16th March 2013, 15:27
DXVA forces the GPU into (at least) medium power state, iirc.
Might be GPU dependent.That's true, but I don't think the GPU will drop down into the low power (P12) state when playing videos regardless of GPU load though.
The only way I have been able to do that, is to force the card into the low power state with Nvidia Inspector, but that can cause other problems.
At least, that's what I have found when using CPU decoding and testing with very low resolution (non-demanding) videos played at 100% size. Even when GPU load is below 5%, it never drops down from the medium (P8) power state, into the low (P12) state.
You really do need to measure these things with some kind of meter though, as it's easy to assume something will lower power consumption when it may not. If the GPU is going to be stuck in the P8 state regardless, it might be more efficient to use DXVA than QuickSync - even if QuickSync should technically be more efficient than DXVA decoding.
If CUVID forces your video card into the full power (P0) state unnecessarily, then it may actually be more efficient to use CPU decoding for example. (though I would recommend DXVA)
I would love option to lock my GPU on medium power state. It works great with DXVA, but I don't want to use DXVA... and without it GPU runs in full power which is highly power consuming ;|Why is it that you don't want to use DXVA?
corporalgator
16th March 2013, 15:54
Thanks for the replies everyone. I'll order a kill-a-watt and test it directly and let everyone know how it turns out.
JarrettH
16th March 2013, 17:52
Interesting, I tested out the CPU vs GPU decoding yet again, and my result was, since I mostly play 720p upscaled, it makes little difference and that CPU decoding has a slight edge. I balanced out my upscaling settings with Jinc+Jinc instead of Jinc+Bicubic as a result :)
kasper93
17th March 2013, 01:50
Why is it that you don't want to use DXVA?
Well, I have AMD GPU :scared: L3.1 is completely broken and generally DXVA is not stable as software decoding.
G_M_C
17th March 2013, 09:33
Chipping in on the DXVA /power usage / performance discussion:
My PC has a Q9650 CPU and ive fitted an MSI PE HD7850, coming from a HD5770. The CPU runs on stock speeds. I also make use of an SSD and low-RPM / green data drives. I output via HDMI to my receiver, which has a Panasonic plasma connected to it.
I'v downclocked and downvolted the GPU. This way it uses less energy. Accoring to my measurements the power usage of the downclocked 7850 is about the same as my 5770 used. This is because the HD7xxx series has much more performance/watt, uses almost no power in idle mode and of course the downclocking/downvolting.
In my installation is LAV filters/madVR/MPC-HT.
I have LAV filters installed and use CPU decoding only, and have madVR use the GPU for itself. This has several advantages:
Firstly LAV in CPU mode is -to me at least- a 'set-and-forget' installation. It always works, decodes everything I have which also inclused high-bitdepth encodes. It is rock stable for me.
Secondly software decoding is efficient to such a degree that my (not to recent) CPU doesn't even flex. That means the CPU doesn't need to be full-on, and as a result uses less energy and doesn't run hot.
On top of that this means that madVR can use the GPU for itself.
The GPU swithes to the downclocked/downvolted '3d-speed profile', without having DXVA interfering as some of the above have seen happen.
And even when downclocked/downvolted, my GPU hasn't been over 63% usage (43 degrees c and 35% fanspeed = no noise). And that was when testing a 1080i50 BBC-HD capture and madVR deinterlacing plus smoothmotion, using jinc 3 + AR (chroma) jinc 4 + AR (image) resulting in a 1080p50. A configuration/situation not often used to be honest (smoothmotion has no advantage here imho). [added] In normal situations GPU usage is approx 30%-40%.
My conclusion is that using CPU decoding and a relatively recent GPU is a good option. You can control both through BIOS and other tools, set their speeds/powerusage to your needs individually. Imho this is the easiest '-works-without-having-to-think-about-it-even-my-girlfriend-can-do-it-' installation you can have.
Dodgexander
17th March 2013, 09:54
Chipping in on the DXVA /power usage / performance discussion:
My PC has a Q9650 CPU and ive fitted an MSI PE HD7850, coming form a HD5770. The CPU runs on stock speeds. I also make use of an SSD and low-RPM / green data drives. I output via HDMI to my receiver, which has a Panasonic plasma connected to it.
I'v downclocked and downvolted the GPU. This way it uses less energy. Accoring to my measurements the power usage of the downclocked 7850 is about the same as my 5770 used. This is because the HD7xxx series has much more performance/watt, uses almost no power in idle mode and of course the downclocking/downvolting.
In my installation is LAV filters/madVR/MPC-HT.
I have LAV filters installed and use CPU decoding only, and have madVR use the GPU for itself. This has several advantages:
Firstly LAV in CPU mode is -to me at least- a 'set-and-forget' installation. It always works, decodes everything I have wich also inclused high-bitdepth encodes. It is rock stable for me.
Secondly software decoding is efficient to such a degree that my (not to recent) CPU doesn't even flex. That means the CPU doesn't need to be full-on, and as a result uses less energy and doesn't run hot.
On top of that this means that madVR can use the GPU for itself.
The GPU swithes to the downclocked/downvolted '3d-speed profile', without having DXVA interfering as some of the above have seen happen.
And even when downclocked/downvolted, my GPU hasn't been over 63% usage (43 degrees c and 35% fanspeed = no noise). And that was when testing a 1080i50 BBC-HD capture and madVR deinterlacing plus smoothmotion, using jinc 3 + AR (chroma) jinc 4 + AR (image) resulting in a 1080p50. A configuration/situation not often used to be honest (smoothmotion has no advantage here imho).
My conclusion is that using CPU decoding and a relatively recent GPU is a good option. You can control both through BIOS and other tools, set their speeds/powerusage to your needs individually. Imho this is the easiest '-works-without-having-to-think-about-it-even-my-girlfriend-can-do-it-' installation you can have.
Agreed
Sent from my Blade S using Tapatalk 2
ryrynz
17th March 2013, 13:25
Anyone had a random black frame appear whilst playing? I'm running Overlay and FSE with Smooth motion on an Intel HD 3000 using 2932 drivers. Seems to be the same thing that TheShadowRunner mentioned with switching between windowed and FSE mode although it happens after some extended viewing for me. I've got a number of things to rule out but I think I'll start with flushing settings, just wondering if any sharp eyed viewers have seen the same thing and fixed it.
DragonQ
17th March 2013, 15:33
Yes it happens occasionally when using Smooth Motion for me.
olli66
17th March 2013, 15:39
hi guys,
there are so many threads about this topic...hard to get an overview...so I hope you don't mind me asking some questions that may have been asked and answered many times before....
Even after a lot of research i don't quite understand the thing with the color range. I have a Panasonic VT20. I assume via HDMI it has limited color range. So I set my AVR to limited. madvr to limited and normally I would have thought I set my NVIDIA controls to limited, too. But I heard to set the desktop color range to full. Is this correct? Will madvr work best this way and the colors will be correct?
Next issue I still don't quite understand. My mkvs finally run smoothly after setting up madvr. Now my display automoatically switches to 1080p/24, 1080p/23, for my recordings with camcoder to 1080p/50 and so on. Finally mkv movies play smoothly. But several times when watching a movie there is a little "skip" in the picture. No dropped frame or something like this. Just a picture seems to be missing. What causes this and how could it be fixed?
I read a lot about the upscaling functions. Still don't know which settings are best and most recommended. Also there was one thing with further color correction but this seemed quite complicated...are there any "easy" guides or do I need a color measuring device for this procedure?
thanks for your tips
huhn
17th March 2013, 16:24
hi guys,
there are so many threads about this topic...hard to get an overview...so I hope you don't mind me asking some questions that may have been asked and answered many times before....
Even after a lot of research i don't quite understand the thing with the color range. I have a Panasonic VT20. I assume via HDMI it has limited color range. So I set my AVR to limited. madvr to limited and normally I would have thought I set my NVIDIA controls to limited, too. But I heard to set the desktop color range to full. Is this correct? Will madvr work best this way and the colors will be correct?
Next issue I still don't quite understand. My mkvs finally run smoothly after setting up madvr. Now my display automoatically switches to 1080p/24, 1080p/23, for my recordings with camcoder to 1080p/50 and so on. Finally mkv movies play smoothly.
first of all put ur avr to direct untouched or what ever the name is.
if ur display is a limited range display u have two options.
1. put the madvr output to unlimited and set the graphic card to limited. now the desktop and the video are limited und totally fine but the video was changed from limited to unlimited to limited.
2. put the madvr output to limited and set the graphic card to unlimited. now ur desktop colors are wrong becource ur tv ignores the the extra informations in the unlimited stream but the video is fine and was never changed from limited to unlimited this is a little bit better then option 1.
if ur display is unlimited.
put madvr to unlimited and the graphic card desktop and video is now fine.
same tv can handle both unlimited and limited for exsample my philiphs tv needs unlimted in pc mode and limited in the rest. try a test picture like this http://i155.photobucket.com/albums/s297/mikeyurkus/0-255BWDVD.png
I read a lot about the upscaling functions. Still don't know which settings are best and most recommended.
jinc 3 ar for both is recommended if ur card can handle it. but it is all about taste so u have to figure this out by ur self.
after long time of trouble shooting finally I found why madvr was never working
madVR 0.79 (and older versions) give me error "creating Direct3D device failed (8876086a)"
madVR 0.80 .. 0.86.1 just black screen (no video, nor error message), and mpc-hc freeze computer after I try to close it
solution (win2003 r2 x86) :
[win]+[r] dxdiag > display > enable acceleration
I suggest to add some information to readme file, and may be fix this 0.80 regression (not showing any error like 0.79 and older versions)
Ihmemies
17th March 2013, 23:06
I once had problems updating from older madvr (mpc-hc crashing instantly), finally tried "reset to default settings.bat" and it solved the problem.
Smooth motion looks very nice, I have a 60Hz 30" 2560x1600 display and I don't notice judder anymore. I earlier used a terrible avisynth script which did some frame blending, but the results looked especially bad with checkered shirts and some other stuff. I saw no ghosting with smooth motion enabled, maybe it's there but it's nothing compared to what I had with the avisynth script.
Since I need to upscale all videos and original pixels are lost I didn't notice any sharpness difference between smooth motion on/off. But I will definitely keep it always on because movies are unwatchable with 3:2 pulldown.
About GPU usage, I have HD6970 and without smooth motion I get ~21%, with ~27%. So basically no difference with gpu usage (as long it's under 99% I suppose it makes no difference) but very much improved motion quality.
Thanks for the great update and keep up the good work :)
Edit: for the first time I looked at madvr's osd and noticed there's one fropped frame every 30.04 - 30.06s, so roughly 0,14% of frames get dropped. I don't know what causes this but at least that isn't visible while watching videos :)
corporalgator
18th March 2013, 06:48
According to Madshi, you should set the video card to full then madvr and the tv to limited. That lets you get black at 16 since Blu-rays don't go lower than that anyway, but also whiter than white that some blu-rays do have.
Madshi: I experienced a really weird issue. I finally decided to just disable my igpu since I was tired of all the blue-screens losing intel quicksync for decoding through lav and going with dxva copy-back. When I then went to play a video, I got horrible frame drops for a minute or so before the screen would turn green. I finally found the problem to be use a separate device for dxva processing. When I disabled it, everything went back to normal with no frame drops.
olli66
18th March 2013, 08:44
thanks guys, so I was right to set my NVIDIA desktop to full range and madvr to limited for best video playback (I don't care about desktop colors)
but what happens with these settiings if I use other software for playback? (Powerdvd for example)
also I could not find an option in my AVR that says "untouched", there is just limited and full color range so I put it to limited...
DarkSpace
18th March 2013, 13:06
also I could not find an option in my AVR that says "untouched", there is just limited and full color range so I put it to limited...
In that case, why don't you set the it to full color range?
That way, you won't crush desktop colors, and you can set madVR to output full color range as well.
but what happens with these settiings if I use other software for playback? (Powerdvd for example)
Well, if you use the current setup, PowerDVD will most likely produce crushed color output to the TV. All will work, however, if you do as I suggested above and set everything to use the full color range.
olli66
18th March 2013, 14:44
when I set my AVR to full color range but my TV cannot display full color range then my tv will crush the colors from my understanding?
corporalgator
18th March 2013, 15:18
when I set my AVR to full color range but my TV cannot display full color range then my tv will crush the colors from my understanding?
Yes, you want Madvr outputting limited. I used to have everything at full because my TV supported it, but then I lost whiter than white and blacks weren't what they were supposed to be.
Computer at full and everything else limited is the way to go. Once you set it up, grab some calibration slides, like these
http://www.avsforum.com/t/948496/avs-hd-709-blu-ray-mp4-calibration
and dial in black so that everything below 16 disappears and then get whites so you seesome above 235.
DragonQ
18th March 2013, 15:39
Why do BDs have WTW but not BTB? I thought the whole point was that either 0-255 or 16-235 was used, why would a mixture be used?
corporalgator
18th March 2013, 15:58
Why do BDs have WTW but not BTB? I thought the whole point was that either 0-255 or 16-235 was used, why would a mixture be used?
There's some debate as to whether the information is actually useful. Read this thread starting here:
http://www.avsforum.com/t/1240153/setting-contrast-with-spears-and-munsil-disc/420#post_18599222
You can just set it to 235 for white if you like.
olli66
18th March 2013, 16:13
thanks! just to be 100 percent sure: with "computer" you mean I should set NVIDIA control panel to full? how about my avr? my htpc goes into my avr and my avr outputs everything to my HDTV
those calibration slides are still needed when everything is set this way? is it for checking if everything is right or do I need to manually adjust some settings? how about powerdvd? I need madvr and powerdvd to run with correct color range without having to switch settings each time...
Yes, you want Madvr outputting limited. I used to have everything at full because my TV supported it, but then I lost whiter than white and blacks weren't what they were supposed to be.
Computer at full and everything else limited is the way to go. Once you set it up, grab some calibration slides, like these
http://www.avsforum.com/t/948496/avs-hd-709-blu-ray-mp4-calibration
and dial in black so that everything below 16 disappears and then get whites so you seesome above 235.
corporalgator
19th March 2013, 04:14
thanks! just to be 100 percent sure: with "computer" you mean I should set NVIDIA control panel to full? how about my avr? my htpc goes into my avr and my avr outputs everything to my HDTV
those calibration slides are still needed when everything is set this way? is it for checking if everything is right or do I need to manually adjust some settings? how about powerdvd? I need madvr and powerdvd to run with correct color range without having to switch settings each time...
Yeah Nvidia to full, everything else limited. The calibration will be through changing the settings directly on your tv: brightness, contrast, etc.
This will leave your desktop colors crushed, but it's the trade-off for getting the correct colors out of movies.
6233638
19th March 2013, 07:48
That is completely wrong. There is nothing useful below black or above white. At most there will be specular highlights, which are not detail, and often what you will see is sensor noise/saturation, which should definitely not be visible.
Valid video ranges are 16-235. If you are using the PC for anything other than video playback, it will also give you the perception that video looks dull if you do this, because video white will be at a much lower level than white on the desktop.
In the madVR device properties, output should be set to PC levels (0-255) regardless of what levels your display accepts. What this option does, is fix the video levels to match your desktop output levels. It does this by discarding below black and above white - but that does not contain picture content, and is no longer even necessary for display calibration with flat panels. (only necessary with CRT)
If your display accepts it, you should send it a full range 0-255 signal via HDMI. Most displays will have a "video levels" or "black level" option if they support this - I can't think of anything that automatically switches and does not have a manual override. So if your TV doesn't have the option, it probably doesn't support it.
With Nvidia, the card will output a limited range 16-235 signal when connected via HDMI unless the display explicitly states that it can support a 0-255 signal. My Sony TV does, but it seems that most do not. There is no driver setting for this, but madNvLevelsTweaker.exe inside the madVR folder can force a 0-255 output if your display supports it.
The reason that you want to output 0-255 to the display is because everything on your PC is natively 0-255, and the 16-235 output from the card compresses the levels (rather than clipping them) which can introduce banding, because there are fewer levels of gradation.
Even if you are outputting 16-235 to your display through the graphics card, madVR itself should still be set to 0-255, as this matches the video levels to the desktop levels. As the desktop levels are being compressed to 16-235 in this case, it means that video is contained within the 16-235 range.
truexfan81
19th March 2013, 08:56
That is completely wrong. There is nothing useful below black or above white. At most there will be specular highlights, which are not detail, and often what you will see is sensor noise/saturation, which should definitely not be visible.
Valid video ranges are 16-235. If you are using the PC for anything other than video playback, it will also give you the perception that video looks dull if you do this, because video white will be at a much lower level than white on the desktop.
In the madVR device properties, output should be set to PC levels (0-255) regardless of what levels your display accepts. What this option does, is fix the video levels to match your desktop output levels. It does this by discarding below black and above white - but that does not contain picture content, and is no longer even necessary for display calibration with flat panels. (only necessary with CRT)
If your display accepts it, you should send it a full range 0-255 signal via HDMI. Most displays will have a "video levels" or "black level" option if they support this - I can't think of anything that automatically switches and does not have a manual override. So if your TV doesn't have the option, it probably doesn't support it.
With Nvidia, the card will output a limited range 16-235 signal when connected via HDMI unless the display explicitly states that it can support a 0-255 signal. My Sony TV does, but it seems that most do not. There is no driver setting for this, but madNvLevelsTweaker.exe inside the madVR folder can force a 0-255 output if your display supports it.
The reason that you want to output 0-255 to the display is because everything on your PC is natively 0-255, and the 16-235 output from the card compresses the levels (rather than clipping them) which can introduce banding, because there are fewer levels of gradation.
Even if you are outputting 16-235 to your display through the graphics card, madVR itself should still be set to 0-255, as this matches the video levels to the desktop levels. As the desktop levels are being compressed to 16-235 in this case, it means that video is contained within the 16-235 range.
and yet it looks better when forced to 16-235 :rolleyes:
6233638
19th March 2013, 08:58
and yet it looks better when forced to 16-235 :rolleyes:Please post examples of content that has meaningful information above 235 if you have them.
rahzel
19th March 2013, 09:05
and yet it looks better when forced to 16-235 :rolleyes:
It does not. Everything 6233638 said is correct.
nevcairiel
19th March 2013, 09:49
and yet it looks better when forced to 16-235 :rolleyes:
If it does, then your system is either setup to only work with 16-235, or doesn't properly support full-range content.
DragonQ
19th March 2013, 11:36
So when using EVR, it's best to keep everything at 16-235 to avoid the nasty truncation and banding brought about by conversion to 0-255, right? MadVR presumably doesn't have this problem with the higher bit depth used for conversions, so 0-255 makes more sense (matches desktop graphics).
6233638
19th March 2013, 14:11
So when using EVR, it's best to keep everything at 16-235 to avoid the nasty truncation and banding brought about by conversion to 0-255, right? MadVR presumably doesn't have this problem with the higher bit depth used for conversions, so 0-255 makes more sense (matches desktop graphics).I can't speak for EVR, but yes, madVR uses more than enough precision to eliminate any problems with levels expansion from 16-235 to 0-255.
huhn
19th March 2013, 14:31
Please post examples of content that has meaningful information above 235 if you have them.
it's possible with pc game content i try to make a sample later but i never tryed something like this. normal capture software allways change the input rgb 0-255 to yua 4:2:0 16-235.
but does this even matter i mean madvr will see the stream information and everything will be correct...
6233638
19th March 2013, 14:55
it's possible with pc game content i try to make a sample later but i never tryed something like this. normal capture software allways change the input rgb 0-255 to yua 4:2:0 16-235.
but does this even matter i mean madvr will see the stream information and everything will be correct...Oh, no need for a sample of that. Game footage will be 0-255, but it will be handled correctly.
What I meant is that in commercial content (e.g. films) there should be no meaningful content (if anything) above 235.
olli66
19th March 2013, 18:12
this leads to my next question...desktop better set to rgb or yuv?
it's possible with pc game content i try to make a sample later but i never tryed something like this. normal capture software allways change the input rgb 0-255 to yua 4:2:0 16-235.
but does this even matter i mean madvr will see the stream information and everything will be correct...
LigH
19th March 2013, 18:37
Will the OSD ever be configurable? It is so huge in MPC-HC.
dansrfe
19th March 2013, 18:54
The OSD is pretty small if the resolution of your desktop and MPC-HC is of reasonable size relative to the resolution of monitors today.
LigH
19th March 2013, 19:02
But if I start a CIF resolution video, already the filename hardly fits in the window, as long as I don't maximize the window.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.