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
Hi, I'm just trying to do something modest.
I've buyed some time ago a monitor that says 165Hz in the box, the guy that sold me says that I have to overclock it to reach that.
Now I'm here, when I add a Detail resolution 1980x1920@165Hz with CRU (with the timings [Automatic (PC)])
It doesn't appear as an option when I restart my pc/ execute "restart64.exe" in any place.
What's curious is that, now in my Intel Graphics Command Center appears listed as a supported mode, but I still can't change my monitor to 165Hz, why is that? how can I fix it?
Thanks for the work on this program Big Grin
(I leave my Exported .bin file in here too)
- Intel UHD 730 Graphics
- Monitor WP-M0270 (A peruvian brand bought from a chinese OEM and sell it to me, it has a dead pixel and they were selling it very cheap because of that Big Grin)
(05-25-2022 07:28 PM)pragmaticmero Wrote: [ -> ]What's curious is that, now in my Intel Graphics Command Center appears listed as a supported mode, but I still can't change my monitor to 165Hz, why is that? how can I fix it?
That means the driver recognizes the resolution but there's a bandwidth limitation. Are you using HDMI or DisplayPort? HDMI 1.x is limited to 340 MHz pixel clock, and I don't think that monitor has HDMI 2.0. The monitor probably only supports 1920x1080 @ 165 Hz with DisplayPort.
(05-25-2022 02:55 PM)ToastyX Wrote: [ -> ]
(05-25-2022 04:54 AM)carbs Wrote: [ -> ]The res just doesn't appear as a possible mode. No errors or anything. Just doesn't show up in the list.
Then you'll have to show me exactly what you're doing. Export a file with the changes and post it here.

I have attached the default file that generates on a complete reset and my attempt to add forced display scaled 1440x1080.
(05-26-2022 02:37 AM)carbs Wrote: [ -> ]I have attached the default file that generates on a complete reset and my attempt to add forced display scaled 1440x1080.
You need to read the part about extension blocks.
For years, I used a 1080p LCD monitor with an HDMI connection and an old Toshiba 34HF84 1080i CRT HDTV via an old Panasonic XR57 A/V receiver. The receiver only has one HDMI input and one output and only supports 1080i. My old video card was an AMD RX460 and this setup worked fine and allowed me to see both video and hear audio (I had the main monitor hooked up via the HDMI output and the Receiver/TV with a DVI to HDMI adapter). Well, I recently upgraded to an AMD RX 6600 XT card and now I can't get the same setup to work.

I removed the DVI to HDMI adapter from the setup because the new card has two HDMI outputs. When I installed the new card, the computer monitor worked fine, but I didn't get a picture on the CRT. I then rebooted with the computer monitor off and the CRT on and saw the boot screen appear on the CRT, but then I couldn't see anything on the LCD when I turned it on. I tried uninstalling and reinstalling the drivers to no avail. I see in the settings that my BenQ LCD monitor is detected as well as the XR57 receiver, but for the receiver it's giving it a 1080p signal at 60Hz that it doesn't support. I tried to manually add a 1080i 30Hz resolution through the AMD software, but that doesn't work. It says the custom resolution isn't compatible with the display.

I then downloaded CRU to try to add this resolution, but after adding it to the detailed resolutions and the CTA-861 Extension block and restarting the display driver, I still don't see 1080i as 30Hz as an option when I "list all modes" for the display adapter and Monitor under Windows 11, I only see the 1080p options with 50Hz, 59Hz and 60Hz options. I don't see anything for 1080i and 30Hz like I used to on my old setup. Does anyone have any suggestions? I just want to have the 1080p 60Hz LCD as my work monitor and use the CRT/AVR setup to watch video files and haven't had much luck after several hours of trouble shooting. I'm new to this program, so may be missing something obvious.
(05-26-2022 05:53 PM)althoma1 Wrote: [ -> ]I then downloaded CRU to try to add this resolution, but after adding it to the detailed resolutions and the CTA-861 Extension block and restarting the display driver, I still don't see 1080i as 30Hz as an option when I "list all modes" for the display adapter and Monitor under Windows 11, I only see the 1080p options with 50Hz, 59Hz and 60Hz options. I don't see anything for 1080i and 30Hz like I used to on my old setup. Does anyone have any suggestions? I just want to have the 1080p 60Hz LCD as my work monitor and use the CRT/AVR setup to watch video files and haven't had much luck after several hours of trouble shooting. I'm new to this program, so may be missing something obvious.
AMD's driver does not support interlaced for RX 5000/6000-series GPUs.
(05-25-2022 07:28 PM)pragmaticmero Wrote: [ -> ]Hi, I'm just trying to do something modest.
I've buyed some time ago a monitor that says 165Hz in the box, the guy that sold me says that I have to overclock it to reach that.
Now I'm here, when I add a Detail resolution 1980x1920@165Hz with CRU (with the timings [Automatic (PC)])
It doesn't appear as an option when I restart my pc/ execute "restart64.exe" in any place.
What's curious is that, now in my Intel Graphics Command Center appears listed as a supported mode, but I still can't change my monitor to 165Hz, why is that? how can I fix it?
Thanks for the work on this program Big Grin
(I leave my Exported .bin file in here too)
- Intel UHD 730 Graphics
- Monitor WP-M0270 (A peruvian brand bought from a chinese OEM and sell it to me, it has a dead pixel and they were selling it very cheap because of that Big Grin)

