[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f119xc14jykeqc":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"Binaryify\u002FMonitorBar",15,"macOS 菜单栏 \u002F Windows 托盘的显示器管理工具：不依赖 DDC\u002FCI，通过澎湃 OS 局域网接口切换输入源、调节音量","Go",162,12,16,10,[],"Menu-bar and tray tool that switches inputs and volume on HyperOS monitors without DDC\u002FCI, plus dimming and resolution controls.","MonitorBar is worth a look if you own a REDMI HyperOS monitor and a Mac or Windows PC, and you are tired of reaching for the on-screen menu to switch between them. Everyone else should check that the probe finds their display first, because the README is explicit that only one model was tested.\n\n## The problem\n\nYou have a dual-mode monitor with your Mac on USB-C and a Windows machine on DisplayPort, and you want to flip between them or nudge volume without touching the monitor's joystick. On DDC\u002FCI monitors, existing menu-bar tools do this. On the REDMI G Pro 27U 2026, they cannot: the README attributes this to REDMI not supporting DDC\u002FCI, so input switching and volume are locked to the physical menu. MonitorBar replaces that trip with a menu-bar\u002Ftray panel, and on the resolution tab it also exposes the 4K 160Hz \u002F 1080p 320Hz mode switch, which otherwise requires digging through the monitor OSD and waiting a few seconds while the system redetects the display.\n\n## What's different\n\nThe mechanism, not the UI, is the point. MonitorBar probes three channels at launch and routes each action to whichever is available: the HyperOS LAN remote API on port 6095 (source list, source switching by number, volume, remote key events), DDC\u002FCI over IOAVService on Apple Silicon or the Windows Monitor Configuration API, and the GPU gamma table for software dimming and color temperature. Input and volume prefer LAN, then DDC\u002FCI; brightness uses hardware backlight when DDC\u002FCI exists and falls back to gamma dimming otherwise. Because the gamma route works on any cable and any monitor, a display with neither HyperOS nor DDC\u002FCI still gets dimming, color temperature, scenes, resolution switching and screen time — just not input switching, volume or hardware backlight. The trade-off is a split feature set that depends on what the display answers, which the README handles by hiding unsupported controls.\n\nThe less obvious cost is trust in the LAN path. The README says the app scans the local \u002F24 subnet on first launch to find the monitor and remembers the address afterwards, and the macOS build is unsigned, so first launch needs the right-click → Open workaround and a local-network permission grant. The gamma implementation also differs by platform: Windows only accepts gamma values near the standard curve (darkest around 50%) and clamps below that, while macOS has no such limit. Both restore the original curve on exit.\n\n## Who should try it\n\nA good fit is someone with the G Pro 27U 2026 and two computers attached to different ports, who wants one-click input switching from either machine and a keyboard shortcut for volume. A reasonable second fit is a DDC\u002FCI-capable monitor owner who wants software dimming below the hardware minimum via the combined-brightness slider. A poor fit is anyone with an untested HyperOS model who expects it to work out of the box: the README warns that interface and source numbering can differ by model, and adapting means editing Go files in internal\u002Fmitv or internal\u002Fdisplay. Windows users also lose follow-internal-display-brightness, which is macOS-only and needs DDC\u002FCI backlight.\n\n## Requirements and limitations\n\nYou need macOS 12+ (Apple Silicon or Intel) or Windows 10\u002F11, and for the headline feature a HyperOS monitor on the same network as the computer. The tested-hardware caveat is the big one: only the REDMI G Pro 27U 2026 is listed as tested, so probe your display before relying on it. Screen-time tracking is inferred differently on each platform — macOS reads monitor sleep state, Windows derives it from idle time versus the power plan's display-off timeout — so the numbers are not a direct measurement on Windows. Auto-update checks GitHub releases and applies signed delta packages, which means ongoing network access and accepting an unsigned app bundle that updates itself. The [project instructions](https:\u002F\u002Fgithub.com\u002FBinaryify\u002FMonitorBar\u002Fblob\u002Fmain\u002FREADME.md) cover adaptation for other monitors, and [releases](https:\u002F\u002Fgithub.com\u002Fbinaryify\u002FMonitorBar\u002Freleases) carry the signed builds.\n\n## HotRepo's take\n\nHotRepo has only a two-date sample (2026-10-24 to 2026-10-25) and one observation: #21 on the NEW-REPOSITORY board with 162 total stars on 2026-10-25, which is not a daily growth figure. There is not enough comparable daily history to judge whether interest persists, so treat the attention as a snapshot only. The decisive question is compatibility: confirm the probe output lists your monitor and its source identifiers before committing.",{"slug":19,"name":20},"productivity","Productivity & Utilities",[],"MIT",null,"2026-10-25T03:17:50Z",[],1792912498]