Pg27uq

[Neon_Lights]

MarshallR wrote:
Just checked: PG27 production starts now in May, so mid/late May/early June for first markets depending on how it's being shipped.

Not sure X series yet. It's often mostly waiting for mass-production of panel availability and/or mass production to meet a certain quality standard.

For the record: Monitors don't wait for graphics cards. They just launch on their own schedule.*

My original post:

https://www.inet.se/produkt/2210502/acer-27-predator-x27-4k-144hz-hdr-g-sync-quantum-dot

On this retailer site, the Acer Predator X27 is listed as to be shipped April 5th. Because ASUS usually release their version a little earlier than Acer/the other manufacturers, it is likely that the PG27UQ will be released (assuming that shipping date is correct) during March, this would also still stick to the Q1 2018 release window.


For reference, see the posts in this thread:

http://www.overclock.net/t/1620061/vc-asus-announces-swift-pg27uq-4k-ips-144hz-g-sync-hdr-monitor/10...

http://www.overclock.net/t/1620061/vc-asus-announces-swift-pg27uq-4k-ips-144hz-g-sync-hdr-monitor/11...

[deadchip12]

briansu wrote:
Blooming on mine....

Pic 2 is definitely overexposed. Pic 1 though...is this exactly what you see in real life? That blooming looks pretty bad.

[briansu]

deadchip12 wrote:
Pic 2 is definitely overexposed. Pic 1 though...is this exactly what you see in real life? That blooming looks pretty bad.

Yes when the app, in this case PowerDVD switches the display to HDR mode, this happens.

[greekwow]

kevinmaster5000 wrote:
So I just got my PG27UQ today. I am using a dual monitor set up with a 1080p TN panel I have had for the last 6 years. While this monitor absolutely blows it away, the TN panels (VG278H) seems to have whiter whites. I am genuinely concerned about it. It's tiring for my eyes to see such a drastic difference. The camera captures the difference pretty accurately.

Any ideas what to do? (PG27UQ left vs VG278H right)

Try lower vaules on Red and Green, ( i set at 76 and 86 but i am not sure, i am not home now) let the blue 100 on OSD

[KOT0005]

kevinmaster5000 wrote:
So I just got my PG27UQ today. I am using a dual monitor set up with a 1080p TN panel I have had for the last 6 years. While this monitor absolutely blows it away, the TN panels (VG278H) seems to have whiter whites. I am genuinely concerned about it. It's tiring for my eyes to see such a drastic difference. The camera captures the difference pretty accurately.

Any ideas what to do? (PG27UQ left vs VG278H right)

u need to change it to user mode and tinker with other settings like racing sRGB..a photo of OSD with information open would be a lot helpful than just a photo. Change some of those and see how u go.



I still dont understand all these blooming question.. what else do you expect? This isnt oled..its illuminating pixels using the 384LED's....I wonder if this site has ignore option..

[deadchip12]

KOT0005 wrote:
u need to change it to user mode and tinker with other settings like racing sRGB..a photo of OSD with information open would be a lot helpful than just a photo. Change some of those and see how u go.



I still dont understand all these blooming question.. what else do you expect? This isnt oled..its illuminating pixels using the 384LED's....I wonder if this site has ignore option..

But when 384 zones IPS is worse that edge lit 60 zones VA then it comes the question of value per dollar. Should I pay $2500 for 27 inch Gsync 144 Hz monitor with inferior image quality or $1500 for 55 inch TV 60Hz with better image quality?

[kathampy]

kevinmaster5000 wrote:
To PG27UQ owners, the monitor has 6 GameVisual modes, for stuff like FPS,RTS,Scenary, sRGB, etc. What mode would you use universally? I really dont like switching back and forth through modes. Do you guys switch through modes? If not, what mode would you recommend for permanant usage. There's no standard mode.

Racing mode is the same as Standard. "Standard" mode means the monitor uses its full colour gamut and ideally does not transform colour values. This mode must be calibrated with a colorimeter and requires a colour aware workflow.

In SDR mode you can either:
1) Use Racing mode with custom RGB values, use DisplayCAL to create a custom ICC profile, and use DisplayCAL Profile Loader to preserve the calibration (gamma curve). This gives you accurate wide gamut colour in colour aware applications like Firefox and Photoshop. However, virtually every other application including the desktop will be oversaturated since they render in sRGB and the monitor will map it to a wider gamut. Some games like Source engine games have a -nogammaramp option which lets DisplalyCAL profile loader preserve the calibrated gamma curve, resulting in better shadow detail, but the colours will still be oversaturated since the engine is not colour aware.

2) Use sRGB mode and choose the default sRGB ICC profile in Windows. This makes use of the monitor's accurate factory calibration. Everything will be accurate but limited to the sRGB colour space. The monitor will also restrict the brightness to ~100 nits. I suggest getting used to this brightness in SDR because it will look the same as HDR and only highlights will be above 100 nits.

In HDR mode:
HDR10 is an absolute standard - there is only one correct gamma (the PQ curve), one correct colour space (BT.2020), and one correct brightness (diffuse white is 100 nits). The desktop and non-HDR aware applications will continue to use the 2.2 gamma curve and sRGB colour space resulting in an incorrect image.

