Post Reply
Custom Resolution Utility (CRU)
08-02-2015, 01:27 AM
Post: #1531
RE: Custom Resolution Utility (CRU)
Any issues using this with Windows 10? I also plan to use the AMD patcher, as I have an overclockable monitor and an AMD 290X.
Find all posts by this user
Quote this message in a reply
08-02-2015, 02:36 AM
Post: #1532
RE: Custom Resolution Utility (CRU)
(08-02-2015 01:27 AM)NateZ28 Wrote:  Any issues using this with Windows 10? I also plan to use the AMD patcher, as I have an overclockable monitor and an AMD 290X.
It works fine with Windows 10. The only "issues" are the disabled buttons are ugly and the taskbar ruins the icon by scaling it. Tongue
Find all posts by this user
Quote this message in a reply
08-02-2015, 02:38 AM
Post: #1533
RE: Custom Resolution Utility (CRU)
(08-02-2015 12:30 AM)Haemato Wrote:  According to the Enhanced EDID VESA spec it is required. Specifically states that "A Monitor Range Limits Descriptor must be provided" under section 3.10. A Monitor name descriptor is required as well. Earlier versions of the spec didn't require this (prior to 1.3) so hosts can expect to run into this scenario. It's possible that nvidia is doing a strict interpretation of the spec and thus failing to parse the EDID.
EDID version 1.4 does not require a range limits descriptor. Older versions of CRU upgraded the EDID to version 1.4, but this caused problems with the way AMD's driver handled HDMI audio with older GPUs, so I removed the upgrade. EDID version 1.3 says it's required, but not including it doesn't invalidate any of the information in the EDID. I have a monitor that doesn't have a range limits descriptor. Neither AMD nor NVIDIA require a range limits descriptor as far as I have seen.
Find all posts by this user
Quote this message in a reply
08-02-2015, 11:05 PM
Post: #1534
RE: Custom Resolution Utility (CRU)
Hi, thanks for this. But when I set the blink/total etc at the bottom it doesn't seem to remember that part, CVT Reduced Blank works for 1920x1080/70 in nvidia control panel or
1920 1080 / 72
24 3
16 5
1980 1092
- -
Works in Nvidia control panel, but if set in CRU i do get picture but randomly receive input not supported for 4 seconds at a time, audio also skips. I was also wondering, if there was a way to add two audio profiles to the panel, like nvidia notices when it's pass through the stereo or being amped, so I can set a tv audio format and a receiver audio format, [if it is mixed to the same profile I have to reconfigure the audio channels to 2 for the tv or 5.1 for the receiver]. Also how do I add RGB FUll to the EDID as I only see ycbcr
Thanks again, and sorry if either question was answered above.
System Specs:
Un55fh6030 3d TV
Pioneer VSX-522-k receiver
GTX 970 [outputting a/v over hdmi]
I7 4790k @4.8ghz
Kingston Fury X 2x8GB
Z97n-wifi ITX motherboard
mx100 256Gb SSD
Windows 10 x64 Enterprise
Find all posts by this user
Quote this message in a reply
08-03-2015, 12:41 AM
Post: #1535
RE: Custom Resolution Utility (CRU)
(08-02-2015 02:38 AM)ToastyX Wrote:  EDID version 1.4 does not require a range limits descriptor. Older versions of CRU upgraded the EDID to version 1.4, but this caused problems with the way AMD's driver handled HDMI audio with older GPUs, so I removed the upgrade. EDID version 1.3 says it's required, but not including it doesn't invalidate any of the information in the EDID. I have a monitor that doesn't have a range limits descriptor. Neither AMD nor NVIDIA require a range limits descriptor as far as I have seen.

