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 812 813 814
(03-06-2019 08:56 PM)alexander1986 Wrote: [ -> ]so anyway after a lot of unsucessful attempts of fixing the issue/going back to how it was before my updates, I found your CRU app, and tried to use that instead of nvidia driver to set up the stretched res, so when I set my stretched 1600x1080 res in CRU @ 119 hz it seems to work fine both in the game and on desktop, aswell as the OSD on monitor reading 1600x1080 instead of 1920x1080 which is great, the only problem is I have no idea how to set up lightboost enabled in CRU for this res and hz, and wonder if this is possible at all? it seems to be done automatically in nvidia somehow when strobelight is active,?
LightBoost only works correctly at the native resolution. You have to use GPU scaling to have LightBoost at lower resolutions, which is what the NVIDIA control panel is doing by default when you create a custom resolution with the "Automatic" timing standard (look at the active pixels). GPU scaling should not add lag. The mouse offset sounds like a separate unrelated problem, but I'm not sure what would cause that. Maybe adding the resolution with CRU will have a different effect. If GPU scaling is enabled, the timing parameters won't matter since it will be using the native resolution anyway.
(03-06-2019 09:18 PM)ToastyX Wrote: [ -> ]
(03-06-2019 08:56 PM)alexander1986 Wrote: [ -> ]so anyway after a lot of unsucessful attempts of fixing the issue/going back to how it was before my updates, I found your CRU app, and tried to use that instead of nvidia driver to set up the stretched res, so when I set my stretched 1600x1080 res in CRU @ 119 hz it seems to work fine both in the game and on desktop, aswell as the OSD on monitor reading 1600x1080 instead of 1920x1080 which is great, the only problem is I have no idea how to set up lightboost enabled in CRU for this res and hz, and wonder if this is possible at all? it seems to be done automatically in nvidia somehow when strobelight is active,?


LightBoost only works correctly at the native resolution. You have to use GPU scaling to have LightBoost at lower resolutions, which is what the NVIDIA control panel is doing by default when you create a custom resolution with the "Automatic" timing standard (look at the active pixels). GPU scaling should not add lag. The mouse offset sounds like a separate unrelated problem, but I'm not sure what would cause that. Maybe adding the resolution with CRU will have a different effect. If GPU scaling is enabled, the timing parameters won't matter since it will be using the native resolution anyway.



I see, thanks for the answer ! interesting, yes I see the active pixels are still at 1920x1080 when I set a 1600x1080 custom res in nvidia with automatic timing, I suppose changing them to 1600x1080 wont work as I want? Tongue probably only without lightboost?

so anyway in my case, is it possible to use CRU instead of nvidia somehow to add the 1600x1080 stretched res with lightboost, even if its being scaled from 1920x1080 ? basically use CRU for gpu scaling ? take over the job from nvidia default somehow?

PS. I also remember if it makes any difference that when I was able to use nvidia custom 1600x1080 res without the mouse offset cursor issue a while back before my updates, I had several additional resolutions to select in nvidia that arent there now, looked like TV/HDTV options, I didnt use them but seems the scaling worked differently when they were there (for example the screen went black for several seconds when switching from stretched game 1600x1080 to native 1920x1080, even if both modes were confirmed running lightboost enabled, now it switches instantly) any clue as to what that could be?

ah well! what I want is maybe not possible at all with lightboost enabled but yeah, if I could somehow get CRU to do the job instead of nvidia its worth a try atleast, thanks again !
(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]I see, thanks for the answer ! interesting, yes I see the active pixels are still at 1920x1080 when I set a 1600x1080 custom res in nvidia with automatic timing, I suppose changing them to 1600x1080 wont work as I want? Tongue probably only without lightboost?
Depending on the timing parameters, it will either work without LightBoost, or LightBoost will be active but it won't be scaled correctly. You can give it a shot to see what happens.


(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]so anyway in my case, is it possible to use CRU instead of nvidia somehow to add the 1600x1080 stretched res with lightboost, even if its being scaled from 1920x1080 ? basically use CRU for gpu scaling ? take over the job from nvidia default somehow?
CRU doesn't deal with scaling, but you can add custom resolutions with CRU and enable GPU scaling in the NVIDIA control panel with the scaling mode set to full screen.


(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]PS. I also remember if it makes any difference that when I was able to use nvidia custom 1600x1080 res without the mouse offset cursor issue a while back before my updates, I had several additional resolutions to select in nvidia that arent there now, looked like TV/HDTV options, I didnt use them but seems the scaling worked differently when they were there (for example the screen went black for several seconds when switching from stretched game 1600x1080 to native 1920x1080, even if both modes were confirmed running lightboost enabled, now it switches instantly) any clue as to what that could be?
There shouldn't be any TV/HDTV resolutions when using Strobelight, so I don't know.
pc: nuc8i7beh
connection: hdmi
display: lg oled55B8pua