Use displayport and not HDMI - your intel graphics may simply not work at 165Hz
Hi everyone, new here, first post following a recommendation from someone in the Kodi forums. I've scanned this *huge* thread but it's massive so it's likely I missed it - hope posting here is the right thing to do.

My issue is that I am trying to force Kodi to play all media files at their native resolution - 1080p or 2160p. I want all necessary scaling to be done by my TV, not by Kodi or my graphics drivers.

I'm doing all of this on: Intel NUC8i3BEK (Intel Iris Plus Graphics 655, latest driver version and Win 11) running Kodi 19.4.

The issues I'm having are summarised by this behaviour:

1. Intel Graphics Command Centre: set scaling to "maintain display scaling" and choose desktop resolution to be 1920x1080p60.
2. TV confirms it is receiving a 1920x1080p60 input signal, and Windows advanced display settings confirm that "desktop resolution" and "active signal resolution" are both the same, 1920x1080p60.
3. Start Kodi. Kodi GUI is set at 1920x1080p60 and the TV confirms it is receiving this input signal.
4. Play a 1920x1080p video. TV switches refresh rate to match the video, but the input resolution it reports changes to 3840x2160. Something is scaling the video up before it gets to the display.
5. When I then exit Kodi, I find that the Intel Graphics Command Centre has reset itself to "maintain aspect ratio" and the "active signal resolution" is back to 2840x2160p60. "Desktop resolution" is still 1920x1080p.

Alt-O during playback confirms that Kodi is rendering each file I play in its native resolution, while the TV signal input info confirms it is receiving a 2160p signal regardless of source file resolution. This means that the change from 1080p to 2160p is happening in the intel driver / Windows portion of the chain. As I've described above, playing a media file back in Kodi seems to override my Intel driver settings and cause it to revert the active display resolution back to 2160p and scaling to "keep aspect ratio".

So my default position is that Windows display settings "active signal resolution" says 2160p but the display driver is set to render the desktop at 1080p. I'm completely lacking any confidence that the native res output from Kodi isn't being manipulated down to 1080p by the Intel driver then back up to 2160p by Windows to meet its "active display resolution" setting.

What is going on? I'm sure sending a video file to my TV at native resolution with no scaling shouldn't be this hard to achieve. Can CRU help me achieve what I want to achieve?

My thread on this in the Kodi forums is here FYI https://forum.kodi.tv/showthread.php?tid=366528
(05-27-2022 11:36 AM)Bertie_bassett Wrote: [ -> ]So my default position is that Windows display settings "active signal resolution" says 2160p but the display driver is set to render the desktop at 1080p. I'm completely lacking any confidence that the native res output from Kodi isn't being manipulated down to 1080p by the Intel driver then back up to 2160p by Windows to meet its "active display resolution" setting.

What is going on? I'm sure sending a video file to my TV at native resolution with no scaling shouldn't be this hard to achieve. Can CRU help me achieve what I want to achieve?
It sounds to me like there might be a driver bug that causes the scaling option to reset after certain resolution changes. The way Windows drivers are supposed to work is refresh rates at the native resolution are added at lower resolutions as scaled resolutions if the EDID does not have that specific resolution defined. For example, if 3840x2160 @ 24 Hz exists but not 1920x1080 @ 24 Hz, it will scale 1920x1080 @ 24 Hz to 3840x2160. You have to make sure the refresh rates you want exist for all the resolutions you want in the EDID. If this is happening with all the resolutions and refresh rates defined in the EDID, then it might be a driver bug. Unfortunately, CRU can't read the extension block with Intel GPUs, so that makes it harder to see what's defined by default. What is the product ID for your TV as shown in the CRU monitor list?
(05-27-2022 10:15 PM)ToastyX Wrote: [ -> ]
(05-27-2022 11:36 AM)Bertie_bassett Wrote: [ -> ]So my default position is that Windows display settings "active signal resolution" says 2160p but the display driver is set to render the desktop at 1080p. I'm completely lacking any confidence that the native res output from Kodi isn't being manipulated down to 1080p by the Intel driver then back up to 2160p by Windows to meet its "active display resolution" setting.

What is going on? I'm sure sending a video file to my TV at native resolution with no scaling shouldn't be this hard to achieve. Can CRU help me achieve what I want to achieve?
It sounds to me like there might be a driver bug that causes the scaling option to reset after certain resolution changes. The way Windows drivers are supposed to work is refresh rates at the native resolution are added at lower resolutions as scaled resolutions if the EDID does not have that specific resolution defined. For example, if 3840x2160 @ 24 Hz exists but not 1920x1080 @ 24 Hz, it will scale 1920x1080 @ 24 Hz to 3840x2160. You have to make sure the refresh rates you want exist for all the resolutions you want in the EDID. If this is happening with all the resolutions and refresh rates defined in the EDID, then it might be a driver bug. Unfortunately, CRU can't read the extension block with Intel GPUs, so that makes it harder to see what's defined by default. What is the product ID for your TV as shown in the CRU monitor list?

This sounds promising, thank you for such a detailed reply. I haven’t actually been able to install CRU yet so I can’t answer your question about the product ID, but as soon as I can I’ll post back here. However, I am routing the signal to my TV via one of these which could well be reporting the EDID info incorrectly. This device does support EDID editing, and I suspect that the only remedy would be to manually edit the EDID… that’s a bit daunting to say the least. But I will explore.

Thanks again!
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