(2018-04-05, 06:51)nayef Wrote: but it working with dsplayer jarvis 16

(2018-04-05, 13:54)netguru Wrote: Hi,

two questions.
1) I installed DsPlayer without PVR addons, how to install them later on, without wiping Kodi Data? Installing nextpvr etc is not possible ...
2) new LAV Filter nightly is out, how to update my lav filter, there is only an .exe file? (without losing my Settings)

(2018-04-05, 17:07)Warner306 Wrote:

(2018-04-05, 06:28)mkohman Wrote:

(2018-04-05, 06:20)Warner306 Wrote:  For responsiveness, you want to set the desktop to 60hz. You could set it to 23hz, but Kodi will be very laggy. It could also be that refresh rates changes are causing this problem, but I wouldn't give it up until I had to. Changing refresh rates from 60hz and back again is normal for a HTPC. You can't choose 10-bits at 60hz because HDMI 2.0 doesn't support this spec. But you can choose 10-bits at 23hz (or 10-bits at 30hz for that matter).

I don't know what your gamma is, but I can guess it is 2.40. This is only important when doing HDR -> SDR conversions.

Don't know anything about the power supply. Your GPU seems to be performing alright.   

Thank you so much. I will keep it at 60 hz as you say and will briefly change to 23 and 24 hz and set it at 10bit.. If you look at my previous pictures, the JVC info section is showing it at 12Bit , isn't that better? MadVR option is 10bit or above. Would appreciate if you could advise .. thanks..

Also I don't do any HDR to SDR conversion as my projector is HDR and does HDR with MadVR , should I still select the "this display is calibrated" and choose BT2020.? What will this do? Thank you   

 It doesn't matter what madVR reports. It matters what the GPU sends to the display. madVR doesn't know this information. This should be 10-bits. I don't know why your projector says 12-bits, as that is not possible with AMD. Check the output at 23hz. It should be 10-bits.

You want to use this display is already calibrated to select the correct gamut. The gamma value is ignored, so don't worry about it. The gamma is only relevant if you are doing HDR -> SDR conversion. Otherwise, it does nothing. But the choice of gamut will do something. Changing the gamut will cause madVR to convert all BT.709 content to BT.2020 before output. Otherwise, madVR will output BT.709 if calibration controls are disabled, as this is the defaut. 

(2018-04-05, 22:24)spencerjford Wrote: @Warner306 AMD indeed can do 12bit at 23hz.    Mine does.

(2018-04-05, 22:29)spencerjford Wrote: @mkohman My tv looks better with 10bit, it just matters what looks best.  if 12 looks best use that, if 10 looks better, use that.    it's up to your eyes.

(2018-04-06, 05:53)Warner306 Wrote: madVR outputs at 10-bits, so you might as well match 10-bits at the GPU.

(2018-04-06, 06:42)brazen1 Wrote: I just went through this a week ago again so I'll share.  When I use 12bit with NVidia, it introduces banding.  You should check what happens when using AMD.  If your display supports 12bit this may not be a problem no matter what GPU you use but still worth a check.  Also, you should consider matching the source as well be it 8, 10, or 12bit and report your findings.  All SDR is 8bit.  Most HDR is 10bit.  I think DV is 12bit.  A good test is the movie Allied 2016. Scene 2:15 through 3:00.  If you see bands in the sky, reduce the 12bit to 10 or even 8.  If you don't, leave it at 12bit.

"Is that what you select? 23hz RGB 444 12 bit? and then RGB 444 8bit for 60hz?"
Yes, that is what you want to achieve unless banding occurs.  Honestly the difference between 8bit, 10bit, and 12bit is slight to unnoticeable.

(2018-04-04, 19:12)Warner306 Wrote:

(2018-04-04, 17:50)Bibio Wrote: so can someone please explain to me why it matters what your desktop display mode is set to.

The video player (Kodi DSPlayer or otherwise) outputs to the GPU. The GPU then outputs to the display. So you want your output bit depth in madVR to match the output bit depth of the GPU to keep the video processing chain as lossless as possible. This is also why WASAPI Exclusive is used for audio; to avoid any interference from the audio renderer to the AVR or display. RGB Full is considered lossless in most cases, even though madVR has to convert from YCbCr to RGB to start the process.

The refresh rate of the GPU must be considered. The desktop defaults to 60hz but changes to match the video refresh rate in most cases. So you can have different RGB values and different bit depths in the GPU control panel for different refresh rates. It is the GPU that ultimately dictates what is sent to the display, so it is important to configure this correctly. madVR attempts to process the video in the highest-quality possible, and you want the GPU to passthrough this output as faithfully as possible. This would be RGB Full from madVR to RGB Full from the GPU, in most cases. And you need your display to be set to RGB Full, as well.