Gigabyte AORUS FO48U 48" 4K 120Hz OLED

RTings review is up...

in their color calibrated section they used:
RGB Controls 100-92-79
Gamma Setting 2.2

which is close to what I was running when I first got it.. but I noticed some weird artifacting if gamma is set to anything but off, and quite a brightness drop off by lowering blue that much. Of course they have brightness set at 27 so perhaps they were in a dark room..
 
That's gonna be a hard disagree from me. I've left it powered on just to let it go into sleep mode and I eventually got the protection warning message while in a game a few hours ago. You still have to power it off like an OLED TV for the compensation cycles to run.
Huh, I swear the couple times I forgot to turn it off it started flashing when I tried to wake it up
 
RTings review is up...

in their color calibrated section they used:
RGB Controls 100-92-79
Gamma Setting 2.2

which is close to what I was running when I first got it.. but I noticed some weird artifacting if gamma is set to anything but off, and quite a brightness drop off by lowering blue that much. Of course they have brightness set at 27 so perhaps they were in a dark room..

Thanks I thought it would be in early access for a bit longer:

https://www.rtings.com/monitor/reviews/gigabyte/aorus-fo48u-oled

In summary:

"The Gigabyte AORUS FO48U OLED is a 48 inch monitor with an OLED panel. Like all displays with OLED panels, it delivers deep, inky blacks with no blooming around bright objects, and it has wide viewing angles. It's very similar to the LG 48 C1 OLED but with connectivity options that are more in-line with a traditional monitor, with a DisplayPort connection and built-in USB hub, and even a keyboard-video-mouse (KVM) switch. It has a near-instantaneous response time, resulting in crystal-clear motion behind fast-moving objects, as well as low input lag and support for FreeSync and G-SYNC Compatible variable refresh rate. Unfortunately, it's not very bright, and the automatic static brightness limiter (ASBL) causes some issues with desktop use, as the screen dims automatically after a few minutes of relative inactivity. This can be an issue when typing or reading a webpage with a lot of text, as the screen doesn't change enough to trigger the timer. Like all OLEDs, there's also a risk of permanent burn-in, although there are things you can do to reduce the likelihood of this problem."

Compared To Other Monitors:

"The Gigabyte AORUS FO48U is an amazing gaming monitor that delivers exceptional picture quality and a responsive gaming experience. The OLED panel delivers inky blacks with perfect black uniformity, but there are some distracting issues with dimming, and there's a possibility of permanent burn-in. There aren't many OLED monitors available, but we've also tested two LG TVs as monitors, the LG 48 C1 OLED and the LG 48 CX OLED, and both of them are better choices overall than the Gigabyte."
 
Huh, I swear the couple times I forgot to turn it off it started flashing when I tried to wake it up
I've had something like what you describe happen on F04 firmware. If the display woke up quicky upon detecting a signal, it would blank out again before reappearing. This does not happen for me on F05 beta.
 
So based on Gsync Compatible not working over DisplayPort for them, seems like Rtings was using the F05 beta firmware.

Interesting that the vivid mode actually does seem to have similar brightness numbers to the LG C1 (and brighter at 2%), but the "real scene" brightness is significantly lower.
 
Unless you don't have an HDMI 2.1 port on your GPU.
Even then the only GPUs that I consider good enough for 4K with good frame rates is at least an RX 6800 or RTX 3080. So the DP advantage for previous gen cards is moot.
 
Even then the only GPUs that I consider good enough for 4K with good frame rates is at least an RX 6800 or RTX 3080. So the DP advantage for previous gen cards is moot.
Unless you want multiple displays or need to use that single HDMI port for something else.

And for older games you don’t necessarily need a 3080 or better.

Overall the issues do actually seem fixable. Question is whether or not gigabyte will bother.
 
My panel usage time is counting up correctly now instead of resetting to 5 hours everytime I turn it off or when it goes to sleep. It's at 57 hours now. Not sure what I did differently other than disconnecting my KB&M from the USB hub and unplugging it from the power strip briefly.
 
My panel usage time is counting up correctly now instead of resetting to 5 hours everytime I turn it off or when it goes to sleep. It's at 57 hours now. Not sure what I did differently other than disconnecting my KB&M from the USB hub and unplugging it from the power strip briefly.
Might be the F05 firmware. Mine seems to be counting correctly now too. I just need them to fix the EDID they fucked up, since DisplayPort is 99% of the reason I bought this thing in the first place.
 