i would like to add the following custom resolutions which my 4ktv supports:

[Image: 01.png]

here is some more info that i captured:

LG TV EDID: 4K60 444 HDR BT2020
4K30 RGB BT2020 8b HDR 297MHz
HVS: 81:01:05:49:03:0c:00:20:01
HDR: 87:01:1a:bf:02:00:bb:2f:f9:82:64:19: d4:07: df:80:71:42:18:3d:57:40: db:05:00:00: db:05:1f:03

edid:
00 FF FF FF FF FF FF 00 1E 6D 01 00 01 01 01 01
01 1C 01 03 80 A0 5A 78 0A EE 91 A3 54 4C 99 26
0F 50 54 A1 08 00 31 40 45 40 61 40 71 40 81 80
01 01 01 01 01 01 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 40 84 63 00 00 1E 02 3A 80 18 71 38 2D 40
58 2C 45 00 40 84 63 00 00 1E 00 00 00 FD 00 3A
79 1E 88 3C 00 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 47 20 54 56 0A 20 20 20 20 20 20 20 01 62
02 03 63 F1 5A 61 60 10 1F 66 65 04 13 05 14 03
02 12 20 21 22 15 01 5D 5E 5F 62 63 64 3F 40 32
09 57 07 15 07 50 57 07 01 67 04 03 3D 1E C0 5F
7E 01 6E 03 0C 00 10 00 B8 3C 20 00 80 01 02 03
04 67 D8 5D C4 01 78 80 03 E2 00 CF E3 05 C0 00
E3 06 0D 01 E2 0F 33 EB 01 46 D0 00 26 10 03 25
7E 73 A4 66 21 50 B0 51 00 1B 30 40 70 36 00 40
84 63 00 00 1E 00 00 00 00 00 00 00 00 00 00 07

how would i use this info with csu in order to create the above custom resolutions? thank you very much in advance for your help!
(03-07-2019 11:41 PM)ToastyX Wrote: [ -> ]
(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]I see, thanks for the answer ! interesting, yes I see the active pixels are still at 1920x1080 when I set a 1600x1080 custom res in nvidia with automatic timing, I suppose changing them to 1600x1080 wont work as I want? Tongue probably only without lightboost?
Depending on the timing parameters, it will either work without LightBoost, or LightBoost will be active but it won't be scaled correctly. You can give it a shot to see what happens.


(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]so anyway in my case, is it possible to use CRU instead of nvidia somehow to add the 1600x1080 stretched res with lightboost, even if its being scaled from 1920x1080 ? basically use CRU for gpu scaling ? take over the job from nvidia default somehow?
CRU doesn't deal with scaling, but you can add custom resolutions with CRU and enable GPU scaling in the NVIDIA control panel with the scaling mode set to full screen.


(03-06-2019 10:43 PM)alexander1986 Wrote: [ -> ]PS. I also remember if it makes any difference that when I was able to use nvidia custom 1600x1080 res without the mouse offset cursor issue a while back before my updates, I had several additional resolutions to select in nvidia that arent there now, looked like TV/HDTV options, I didnt use them but seems the scaling worked differently when they were there (for example the screen went black for several seconds when switching from stretched game 1600x1080 to native 1920x1080, even if both modes were confirmed running lightboost enabled, now it switches instantly) any clue as to what that could be?
There shouldn't be any TV/HDTV resolutions when using Strobelight, so I don't know.


thanks a lot for answer!

I was wondering, why I cant see the custom resolutions I set in nvidia showing up in CRU ?

I have a custom 1920x1080@119hz res and a 1600x1080@119hz res set in nvidia, but can only see the default or rather the ones from strobelight in CRU as far as I can tell,

screenshot here of nvidia res + what I see on active monitor in CRU:

[Image: fckPqpx.png]

checked everywhere I could in CRU and rebooted but cant see my 1600 or 1920 @119 hz res there, am I supposed to? Tongue

because it seems my mouse cursor offset issue is fixed in the games menu when the desktop refreshrate matches the stretched refreshrate exactly for some reason, 120hz stretched ingame and 120 hz native desktop = no mouse cursor offset problem,

but the thing is I want 119hz stretched ingame and 119hz native desktop, managed to have it like this before without mouse issue but forgot how.. anyway, my idea now was to add the 119hz to CRU or modify the 120hz 1920 res in CRU to 119hz, but the values are slightly different from the ones nvidia automatically creates and some fields like back porch and so on don't show up like they do in nvidia,

so was thinking, if I could get my custom nvidia resolutions to show up in CRU, I could perhaps delete the 120 hz res from there so its not available for selection at all and kind of force 119hz desktop/119hz stretched game to be the only options?


