THX for the CRU 1.4 Bratan'
(02-13-2018 02:03 AM)caenlen Wrote: [ -> ]I just ordered the new AMD 2400G Raven Ridge APU, will I still be able to use Toastyx Cru and AMD Patcher with this new setup on my QNIX 27" 1440p panel, I normally OC it from 60hz to 110hz, but thats only using normal setups, not sure if these new APU's are supported or not with your tools.
You'd need a motherboard with dual-link DVI.
Was wondering if someone could help me out. Here's my setup:
Monitor: ASUS VG248QE
Videocard: AMD RX480
Connection Type: DisplayPort
I'm CS:GO player and play CS in a lower resolution. For some reason the RX480 does not support the resolution that I would like to play in by default (1280x960). So what I have done in the past is added it via CRU and used it that way. I recently updated my drivers to 18.2.2, and since then I am unable to play in 1280x960 at 144hz.
When I try to change my windows desktop to the added resolution, it works fine at 60hz. However when I try and run it at 144hz it changes the resolution to 640x480 and does not work properly. If I try to launch my game at 1280x960 144hz, it has odd lines all over the screen. I suspect it's an issue with me not knowing the correct timings and CRU pulling the 60HZ onesby default, because when I open CRU it says my 'native' is 1920x1080 @ 60hz.
Here is what my CRU looks like:
https://imgur.com/a/omFIO
I have tried rolling back my videocard drivers to the version I used previously (17.10.2) and I'm unable to get it working on that now too.
And if I want to take advantage of the data exported by CRU to store this information in the EDID data on the display?
Are there any programs available to change the EDID data stored on the display?
By the way, CRU in Portuguese means raw.
I'm having some problems with CRU. ToastyX, if you could please help me, it would be greatly appreciated.
Last year, I built a new PC and used the latest stable version of CRU to add two custom resolutions (lower than UHD, or 3840x2160 - 3456x1944 and 3200x1800) and also to remove the highest supported resolution by my display (4K, or 4096x2160), an LG B7 4K TV.
At first, I was running an HDMI cable straight from the HDMI out on my 1080 Ti to the TV, for both audio and video. I later added a 9.2 Denon AVR-X4400H into the mix, running an HDMI cable from the GPU to the receiver, and another one from the receiver to the TV - again using only HDMI for both audio and video ("premium certified" cables).
Everything was working flawlessly. Even after adding the receiver, the custom resolutions "stuck", 4096x2160 was gone and spatial sound (Dolby Atmos for home theater) sounded perfect. Then, recently, I decided to try the Steam Link and that's when the issues started.
After using Steam in-home streaming, sound was gone from the host PC. Since the graphics drivers were due for an upgrade, I uninstalled the old ones using DDU and installed the new ones manually (not using GeForce Experience). I got audio working on the host PC, but only until I opened Steam again.
After trying countless solutions, I decided to format my PC, perform a clean install of Windows 10 and never use the Link again. I set up everything, downloaded CRU a second time and did the same thing I'd done before (adding two custom resolutions, removing the highest supported one).
This time, I couldn't get spatial sound working at all. All the drivers were up to date, and no software other than CRU had been installed. Still, only stereo sound was working. I reset the display using reset-all.exe and audio settings were back to normal. However, every time I used CRU, the playback device would default back to stereo and spatial sound would break (I couldn't even test the speakers without receiving an error message).
I struggled for a bit and decided to try one last thing before asking for help here on these forums. I connected the GPU directly to the TV once more, bypassing the receiver, and used CRU after that. I then switched back to the setup that I was using before (GPU - receiver - TV). Audio automatically changed to Dolby Atmos (working correctly), but all changes made by CRU were gone. None of the custom resolutions I'd added were showing up, and 4096x2160 was still listed as the highest supported resolution.
I don't know how I got both custom resolutions and spatial sound working last year, but now I can't seem to do it again and could really use some help. I'm running Windows 10 Pro, with the system and all of its drivers more than up to date.
Edit: These are the actual error messages after using CRU in the GPU - receiver - TV setup:
When I try to select Dolby Atmos for home theater under Sound > Properties > Spatial sound, I get an error message saying that "Something went wrong while trying to turn on spatial sound". When I try to test my speakers (Sound > Configure > Test), I get a different error message ("Device in use"), saying that "The device is being used by another application" and "If you continue, that application may stop working". When I click yes, to continue, a final error message pops up with the following text: "Error! Failed to play test tone".
(02-20-2018 06:32 AM)EeK Wrote: [ -> ]After trying countless solutions, I decided to format my PC, perform a clean install of Windows 10 and never use the Link again. I set up everything, downloaded CRU a second time and did the same thing I'd done before (adding two custom resolutions, removing the highest supported one).
This time, I couldn't get spatial sound working at all. All the drivers were up to date, and no software other than CRU had been installed. Still, only stereo sound was working. I reset the display using reset-all.exe and audio settings were back to normal. However, every time I used CRU, the playback device would default back to stereo and spatial sound would break (I couldn't even test the speakers without receiving an error message).
HDMI audio is transmitted during the blanking periods, so you have to make sure the blanking is large enough to accommodate the audio. I would try using the timing parameters for 3840x2160 @ 60 Hz and change the resolution only. Also, keep in mind that direct connection vs. through receiver will appear as different monitors. I don't know if one of the configs got messed up somehow. I don't deal with audio, so I'm not familiar with all the driver issues.
(02-18-2018 08:42 AM)MSXManiac Wrote: [ -> ]And if I want to take advantage of the data exported by CRU to store this information in the EDID data on the display?
Are there any programs available to change the EDID data stored on the display?
This page details a couple of methods:
https://www.blurbusters.com/zero-motion-...dware-mod/
Keep in mind the EDID might be write-protected.
(02-13-2018 09:06 PM)iannn Wrote: [ -> ]I'm CS:GO player and play CS in a lower resolution. For some reason the RX480 does not support the resolution that I would like to play in by default (1280x960). So what I have done in the past is added it via CRU and used it that way. I recently updated my drivers to 18.2.2, and since then I am unable to play in 1280x960 at 144hz.
When I try to change my windows desktop to the added resolution, it works fine at 60hz. However when I try and run it at 144hz it changes the resolution to 640x480 and does not work properly. If I try to launch my game at 1280x960 144hz, it has odd lines all over the screen. I suspect it's an issue with me not knowing the correct timings and CRU pulling the 60HZ onesby default, because when I open CRU it says my 'native' is 1920x1080 @ 60hz.
Here is what my CRU looks like:
https://imgur.com/a/omFIO
I have tried rolling back my videocard drivers to the version I used previously (17.10.2) and I'm unable to get it working on that now too.
Try "LCD standard" and "LCD reduced" instead. If that doesn't help, try enabling GPU scaling.
(02-20-2018 03:59 PM)ToastyX Wrote: [ -> ]HDMI audio is transmitted during the blanking periods, so you have to make sure the blanking is large enough to accommodate the audio. I would try using the timing parameters for 3840x2160 @ 60 Hz and change the resolution only. Also, keep in mind that direct connection vs. through receiver will appear as different monitors. I don't know if one of the configs got messed up somehow. I don't deal with audio, so I'm not familiar with all the driver issues.
Thanks for replying, ToastyX.
I never changed any values other than the active horizontal and vertical pixels, when adding detailed resolutions. So, the timing parameters ended up being the standard ones for 3840x2160 @ 60Hz even before you suggested that.
I asked you before what I should choose, and
you said that because I was using GPU scaling, it didn't matter, so I left those values unchanged, since everything was working.
This is what the timing parameters looked like (and still did, after my last failed attempts):
3456x1944
3200x1800
What's weird is that I don't remember using CRU after I bought the receiver, but my custom resolutions were still showing up and spatial sound was working perfectly. I know that because I was playing Rise of the Tomb Raider in 3200x1800, and that game makes use of surround sound as well.
Now that you mentioned, I can clearly see both the Denon receiver and the LG TV listed as "displays" in CRU. I tried making the changes to either one of each at a time and both of them at the same time, but nothing seems to help. Any other suggestions?
Update: I managed to create the two custom resolutions that I wanted via the Nvidia Control Panel (Customize, under Display > Change Resolution) and still get spatial sound working. Is there any difference between that method and using CRU? I was also able to remove the 4096x2160 resolution without affecting the audio, so it's an issue exclusive to the detailed resolutions.
Hi everyone
Wondered if anyone could help me. I have 4K HDR working with Intel 630 graphics when connecting directly to my TV (LG 950), but not when I go through my AVR (Yamaha RXV-2079) -- when I go through the AVR, there is no HDR option in Displays settings (as there is when I go straight to the TV). The AVR has HDMI 2.0a, HDCP 2.2 and can pass 4K HDR through all other sources. (It is set to Mode 1 also.)
So, I think it may be that the AVR is not passing through all of the EDID information it needs to. Here is my dxdiag report for direct connection to the TV (HDR available but not currently selected):
Code:
Card name: Intel(R) UHD Graphics 630
Manufacturer: Intel Corporation
Chip type: Intel(R) UHD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_3E92&SUBSYS_D0001458&REV_00
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4146 MB
Dedicated Memory: 128 MB
Shared Memory: 4018 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.659680,0.340344), Green(0.244641,0.670422), Blue(0.130383,0.040539), White Point(0.313000,0.329602)
*** Display Luminance: Min Luminance = 0.010000, Max Luminance = 1499.000000, MaxFullFrameLuminance = 799.000000 ***
Monitor Name: Generic PnP Monitor
Monitor Model: LG TV
Monitor Id: GSM0001
Native Mode: 3840 x 2160(p) (60.000Hz)
Output Type: Displayport External
*** Monitor Advanced Color Capabilities: BT2020RGB BT2020YCC Eotf2084Supported AdvancedColorSupported ***
...and here is the dxdiag report for the AVR (HDR not available):
Code:
Card name: Intel(R) UHD Graphics 630
Manufacturer: Intel Corporation
Chip type: Intel(R) UHD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_3E92&SUBSYS_D0001458&REV_00
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4146 MB
Dedicated Memory: 128 MB
Shared Memory: 4018 MB
Current Mode: 3840 x 2160 (32 bit) (59Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.659680,0.340344), Green(0.244641,0.670422), Blue(0.130383,0.040539), White Point(0.313000,0.329602)
*** Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 ***
Monitor Name: Generic PnP Monitor
Monitor Model: RX-V2079
Monitor Id: YMH31BF
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: Displayport External
*** Monitor Advanced Color Capabilities: BT2020RGB BT2020YCC Eotf2084Supported ***
Thanks to CRU I was able to add BT2020RGB BT2020YCC to the Monitor Advanced Color Capabilities, but it is still missing AdvancedColorSupported which I think is why I'm still not getting the HDR option.
I wondered whether this had something to do with the Display Luminance settings, which show higher minimum and much lower maximum (ie less dynamic range) on the AVR compared to the TV.
So I wondered first whether there was any way to adjust the Display Luminance settings using CRU? These are apparently stored in the EDID or an override according to the Windows documentation. But I don't know whether CRU can address these (or even if that is the issue).
Any insights gratefully appreciated!