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
(05-12-2016 12:46 AM)laika Wrote: [ -> ]Toasty, before anything, amazing program. But I've been having a tough time transmitting audio through my HDMI to my hdtv (serving as monitor).

CRU does what is expected, it allows my crappy hdtv resolution to work with (real) 1920x1080.

But when I try using the hdmi.audio custom extension block, my resolution goes back to the crappy one.
The only way to fix this is to set it as 'No Extension Block', but this way I can't have working hdmi audio, because it's detected as a DVI.
The resolution is working. The problem is the TV is treating 1920x1080 differently with HDMI vs. DVI signals, and the only way to get audio is with HDMI support. The only idea I have is to try the "LCD reduced" timing option (and remove 1920x1080 @ 60 Hz from standard resolutions). That will cause some TVs to treat it as a PC resolution. If that doesn't help, there's not much you can do other than to route the sound from the TV through some other method.
(05-12-2016 02:35 AM)ToastyX Wrote: [ -> ]
(05-12-2016 12:46 AM)laika Wrote: [ -> ]Toasty, before anything, amazing program. But I've been having a tough time transmitting audio through my HDMI to my hdtv (serving as monitor).

CRU does what is expected, it allows my crappy hdtv resolution to work with (real) 1920x1080.

But when I try using the hdmi.audio custom extension block, my resolution goes back to the crappy one.
The only way to fix this is to set it as 'No Extension Block', but this way I can't have working hdmi audio, because it's detected as a DVI.
The resolution is working. The problem is the TV is treating 1920x1080 differently with HDMI vs. DVI signals, and the only way to get audio is with HDMI support. The only idea I have is to try the "LCD reduced" timing option (and remove 1920x1080 @ 60 Hz from standard resolutions). That will cause some TVs to treat it as a PC resolution. If that doesn't help, there's not much you can do other than to route the sound from the TV through some other method.
Didn't work, the resolution resets every time I add a 'hdmi support' data block.
Is this a bug, or what?
(05-12-2016 08:22 PM)laika Wrote: [ -> ]Didn't work, the resolution resets every time I add a 'hdmi support' data block.
Is this a bug, or what?
HDMI ports can operate as HDMI or single-link DVI. HDMI is treated as single-link DVI if an HDMI support data block is not defined in the extension block. Your TV is handling 1920x1080 differently with HDMI vs. DVI signals, and there's no way to get audio with single-link DVI.
Hi! First of all thanks to ToastyX for continued support of this utility.

I finally decided to use it when trying to fix the clock deviations (audio/video) for my HTPC. Being fed up with Nvidia messy custom resolutions handling, I was advised about CRU. And here I am Smile

My system is Win 8.1 x64, I use a Nvidia GTX 660 (361.75 drivers, it being an HTPC I try to avoid updating needlessly) connected to a Pioneer Kuro plasma LX-6090 through HDMI (through which audio from GTX 660 is routed too).

Without CRU, the custom resolutions I generated appeared in the Nvidia Control Panel (NCP from here on) on top of all others, under the Custom entry, with other resolutions I used (1080p 50Hz already had perfect timing by default, for instance) appearing under the "Ultra HD, HD, SD" entry, just below.

In CRU I found my plasma as the single device connected, I proceeded to download all Detailed resolutions and Standard resolutions I found there.

I then created a 1920x1080@60Hz detailed resolution (main screen) and then went to Custom extension block.

