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 811
(12-28-2015 05:36 AM)MightyUnit Wrote: [ -> ]You mean this, correct? If not please tell me what you need. Thank you for helping me!
I wanted a .bin file, but this has the information I need. The only problem I see is the monitor says there's an extension block when there isn't one, but the Catleap/QNIX monitors have the same problem, and those monitors work with NVIDIA cards, although they did have similar black screen issues with certain driver versions until NVIDIA fixed the problem.

Have you tried anything with CRU? Setting a custom extension block would fix the EDID, but I don't think that will work if the monitor isn't detected properly. This seems like a driver issue that NVIDIA needs to fix.

I don't think the EDID is write-protected on these monitors, so you might be able to fix the problem by using CRU to export an EDID with no extension block and flashing the EDID using one of these methods: http://www.blurbusters.com/zero-motion-b...dware-mod/
(12-31-2015 05:30 AM)ToastyX Wrote: [ -> ]
(12-28-2015 05:36 AM)MightyUnit Wrote: [ -> ]You mean this, correct? If not please tell me what you need. Thank you for helping me!
I wanted a .bin file, but this has the information I need. The only problem I see is the monitor says there's an extension block when there isn't one, but the Catleap/QNIX monitors have the same problem, and those monitors work with NVIDIA cards, although they did have similar black screen issues with certain driver versions until NVIDIA fixed the problem.

Have you tried anything with CRU? Setting a custom extension block would fix the EDID, but I don't think that will work if the monitor isn't detected properly. This seems like a driver issue that NVIDIA needs to fix.

I don't think the EDID is write-protected on these monitors, so you might be able to fix the problem by using CRU to export an EDID with no extension block and flashing the EDID using one of these methods: http://www.blurbusters.com/zero-motion-b...dware-mod/

Thanks for the reply Toastyx,

What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?

EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip

EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin
(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]
(12-31-2015 05:30 AM)ToastyX Wrote: [ -> ]
(12-28-2015 05:36 AM)MightyUnit Wrote: [ -> ]You mean this, correct? If not please tell me what you need. Thank you for helping me!
I wanted a .bin file, but this has the information I need. The only problem I see is the monitor says there's an extension block when there isn't one, but the Catleap/QNIX monitors have the same problem, and those monitors work with NVIDIA cards, although they did have similar black screen issues with certain driver versions until NVIDIA fixed the problem.

Have you tried anything with CRU? Setting a custom extension block would fix the EDID, but I don't think that will work if the monitor isn't detected properly. This seems like a driver issue that NVIDIA needs to fix.

I don't think the EDID is write-protected on these monitors, so you might be able to fix the problem by using CRU to export an EDID with no extension block and flashing the EDID using one of these methods: http://www.blurbusters.com/zero-motion-b...dware-mod/

Thanks for the reply Toastyx,

What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?

EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip

EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin

I don't know what you linked, but that EDID program says the 30 day period has expired and won't run.

