Devices > Video Cards, Monitors, Televisions, and Projectors
madVR Guide
6233638:
--- Quote from: alyupb on April 29, 2013, 11:51:26 am ---Hello, thanks for the guide 6233638!
Any idea if MadVR will perform colorspace transformations on SD content when using the "calibrate this display by using yCMS" option? (or is it exclusive to "this display is already calibrated"?)
--- End quote ---
I think yCMS assumes you are calibrated to a BT.709 target, so the colorspace transformations should still work.
Hit Ctrl+Alt+Shift+P to see if they do. (you will receive an error message if they don't)
More than just SD content, an example of where this is useful in my experience is newer releases of Office Space.
That film appears to be using SMPTE-C primaries encoded as BT.709 (at least my disc is) so everyone looks red in the face until you correct it with that shortcut. (or append primaries=smptec to the filename)
mdav:
--- Quote from: 6233638 on April 29, 2013, 07:54:59 am ---Regardless of what your display accepts, whether it is 16–235 or 0–255, it should be left at 0–255 to avoid having the image appear “washed out”.
Typically if you need to send 16–235 to a display, you will use the video card output to set that, not the video renderer.
--- End quote ---
I think nevcairiel suggested preferably setting madVR to output 16-235 (when your display only support 16-235) in this thread http://yabb.jriver.com/interact/index.php?topic=77540.msg527128#msg527128 and "For NVIDIA always set stuff to "Use video player settings", and madVR should output stuff untouched".
6233638:
--- Quote from: mdav on April 29, 2013, 02:22:26 pm ---I think nevcairiel suggested preferably setting madVR to output 16-235 (when your display only support 16-235) in this thread http://yabb.jriver.com/interact/index.php?topic=77540.msg527128#msg527128 and "For NVIDIA always set stuff to "Use video player settings", and madVR should output stuff untouched".
--- End quote ---
Nevcariel's advice is good, in that it avoids double expansion/compression.
And if you want the absolute best image quality for video alone, having the graphics card output 0-255 and madVR output 16-235, when the display only supports 16-235, should in theory produce better results.
But if you do that, everything on the computer outside of madVR is going to have severe highlight and shadow clipping, as it's being rendered to 0-255 and the display is only showing 16-235 from that.
If you have madVR output 0-255 so that it matches the desktop (the desktop and other applications are always 0-255) and then have the video card compress the 0-255 output to 16-235, you avoid that shadow/highlight clipping - but you are potentially introducing posterization/banding from the levels compression. (255 steps compressed to 219)
Neither solution is ideal - ideally, you would have a display that properly displays an 0-255 input.
But in my opinion, having madVR output 0-255 and letting the video card compress the levels is the better compromise in most cases - I think it's rare that people going to use their system exclusively for video playback.
Z0001:
I am currently looking at getting a new av reciever so I have been thinking about how all the audio and video is decoded, processed and sent down the wires from the pc to the reciever and on to the tv. So my question is what processes are happening at each stage in each device. Eg is video only rendered in the pc using madVR, or can the reciever do it? If anyone has a good reference text on the process blocks and how digital content is converted and finally presented to my eyes and ears, for the lay enthusiast, I would find that very useful.
Thank you
mojave:
--- Quote from: 6233638 ---The main downside to Fullscreen Exclusive mode is that when switching in/out of FSE mode, the screen will flash black for a second. (similar to changing refresh rates) Most of Media Center's OSD is rendered in such a way that it would not be visible in FSE mode, so madVR gets kicked out of FSE mode any time you use MC's interface and you get that black flash on the screen. I personally find this distracting, and as such, have disabled FSE mode, because I don't need the additional performance for smooth playback on my computer. (I have an Nvidia GTX 570)
--- End quote ---
--- Quote ---Delay switch to exclusive mode by 3 seconds. If your media player switches into fullscreen mode, and FSE is enabled, it will always switch instantly.
This option is for when something such as Media Center's UI breaks FSE mode and kicks it into Windowed Mode. If the option is enabled, it will wait 3 seconds before going back into FSE mode, rather than switching instantly.
This can be useful if you are going to make a couple of changes, such as switching subtitle track, and adjusting its size and position, without it going in/out of FSE mode each time you bring up the menus.
--- End quote ---
Thanks for writing up the guide. It clarified several things I had wondered about.
JRiver has two OSD's: a 10' interface that works in FSE and one that is primarily used when sitting in front of a monitor. The one that works in FSE is activated by a down or up arrow and provides access to titles, chapters, subtitles, size, position, and other settings. The windowed mode OSD you bring up by right clicking contains a few more options for aspect ratio and cropping. I use FSE on two computers and have found the FSE compatible OSD to be suitable 99% of the time. Your statements sound like you can't use an OSD at all with JRiver in FSE without being kicked out of FSE and into Windowed Mode and that isn't true.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version