In Custom extension block I added the other resolutions I needed under detailed resolutions (Extension Block screen) and I added HDMI support and Audio formats under the Data blocks entry (Extension Block screen). I did this by importing the files downloadable from the opening post, modifying only the DSD entry under bitstreaming formats supported (as my AVR doesn't support DSD bitstreaming if I'm not mistaken, anyway it's not relevant to my problem Smile).

OK, OK, OK, Restart64.exe. Custom resolutions looking good (some trial and error for some refresh rates but I ended up with what I wanted), audio working. Great! Resolutions created with CRU appeared in NCP under the PC entry. No more "Ultra HD, HD, SD" entry there.

Unfortunately I soon discovered that colors seemed off. So I went to check Output colour format and Output dynamic range in NCP. And they were as they always have been set up: RGB, Full output dynamic range. But colors were off. I tested them with a gray ramp and I had blacks crushed.
My plasma is set up with automatic colour format detection but moving from auto to the manual settings I discovered that there was a mismatch between what dynamic range the HDMI was "telling" the TV it was sending and the actual color information it was sending.

To cut things short, whereas before I had my whole "reproduction chain" setup for RGB full (and I calibrated my TV as such, being ISF trained and everything) I now have a situation where I have to set RGB Limited, while keeping my TV to auto (which gets the Limited range correctly at that point) but in madVR (a video renderer for video playback) I still need to have the setting "The display expects the following RGB output levels" to PC levels (0-255). If I set it up to TV Levels (16-235), colors become washed out.

Reproduction chain before CRU: NCP set at RGB Full, madVR set at PC Levels (0-255), tv set to Auto
Reproduction chain after CRU: NCP set at RGB limited, madVR set at PC Levels (0-255), tv set to Auto

In both cases desktop colors look right, black and white ramps show correctly only the 16-235 range (which is what the TV had been calibrated to).

Now... why the difference? Not being sure of what happens behind scenes I'm wary of unneeded or wrong color conversions happening.
(05-20-2016 11:44 AM)ashlar Wrote: [ -> ]Unfortunately I soon discovered that colors seemed off. So I went to check Output colour format and Output dynamic range in NCP. And they were as they always have been set up: RGB, Full output dynamic range. But colors were off. I tested them with a gray ramp and I had blacks crushed.
My plasma is set up with automatic colour format detection but moving from auto to the manual settings I discovered that there was a mismatch between what dynamic range the HDMI was "telling" the TV it was sending and the actual color information it was sending.

To cut things short, whereas before I had my whole "reproduction chain" setup for RGB full (and I calibrated my TV as such, being ISF trained and everything) I now have a situation where I have to set RGB Limited, while keeping my TV to auto (which gets the Limited range correctly at that point) but in madVR (a video renderer for video playback) I still need to have the setting "The display expects the following RGB output levels" to PC levels (0-255). If I set it up to TV Levels (16-235), colors become washed out.

Reproduction chain before CRU: NCP set at RGB Full, madVR set at PC Levels (0-255), tv set to Auto
Reproduction chain after CRU: NCP set at RGB limited, madVR set at PC Levels (0-255), tv set to Auto

In both cases desktop colors look right, black and white ramps show correctly only the 16-235 range (which is what the TV had been calibrated to).

Now... why the difference? Not being sure of what happens behind scenes I'm wary of unneeded or wrong color conversions happening.
I can only think of three factors that would cause a color difference:

1. HDMI vs. DVI signals: Since you included HDMI support in the extension block, this shouldn't be a factor.

2. RGB vs. YCbCr: You said you set the color format to full-range RGB, so this shouldn't be a factor. YCbCr is always limited-range.

3. Timing differences: If you're not using the official CEA standard timing parameters, the TV may treat it as a PC resolution and assume full-range RGB, but you're saying it's receiving limited-range RGB. If the video card is sending limited-range RGB when you set full-range RGB, then that's a driver bug. Try using this: http://blog.metaclassofnil.com/?p=83

Other than that, there shouldn't be any color differences.
Thanks for your reply.

1) You are correct, I do have the extension block with HDMI support. I wonder if any of the options there are relevant. I know I managed to get 12 bit output correctly (Plasma reports 36 bits input).

2) Yes.

3) I tried the program you linked. Didn't seem to do much. Nvidia now offers that setting through its control panel and it seems to be working.

The problem is that the opposite of what you mention seems to be happening. The TV "thinks" it's receiving limited range no matter what I do. If I force RGB full range (instead of leaving signal detection to "Auto" in the TV settings), everything goes back being correct. Before using CRU, I had everything set to full range in the PC (Nvidia Control Panel and madVR) and the TV correctly interpreted the signal as 0-255 automatically.

