Set arpeggio beep sounds for entering and exiting keybinding modes.

[Giresharu]

Required Program:
nircmd (The download button is at the bottom of the page)

After downloading, place it anywhere and add its directory to your system's PATH environment variable.

You can now use this command to play a beep:

nircmd beep [frequency] [duration]

We can achieve an arpeggio effect by sequentially playing multiple beeps with different frequencies.

For example:
The frequencies 783.991 1987.77 1174.66 1396.91 correspond to the notes G B D F, which form a G7 chord.
This chord has a sense of "suspense" or "unresolved tension," reminding you that you should exit this state soon.

Conversely, the sequence 1396.91 1174.66 987.77 1046.50 (with the first three notes being F D B followed by C) represents a Bdim resolving to C. This process sounds very comfortable and satisfying.

However, simply using nircmd beep does not work well for sequential playback within GlazeWM. If you write multiple shell-exec commands in the command array, the execution efficiency is low, and the intervals between beeps are inconsistent (sometimes fast, sometimes slow). On the other hand, if you write the nircmd beep commands in a .bat file and call it with shell-exec, a CMD window will flash briefly. I was unsure how to resolve this issue.

Therefore, I chose to use VBS to write these two sound effects:

Set WshShell = CreateObject("WScript.Shell")
WshShell.Run "cmd /c ""start """" /b nircmd beep 783.99 55 && start """" /b nircmd beep 987.77 55 && start """" /b nircmd beep 1174.66 55 && start """" /b nircmd beep 1396.91 150""", 0, False
Set WshShell = Nothing
WScript.Quit

Set WshShell = CreateObject("WScript.Shell")
WshShell.Run "cmd /c ""start """" /b nircmd beep 1396.91 55 && start """" /b nircmd beep 1174.66 55 && start """" /b nircmd beep 987.77 55 && start """" /b nircmd beep 1046.50 150""", 0, False
Set WshShell = Nothing
WScript.Quit

Subsequently, you can play the corresponding sound by adding this line to your commands:

shell-exec wscript c:/path_to_script/vbs_name.vbs

There is an even simpler way: set the default open action for .vbs files to Microsoft Windows Based Script Host, and place the .vbs files in a directory that is included in your PATH environment variable.

Then you can simply write:

shell-exec vbs_name.vbs

Here is my actual usage effect:

2026-01-17.05-55-16.mp4