(07-03-2021 01:42 PM)ashlar Wrote: [ -> ]I'm not sure I follow when you say I can't have both.
I attach two pictures, photos taken at the TV while activating the service function for HDMI input details. As you can see, the total res and pixel clock values are different for 24 and 23.976. And madVR confirms as well that they are.
Also, when you say "seems to have non-standard timing parameters", can you suggest a source somewhere where I could check what standard timing parameters are? I used Pixel Clock Calculator here (https://www.monitortests.com/pixelclock.php).
I'm not sure what's happening here. Windows will list 23.976 Hz as 24 Hz, and then 23 Hz is added as an alias, so something must have changed because this is new behavior that I haven't seen before. Do you have 3840x2160 @ 24 Hz in the HDMI data block?
"Automatic (HDTV)" will give you the standard timing parameters, but 24 Hz uses a high horizontal front porch, so the CTA-861 timing will only appear if you add it in a DisplayID extension block. Adding it as a TV resolution will also use the CTA-861 timing.
(07-03-2021 04:04 AM)whoareyouxda Wrote: [ -> ]With the rise of ARM64 and the clear intent of M$ to move their product line that direction, is there any intention on your part to include ARM GPUs (specifically the Adreno 680/685/690 series?)
I'd love to be able to set my Surface Pro X to 90 or even 120hz.
It's up to the graphics driver to implement EDID overrides. I don't think the Adreno driver does.
I've come to learn that Win10 sound is a hot mess but I'm still looking for a solution to my problem and failing that, a viable PC 5.1 surround alternative.
My setup:
Win10 PC (Multipurpose, HTPC, games, etc.)
Nvidia 1660 GTX (1x HDMI v2.0b, 3x DP v1.4) currently using Nvidia HD audio driver. Also tried Microsoft HD Audio Driver.
LG B9 OLED
Pioneer VSX-S520 AVR
I have the PC connected via Nvidia HDMI to the TV for video.
I have the PC connected via Nvidia passive DP adapter/HDMI cable to the AVR for audio. I used Nvidia Control Panel to add the AVR as a second monitor and disabled sound to the TV. (I did have PC ---> eARC TV ---> ARC AVR but that wasn't working properly either and not optimal)
Win10 sound settings: 5.1 rear surround, 16bit 48000Hz.
My problem:
Win10 speaker test results in the FL and FR working properly, but the Centre test sound is coming only from both FL&FR and the RL&RR test sound also comes through both FL&FR.
AVR shows it is receiving PCM. DTS HD Master encoded files play properly through all speakers. AVR self-speaker test works correctly. Some games I play are obviously using the Windows sound settings and not producing audio correctly.
What I've tried:
Uninstall drivers, remove device, reinstall
Changed bit depth and sample rate settings
Used different HDMI cables
Tried all the Win10 speaker configurations
I've also tried a different Onkyo receiver but no change
When I used the ARC route the centre channel and sub worked but surround still came thru the front speakers.
I tried an EDID merge when using ARC but no change; I'm not sure I did it correctly.
A bunch of other things I can't remember
Is there a way to force Win10 to tell it to map the correct sounds to the correct speakers? I'm ready to give up and buy a soundcard with optical out.
I've tried this from another forum but no joy:
Not sure if this helps, but have you tried CRU to alter the EDID of the pioneer that windows is reading (it may not be reading it correctly).
Select the pioneer display from top menu
edit extension blocks.
edit audio formats.
select PCM and copy settings as in picture (pioneer manual states it supports these for PCM 5.1)
edit speaker setup and select 5.1 preset at the bottom to auto fill the selection.
okay to exit then run restart64 to apply the changes.
See if that changes anything in its behaviour, there are more advanced options in the speaker setup but I'm not familiar with and the CRU support thread on their forum might be able to help better.
Have you used the eARC Sharc adapter ?
I tried All the speaker options just to attempt to get sound out of my centre speaker; no luck, however Windows did accept the change in LPCM from 8 to 6 channels so that worked.
(07-08-2021 02:32 AM)ToastyX Wrote: [ -> ] (07-06-2021 09:17 PM)MPCRU Wrote: [ -> ]I have a samsung s34j55w, with freesync range 48-75. Its been happy to OC to 95Hz, most people take it that far. But I want to change the freesync range to 45-95z.
Its totally fine up to 40Hz, but blacks out at 33Hz.
How do I stop it going to 33Hz? I use the gsync demo by Nvidia, and it works great, but when i drop fps to 41, i expect the monitor to NOT go down to 41hz, because I limited the range. Instead, it carries on dropping to 33Hz, so instead of frame mismatches, I get black screens.
The monitor might not be able to handle the increased range correctly. FreeSync uses the max refresh rate as the base resolution, so that can affect the lower end as well. You might have to increase the lower end of the range. LFC is probably making it jump to 66 Hz when it's at 33 FPS.
Thanks toasty - why would my monitor black out (as if out-of-range) if @66Hz? Is that typical? Because it's very comfortable between 50-80Hz for sure.
Can it still black out so?
Thanks
(07-08-2021 02:39 AM)ToastyX Wrote: [ -> ]I'm not sure what's happening here. Windows will list 23.976 Hz as 24 Hz, and then 23 Hz is added as an alias, so something must have changed because this is new behavior that I haven't seen before. Do you have 3840x2160 @ 24 Hz in the HDMI data block?
"Automatic (HDTV)" will give you the standard timing parameters, but 24 Hz uses a high horizontal front porch, so the CTA-861 timing will only appear if you add it in a DisplayID extension block. Adding it as a TV resolution will also use the CTA-861 timing.
I've redone the whole process. I set up the 23.976 and 24.000 custom resolution in the CTA-861 extension block, starting from HDTV timings.
Worked perfectly this time, with no need for DisplayID extension block. The only "strange" thing is that while the default resolutions
show as RGB 10b 4L10, the custom ones are shown as RGB 10b TM. But everything is good, 10 bit and all (2160p24/23.976 does not need HDMI 2.1).
i have lenovo yoga 6 13 laptop with
- Ryzen 4500u
- AUO5F2D screen with 40-60hz freesync range.
any idea why i cant change the freesync range to 30-40hz? I've tested with custom resolution at 30hz and the monitor works fine.
the spec
[
attachment=764]
[
attachment=765]
i tried this in CRU, but still stuck with 40-60hz range
[
attachment=766]
i copied the H rate and pixel clock from a tutorial someone posted on reddit, for a completely different monitor.
is my issue due to incorrect pixel clock and h rate? how to find the right values?
thank you
(07-09-2021 03:54 PM)orangpelupa Wrote: [ -> ]i copied the H rate and pixel clock from a tutorial someone posted on reddit, for a completely different monitor.
is my issue due to incorrect pixel clock and h rate? how to find the right values?
The range limits is not the FreeSync range unless it's DisplayPort, in which case it would already be filled in. Use the HDMI method: add a CTA-861 extension block and add a FreeSync data block. You will also need a 40 Hz detailed resolution.
(07-08-2021 10:52 PM)Alex Wrote: [ -> ]I use 3 monitors, 1 PG278Q (2560x1440 144hz), 1 PG278QR (2560x1440 165hz OC), 1 PG278QR (2560x1440 165hz OC).*
I use 3 displayports.
With Nvidia surround I can only have 7680x1440@ 120hz and 5760x1080@60hz.
Is it possible to use CRU to play at 7680x1440@144hz and 5760x1080@144zh ?
Yes, make the timing parameters and frequencies for 2560x1440 @ 144 Hz match exactly on all three monitors.
(07-08-2021 10:31 AM)MPCRU Wrote: [ -> ]Thanks toasty - why would my monitor black out (as if out-of-range) if @66Hz? Is that typical? Because it's very comfortable between 50-80Hz for sure.
Can it still black out so?
Might be because if it drops below a certain range, LFC kicks in and doubles the refresh rate, so it might not be handling the sudden refresh rate change correctly with a custom range.