again sorry if this is confusing lol, but yeah if I could atleast see the custom resolutions from nvidia in CRU to test few things would be great, if not possible I understand Tongue cheers and thanks a lot again dude!
(03-08-2019 12:24 PM)alexander1986 Wrote: [ -> ]I was wondering, why I cant see the custom resolutions I set in nvidia showing up in CRU ?
CRU is separate and has nothing to do with the NVIDIA control panel. Resolutions added with CRU would be listed under the "PC" section. You should be able to use the same timing parameters with CRU. The back porch and blanking are automatically calculated from the totals.
(03-08-2019 08:52 AM)aeneas1 Wrote: [ -> ]how would i use this info with csu in order to create the above custom resolutions? thank you very much in advance for your help!
I don't understand what you're asking. The TV already defines those resolutions in the EDID. You shouldn't need to add them.
(03-08-2019 09:36 PM)ToastyX Wrote: [ -> ]
(03-08-2019 08:52 AM)aeneas1 Wrote: [ -> ]how would i use this info with csu in order to create the above custom resolutions? thank you very much in advance for your help!
I don't understand what you're asking. The TV already defines those resolutions in the EDID. You shouldn't need to add them.

i'd like to add those resolutions because i sometimes need to make changes to the pc configuration remotely (chrome remote), with the 4ktv off, in which case the pc no longer sees the 4ktv edid and instead defaults to 1920x1080... for example, i'm in the process of setting up the pc for 4k uhd hdr file streaming and in order to do it correctly i need have the pc see a 4k hdr capable panel connected so that windows 10 hdr settings will become available/usable... does that make sense? btw, the job you do here, and the help you offer, is nothing short of incredible.
(03-08-2019 09:34 PM)ToastyX Wrote: [ -> ]
(03-08-2019 12:24 PM)alexander1986 Wrote: [ -> ]I was wondering, why I cant see the custom resolutions I set in nvidia showing up in CRU ?
CRU is separate and has nothing to do with the NVIDIA control panel. Resolutions added with CRU would be listed under the "PC" section. You should be able to use the same timing parameters with CRU. The back porch and blanking are automatically calculated from the totals.


I see I see, thanks again for answer Tongue

anyway im not quite sure how even but finally managed to resolve my issue and get 1920x1080@119 hz/lightboost enabled on desktop and 1600x1080 stretched @119 hz/lightboost enabled ingame without the mouse cursor being offset in the menus, feels like the mouse is also a lot more precise as if some input lag is gone now, just like it was before my windows/system update, yay x)


confirmed the refreshrates being 119 with blurbusters refreshrate checker https://www.testufo.com/refreshrate but the OSD says 120, the site says 120 when its 120 though and 119 when its 119 so guess its really 119 and OSD is wrong?


what finally solved the issue for me was instead of adding 1600x1080 to nvidia I did it in CRU @ 119 hz, and in nvidia I added custom res 1920x1080 @119 hz, then by some automagical way both resolutions are strobed, not sure how really lol as I think its not meant to be the case since neither of them exist as strobed resolutions in CRU or strobelight, but guessing nvidia is taking care of it somehow as long as there is like for example a 1920x1080 120 hz strobed res, or something... lol


it works great and when swapping between game/desktop monitor goes black for a while instead of instantly switching and also the mouse cursor being offset is fixed, just like I had it before so am happy now Tongue


if you wonder why I want 119 on desktop/game instead of 120/120 which would be a lot easier to setup I can only say IDK why but for some reason capping 1 frame below refreshrate, even with vsync off, feels a lot snappier and more responsive mousefeeling on my setup, capping with rivatuner at 119.0 and hz is 119.0 exactly aswell,


oof glad to be done with this tweaking for now! anyway, big thanks for help and for both CRU and Strobelight ! my gaming experience would not be the same without them Tongue cheers !
(03-09-2019 03:38 AM)alexander1986 Wrote: [ -> ]confirmed the refreshrates being 119 with blurbusters refreshrate checker https://www.testufo.com/refreshrate but the OSD says 120, the site says 120 when its 120 though and 119 when its 119 so guess its really 119 and OSD is wrong?


what finally solved the issue for me was instead of adding 1600x1080 to nvidia I did it in CRU @ 119 hz, and in nvidia I added custom res 1920x1080 @119 hz, then by some automagical way both resolutions are strobed, not sure how really lol as I think its not meant to be the case since neither of them exist as strobed resolutions in CRU or strobelight, but guessing nvidia is taking care of it somehow as long as there is like for example a 1920x1080 120 hz strobed res, or something... lol
It's probably scaling 1600x1080 @ 119 Hz to 1920x1080 @ 119 Hz, and with the right timing parameters, 119 Hz can still be strobed. The OSD might be wrong in this case.
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 812 813 814
Reference URL's