A work around for the Gsync issue is to go into CRU and raise the lower limit of the VRR range to at least 40. That's what previous firmwares had it set to. Hopefully Gigabyte can fix it in the non-beta firmware (either by raising it back to 40 or changing whatever else is needed in the firmware to allow the range to go down to 24).
I still seem to have Gsync issues even with the CRU edit. I have similar issue to darkphyber . Screen goes black for a few second during scene changes when running 120hz/VRR and disabling gsync fixes the issue. Seems to only be a problem with full screen content, windowed content works OK.
 
There's an F05 non-beta now. Going to flash that and see if it fixes anything.

Edit: Seems to have fixed the issue. They did change the minimum in the EDID to 48Hz instead of 40Hz like with F02-F04, but it's still a wide enough range for LFC so it should be fine.
 
Last edited:
There's an F05 non-beta now. Going to flash that and see if it fixes anything.

Edit: Seems to have fixed the issue. They did change the minimum in the EDID to 48Hz instead of 40Hz like with F02-F04, but it's still a wide enough range for LFC so it should be fine.

Can confirm the Gsync issues i was having are fixed on the new firmware.
 
"Update include:
1. Optimize the brightness performance in HDR mode."

Did anyone actually notice a difference in brightness compared to F04?
 
"Update include:
1. Optimize the brightness performance in HDR mode."

Did anyone actually notice a difference in brightness compared to F04?
That's just for the HDR vivid picture mode. Definitely don't use it because real scene HDR brightness is even lower despite peak brightness going up to 850 nits according to rtings.
 
Does sRGB mode on the FO48U come out of black too quickly? Rtings review says that sRGB is too dark in dark scenes, but that's not what I'm seeing.
Using lagom.nl LCD black level test image, RGB 1,1,1 is easily distinct compared to true black when it should transition smoothly and blend in.
It looks similar to SDR emulation in Windows 10 when HDR is enabled because near blacks are elevated there too.
 
Does sRGB mode on the FO48U come out of black too quickly? Rtings review says that sRGB is too dark in dark scenes, but that's not what I'm seeing.
Using lagom.nl LCD black level test image, RGB 1,1,1 is easily distinct compared to true black when it should transition smoothly and blend in.
It looks similar to SDR emulation in Windows 10 when HDR is enabled because near blacks are elevated there too.
For me, the sRGB mode seems to have a lower peak SDR brightness than the other modes so you have crank up the contrast/brightness to compensate. I also noticed not just in sRGB mode, but in any other combination of color-space/gamma settings that doesn't crush blacks will quickly reveal the near black quantization issue notorious on all LG OLED panels.
 
Does sRGB mode on the FO48U come out of black too quickly? Rtings review says that sRGB is too dark in dark scenes, but that's not what I'm seeing.
Using lagom.nl LCD black level test image, RGB 1,1,1 is easily distinct compared to true black when it should transition smoothly and blend in.
It looks similar to SDR emulation in Windows 10 when HDR is enabled because near blacks are elevated there too.
Only partially relevant but the FV43U does this too. It seems to overcompensate for the high contrast ratio of the panel and there's more of a difference between the black background and the first square on lagom than square 1 vs. square 2. Full native panel gamut looks more like I would expect from this test.
 
Does sRGB mode on the FO48U come out of black too quickly? Rtings review says that sRGB is too dark in dark scenes, but that's not what I'm seeing.
Using lagom.nl LCD black level test image, RGB 1,1,1 is easily distinct compared to true black when it should transition smoothly and blend in.
It looks similar to SDR emulation in Windows 10 when HDR is enabled because near blacks are elevated there too.
I'll have to compare to my TV, but to some degree that's just going to be reality when 0,0,0 is literally off and 1,1,1 isn't when you only have 256 steps. I imagine 1,1,1 in 10-bit would be much darker.
 
For me, the sRGB mode seems to have a lower peak SDR brightness than the other modes so you have crank up the contrast/brightness to compensate. I also noticed not just in sRGB mode, but in any other combination of color-space/gamma settings that doesn't crush blacks will quickly reveal the near black quantization issue notorious on all LG OLED panels.
I noticed that too, Gigabyte's tuning seems to negotiate around the panels weak points well, if they could just fix the ABL hiccups...
 
Still seeing some bugs with the new f05 firmware. When i power on the monitor via the remote i occasionally get a power protection warning. Panel usage time still seems to be way out but APCS seems to be running correctly based on the counter.
 