Ok, good to know. I was just looking for differences between the stock EDID in the projector and the one I created. In the new one I:
1) removed all established timings that weren't 60Hz
2) removed all standard timings except 800x600@120Hz, 1024x768@120Hz, 720p60, 720p120, 800p60 and 800p120
3) swapped out the 1280x800@60Hz detailed timing for the 1280x800@120Hz reduced blanking VESA timing
4) changed monitor name
5) serial number was set to 1, 2, 3 (each board respectively)
6) new EDID had no plain text serial number descriptor
7) new EDID had no Monitor Limits Descriptor
8) just noticed that the old projector had zero extension blocks whereas my new one had 1 that was left blank (all 0x00)

Perhaps #8 is the issue and not the missing Monitor Limits Descriptor. Or maybe the driver didn't like the established timings section being so restrictive. Will be able to experiment more once I get a "write-edid" program written.
Find all posts by this user
Quote this message in a reply
08-04-2015, 12:47 PM
Post: #1536
RE: Custom Resolution Utility (CRU)
(08-02-2015 11:05 PM)chaython Wrote:  Hi, thanks for this. But when I set the blink/total etc at the bottom it doesn't seem to remember that part
I'm not sure what you mean. Are the values not being saved? If you mean the radio buttons, those are just there to indicate only one of the values are needed to calculate the other two. It's not a setting that gets saved. The values should be saved.

(08-02-2015 11:05 PM)chaython Wrote:  CVT Reduced Blank works for 1920x1080/70 in nvidia control panel or
1920 1080 / 72
24 3
16 5
1980 1092
- -
Works in Nvidia control panel, but if set in CRU i do get picture but randomly receive input not supported for 4 seconds at a time, audio also skips.
HDMI audio requires a large enough blanking period to transmit the data, so I'm not sure why the custom resolution is working with the NVIDIA control panel. I would use the "LCD native" timing option if the TV can handle that. Keep in mind that HDMI will act like single-link DVI if HDMI support is not defined in the custom extension block, so the TV might handle that differently. HDMI also supports both RGB and YCbCr, but custom resolutions usually use RGB.

(08-02-2015 11:05 PM)chaython Wrote:  I was also wondering, if there was a way to add two audio profiles to the panel, like nvidia notices when it's pass through the stereo or being amped, so I can set a tv audio format and a receiver audio format, [if it is mixed to the same profile I have to reconfigure the audio channels to 2 for the tv or 5.1 for the receiver].
I don't know a way to do that without switching EDIDs. Shouldn't the receiver have a way to do that?

(08-02-2015 11:05 PM)chaython Wrote:  Also how do I add RGB FUll to the EDID as I only see ycbcr
RGB is automatically supported, so it's not defined in the EDID. Use the NVIDIA control panel to set the color format.
Find all posts by this user
Quote this message in a reply
08-05-2015, 06:53 AM
Post: #1537
RE: Custom Resolution Utility (CRU)
(08-03-2015 12:41 AM)Haemato Wrote:  Ok, good to know. I was just looking for differences between the stock EDID in the projector and the one I created. In the new one I:
1) removed all established timings that weren't 60Hz
2) removed all standard timings except 800x600@120Hz, 1024x768@120Hz, 720p60, 720p120, 800p60 and 800p120
3) swapped out the 1280x800@60Hz detailed timing for the 1280x800@120Hz reduced blanking VESA timing
4) changed monitor name
5) serial number was set to 1, 2, 3 (each board respectively)
6) new EDID had no plain text serial number descriptor
7) new EDID had no Monitor Limits Descriptor
8) just noticed that the old projector had zero extension blocks whereas my new one had 1 that was left blank (all 0x00)

Perhaps #8 is the issue and not the missing Monitor Limits Descriptor. Or maybe the driver didn't like the established timings section being so restrictive. Will be able to experiment more once I get a "write-edid" program written.

Got the EERPOMs on the interceptor boards reprogrammed today with my hand-coded EDID. Surround works now at 3840x800@120Hz.

In the new EDID I added a text serial number and a monitor limits descriptor. I also set the number of extension blocks to 0. One of those 3 changes seems to have fixed the issue with the nvidia driver.

