Hey, I've been using CRU for quite a while now with my CRT monitor, and I just wanted to say a big THANK YOU for your work on the software. I appreciate your work and hope that good fortune comes to you. That's it. Thanks
@ToastyX hi when you will have time can u respond to my private msg it will be verry fun ^^
THX for the Great work.
I can see in 1.4.1
- FreeSync range: added support for editing FreeSync 2 ranges
- Added support for HDR static metadata blocks
Can you elaborate the HDR settings ?
What we can do in this, i can see that Values are from 1-100 it mean 100%?
(10-06-2018 09:44 PM)loccothan Wrote: [ -> ]Can you elaborate the HDR settings ?
What we can do in this, i can see that Values are from 1-100 it mean 100%?
The values are 1-255 and represent the luminance calculated using formulas. The max values are 50 * 2 ^ (Value / 32), and the min value is Max * (Value / 255) ^ 2 / 100. I don't expect most people to find this useful. It's mainly there to show what the monitor supports.
(10-08-2018 12:44 PM)ToastyX Wrote: [ -> ] (10-06-2018 09:44 PM)loccothan Wrote: [ -> ]Can you elaborate the HDR settings ?
What we can do in this, i can see that Values are from 1-100 it mean 100%?
The values are 1-255 and represent the luminance calculated using formulas. The max values are 50 * 2 ^ (Value / 32), and the min value is Max * (Value / 255) ^ 2 / 100. I don't expect most people to find this useful. It's mainly there to show what the monitor supports.
THX
Another words, do not touch it
(10-09-2018 07:06 AM)loccothan Wrote: [ -> ] (10-08-2018 12:44 PM)ToastyX Wrote: [ -> ] (10-06-2018 09:44 PM)loccothan Wrote: [ -> ]Can you elaborate the HDR settings ?
What we can do in this, i can see that Values are from 1-100 it mean 100%?
The values are 1-255 and represent the luminance calculated using formulas. The max values are 50 * 2 ^ (Value / 32), and the min value is Max * (Value / 255) ^ 2 / 100. I don't expect most people to find this useful. It's mainly there to show what the monitor supports.
THX
Another words, do not touch it
http://www.quantumdata.com/support/downl..._Win32.msi with this you can eddid the hdr and know in cdm2
hello i'm in the big rush. i would like some help because when i select freesync range 50 60 my scoring i have black screen the temp of a second. i think it's a skip frame and i'd like to have an edid fix with the good freesync resolutions
(10-10-2018 01:03 AM)gabrieldesrochers@hotmail.com Wrote: [ -> ] (10-09-2018 07:06 AM)loccothan Wrote: [ -> ] (10-08-2018 12:44 PM)ToastyX Wrote: [ -> ] (10-06-2018 09:44 PM)loccothan Wrote: [ -> ]Can you elaborate the HDR settings ?
What we can do in this, i can see that Values are from 1-100 it mean 100%?
The values are 1-255 and represent the luminance calculated using formulas. The max values are 50 * 2 ^ (Value / 32), and the min value is Max * (Value / 255) ^ 2 / 100. I don't expect most people to find this useful. It's mainly there to show what the monitor supports.
THX
Another words, do not touch it
http://www.quantumdata.com/support/downl..._Win32.msi with this you can eddid the hdr and know in cdm2
Ok, but my Monitor is not HDR Native
-> 1440p 10Bit with Max Luminosity (Peak) at 400 cd/m²
So it can theoretically display HDR-400 format (but maby not? dunno, but we do like to OC
)
CRU v1.4.1
nvlddmkm-patcher v1.4.3
Windows 10 version 1803 build 17134.34
nVidia Driver 416.34
I've been using CRU for years, but now
CRU on Windows 10 with nVidia driver 416.34
no longer works.
I recently updated my graphics driver 2 weeks ago, patched it with the latest nvlddmkm-patcher, and had no issues until today when I turned my PC on.
My custom refresh rate is no longer an option in display adapter properties, even though I've have it set up in CRU:
http://puu.sh/BPYEC/9bc49861ff.png
Maybe this is due to a recent Windows 10 update? Anyone have any ideas?
(10-24-2018 01:56 AM)hutt132 Wrote: [ -> ]I've been using CRU for years, but now CRU on Windows 10 with nVidia driver 416.34 no longer works.
The problem is the latest NVIDIA driver (416.34) made the patcher ineffective. I don't have a solution yet.