Note that 8-bit / 10-bit and RGB / YCbCr have nothing to do with the above. When the signal is YCbCr, the display probably uses the BT.1886 gamma curve commonly used with Rec.709 video, which is slightly different from the sRGB 2.2 gamma curve commonly used with an RGB signal. This is the reason for the black crush in 144 Hz YCbCr422 mode. The monitor is actually behaving accurately, but the desktop and applications are incorrectly using the 2.2 gamma curve. Since this system wide problem will never be fixed in the foreseeable future, I presume ASUS decided to use the 2.2 gamma curve for YCbCr in the updated firmware so that desktop applications look correct.

[kevinmaster5000]

kathampy wrote:
Racing mode is the same as Standard. "Standard" mode means the monitor uses its full colour gamut and ideally does not transform colour values. This mode must be calibrated with a colorimeter and requires a colour aware workflow.

In SDR mode you can either:
1) Use Racing mode with custom RGB values, use DisplayCAL to create a custom ICC profile, and use DisplayCAL Profile Loader to preserve the calibration (gamma curve). This gives you accurate wide gamut colour in colour aware applications like Firefox and Photoshop. However, virtually every other application including the desktop will be oversaturated since they render in sRGB and the monitor will map it to a wider gamut. Some games like Source engine games have a -nogammaramp option which lets DisplalyCAL profile loader preserve the calibrated gamma curve, resulting in better shadow detail, but the colours will still be oversaturated since the engine is not colour aware.

2) Use sRGB mode and choose the default sRGB ICC profile in Windows. This makes use of the monitor's accurate factory calibration. Everything will be accurate but limited to the sRGB colour space. The monitor will also restrict the brightness to ~100 nits. I suggest getting used to this brightness in SDR because it will look the same as HDR and only highlights will be above 100 nits.

In HDR mode:
HDR10 is an absolute standard - there is only one correct gamma (the PQ curve), one correct colour space (BT.2020), and one correct brightness (diffuse white is 100 nits). The desktop and non-HDR aware applications will continue to use the 2.2 gamma curve and sRGB colour space resulting in an incorrect image.

Note that 8-bit / 10-bit and RGB / YCbCr have nothing to do with the above. When the signal is YCbCr, the display probably uses the BT.1886 gamma curve commonly used with Rec.709 video, which is slightly different from the sRGB 2.2 gamma curve commonly used with an RGB signal. This is the reason for the black crush in 144 Hz YCbCr422 mode. The monitor is actually behaving accurately, but the desktop and applications are incorrectly using the 2.2 gamma curve. Since this system wide problem will never be fixed in the foreseeable future, I presume ASUS decided to use the 2.2 gamma curve for YCbCr in the updated firmware so that desktop applications look correct.

Thank you for such an informative post, I learned alot of it. One question I have is regarding your first point. If the monitor is already calibrated out of the box, wouldn't there be no need to calibrate the monitor? Particularly if racing mode is equivalent to standard mode.

[kathampy]

kevinmaster5000 wrote:
Thank you for such an informative post, I learned alot of it. One question I have is regarding your first point. If the monitor is already calibrated out of the box, wouldn't there be no need to calibrate the monitor? Particularly if racing mode is equivalent to standard mode.

Standard / Racing mode is an undefined colour space - it's whatever the panel is physically capable of. The factory calibration for this mode will just linearly expand the input to the panel's native colour space. Since it does not have a label like DCI-P3 or AdobeRGB, you cannot use it out of the box with a default ICC profile - it must be profiled with a colorimeter.

The sRGB mode will exactly map the input to sRGB on the panel, so you can use the default sRGB ICC profile. If a monitor has an AdobeRGB mode, you can use it with the default AdobeRGB profile, but non-colour aware applications will still be incorrect because they only output sRGB.

[kevinmaster5000]

kathampy wrote:
Standard / Racing mode is an undefined colour space - it's whatever the panel is physically capable of. The factory calibration for this mode will just linearly expand the input to the panel's native colour space. Since it does not have a label like DCI-P3 or AdobeRGB, you cannot use it out of the box with a default ICC profile - it must be profiled with a colorimeter.

The sRGB mode will exactly map the input to sRGB on the panel, so you can use the default sRGB ICC profile. If a monitor has an AdobeRGB mode, you can use it with the default AdobeRGB profile, but non-colour aware applications will still be incorrect because they only output sRGB.

Thank you again for a great reply. This becomes a complication for someone like me who does not own a colorimeter. I had originally thought factory calibration was good enough, and provided a close to optimal performance. Then what mode or setting adjustments would you recommend for someone like me (that plays most type of games with or without HDR, likes beautiful graphics, and loves netflix lol) and does not have a colorimeter. I was hoping I could have set a mode I can just leave and forget. Any recommendation?

[briansu]

kevinmaster5000 wrote:
To PG27UQ owners, the monitor has 6 GameVisual modes, for stuff like FPS,RTS,Scenary, sRGB, etc. What mode would you use universally? I really dont like switching back and forth through modes. Do you guys switch through modes? If not, what mode would you recommend for permanant usage. There's no standard mode.

I use Racing mode to play CSGO just because it's been calibrated with that mode. Mine's been calibrated using the Spyder 5 ELITE while it was set to Racing mode. Most games run in HDR anyway so those modes are irrelevant.