I tried attaching the new EDID to this post but bin files aren't allowed.
Find all posts by this user
Quote this message in a reply
08-05-2015, 10:31 AM
Post: #1538
RE: Custom Resolution Utility (CRU)
(08-01-2015 02:05 PM)ToastyX Wrote:  
(08-01-2015 02:48 AM)DLee Wrote:  I thought that this monitor was able to display 1920x1080 resolution, however only thing that was originally showing up was "1400x1200" which skewed the icons on my desktop. So I went ahead and tried this program and it showed that the detailed resolution was 1920x1080 @ 60hz, so I put that in in the standard resolution (kept it as "No extension block).
You shouldn't need to add any custom resolutions. CRU will not help if the monitor already defines the correct resolution.

(08-01-2015 02:48 AM)DLee Wrote:  When I pressed OK and used restart (I wasn't sure which restart I should use so I just used a regular restart, instead of restart 64, but my operating system is Windows 8.1 64 bits).
Restart.exe just runs Restart64.exe on 64-bit systems, so you can use either one.

(08-01-2015 02:48 AM)DLee Wrote:  I'm not sure if my on board graphic card doesn't support 1920x1080 or i'm doing something wrong. Please let me know how to best resolve this issue. I greatly appreciate it thank you.

P.S. Info on my display card:
Name: Microsoft Basic Display Adapter
Chip type: ATI ATOMBIOS
Approx. Total Memory: 256MB
Thank you once again!
Microsoft Basic Display Adapter is the generic Microsoft video driver. You need to download and install the driver for your video card: http://support.amd.com/en-us/download

Thank you for the quick reply. Here's the situation right now
1) I believe that my display can display upto 1920x1080, however the only options I have right now are 1600x1200, 1400x1050, 1152x864. When I said it showed 1920x1080, it only showed on the detailed section (when I ran the program you've created). However even when I used restart.exe, the resolution didn't show up as 1920 x1080.
2) I tried downloading the installing the driver of my video card, but I think it's motherboard integrated video card. When I use the 'auto detection' method from the amd support link you've provided to me, it shows up as "we are unable to find a driver for your system" and following things are visible:
Graphics Hardware: A-series APU
Processor: AMD FX™-4130 Quad-Core
Operating System: Windows 8.1 64-bit
Please let me know how I can fix my issues
Thanks
Find all posts by this user
Quote this message in a reply
08-05-2015, 04:48 PM
Post: #1539
RE: Custom Resolution Utility (CRU)
(08-05-2015 10:31 AM)DLee Wrote:  Thank you for the quick reply. Here's the situation right now
1) I believe that my display can display upto 1920x1080, however the only options I have right now are 1600x1200, 1400x1050, 1152x864. When I said it showed 1920x1080, it only showed on the detailed section (when I ran the program you've created). However even when I used restart.exe, the resolution didn't show up as 1920 x1080.
That means the monitor already defines 1920x1080 @ 60 Hz. CRU can't help you if the resolution is already defined by the monitor. This would be a graphics driver issue.

(08-05-2015 10:31 AM)DLee Wrote:  2) I tried downloading the installing the driver of my video card, but I think it's motherboard integrated video card. When I use the 'auto detection' method from the amd support link you've provided to me, it shows up as "we are unable to find a driver for your system" and following things are visible:
Graphics Hardware: A-series APU
Processor: AMD FX™-4130 Quad-Core
Operating System: Windows 8.1 64-bit
Please let me know how I can fix my issues
Thanks
Don't use the auto detection method. Get the latest AMD Catalyst drivers.
Find all posts by this user
Quote this message in a reply
08-06-2015, 02:27 AM
Post: #1540
RE: Custom Resolution Utility (CRU)
Hello friends!
I would like some help.

This tool really helped me to add some missing resolutions for my screen but it isn't heling me get rid of others...

I have a 16:10 monitor.
It was lacking those two resolutions (which i added now)
1680x1050
1440x900

But it shows 16:9 resolutions like:
1920x1080
1680x900
1280x720

etc...

Any way to remove those?

I would like to keep only those:
1920x1200
1680x1050
1440x900
1280x800
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: Kriswastaken, 138 Guest(s)