mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #300] Samsung G9 not working at all #237
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#237
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @StErMi on GitHub (Oct 3, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/300
Originally assigned to: @waydabber on GitHub.
Checklist
Describe the issue
I tried to make research but I really don't know if the Samsung G9 supports DDC.
I load up the application and try to change the brightness of it but it does not seem to work at all.
When I click on the app all the areas are greyed out, I don't know if it means that the monitor is not supported
Expected behavior
When I change the mbp brightness the external monitor should sync according to the same value.
Screenshots
None
Additional context
None
Environment Information (please complete the following information):
@haakon-nergaard commented on GitHub (Nov 5, 2020):
If it helps, I've just tested the Samsung G9 with ddcctl and that didn't work either.
@douginator2000 commented on GitHub (Jan 16, 2021):
Same issue for me on the Samsung CRG9. The tool launches into the menu bar but the sliders are grayed out. Brightness up/down buttons show on-screen indication and it does adjust the slider for MonitorControl, but it does not actually change the brightness.
@jrfernandes commented on GitHub (Jan 27, 2021):
I have a CRG9 and it can control the brightness, but the volume doesn't work. The sliders are functional, it just doesn't change the volume.
@douginator2000 commented on GitHub (Jan 28, 2021):
Did you have to do anything in particular to make it work @jrfernandes ?
I've found that if I switch freesync modes or turn the monitor off/on, the brightness buttons do work on my keyboard.
@waydabber commented on GitHub (Aug 21, 2021):
Hi all, this seems to be a monitor issue and probably there is nothing much to do on MonitorControl's side especially if a different tool (namely ddcctl) can't control the display either. The new 3.0.0 version has a great software fallback option (better than nothing) if you can't make this work.
I'll close this issue for now but feel free to comment if there is anything we can help with! Thank you!
@voltechs commented on GitHub (Feb 18, 2022):
Adding more information (searched for existing issues like a good citizen).
I have the Samsung 49" Odyssey G9 Gaming Monitor (LC49G95T). Maybe somewhat irrelevantly, I'm noticing that Samsung has two SKUs for this, one of which is discontinued. I purchased this a few days ago and it looks like they sent me a discontinued version so I'll have to get on the phone with them and see what's going on. That being said, I can confirm that even with the latest firmware (1015.0 at this time) no hardware dimming.
I "upgraded" from the CRG9 model, which did work great with MonitorControl dimming.
All that to say, is there anything I can do as an owner of the device to help you debug/develop support for it?
Edit: I decided to do some poking around, but I was quickly stymied. I was looking around on ddcctl, and found this feature request (because I use PIP, but that's irrelevant) and saw mention of an app (for Windows) called ControlMyMonitor. I thought maybe I would get a bunch of control codes or whatnot from it to relay here in hopes that it would help further support for the monitor, but I only got this error instead (see screenshot). I tried turning PIP off too, for what it's worth. Seems either I have a lemon, or these monitors simply don't support DDC? Seems unlikely and if so, outrageous.
Screenshot
Edit2: More sleuthing, found this documentation from www.ddcutil.com.
@henryhobhouse commented on GitHub (Feb 26, 2022):
I've got a CRG9 and have also been trying to get something working here.
I'm almost there. I'm using monitor control to adjust brightness but as other have said no dice on volume. I have, however, found that eqMac does work adjusting volume including supporting native volume keys.
The only downside is eqMac isn't particularly stable and crashes frequently when coming out of sleep or changing monitor setting (in my case turning pbp on or off)
So almost there but not quite. Not sure eqMac is doing a different path to make volume work but would be above awesome if monitor control could utilise there approach as it's brilliant, and importantly, stable app.
@voltechs commented on GitHub (Oct 11, 2022):
FYI, this issue/thread is for the CRG9's "successor" (of sorts), the Odyssey G9 Gaming Monitor, not the CRG9 itself. I also noted above that I upgraded from that monitor and MonitorControl was working just fine with it (as far as brightness). I think we're still SOL on the Odyssey G9 for now 😔
@TeaRex-coder commented on GitHub (Jul 6, 2024):
Not being able to use DDC on DisplayPort with my G9 has been bothering me as well :\
I've been working on a fix, so us G9 users might not be SOL
It's a custom PCB that uses the HDMI input to send the DDC commands from the host computer while using DP for video.
Still working out a few core features, but trying to gauge from the community if ppl actually care lol.
If this isn't a great place to talk about this, feel free to email me or DM me on Twitter/X
@waydabber commented on GitHub (Jul 7, 2024):
Wow, nice! :)
@voltechs commented on GitHub (Jul 7, 2024):
That's pretty clever! I'm definitely interested. Keep us posted!
@TeaRex-coder commented on GitHub (Jul 7, 2024):
Thanks, I'll keep you guys posted :)
@waydabber commented on GitHub (Jul 7, 2024):
I'll move this over to discussion so it is not a closed issue (difficult to find).