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 810
Thanks, Toasty,
However there is no 1280x720@60hz to remove.
It's shown in the list of resolutions in CCC and in display settings, but I can't remove it.

Here's something else I just found out: Maybe this will help you with what's going on:

If I use reset-all, restart the computer, etc, 50 hz is gone (well its in italics, so its "unsupported") at 1920x1080.
HOWEVER.....

if I export the cru file right after doing reset all (and restarting before exporting), then reboot, then re-import the stock file I just exported....guess what?
50 hz is there again, even though I "changed" nothing...

It seems that if I make *ANY* change to anything in CRU, even if its an edit and a remove of something, 50 hz is added, but only at 1920x1080....
(04-11-2014 08:54 AM)falkentyne Wrote: [ -> ]Here's something else I just found out: Maybe this will help you with what's going on:

If I use reset-all, restart the computer, etc, 50 hz is gone (well its in italics, so its "unsupported") at 1920x1080.
HOWEVER.....

if I export the cru file right after doing reset all (and restarting before exporting), then reboot, then re-import the stock file I just exported....guess what?
50 hz is there again, even though I "changed" nothing...

It seems that if I make *ANY* change to anything in CRU, even if its an edit and a remove of something, 50 hz is added, but only at 1920x1080....
I just checked with the VG248QE. For some reason, AMD's driver is adding 50 Hz even if I reset everything and don't make any changes with CRU. I don't know why the driver is behaving that way. The monitor's EDID doesn't even define any 50 Hz resolutions.

The driver won't add 50 Hz and 60 Hz if you remove all the standard and established resolutions. Technically, you don't need them anyway because the driver will automatically add lower resolutions with GPU scaling.
ToastyX, sometimes I can see a very brief flash and some line across the screen, but that is just sometimes. Now Im thinking is that because of this overclock ? Should I be worried ? How can I spot if my overclock is not good?
(04-10-2014 09:22 PM)ToastyX Wrote: [ -> ]
(04-09-2014 06:44 AM)monitor Wrote: [ -> ]Yes iv seen in this thread people lowering the blanking/total values to reduce the pixel clock and acheive higher refresh rates. What im needing explained is what the front porch, sync width, back porch, blanking and total values are and if a higher or lower number is best. Is increasing the pixel clock beneficial and what is the pixel clock limit.
The front porch is the period before the sync pulse. The sync width is the length of the sync pulse. The back porch is the period after the sync pulse. There are no "best" values for those parameters. The actual values don't matter much with most LCD monitors. Just use whatever works with the monitor.

The blanking is the period between each line and frame that includes the front porch + sync width + back porch. If you want to reduce the blanking, you'd have to reduce at least one of those values. CRU changes the back porch if you change the blanking or total values. The total is the active + blanking.

The pixel clock is the total number of pixels per second: horizontal total * vertical total * refresh rate. If you were trying to get higher refresh rates and the standard values weren't working, you'd want to try lower blanking/total values to reduce the pixel clock. Increasing the pixel clock is not beneficial because it wastes bandwidth and can cause signal quality problems if the hardware or the cable can't handle it.

I don't know what you're trying to do because you're not trying to get higher refresh rates and the standard values work with your monitor.

Thanks for the explanation. At first i was trying to downsample with CRU but all it resulted in was a blurry screen. So i then decided to see if i could improve the monitor with different settings. What i dont understand is that if there are no best settings and higher or lower settings dont matter then why are the still shipping 60Hz IPS monitors when those monitors are capable of at least 72Hz ?
(04-12-2014 12:23 PM)monitor Wrote: [ -> ]Thanks for the explanation. At first i was trying to downsample with CRU but all it resulted in was a blurry screen. So i then decided to see if i could improve the monitor with different settings. What i dont understand is that if there are no best settings and higher or lower settings dont matter then why are the still shipping 60Hz IPS monitors when those monitors are capable of at least 72Hz ?
Manufacturers don't seem to care. They must not consider it a significant market.

While there are no best settings, there are standards to make sure everything can interoperate with each other. For 1920x1080 monitors, 72 Hz with standard timing parameters exceeds the 165 MHz pixel clock limit for single-link DVI. Using dual-link DVI would increase cost and reduce compatibility with systems that don't have dual-link DVI. It could be done with HDMI, but only newer GPUs support going past 165 MHz with HDMI, and HDMI requires paying royalties.

