diff options
author | cbdev <cb@cbcdn.com> | 2020-01-05 23:26:04 +0100 |
---|---|---|
committer | cbdev <cb@cbcdn.com> | 2020-01-05 23:26:04 +0100 |
commit | e08b473d0eeb467ad358ba5314157753b4f37c18 (patch) | |
tree | d847784ab3a926054b586877e6d77865af574be1 /README.md | |
parent | f8ed6c26683c041ec61dac46d740b4b87df811ad (diff) | |
download | midimonster-e08b473d0eeb467ad358ba5314157753b4f37c18.tar.gz midimonster-e08b473d0eeb467ad358ba5314157753b4f37c18.tar.bz2 midimonster-e08b473d0eeb467ad358ba5314157753b4f37c18.zip |
Implement commandline config override (Fixes #26)
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -48,6 +48,8 @@ The MIDImonster takes as it's first argument the name of an optional configurati to use (`monster.cfg` is used as default if none is specified). The configuration file syntax is explained in the next section. +The current MIDIMonster version can be queried by passing *-v* as command-line argument. + ## Configuration Each protocol supported by MIDIMonster is implemented by a *backend*, which takes @@ -76,6 +78,11 @@ To make an instance available for mapping channels, it requires at least the `[<backend-name> <instance-name>]` configuration stanza. Most backends require additional configuration for their instances. +Backend and instance configuration options can also be overriden via command line +arguments using the syntax `-b <backend>.<option>=<value>` for backend options +and `-i <instance>.<option>=<value>` for instance options. These overrides +are applied when the backend/instance is first mentioned in the configuration file. + ### Channel mapping The `[map]` section consists of lines of channel-to-channel assignments, reading like |