- #Samsung odyssey g5 sound not working update
- #Samsung odyssey g5 sound not working pro
- #Samsung odyssey g5 sound not working plus
Laptop: Apple MacBook Pro 14" 2023: M2 Pro, 16 GB RAM, NVMe 512 GB, Asus VivoBook 15 OLED : Intel® Core™ i3-1125G4, Intel UHD, 8 GB RAM, Micron NVMe 512 GB, Windows 11 Home (21H2), Illegear Z5 SKYLAKE: Intel Core i7-6700HQ, Nvidia Geforce GTX 970M, 16 GB RAM, ADATA SU800 M.2 SATA 512GB, Windows 11 Pro (22H2).
#Samsung odyssey g5 sound not working plus
PC: AMD Ryzen 9 5900X, Gigabyte GeForce RTX 4090 OC 24G, X570 AORUS Elite WIFI Motherboard, HyperX FURY 32GB DDR4-3200 RGB RAM, Creative Sound Blaster AE-9 Sound Card, Samsung 970 Evo Plus M.2 SATA 500GB, ADATA XPG SX8200 Pro M.2 SATA 2TB, Asus HyperX Fury RGB SSD 960GB, Seagate Barracuda 7200RPM 3.5 HDD 2TB, Cooler Master MASTERLIQUID ML240R ARGB, Cooler Master MASTERFAN MF120R ARGB, Cooler Master ELV8 Graphics Card Holder ARGB, Asus ROG Strix 1000G PGU, Lian Li LANCOOL II MESH RGB Case, Windows 11 Pro (22H2). I'm thinking at this point that my only option is to wait for a firmware fix from Samsung, but if someone has a suggestion more optimistic than that, please let me know!
#Samsung odyssey g5 sound not working update
Running the tool here: to update my GPU firmware for DP 1.4 Plugging the DP cable into both DP outputs on my GPU Plugging the DP cable into both DP inputs on the monitor
Toggling eco-off and auto-off settings in monitor's OSD - same issue in both whether the settings are on and off Setting monitor to DP v 1.2 and 1.4 - same issue in both cases Swapping DP cables - I've used both the cable that came with the monitor, and another cable with sufficient bandwidth I got off Amazon - same result in both cases.
My third monitor, an old HP 2711x, is connected by HDMI, and it's this monitor that all my windows from the G7 end up on after sleep. I don't think that's the issue, though, because I have another monitor (Dell S2716DG) also connected by Displayport that is not plagued by this issue. One culprit that's been pointed to is an apparent "feature" of DP that causes monitors to behave like this when sleeping. Doing some research online, I've found many people with similar issues, but no solutions yet. Aside from making the wakeup process slow (which I could live with), it causes all of my windows to be moved to another monitor - super annoying. When the monitor goes to sleep after the time set in Windows settings expires, it goes through a disconnect/reconnect process when it wakes up, as if I had unplugged/replugged the Displayport cable. There's just one issue that's been perpetually bugging me. I've recently gotten a G7 (27 inch), and it's a really nice monitor. That said, it is true that a global level, it helps alleviate power consumption, which is important for areas who isn't powered by clean energy or have limited power availibility) in an office with thousands of the same monitors. So, all I can say is ensure you have the latest firmware, and make sure all eco-mode garbage features are turned off (none of them make sense in a home setting in my opinion. It was made for laptops being docked with multiple screens, then undocked, and later docked back again restoring all window placements. This wasn't done for DP Deep Sleep, it's just an accidental coincidence it helps. Windows 11 corrects this problem by memorizing window placement when display configuration changes and comes back. The issue of this feature is that, as you noted, when you have a multiple monitor setup, your GPU thinks that the cable was disconnected and so tells Windows that the display has been lost, and so Windows moves all windows to the other screen. Some monitor manufacturers offer the option to turn it off (meaning it won't use that deep sleep feature), other, sadly, don't.Īs you mentioned/read, DP Deep Sleep means that the monitor goes in deeper sleep power state than the normal standby (save more power), which result in the monitor completely disconnecting from the system. The issue is that the monitor has implemented DisplayPort Deep Sleep feature.
0 kommentar(er)
