- Basic 1.1.1.9
- Banana 2.1.1.9
- Potato 3.1.1.9
.\vmrcli.exe [-h] [-v] [-i|-I] [-f] [-k] [-l] [-e] [-c] [-m] [-s] <api commands>Where:
h: Print the help message.v: Print the version of vmrcli.i: Enable interactive mode, use (-I) to disable the '>>' prompt.- If set, any api commands passed on the command line will be ignored.
f: Do not split input on spaces.k: The kind of Voicemeeter (basic, banana or potato). Use this to launch the GUI.l: Set log level, must be one of TRACE, DEBUG, INFO, WARN, ERROR, or FATALe: Enable extra console output (toggle, set messages)c: Load a user configuration (give the full file path)m: Launch the MacroButtons applications: Launch the StreamerView application
- Commands starting with
!will be toggled, use it with boolean parameters. - Commands containing
=will set a value. (use+=and-=to increment/decrement) - All other commands with get a value.
Examples:
Launch basic GUI, set log level to INFO, Toggle Strip 0 Mute, print its new value, then decrease Bus 0 Gain by 3.8
.\vmrcli.exe -kbasic -lINFO !strip[0].mute strip[0].mute bus[0].gain-=3.8Launch banana GUI, set log level to DEBUG, set Strip 0 label to podmic then print Strip 2 label
.\vmrcli.exe -kbanana -lDEBUG strip[0].label=podmic strip[2].labelIt may be desirable to send a string request containing spaces, for example to change an output device. By default the CLI splits such strings, to avoid this pass the -f flag. It's probably best to use this with single commands only due to its effect on how the CLI parses strings. Also note the inclusion of the double quotation marks, it seems the C API requires them.
.\vmrcli.exe -lDEBUG -f bus[1].device.wdm='"Realtek Digital Output (Realtek(R) Audio)"'
.\vmrcli.exe -lDEBUG -f strip[0].label='"My Podmic"'A short list of quick commands are available:
lock: command.lock=1unlock: command.lock=0show: command.show=1hide: command.show=0restart: command.restart=1
They may be used in direct or interactive mode.
Running the following command in Powershell:
.\vmrcli.exe -iWill open an interactive prompt:
Interactive mode enabled. Enter 'Q' to exit.
>>API commands follow the same rules as listed above. Entering Q or q will exit the program.
Scripts can be loaded from text files, for example in Powershell:
.\vmrcli.exe -lDEBUG $(Get-Content .\example_commands.txt)You may also pipe a scripts contents to the CLI:
$(Get-Content .\example_commands.txt) | .\vmrcli.exe -lDEBUG -IMultiple API commands can be in a single line, they may be separated by space, ; or ,.
Lines starting with # will be interpreted as comments.
Run the included makefile with GNU Make.
The binary in Releases is compiled with coloured logging enabled. To disable this you can override the LOG_USE_COLOR variable, for example:
make LOG_USE_COLOR=no