(08-19-2017 03:16 PM)sevs Wrote: [ -> ]Anything with a pixel clock of more than 330MHz doesn’t show up in the List All Modes window or anywhere else in Windows. They do show up in the Radeon settings though.
Are you sure it's 330 MHz? Radeon Settings can't create custom resolutions greater than 327.67 MHz unless you pick a timing standard. That's an API limitation, not a pixel clock limitation in the driver. CRU doesn't have this limitation.
(08-19-2017 03:16 PM)sevs Wrote: [ -> ]Keep in mind that i’m adding custom resolutions inside of the Radeon settings, and not using CRU, as i still have issues with CRU, becuase of the (pseudo-) GPU scaling that is always enabled.
So did you try the option to either use the EDID or to manually set the maximum resolution and refresh rate? If that's not possible with the current driver, try an older driver that still has these options.
(08-19-2017 12:11 PM)Italia1 Wrote: [ -> ]Hi to all, i'm new and i'm here because i've downloaded CRU 1.30 for try to enable Freesync on my AOC U3277PQU monitor. I've done several test enabling freesync range etc, but none: Amd driver always write "freesync unsupported". Have i forget something or it's impossible ? AOC create another monitor, called AOC U3277PWQU and that's with freesync enabled, so i think is only a firmware question. I've got a Radeon 290x and DP cable
CRU can't enable FreeSync with DisplayPort. It can only edit the range.
(08-20-2017 07:37 AM)aliquis Wrote: [ -> ]I own a samsung cf791 monitor (21:9, 3440 x 1440 , 100hz, VA, that supports freesync). There is a wide reported issue (it seems 100% of users have this problem) that the monitor starts to flicker when freesync is turned on (more so if the framerates are low (roughly lower then 60fps, and therefore the monitor is running at lower hz because of freesync)
The freesync range used is 48-100hz. It works (tested with games and techdemos like gsync demo) and LFC also works.
Now i have read a lot, exchanged opinions and experiences with other users and tried a lot, and it seems at least so far i have found and fixed the problem, or at least the problem has disappeared: Someone posted that the pixel clock and h rate was wrong:
please correct me if i am wrong but as far as i read it pixel clock = v total * h total * refresh rate but when i openened cru and looked at the settings for the cf791 the pixel clock rate was too fast (it was set to 550 mhz and the h rate was too fast too)
but if we take the formula: 3600 * 1481 * 100 = 533, 160 mhz (lower then the pixel clock rate that was set) and the standard h rate was too high too ( i corrected it to the correct one)
After i did these corrections the flicker in freesync disappeared, now my question is were these standard settings really wrong and is it likely that these slightly too high pixel clock and h rate caused this flicker ?, and if so, how can it be that wrong values/settings are used for this monitor and whose fault is this (the radeon driver or samsung firmware)?
You'll have to show me what you changed because I'm not understanding what corrections you made. The pixel clock and horizontal scan rate can't be wrong because as you noted it's calculated from the totals. Reducing the pixel clock or horizontal scan rate without changing the totals would reduce the refresh rate. If the monitor can't handle the timing parameters specified by the monitor itself, then that's a flaw in the monitor.
Hello, thank you for the response.
Here is a screenshot of the modified pixel clock and h rate (after i changed it) The monitor is connected through hdmi 2.0 .
[Image:
http://imgur.com/a/wQi0l]
The values before (standard, out of the box settings) were the same for all totals (i changed nothing other than the pixel clock and h rate and the frequency to 100hz in the custom resolution), the frequency was 99,981hz , but the pixel clock was 550mhz and the h rate 152khz.
(08-20-2017 08:14 AM)ToastyX Wrote: [ -> ] (08-19-2017 12:11 PM)Italia1 Wrote: [ -> ]Hi to all, i'm new and i'm here because i've downloaded CRU 1.30 for try to enable Freesync on my AOC U3277PQU monitor. I've done several test enabling freesync range etc, but none: Amd driver always write "freesync unsupported". Have i forget something or it's impossible ? AOC create another monitor, called AOC U3277PWQU and that's with freesync enabled, so i think is only a firmware question. I've got a Radeon 290x and DP cable
CRU can't enable FreeSync with DisplayPort. It can only edit the range.
Ok, thanks for answer. I'll search for another way
(08-20-2017 09:44 AM)aliquis Wrote: [ -> ]Hello, thank you for the response.
Here is a screenshot of the modified pixel clock and h rate (after i changed it) The monitor is connected through hdmi 2.0 .
[Image: http://imgur.com/a/wQi0l]
The values before (standard, out of the box settings) were the same for all totals (i changed nothing other than the pixel clock and h rate and the frequency to 100hz in the custom resolution), the frequency was 99,981hz , but the pixel clock was 550mhz and the h rate 152khz.
That doesn't make sense. You're not giving me the correct information. If you reduced the pixel clock and horizontal scan rate to get 100 Hz without changing the totals, then the old refresh rate would have been higher. There's no way to get 550 MHz and 152 kHz at 99.981 Hz with the timing parameters you showed me. The only way that's possible is if the totals were different.
You also have 3440x1440 @ 100 Hz defined twice. The first one is listed as 99.981 Hz at 543.50 MHz, which is what I would expect for 100 Hz. That one should be taking precedence since it's listed first, so I don't see how changing the second one would affect anything.
I am really confused. Of course you are correct, all the values are correct and after taking a closer look at the different custom resolutions, it all makes sense.
The thing is , i have had trouble with this monitor for a very long time and tried/tested a lot of different things. The last time i took a closer look at the freesync flicker(this was also when i recorded the flicker in the video i linked) was some weeks ago.
I just assumed that the problem still existed and that these changes i made in cru fixed the flicker, but it may just as well have been a newer amd driver or windows update or another cause that fixed the problem instead, i should have of course checked if the problem still existed before i made any modifications.
It's probably like you wrote, i modified a resolution that wasn't even applied, kind of stupid of me, sorry.
Hello,
I am trying to adjust the Range Limits for my new 34inch monitor but am not able to. My monitor is semi off branded (Viotek GN34C) but does Freesync with a stock range of 80-100hz, I'd like to set that to closer to 40-100hz.
When I click Edit for the display properties screen I can edit the range limits but the Ok button is greyed out so I cannot save the settings, and my monitor driver name is off and has red text I'm assuming this is the culprit (image attached).
I'm able to run the monitor with Freesync enabled at 100hz and everything seems to work fine, just can't edit my hz range limits. Any advice is greatly appreciated!!
Thanks.
(08-20-2017 11:34 PM)dinova1 Wrote: [ -> ]Hello,
I am trying to adjust the Range Limits for my new 34inch monitor but am not able to. My monitor is semi off branded (Viotek GN34C) but does Freesync with a stock range of 80-100hz, I'd like to set that to closer to 40-100hz.
When I click Edit for the display properties screen I can edit the range limits but the Ok button is greyed out so I cannot save the settings, and my monitor driver name is off and has red text I'm assuming this is the culprit (image attached).
I'm able to run the monitor with Freesync enabled at 100hz and everything seems to work fine, just can't edit my hz range limits. Any advice is greatly appreciated!!
Thanks.
That looks like a partially corrupt or misprogrammed EDID. It's possible only the product ID is corrupt, which wouldn't affect any functionality. You can change the product ID to any 3-letter + 4-digit hex value you want. I think the default for that monitor is HKC0000. That should let you save.
(08-20-2017 10:51 PM)aliquis Wrote: [ -> ]I am really confused. Of course you are correct, all the values are correct and after taking a closer look at the different custom resolutions, it all makes sense.
The thing is , i have had trouble with this monitor for a very long time and tried/tested a lot of different things. The last time i took a closer look at the freesync flicker(this was also when i recorded the flicker in the video i linked) was some weeks ago.
I just assumed that the problem still existed and that these changes i made in cru fixed the flicker, but it may just as well have been a newer amd driver or windows update or another cause that fixed the problem instead, i should have of course checked if the problem still existed before i made any modifications.
It's probably like you wrote, i modified a resolution that wasn't even applied, kind of stupid of me, sorry.
There's an easy way to test that. Use CRU to export the settings to a file as a backup. Then run reset-all.exe and reboot. Then check if the flicker comes back. If it does, export another file and post it here so I can see the original data. Then you can import the backup and see if the flicker goes away again.