Two of the same monitors showing different resolutions

I have a pair of LG monitors (https://www.lg.com/us/monitors/lg-27gs75q-b-gaming-monitor) connected to my M2 Max Mac Studio through a KVM switch (https://sabrent.com/collections/accessories/products/sb-tb4k) since I also use my two monitors, my keyboard and my mouse with my work laptop. The monitors are connected to the KVM with a pair of USB-C to DisplayPort cables


These are 1440p monitors (2560x1440 resolution at 180Hz). My work laptop is a Microsoft Surface Laptop 4 (I think, might be a 5) and has no issues with my monitors - both display at 2560x1440p on Windows 11, so I know the cables and KVM are capable of handling the load. I am not sure of what the display Hz is on Windows 11, but it's a work laptop so it really is moot since I'm a system administrator and budding cybersecurity engineer and not do anything with video.


On my Mac Studio it's a different story. Both monitors are the exact same part number - LG27GS75Q. However in Settings on macOS one shows as 2560x1440p at 180Hz natively and the other shows as 1920x1080p at 120Hz. I can force it to 2560x1440p, but cannot force it to 180Hz. And sometimes when I use the KVM the monitors will "flip" and the one that was previously 2560x1440/180 will be 1920x1080/120 and the one that was previously 1920x1080/120 will now be 2560x1440/180.


I'm only experiencing this issue with the Mac Studio. So this issue seems to be related to macOS.


Does anyone have any idea what could be causing this?



[Edited by Moderator]

Mac Studio, macOS 15.5

Posted on Aug 2, 2025 11:44 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 3, 2025 4:36 AM

Connecting one LG monitor to the Mac Studio and one to the KVM switch did nothing - one monitor stayed 2560x1440/180 and the other only 1920x1080/120 that I could force to 2560x1440/180. However plugging both monitors into the Mac Studio allowed both to show up as 2560x1440/180 natively.


So it appears to be some conflict between the KVM and macOS since the KVM works fine with Windows (as both monitors show up natively as 2560x1440) - so both ports on the KVM I'm using for monitors have no issue handling the resolution (as the KVM is rated for dual 4K@60Hz or one 5/6/8K@60Hz and one 4K@120/144Hz) and the cables can handle the load as well. The KVM is marked as being macOS compatible and it worked fine with my Apple Studio Display (5K@60Hz) and one LG display (2560x1440@180) in my initial configuration.


I'll have to contact Sabrent and see if they have any ideas. Or just get a second Studio Display and find a KVM that can handle dual 5K@60.

9 replies
Question marked as Top-ranking reply

Aug 3, 2025 4:36 AM in response to den.thed

Connecting one LG monitor to the Mac Studio and one to the KVM switch did nothing - one monitor stayed 2560x1440/180 and the other only 1920x1080/120 that I could force to 2560x1440/180. However plugging both monitors into the Mac Studio allowed both to show up as 2560x1440/180 natively.


So it appears to be some conflict between the KVM and macOS since the KVM works fine with Windows (as both monitors show up natively as 2560x1440) - so both ports on the KVM I'm using for monitors have no issue handling the resolution (as the KVM is rated for dual 4K@60Hz or one 5/6/8K@60Hz and one 4K@120/144Hz) and the cables can handle the load as well. The KVM is marked as being macOS compatible and it worked fine with my Apple Studio Display (5K@60Hz) and one LG display (2560x1440@180) in my initial configuration.


I'll have to contact Sabrent and see if they have any ideas. Or just get a second Studio Display and find a KVM that can handle dual 5K@60.

Aug 3, 2025 7:38 AM in response to Boss_Chonk

The Mac does not rely on Windows-like side-loaded "Drivers" which are actually packages of resolutions and settings for a specific display. Instead, it goes straight to the immutable source -- it asks the display itself.


To get a Mac display to become active, you need the Mac to query the display, and the display to answer with its name and capabilities. Otherwise, the display will not be shown as present, and no data will be sent to the display. "No signal detected" is generated by the DISPLAY, not by the Mac.

This query is only sent at certain times:

• at startup

• at wake from sleep — so momentarily sleeping and waking your Mac may work

• at insertion of the Mac-end of the display-cable, provided everything on that cable is ready-to-go

• hold the Option key while you click on the (Detect Display) button that will appear in Displays preferences (from another display)


The Apple standard for its built-in hardware-accelerated displays, makes them suitable for full-motion video for production/display of cinema-quality video with NO dropped frames, and NO dropouts or partial-blank scan lines due to memory under-runs or other issues. This requires a hardware rasterizer/display-generator for each fully-accelerated display, supported by Huge memory bandwidth to refresh each display 60 or more times a second. 


NB>> If any transmission errors are detected, such as by signal deterioration from using cables longer than ONE meter total length without signal re-driver circuits, the display resolution may be reduced or the display may drop out entirely.


--------

The Windoze standard for its directly connected displays is,

"Set it manually to whatever you like. If you think it is OK, then it is!"


Aug 3, 2025 5:19 AM in response to Boss_Chonk

Boss_Chonk wrote:

Connecting one LG monitor to the Mac Studio and one to the KVM switch did nothing - one monitor stayed 2560x1440/180 and the other only 1920x1080/120 that I could force to 2560x1440/180. However plugging both monitors into the Mac Studio allowed both to show up as 2560x1440/180 natively.
So it appears to be some conflict between the KVM and macOS since the KVM works fine with Windows (as both monitors show up natively as 2560x1440) - so both ports on the KVM I'm using for monitors have no issue handling the resolution (as the KVM is rated for dual 4K@60Hz or one 5/6/8K@60Hz and one 4K@120/144Hz) and the cables can handle the load as well. The KVM is marked as being macOS compatible and it worked fine with my Apple Studio Display (5K@60Hz) and one LG display (2560x1440@180) in my initial configuration.

I'll have to contact Sabrent and see if they have any ideas. Or just get a second Studio Display and find a KVM that can handle dual 5K@60.


Good luck.

Aug 3, 2025 9:12 AM in response to Boss_Chonk

Let me test my understanding:


You are using TWO Thunderbolt cables from the BACK ports on the Mac Studio to the Sabrent box. These cable have the genuine Thunderbolt symbol on them and are 0.5 meters or shorter. (In this case ONLY, the cables included with high performance KVM/Switch of length 0.7 meters are probably just fine.)


from the Sabrent box, you are using Brand-X USB-C to DisplayPort adapter/cables to the displays. These adapter cables are no longer than ONE meter each.


Your displays support DisplayPort 1.4, so they could transmit directly on a ThunderBolt cable using DisplayPort-HBR3 rules, which at your "2K" resolution has an upper limit of 200 Hz refresh using 10bits/color (HDR=ON) without compression, or at 8 bits/color, 240 hz refresh. that does not appear to be any sort of bottleneck.


Those adapters force the DisplayPort transmission speeds back to DisplayPort-HBR2 speeds that can be supported on a USB cable.


at 10 bits/color, that limits you to around 144 Hz refresh rate (with special timing). 200Hz or up to 240 are only available with Display Stream Compression, and its not completely clear that is getting turned on at the Mac, which is sending its data out on a a Much wider ThunderBolt port, so compression is not needed at the source.


at 8 bits/color (HDR=OFF), that limits you to 165 Hz refresh rate (with special timing). Higher, up to 240 are only available with Display Stream Compression, and again its not completely clear that is getting turned on at the Mac, which is sending its data out on a a Much wider ThunderBolt port, so compression is not needed at the source.


What to try next:


if you do not edit magazine cover art daily, set HDR=OFF on both displays, and re-acquire each display (such as by Sleep/Wake or Restarting your Mac.

Aug 2, 2025 3:38 PM in response to Boss_Chonk

MacOS does not work like Windoz when it comes to detecting and supplying video out to displays. It wants to detect each display independently and then send video out to each display thru a separate connection.


What I would try on the Mac Studio side of the setup. Is to run one display thru the switch and connect the second display directly to the Mac Studio using a short high speed USB-C to DisplayPort cable.

Aug 3, 2025 8:04 AM in response to Grant Bennet-Alder

I’ve reached out to Sabrent regarding the KVM, but I’ve done a little more troubleshooting since then.


With both monitors connected to the KVM and using the work laptop, both display at proper native resolution and refresh.


With both monitors connected to the KVM and using the Mac Studio, only one monitor displays at native resolution and refresh. The other displays at a downgraded resolution and refresh. However both are displaying output at the same time, I can move the mouse and windows between monitors and can force the downgraded monitor to native resolution (but can’t force it to native refresh).


With both monitors connected directly to the Mac Studio, both function fine at native resolution and refresh at the same time. Sadly this is not a sustainable option due to needing to share my setup between my work laptop and personal Mac Studio.


Testing one monitor at a time I cycled each

monitor through each of the three upstream Thunderbolt ports - and with only one monitor connected it displays at native resolution and fresh in all three Thunderbolt ports. Both monitors and cables display properly in all three ports as long as only one is connected.


So the problem only exists when both monitors are connected to the KVM and I’m using the Mac Studio. I also tried different configurations of Thunderbolt ports (1/2, 1/3 and 2/3 a total of six times with each monitor swapped position as well).


I’ve ruled out everything aside it being a problem strictly with the KVM or it being a conflict between the KVM and macOS (although Sabrent says this KVM is compatible with macOS). My KVM is a 4782x serial number, so it has the most current firmware Sabrent offers.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Two of the same monitors showing different resolutions

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.