Monitor Tests Forum

Full Version: Custom Resolution Utility (CRU)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809
(06-02-2018 10:31 PM)spidey Wrote: [ -> ]Hi ToastyX, great program but have a problem with it. The story begins with my current machine - Windows 7 64bit, AMD R7 360 with 18.4.1 driver. And monitor CRT, Dell P1130, which supports refresh rates like 1280x1024@120Hz which is my goal
Apparently there are no other choices but only 60Hz. So I tried the utility - installed the pixel patch, set the custom resolution then restarted the driver with 64bit option, then restarted Windows. After some testing in desktop mode at 120Hz decided to play some games - CS: Source, Crysis, Dota 2, Borderlands and while starting them or playing them the machine suddenly returns to desktop trying to switch the resolution and frequency (I'm sure all of them are set on 1280x1024 in options) and failing just retries again. After that I just reset the things with the CRU and return to 60Hz, removed the pin 12 from the VGA side (connection to monitor is DVI-to-VGA cable, which was picked from similar machine with nvidia card where everything worked at 120Hz) and did another try without success. Note that the monitor before pin removal was correctly installed as Dell P1130 (tested also with integrated drivers of Sony GDM-F520 and Dell P1110), after removal (no more EDID) it was also ok in Device Manager ...

So, toasty, do you have any ideas what's causing this? Thanks in advance
I don't recommend removing pin 12 because AMD's driver has a bug with VGA that causes it to get stuck in a loop trying to redetect the monitor if there's no EDID. I don't know if that's the problem you're seeing, but it's not supposed to happen if the pin is present and the monitor has an EDID.

You might be better off getting an HDMI-VGA converter to work around the problem, or use an NVIDIA card. I don't think AMD cares about fixing VGA bugs anymore. It might work with an older driver. I think 15.7 is the oldest driver that supports the R7 360: https://support.amd.com/en-us/download/d...4&rev=15.7

Make sure to use DDU first to uninstall the newer driver: https://www.wagnardsoft.com/display-driv...aller-ddu-

The old Catalyst drivers also had an option to ignore the EDID and set the maximum resolution and refresh rate manually for VGA connections.
(06-02-2018 10:02 PM)adnansajid33 Wrote: [ -> ]I tried reset-all.exe and rebooted but still see the same thing... Also tried uninstalling and then reinstalling all the graphics drivers but to no avail.
Has it cleared up? It looks like the pixels are stuck that way for some reason. I haven't seen anything like that before. Is it like that in the BIOS screen? That would indicate a hardware issue. Did the problem happen immediately after trying 90 Hz, or was 90 Hz working and the problem appeared later?
(06-04-2018 09:44 PM)ToastyX Wrote: [ -> ]
(06-02-2018 10:02 PM)adnansajid33 Wrote: [ -> ]I tried reset-all.exe and rebooted but still see the same thing... Also tried uninstalling and then reinstalling all the graphics drivers but to no avail.
Has it cleared up? It looks like the pixels are stuck that way for some reason. I haven't seen anything like that before. Is it like that in the BIOS screen? That would indicate a hardware issue. Did the problem happen immediately after trying 90 Hz, or was 90 Hz working and the problem appeared later?

It has not cleared up, 90Hz was working and the problem appeared later. I was able to play games for 2 hours and then is when the problem appeared. It is like that in the bios too.
(06-04-2018 09:40 PM)ToastyX Wrote: [ -> ]I don't recommend removing pin 12 because AMD's driver has a bug with VGA that causes it to get stuck in a loop trying to redetect the monitor if there's no EDID. I don't know if that's the problem you're seeing, but it's not supposed to happen if the pin is present and the monitor has an EDID.

You might be better off getting an HDMI-VGA converter to work around the problem, or use an NVIDIA card. I don't think AMD cares about fixing VGA bugs anymore. It might work with an older driver. I think 15.7 is the oldest driver that supports the R7 360: https://support.amd.com/en-us/download/d...4&rev=15.7

Make sure to use DDU first to uninstall the newer driver: https://www.wagnardsoft.com/display-driv...aller-ddu-

The old Catalyst drivers also had an option to ignore the EDID and set the maximum resolution and refresh rate manually for VGA connections.

Yep, I know the bug (some years worked as repair man, some Sony G models had corrupt EDID due to faulty cable or faulty chip; to be sure checked with another cable with higher quality and with all pins) and it is here without removing the pin

Anyway I managed to fix it at 119Hz, but still trying to loop but rarely (a couple of tests with games), and again checked EDIDs of monitors if the bytes 35-53 are ok by the standard

Edit: After the fiasco with versions after starting 18.x driver line I'm sure AMD was so hardly cornered that they just give it a go and added "Switch driver" option ... So professional
how to uninstall ?
[/size]
thx for software. if CRU dont work for you, try again and again. for me it done after second try ( radeon 7870, 18.6.1 latest driver, cru 1.3.99-p1)
- suddenly my main resolution dissapeared from resolution driver list in w10 - cru help Wink
Hey ToastyX, all,
I've been pulling my hairs for the past couple of days, almost a week now, trying to have the nVidia driver output RGB limited (16-235).
Yes it's the exact inverse problem 99% of the posts on the internet have, where everyone wanted RGB full range (0-255) when using HDMI outputs to their device.

I really could use some help at this point..

Here's the data:
- on Win7 SP1 32bit
- using nVdia driver 342.01 WHQL because it's the last supported by my GPU (Geforce 8 Series 8500GT).
- My main (and only) display is an old (2010) Sony HDTV 40W4500. It doesn't support RGB full range via any HDMI inputs.

The issue:
Although I'm connecting the 8500GT directly to 40W4500 via HDMI (with spdif passthough taken from my mobo to an input on the GPU), I'm always getting RGB full out of the nVidia driver, either from the generic Win7 MS one to the latest nVidia one for my card.
The result is black crush on the desktop and everything except videos (for which madVR does the trick, thank god, to output the correct range).
I tried at least 20 nvidia drivers, from the early 190.x, 250.x up to 342.01 with no difference whatsoever, they're always outputting RGB full.
It's completely nuts as the whole of mankind has been having the exact opposite problem for 8-9 years, and here I just wished it happened to me once xD

Here are my findings:
- nVidia driver 347.09 and newer have a simple (fucking) toggle to select either RGB full or RGB limited, my dream on earth atm. Sadly it doesn't support my GPU. Modding the inf went nowhere (it installed but doesn't recognized the GPU, driver won't start when associated with this GPU as reported in Win7 dev manager).
- On the exact same system, same card, same driver version (342.01 for XP), same HDMI cable, same TV, but using Windows XP, I *do* get RGB limited by default, no questions asked, without any tweaking whatsoever.
I'm absolutely baffled. It seems to me that the nvidia driver on Win7 just won't output RGB limited under any circumstance all. But then why all these posts on the web trying "to force RGB full"...?
- I know I can use YCbCr444 from the nVidia driver for the "Digital color format" to get proper levels but colors are a bit off compared to RGB limited on my device.
- I tried the "Nvidia RGB Full/limited range toggler" (adds SetDefaultFullRGBRangeOnHDMI to registry, of course setting it to "0" to try to force RGB limited, no go).
- I tried changing registry values in the nvidia registry entries trying to force the display to be detected as an HDTV, which IT ALREADY IS IN THE NVIDIA CONTROL PANEL, no go.
I absolutely don't get why the driver doesn't want to output RGB limited when it's clearly detecting an HDMI connection going to an HDTV.
- I started reading CTA-861-G_FINAL_revised_2017 trying to find what to change in the EDID to try to force RGB limited this way but it's sooooo complex it didn't help at all ^^;

Now, I have 2 more leads.
- The first one is possibly the nVidia driver not considering my HDTV really as such because the audio is passthrough and no "nvidia HD Audio driver" is installed on the system.. Before GPUs started to have onboard HDaudio, a couple models including mine had this spdiff plug on the GPU to use as passthrough.
If that's the case, because the driver truly doesn't consider it as an HDTV, it sends RGB full (even though, again, the control panel sees the monitor as an HDTV and the connector is indicated as HDMI - HDTV).
- The second: the EDID from my HDTV is old/incomplete and under Win7 the nVidia driver sees it as supporting only RGB full and so enforces that??
(which would be strange because the same driver version on XP uses RGB limited, then again the XP driver could be hardcoded to send RGB limited regardless of EDID?)

So, is there a way I can modify my HDTV's EDID to specify it (only) expects RGB limited?
Here is the dump of my oridinal EDID:
[attachment=337]


Sorry for the very long post but I needed to put everything down.
If someone can give a hand, by all means..

ps24u
HOLY FUCK!!!!!!!!!!!!!!!!!!
I FOUND THE SOLUTION!
In CRU, I edited the Extension Block > Video Capability. I set "Selectable RGB Range" to OFF.
Restart.exe
Fixed.
I'm absolutely amazed. And confused. And shocked. Been trying so much stuff.
ToastyX, I love you. I really do hahahaHAhahHah.
registered at monitortest.com just so i could personally thank @toastyx for this fantastic tool...

i use an htpc to stream only widescreen movie files to my 2:35 projector screen, and this handy tool allowed me to scale plex (and other media services) to fit the screen very nicely... my system is a windows 10/64 box with an i5 processor / intel hd graphics 6000 - you could set a custom resolution using intel's hd graphics panel, but it just wouldn't stick, it would revert back to the "recommended" rez after every boot.

[Image: image.jpg]

this image is kind of hard to read, but 1920 x 817 has become my new (recommended) resolution:

[Image: image.png]

btw, i didn't install any of the drivers listed on the first page, thought i'd first give it a go without, and everything seems to be working just fine! thanks again!
Hello!

I have a DVI monitor (Samsung SyncMaster SA300) that I was able to push to 1920x1080@77 Hz using a single-link DVI when I had a desktop with a NVIDIA GPU. Since then, I got a laptop with an Intel GPU that has a HDMI 1.4 port. I bought a passive HDMI-DVI adapter to still be able to use the monitor and I could reach 71.017 Hz before the monitor turns black. It seems that anything beyond this value changes the polarity and other parameters and, even though the pixel clock still is below 165 MHz, not even a "Not Optimum Mode" message shows up.

Is the HDMI a limiting factor now, or is something else required for a setup like mine to work with an Intel GPU?
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809
Reference URL's