Custom Resolution Utility (CRU)

[ToastyX]

(12-27-2020 02:20 AM)chillly Wrote:  I was mainly trying to use CRU to enable 7.1 DD+ passthrough ARC from my Samsung Q70 TV. By default, the control panel->sound->Samsung->speaker setup only showed Stereo. But the device properties show it supports DD(5.1) and DD+(7.1), which both should work through ARC (and they do work from the native netflix app on the TV).

So I ran a HDMI cable from a second port on my GFX card to my receiver directly, and looked at that 'monitor' in CRU in the extension block Speaker Setup to see what was checked (that connection allows 7.1 speakers). Then I edited the Samsung in CRU to check those same speakers. Then rebooted.

But this doesn't seem to have had any effect. I also tried exporting those settings as an INF and doing the advanced boot with driver signing disabled, etc. Still didn't do anything... only shows Stereo as an option.

I also tried changing the order of supported formats to move PCM to the bottom and move DD+ to the top, since the TV is still only receiving PCM from the computer. But this also had no effect.

"Speaker setup" is informational and doesn't have any effect. The audio formats data block should have AC-3 and E-AC-3. You said the device properties show it supports DD (5.1) and DD+ (7.1), so they should already be available without any changes. What is the resolution for the "monitor" set to? It needs to be a TV resolution like 1920x1080 @ 60 Hz so there's enough blanking to transmit the audio.

[jarkid]

(12-27-2020 03:14 PM)ToastyX Wrote:  

(12-27-2020 05:51 AM)jarkid Wrote:  so I am guessing the program just needs more blanking time for the video card
to work perfectly, is that possible?

No, that's not normal. Something is wrong with the video card then. What does the flickering look like? Are you overclocking the video card at all? Have you tried another cable?

Dear ToastyX, you are my last resort...

1. The flickering is like this: https://youtu.be/rfGM_hV6UlE?t=49
shortly and occasionally in game or effect other programs outside. It's really annoying.

2. I didn't overclock my video card (AMD RX 570 4GB) in order to reduce the issue.

3. I've tried 3 different HDML cabls including the default one from the unboxing. Even I bought a new 75hz monitor to test, it would still flicker.

I still don't get why my 75hz setting is the standard setting, then it fails with a specific application. But after I changed to LCD native for 75hz, it's all fine like standard 60hz.

Now should I change my card to NVidia indead of AMD RX570 4GB...

[ToastyX]

(12-27-2020 03:34 PM)jarkid Wrote:  1. The flickering is like this: https://youtu.be/rfGM_hV6UlE?t=49
shortly and occasionally in game or effect other programs outside. It's really annoying.

You said the whole screen flickers. That video only shows flickering in BlueStacks, which would be a problem with the software. I don't see how blanking could affect software like that.

[Epic753]

(12-22-2020 02:44 AM)ToastyX Wrote:  Yes, I mean the firmware in the monitor could be faulty and making it produce a bad signal that's causing NVIDIA's driver to crash, which would also be a bug in NVIDIA's driver. If it also happens with HDMI, then I would suspect a hardware problem.

I restart64.exe, (CRU not in effect) connected Y27Q20 to RTX 30370 via HDMI 2.1 high speed cable, disconnected DP 1.2/1.4 from RTX3070.

No Intermittent black screen and nvlddmkm fault. So only happens with DP 1.2 or 1.4

I do have beta Lenovo Y27Q20 firmware available and might install, but could also live with 144 hz 8 bit color (still great) until Lenovo releases final firmware version publicly.

Also, from what I can tell DP 1.2 and 1.4 bandwidth is pushing edge of capacity for 1440p 165 hz 10 bit color, etc. So I wonder about that.

Does this mean that the fix leans away from faulty computer hardware and towards Lenovo (or nvidia) firmware and drivers?

Thanks

Thanks

[ToastyX]

(12-27-2020 06:34 PM)Epic753 Wrote:  Does this mean that the fix leans away from faulty computer hardware and towards Lenovo (or nvidia) firmware and drivers?

