(04-22-2020 09:10 PM)ToastyX Wrote: [ -> ]4k 120 Hz 4:2:0 is still under 600 Mcsc. I don't have a way around the 600 Mcsc limit.
Wait, so is the issue that CRU can not specially create a resolution with only 4:2:0 as the chroma subsampling value is independent of a given resolution?
In other words, in order to create any sort of custom resolution through CRU, you must have the bandwidth to run a given resolution at 8bit 4:4:4 even if you aren't going to be using 8bit 4:4:4?
(04-22-2020 09:19 PM)Nintendo Maniac 64 Wrote: [ -> ]Wait, so is the issue that CRU can not specially create a resolution with only 4:2:0 as the chroma subsampling value is independent of a given resolution?
In other words, in order to create any sort of custom resolution through CRU, you must have the bandwidth to run a given resolution at 8bit 4:4:4 even if you aren't going to be using 8bit 4:4:4?
Detailed resolutions are going to be 4:4:4. In the extension block, you can add a TV resolutions data block and check "4:2:0 resolutions" to add 4:2:0 resolutions, but you're limited to certain resolutions.
(04-22-2020 09:37 PM)ToastyX Wrote: [ -> ]In the extension block, you can add a TV resolutions data block
How does the bandwidth of these "TV resolutions" compare to creating the same detailed resolutions with "LCD Reduced" and "LCD Standard"?
The concern here is that 4k 100Hz 4:2:0 at "LCD Standard" only has enough bandwidth to use 8bit, but 4k 100Hz 4:2:0 at "LCD Reduced" has enough bandwidth for 10bit.
(04-22-2020 09:11 PM)ToastyX Wrote: [ -> ]Then try changing the detailed resolution to "LCD reduced" timing.
Again, nothing changed, apart from it being [+/-]. same issue persists.
(04-22-2020 09:50 PM)Nintendo Maniac 64 Wrote: [ -> ]How does the bandwidth of these "TV resolutions" compare to creating the same detailed resolutions with "LCD Reduced" and "LCD Standard"?
The concern here is that 4k 100Hz 4:2:0 at "LCD Standard" only has enough bandwidth to use 8bit, but 4k 100Hz 4:2:0 at "LCD Reduced" has enough bandwidth for 10bit.
"4:2:0 resolutions" use half the bandwidth. There's no way to add custom 4:2:0 resolutions.
(04-22-2020 10:02 PM)azthek Wrote: [ -> ]Again, nothing changed, apart from it being [+/-]. same issue persists.
Then I don't see a way around this except to get an HDMI-VGA adapter. The TV probably treats VGA differently.
(04-22-2020 11:25 PM)ToastyX Wrote: [ -> ]"4:2:0 resolutions" use half the bandwidth. There's no way to add custom 4:2:0 resolutions.
That wasn't quite what I meant...
If one creates a custom 4:4:4 8bit resolution using the "TV resolutions" function, would the resulting bandwidth be equivalent to a detailed resolution with "LCD Standard" or a detailed resolution with "LCD Reduced"?
(04-23-2020 12:40 AM)Nintendo Maniac 64 Wrote: [ -> ]If one creates a custom 4:4:4 8bit resolution using the "TV resolutions" function, would the resulting bandwidth be equivalent to a detailed resolution with "LCD Standard" or a detailed resolution with "LCD Reduced"?
It would be like "LCD standard" timing.
New question - does the freesync range setting only work for actual proper AMD freesync?
Or can it work for "adaptive sync" on Intel as well as Nvidia's "g-sync compatible"?
(04-23-2020 12:17 PM)ToastyX Wrote: [ -> ]It would be like "LCD standard" timing.
So in other words, there's no way to achieve "LCD reduced" resolutions specifically at 4:2:0 over HDMI?
(04-23-2020 08:17 PM)Nintendo Maniac 64 Wrote: [ -> ]New question - does the freesync range setting only work for actual proper AMD freesync?
Or can it work for "adaptive sync" on Intel as well as Nvidia's "g-sync compatible"?
Range also works with G-SYNC compatible.
(04-23-2020 08:17 PM)Nintendo Maniac 64 Wrote: [ -> ]So in other words, there's no way to achieve "LCD reduced" resolutions specifically at 4:2:0 over HDMI?
Right.