In reality, interoperability shouldn't even be a concern because monitors report what settings to use in the EDID. 1920x1080 @ 72-75 Hz could also be done with non-standard timing parameters, but that's not commonly done. I've only seen 144 Hz monitors use non-standard timing parameters to fit 144 Hz under 330 MHz, and the same timing parameters could be used to fit 72 Hz within 165 MHz.

Regardless, it's technically possible and not even that difficult, so they must not care enough to offer 72-75 Hz IPS monitors.
(04-11-2014 03:24 PM)La9000 Wrote: [ -> ]ToastyX, sometimes I can see a very brief flash and some line across the screen, but that is just sometimes. Now Im thinking is that because of this overclock ? Should I be worried ? How can I spot if my overclock is not good?
Have you tried the "LCD standard" or "LCD reduced" timing options? Overclocking monitors is generally safe. You don't have to worry about 75 Hz damaging your monitor. Either the monitor can handle it, or it won't display a proper picture. If you don't see any problems, then it's good.
Toasty -

I'll be the first to admit I did not search through the 80+ pages of this thread, but I'm hoping you can give me a quick and dirty answer.

I'm looking to lock the resolution on my XP machine regardless of the monitor attached.

Example:

I have an ASUS attached, I set the resolution to 1280x1024 60Hz, I run the EDID override to lock this in.

I connect an LG, I would like the resolution to be locked to 1280x1024 60Hz without needing to perform additional steps. ie EDID is block for every monitor after I've defined my settings.

Is this possible? It appears your tool creates an entry for the monitor attached, is there a way to assign this globally rather than on a per monitor basis?

THANKS! Wink

FYI I have the ability to disable DDC completely in hardware, this may be the necessary solution, let me know your thoughts on that.
(03-20-2014 05:42 AM)ToastyX Wrote: [ -> ]
(03-19-2014 01:50 PM)incep Wrote: [ -> ]However, yesterday I updated my driver to the latest ATI beta (14.3), which put my monitor into a test loop because it couldn't understand the input it was getting anymore. It happened right when the driver started up, in the middle of the installation process. Is this due to an incompatability in this tool, or is it the patchtool which doesn't work?
That shouldn't happen unless you deleted 60 Hz. You need to keep a resolution that the updated driver can use before it's patched.

There shouldn't be any compatibility issues with 14.3. If the patcher needs to be updated, it should tell you which limits were not found.

Hi again. Thanks for your reply. I'm a little slow here. You were right, I had only changed my 60hz mode, and it had nothing to fall back to.

I have now installed the latest AMD 14.3 driver, and while patching it with the atimdag patcher, it couldn't find the DVI/HDMI value, it told me.
I'm setting custom resolutions in CRU, but they're not showing up in CC or Windows resolution settings.

Win 8.1
HD7970GE
Qnix QX2710 monitor

Oh, and by the way.. Thanks for making these tools for the community, and replying to everyones questions in these threads. It's people like you that make the world a slightly better place!
(04-15-2014 10:28 PM)incep Wrote: [ -> ]I have now installed the latest AMD 14.3 driver, and while patching it with the atimdag patcher, it couldn't find the DVI/HDMI value, it told me.
I'm setting custom resolutions in CRU, but they're not showing up in CC or Windows resolution settings.
You need to update the patcher: https://www.monitortests.com/forum/Threa...ck-Patcher
(04-15-2014 10:51 AM)blazin912 Wrote: [ -> ]I'm looking to lock the resolution on my XP machine regardless of the monitor attached.
Windows XP does not support EDID overrides.

(04-15-2014 10:51 AM)blazin912 Wrote: [ -> ]It appears your tool creates an entry for the monitor attached, is there a way to assign this globally rather than on a per monitor basis?
I don't know of a way to do that with software. EDID overrides were meant to apply to specific monitors. The driver considers each monitor with a different EDID to be a separate monitor, so the override would only apply to that monitor. It could be done with a device that sends the same EDID no matter what monitor is connected, or you can try modifying a cable to remove the DDC pin to disable monitor detection.
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 810
Reference URL's