I know you can use Linux to run the file "write-edid.sh" (that was packed in a write-edid.zip file with someone who was having trouble flashing their edid with the more easily obtainable edid-rw Linux file.

The regular edid-rw file is downloaded through a Linux / Ubuntu shell here:

sudo apt-get install python-smbus edid-decode
and ./edid-rw X | edid-decode as shown on the link ToastyX linked.

I had a problem where EDID-RW failed to write the EDID on my VG248QE even though I removed the write protect (by enabling burn-in mode in the service menu). It would just write and do nothing.

But write-edid.sh after compiled with the required libraries worked perfectly.
But I already had an EDID backup to use it in the first place (I had two VG248QE's and one of them had a Benq XL2720Z EDID (don't ask how, trust me, don't ask Smile)
That Edid programmer runs for me. Click past the errors messages and it runs fine. Like I said I used it to flash two L245WPs last week. I am just not sure if .bin is the same as .edid. I am afraid to flash until I know it is.

Concerning Linux, it is my last resort for flashing. I know know, yada yada yada, it is so easy and such but not for me for some reason.
(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?
Why not both? Flash the EDID to check if that's the problem, and then report it to NVIDIA.

Does the monitor support 1280x800? I assume it does since you're able to see the boot screens. The monitor defines 1280x800 as the native resolution, probably for compatibility with single-link DVI, which could cause a black screen if the monitor didn't support it, but that shouldn't prevent the monitor from being detected. I've seen other 2560x1600 monitors do the same thing. You can make 2560x1600 the first detailed resolution if you want it to be the native resolution. Then GPU scaling should scale to 2560x1600 instead of 1280x800.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip
Where did you find this? I can't run it. It says it uses a demo version of the WinI2C/DDC component and that the 30-day trial period expired. I don't know anything about it since it's not documented anywhere, but if you got it to work with the LG, then it might work with any monitor.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin
No, the included .edid files look like the raw data as tab-separated hex values. I can't run the program, so I can't see if it will accept other types. Most EDID programs support the .bin format.

I manually converted the raw data with the extension block removed and with 2560x1600 as the first detailed resolution:
[attachment=138][attachment=139]
(01-02-2016 04:38 AM)ToastyX Wrote: [ -> ]
(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?
Why not both? Flash the EDID to check if that's the problem, and then report it to NVIDIA.

Does the monitor support 1280x800? I assume it does since you're able to see the boot screens. The monitor defines 1280x800 as the native resolution, probably for compatibility with single-link DVI, which could cause a black screen if the monitor didn't support it, but that shouldn't prevent the monitor from being detected. I've seen other 2560x1600 monitors do the same thing. You can make 2560x1600 the first detailed resolution if you want it to be the native resolution. Then GPU scaling should scale to 2560x1600 instead of 1280x800.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip
Where did you find this? I can't run it. It says it uses a demo version of the WinI2C/DDC component and that the 30-day trial period expired. I don't know anything about it since it's not documented anywhere, but if you got it to work with the LG, then it might work with any monitor.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin
No, the included .edid files look like the raw data as tab-separated hex values. I can't run the program, so I can't see if it will accept other types. Most EDID programs support the .bin format.

I manually converted the raw data with the extension block removed and with 2560x1600 as the first detailed resolution:

Thanks for the reply.

Thank you for converting the raw data. I think I am ready to try to write.... Have a look. I loaded your dnd9220-2560x1600.edid with my edid programmer and I am tempted to hit write.

[Image: http://i866.photobucket.com/albums/ab224/mightyunit/should_zpsn6d0rr1v.jpg]


EDIT: I did contact Nvidia and I have currently made it to level 2 tech support. They asked for my video card part #, msinfo32 report and the edid pulled from my display.
(01-02-2016 05:17 AM)MightyUnit Wrote: [ -> ]
(01-02-2016 04:38 AM)ToastyX Wrote: [ -> ]
(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?
Why not both? Flash the EDID to check if that's the problem, and then report it to NVIDIA.

Does the monitor support 1280x800? I assume it does since you're able to see the boot screens. The monitor defines 1280x800 as the native resolution, probably for compatibility with single-link DVI, which could cause a black screen if the monitor didn't support it, but that shouldn't prevent the monitor from being detected. I've seen other 2560x1600 monitors do the same thing. You can make 2560x1600 the first detailed resolution if you want it to be the native resolution. Then GPU scaling should scale to 2560x1600 instead of 1280x800.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip
Where did you find this? I can't run it. It says it uses a demo version of the WinI2C/DDC component and that the 30-day trial period expired. I don't know anything about it since it's not documented anywhere, but if you got it to work with the LG, then it might work with any monitor.

(12-31-2015 05:53 AM)MightyUnit Wrote: [ -> ]EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin
No, the included .edid files look like the raw data as tab-separated hex values. I can't run the program, so I can't see if it will accept other types. Most EDID programs support the .bin format.

I manually converted the raw data with the extension block removed and with 2560x1600 as the first detailed resolution:

Thanks for the reply.

I run the Edid programmer, click past two error messages and then last message is that this program uses and unregistered version of "WINI2C/DDC component" if that means anything to you.

Thank you for converting the raw data. I think I am ready to try to write.... Have a look. I loaded your dnd9220-2560x1600.edid with my edid programmer and I am tempted to hit write.

[Image: http://i866.photobucket.com/albums/ab224/mightyunit/should_zpsn6d0rr1v.jpg]


EDIT: I did contact Nvidia and I have currently made it to level 2 tech support. They asked for my video card part #, msinfo32 report and the edid pulled from my display.

I know what you're saying
"click past the 2 errors' right?

I KNOW.
I click past them and the program DOES NOT LOAD
at all
Because it's expired or something.
It's not even active in memory.
So, yeah. I can't use this program and ToastyX can't seem to run it either.
I don't know why it runs for you.
That is odd. I tried and I am can run that EDID programmer on my win 7 and win 10 machines.

Before I flash how likely do you think I am to brick my Corssover 30Q5? I am confident in my EDID programmer program and so my concern would be with the modded edid. Chances are that most would be more concerned with my janky edid programmer being the cause of a bad flash... am I right?

EDIT: so I tried to write the EDID. It seemed to work but after power cycling the monitor the original edid is back in there.
@ ToastyX

I've got an old but functional CRT monitor LG F700P which can handle 150hz @ 800x600, but those options aren't avaiable in my NVIDIA settings (I'm on a notebook, with Geforce 740M).

So, I try to use the CRU but after setting my new custom refreshrate, ticking the custom extension block option and reseting the driver/rebooting the computer, I can't find the new Hz as an option... it gets stuck @ 120hz in 800x600.

What am I missing here?

thanks.
(01-04-2016 12:52 AM)qwer Wrote: [ -> ]I've got an old but functional CRT monitor LG F700P which can handle 150hz @ 800x600, but those options aren't avaiable in my NVIDIA settings (I'm on a notebook, with Geforce 740M).

So, I try to use the CRU but after setting my new custom refreshrate, ticking the custom extension block option and reseting the driver/rebooting the computer, I can't find the new Hz as an option... it gets stuck @ 120hz in 800x600.

What am I missing here?
If the NVIDIA control panel does not have custom resolution options and the laptop has an Intel GPU, then the laptop has switchable graphics (Optimus) and can't be used with CRU. The Intel GPU controls the resolutions, and Intel's driver does not currently support EDID overrides. You have to create custom resolutions using Intel's control panel instead.
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 811
Reference URL's