3.0.0 bug fixes and some enhancements#550
Conversation
…umber to acquire framebuffer port on Intel
… is no registered display configuration change (this to prevent some sleep issues on Apple Silicon).
…dard for write operations (should not hurt but improve stability for problematic displays).
… preferences and disable DDC read.
… default value instead of 0 if it is not available and could not read DDC.
…peats or first keydown)
…ring. Alternate fix for M1 sleep issue.
…e involved in volume change.
There was a problem hiding this comment.
I was initially having an issue where, when muting, the monitor OSD and MacOS would display as muted state but volume level would still be at level 6 (even though the display OSD indicated muted), this is probably not a big deal and now I'm unable to reproduce it, but I guess we might get some issues opened for this if it does happen for other people.
edit:
Here it is (had to compress quite a bit to get it allowed on Github):
This might be a part of the fix, and it seems to work fine, I haven't read up on the entire issue thread, so it's fine for me personally. Only happens when "Enable Mute DDC Command" is enabled, so seems like a feature :)
Yes, this is a feature actually. When Mute DDC Command is enabled, the app will never issue Volume=0 since that makes some displays do bad things, it only issues a Mute instead while internally remembering that the volume is logically 0. This is how it worked for the guys who were testing this for me after several attempts. |
2 participants
Bug fixes / enhancements in this pull request:
Please, do a general testing on Intel if possible to make sure everything works. On M1 everything seems all right.