Custom Resolution Utility (CRU)
|
02-21-2018, 06:59 AM
(Last edited: 02-21-2018, 07:10 AM by EeK)
Post: #3429
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(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. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 130 Guest(s)