Last edited:
Still seeing some bugs with the new f05 firmware. When i power on the monitor via the remote i occasionally get a power protection warning. Panel usage time still seems to be way but APCS seems to be running correctly based on the counter.
Same. That protection warning should just not even be there to begin with. And why can't the protection just run in sleep mode? It's a monitor, not a TV.

Sometimes I swear the panel usage time bugs out before counting up normally again.
 
Sometimes I swear the panel usage time bugs out before counting up normally again.

It does work at times but its almost like the panel protection warning causes it to go back xx hours. I haven't worked out what xx is but wonder if its the same amount of hours that triggers the panel protection warning.
 
One more problem I forgot to mention. Does anyone else have problems with slow(ish) alt tabbing out of full screen games? Even with the same res/refresh/mode in game and desktop it takes 4-5 seconds to tab out of game and to the desktop. The display just goes black like it is going to a new res/refresh and then comes back but going back to the game doesn't have an issue.
 
Confirmed, new F05 firmware fixed GSync issues from F05 Beta. ASBL still sucks with no option to turn it off.
 
Good lord why is it so difficult to update the firmware? It took nearly 15 tries from 3 different PCs before I was able to get it to flash to F05 without the "Download fail" error message.
One more problem I forgot to mention. Does anyone else have problems with slow(ish) alt tabbing out of full screen games? Even with the same res/refresh/mode in game and desktop it takes 4-5 seconds to tab out of game and to the desktop. The display just goes black like it is going to a new res/refresh and then comes back but going back to the game doesn't have an issue.
Probably GSYNC being toggled when entering full-screen.
 
Probably GSYNC being toggled when entering full-screen.

Looks like its another "feature" for the display. Using HDMI has no issues with fast switching between full screen games and desktop. Displayport seems to give 3-5 seconds of delay which doesn't sound like much but if you constantly tab in and out of games it becomes a major frustration. The problem with HDMI on this display is it does not support 4k RGB @ 120hz. Might need to try and contact gigabyte about this displayport delay issue.
 
Last edited:
Looks like its another "feature" for the display. Using HDMI has no issues with fast switching between full screen games and desktop. Displayport seems to give 3-5 seconds of delay which doesn't sound like much but if you constantly tab in and out of games it becomes a major frustration. The problem with HDMI on this display is it does not support 4k RGB @ 120hz, might need to try and contact gigabyte about this issue.
Supports 4k RGB @ 120 Hz over HDMI for me. That said, I haven't noticed that delay over DisplayPort unless the resolution is actually changing when going full screen. Though now that I think of it, pretty much all of the games I play support borderless, so that might be the difference.
 
Last edited:
Supports 4k RGB @ 120 Hz over HDMI for me
You are correct !! I missed that and wrongly assumed due to the HDMI bandwidth limitation it wasn't possible but with DSC(i assume again :D) its not a problem.

That said, I haven't noticed that delay over DisplayPort unless the resolution is actually changing when going full screen. Though now that I think of it, pretty much all of the games I play support borderless, so that might be the difference.

The problem is only present when using full screen mode. I had issues in the past with borderless in some games but maybe its time to give it another go if it means better multi-tasking. Thanks for the helpful reply.
 
Is this monitor able to run g-sync compatible mode and HDR at the same time?

Also, what's the range of g-sync compatible? 48-120 Hz or 40-120 Hz?
 
Is this monitor able to run g-sync compatible mode and HDR at the same time?

Also, what's the range of g-sync compatible? 48-120 Hz or 40-120 Hz?
Yes, it can do HDR and gsync compatible at the same time

As of F05, the range is 48 - 120 over DisplayPort and 40 - 120 over HDMI. in F02-F04, it was 40 - 120 for all ports. I find there to be less flicker with the 48 - 120 anyway, and at that point the LFC transition isn't really noticeable.
 
Yes, it can do HDR and gsync compatible at the same time

As of F05, the range is 48 - 120 over DisplayPort and 40 - 120 over HDMI. in F02-F04, it was 40 - 120 for all ports. I find there to be less flicker with the 48 - 120 anyway, and at that point the LFC transition isn't really noticeable.
I see.

I have an RTX 3080 Ti, so I can choose DP 1.4 or HDMI 2.1. Anyway my first throught is always to use DP over HDMI on PC. Moreover I also have a PS5 which I'd obviously plug it via HDMI.

The truth is I'm tired of searching PC monitors which offer a good HDR experience (without being a TV). Is this monitor a good solution? Does it have any remarkable weak points? (appart from the burn-in risk)

Thanks!
 
Back
Top