Seems like it.

[chillly]

(12-27-2020 03:26 PM)ToastyX Wrote:  

(12-27-2020 02:20 AM)chillly Wrote:  I was mainly trying to use CRU to enable 7.1 DD+ passthrough ARC from my Samsung Q70 TV. By default, the control panel->sound->Samsung->speaker setup only showed Stereo. But the device properties show it supports DD(5.1) and DD+(7.1), which both should work through ARC (and they do work from the native netflix app on the TV).

So I ran a HDMI cable from a second port on my GFX card to my receiver directly, and looked at that 'monitor' in CRU in the extension block Speaker Setup to see what was checked (that connection allows 7.1 speakers). Then I edited the Samsung in CRU to check those same speakers. Then rebooted.

But this doesn't seem to have had any effect. I also tried exporting those settings as an INF and doing the advanced boot with driver signing disabled, etc. Still didn't do anything... only shows Stereo as an option.

I also tried changing the order of supported formats to move PCM to the bottom and move DD+ to the top, since the TV is still only receiving PCM from the computer. But this also had no effect.

"Speaker setup" is informational and doesn't have any effect. The audio formats data block should have AC-3 and E-AC-3. You said the device properties show it supports DD (5.1) and DD+ (7.1), so they should already be available without any changes. What is the resolution for the "monitor" set to? It needs to be a TV resolution like 1920x1080 @ 60 Hz so there's enough blanking to transmit the audio.

I'm thinking it's not a matter of support but more of a matter of getting Windows to send DD instead of PCM, which may not be a EDID issue. I'm at 4k but I can send 4k@60 through my receiver and games sends 7.1 PCM fine if I configure that 'monitor' as 7.1 speakers (which it has the option to). But I know my TV can't send 7.1 PCM back through ARC, so need it to encode it. And I'm running freesync to the TV. When I'm playing a movie or something from like Kodi that starts with a DD signal, it will passthrough ok.

[diakou]

I have a quick ish 360Hz question - My G-Sync range is 1-360 obviously as it's the AW2521H

But as we know, CRU can't get the info it needs from NV's reporting because they're being difficult with the way they display information.

With it saying 1-255 as the VRR range, am I not able to change this to 65-255 and have that apply for the real VRR range of 1-360? (aka it would be 65-360?)

Although it's a native g-sync module and does all framerates at any range - there's an awkward unexplainable benefit to this 60fps vsync'd game I'm playing when a g sync module monitor has the VRR range minimum placed at 55-65 for a 240hz, rather than sub 20 for the minimum.

[jarkid]

(12-27-2020 03:50 PM)ToastyX Wrote:  

(12-27-2020 03:34 PM)jarkid Wrote:  1. The flickering is like this: https://youtu.be/rfGM_hV6UlE?t=49
shortly and occasionally in game or effect other programs outside. It's really annoying.

You said the whole screen flickers. That video only shows flickering in BlueStacks, which would be a problem with the software. I don't see how blanking could affect software like that.

Hi,ToastyX,

Last time I changed a monitor, it's the same.

Right now, I just bought a new nVidia card - GTX 1660 ... and the problem has been resolved...

So the root cause is the AMD Video card(RX570) + 75Hz monitor + the Android simulator don't co-exist well...

Although I can use CRU to resolve the problem, I still want to find the root cause, that's why I bought a new card to test it...

[ToastyX]

(12-28-2020 03:29 PM)jarkid Wrote:  So the root cause is the AMD Video card(RX570) + 75Hz monitor + the Android simulator don't co-exist well...

Yes, but that doesn't affect the whole screen, so I don't understand why blanking would make any difference. Either it's a driver bug or a bug in BlueStacks.

[ToastyX]

(12-28-2020 08:06 AM)diakou Wrote:  With it saying 1-255 as the VRR range, am I not able to change this to 65-255 and have that apply for the real VRR range of 1-360? (aka it would be 65-360?)

Native G-Sync monitors don't use the EDID to control the range, so you can't change the range unless they changed something with newer monitors.