Unfortunately I cannot force it to 0-255 because it actually goes to my AVR, which receives many other signals (PS3, Sky receiver, WiiU, etc.) and the routes them all through a single HDMI cable to the TV. If I don't set it to Auto, all other signals are wrongly interpreted as RGB 0-255 (Sky outputs in YCbCr, for instance).
Anything springs to mind? There must be something that Nvidia did differently to the EDID with respect to what CRU is generating.
(05-22-2016 02:57 PM)ashlar Wrote: [ -> ]The problem is that the opposite of what you mention seems to be happening. The TV "thinks" it's receiving limited range no matter what I do. If I force RGB full range (instead of leaving signal detection to "Auto" in the TV settings), everything goes back being correct. Before using CRU, I had everything set to full range in the PC (Nvidia Control Panel and madVR) and the TV correctly interpreted the signal as 0-255 automatically.
I see what you mean. You're saying the video card is sending full-range RGB but not marking it as full-range, so the TV assumes it's receiving limited-range RGB. Try adding a video capability data block, and set "Selectable RGB range" at the bottom.
(05-23-2016 04:16 AM)ToastyX Wrote: [ -> ]I see what you mean. You're saying the video card is sending full-range RGB but not marking it as full-range, so the TV assumes it's receiving limited-range RGB. Try adding a video capability data block, and set "Selectable RGB range" at the bottom.
One further discovery and this extends to custom resolutions created through Nvidia Control Panel too.

In CRU I created one detailed resolution for the basic 1080p@60. I then created detailed resolutions in the extension block for 59.94, 50 and 23.976.

Yesterday I discovered that high resolution formats were not bitstreaming and after A LOT of trials and errors I found out that they were working only for the primary detailed resolution 1080p@60.
I exported my config, reset everything to nvidia defaults and tried with the standard refresh rates offered by Nvidia. At all refresh rates everything was working. I created a custom refresh rate for 23.976 and, once more, TrueHD and DTS-MA were not working.

I wonder what's the difference between the standard resolution/refresh offered by Nvidia and the custom ones we are creating (even more so considering that, for instance, Nvidia's 23.976 turns out to be 23.971).

I'll try the "video capability" you are suggesting for RGB range problems, thank you.
Edit: What about the three entries "TV resolutions", "PC resolutions" and "Native resolution" in the Video Capability screen? Do I leave them at default (not supported/not supported/use tv-pc information)?
Ok, the Video Capability thing fixes that problem.

On the other hand, I can confirm that as soon as a custom resolution is created, on an Nvidia GTX 660, that resolution loses audio capabilities (formats and samplerates). From being capable of bitstreaming DTS-MA, Dolby TrueHD, DD+, everything, up to 192KHz, the audio portion goes to being limited to DD and DTS, up to 48KHz, or you lose 192KHz capability and keep the formats... but it downgrades basically.

I use Win 8.1 x64. If I keep open the Control Panel/Sound/Properties (onboard audio of the GPU)/Supported Formats windows and switch to a custom resolution, that windows goes blank, with just a single written message stating that the device in use has been changed. This doesn't happen if one sticks to the basic resolution/refresh rates offered by Nvidia through the control panel (but those have horrible timings... 23.971 anyone?).

Drivers are 365.19. And yes, I've loaded all the correct extended blocks HDMI and bitstreaming settings (and, again, it does it even if you create a custom res through Nvidia Control Panel).
(05-23-2016 03:49 PM)ashlar Wrote: [ -> ]Ok, the Video Capability thing fixes that problem.
That's interesting. I didn't realize NVIDIA supported that feature.

(05-23-2016 03:49 PM)ashlar Wrote: [ -> ]Edit: What about the three entries "TV resolutions", "PC resolutions" and "Native resolution" in the Video Capability screen? Do I leave them at default (not supported/not supported/use tv-pc information)?
I don't think that matters. Just put what your TV does. Always underscanned means no overscan.

(05-23-2016 08:45 AM)ashlar Wrote: [ -> ]Yesterday I discovered that high resolution formats were not bitstreaming and after A LOT of trials and errors I found out that they were working only for the primary detailed resolution 1080p@60.
I exported my config, reset everything to nvidia defaults and tried with the standard refresh rates offered by Nvidia. At all refresh rates everything was working. I created a custom refresh rate for 23.976 and, once more, TrueHD and DTS-MA were not working.

I wonder what's the difference between the standard resolution/refresh offered by Nvidia and the custom ones we are creating (even more so considering that, for instance, Nvidia's 23.976 turns out to be 23.971).
What timing parameters did you use? Audio is transmitted during the blanking periods, and reducing the refresh rate reduces the amount of data that can be transmitted, so the blanking would need to be increased to account for this. The CEA standard timing parameters have the horizontal front porch set to 638 at 24 Hz and 528 at 25/50 Hz. Start with the "LCD standard" timing parameters, and switch to manual to make adjustments.
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