- Support for the M2 CPU family and the new
- Allow streaming HTTP body in CLI implementation
lunar facelightCLI command
HUDwindow level for the rounded corners mask window
Some clarifications are needed after the last change:
Improve readability in direct sunlight when using
The contrast slider allows adjusting the pixel value formula for the brightest/darkest areas, to get even more contrast out of the miniLED display.
Developed in collaboration with the creator of BetterDummy, using a more native approach to provide:
Allow zero brightnessis off
I'm removing the 1-year of updates restriction and will give everyone unlimited free updates for Lunar 5.
Lunar will move to a major-version upgrade licensing model, where you will only have to pay for a new license if a new major version is launched (e.g. Lunar 6).
If that ever happens, you will also be able to use your previous license as a coupon to get a substantial discount if you previously bought Lunar.
escto cancel Auto BlackOut
"Control all monitors"for Function Hotkeys
externaldisplay filter for CLI
lunar preset "Night Owl"
500nits limit of the new 2021 MacBook Pro and Pro Display XDR
Note: Starting from
v5.5.0 Lunar will require
0.1%on average when no brightness change occurs
lunar blackoutcommand to CLI
lunar gamma --restore-color-synccommand for resetting to system default color settings
ddcutil-serverfor Raspberry Pi OS 64-bit
lunar command can now control the running Lunar app directly instead of spawning a new instance.
If the Lunar app is not running, the CLI will automatically use the old method of running the command directly.
lunarcommand to never spawn a new instance and fail if there's no Lunar app already running
--hostconfigures the hostname where to send the command
--keyconfigures the API key for authenticating the
lunarcommand against the Lunar app server
lunarcommand to always run the command locally and spawn a new instance even if there's a Lunar app already running
Added BlackOut without mirroring on holding
.appOnlyso that the system doesn't remember the BlackOut mirroring state after Lunar is quit
Note: if you have a monitor connected to the HDMI port of the MacBook, disable DDC manually
checkSlowWritefor DDC which could wrongly mark smooth transitions as unsupported
defaults write fyi.lunar.Lunar jitterAfterWake 1
1Fhit is parsed as hex
--hexwill always parse values as hex
It seems that some MacBooks don't support brightness change event notifications which causes the manual adjustments to not be reflected in the system brightnesss curve. In this update we try to detect if a MacBook is missing that support and instead of controlling its brightness, we forward the brightness key events to the system and let it do the brightness changing. Using the sliders for changing the built-in brightness will still have the reverting problem though, because we can't forward those events to the system.
6will allow you to turn off the monitor completely (just like pressing its physical power button) if the monitor supports that function
stationaryto fix it
0.08on brightness 0 to retain visibility
256values might fix this
recursive lockingcrash because of using
CGGetDisplayTransferByTableis buggy on Intel and crashes the app on some systems
Ctrl+Cmd+6to activate it and turn off the display where the cursor is
F15keys and the Brightness keys can send special key codes
lunar displays ultrafine input hdmi
lunar displays dell34 contrast
Thread.privatenot existing anymore
TSL2591library to a known working version
lunar://URLs for easy access to specific parts of the UI
lunar://displays/3for third display)
IsLidClosedflag has been set
default.profrawon every run of the CLI
0.00on some systems
Head over to the front page for more details.
Start at Loginfunctionality