Working with multiple settings
If MidiKey2Key is startet without parameters a default "settings.ini" is loaded and used to store Your changes.
You can save additional setting-files by using the
"Save As..." - command from the the File-menu. All Your settings can be stored in the "My Documents\MidiKey2Key"-folder but do not have to.
Any path is allowed.
To create a new setting, just use the
"New" entry from the "File"-menu and give Your settings file a path and a name.
When no special setting-file is loaded the
title-bar of the programm just shows "MIDIKey2Key vX.X.X.X and nothing else. If a different setting-file is loaded, it shows the name of the
setting in addition:
All changes that You do, are stored in this file. Therefore use
"Save As..." to have the new setting-name in the title-bar and then add or change your actions.
A different setting-file can be loaded by using
"Load Custom..." from the File-menu or start MidiKey2Key.exe with a path and setting-file-name.
For example:
"Path-To-Program\Midikey2Key.exe" "c:\Users\Ben\Documents\MidiKey2Key\NewGamingSetting.ini"
So it is possible to
create a simple shell-script (.bat or .cmd) that starts MidiKey2Key with a special setting. To start automatically other programs, use the built-in
STARTUP action.
For a lot more
easy creation of a shortcut to MidiKey2Key, that starts with a certain setting, You can use the
"Save Shortcut..."-command from the File-menu.
Just choose a new name of Your choice ("MidiKey2Key - " is the default, You can add a settings-name freely, or change it completely to antyhing), choose a directory (Your desktop is the first choice of the program) and click "Save".
The File-menu in overview
- New wants to have a path/name of a new settings-file and creates a new blank action collection. Recommended to start.
- Reload Settings reloads the current settings (named in the title-bar or just settings.ini)
- Load Custom... lets You open a different setting-file
- Save Settings saves Your current settings in the setting-file named in the title-bar or just in settings.ini
- Save As... lets You choose a new setting file to save into
- SaveShortcut... creates a shortcut to MidiKey2Key to startup with the actual settings-file
- Optionsopens a dialogue with general program-settings like "autostart listening", ...
- Exit exits the program.
There are some more additional features:
- From the menu "MIDI" and from the context-menu in the system-tray you can start and stop the listening to the MIDI-input.
Stopping the listening stops the reactions on incoming Midi-events. These menu-buttons act the same as the Start/Stop-button.
- You will need to stop listening first for changing the Monitor settings, which are:
- "Listen to SysEx": This shows SysEx-Midi-events which are not all following the general Midi-rules. Manufacturers of Midi-equipment can use these events to send longer data, to send
setup-data of device-settings or i.e. sample-data. The ability to switch them on is experimental only. Wether a useful result will be generated, will vary much from case to case.
- "Log to file" writes down all incoming Midi-events into a logfile. You can choose the filename by using the button "...".
- There are some more options to set in the options-dialogue (Menu File-Options):
- "Autostart listing": If You check this checkbox, MidiKey2Key will start listening automatically the next time when it is started.
- "Minimize to tray when autostarted": Let´s start MidiKey2Key in the tray in the background (if "Autostart listing" is checked too).
- "Mirror Midi": Mirrors the received Midi-commands back to Your Midi-device if needed.
- "Confirmation after saving action": Enables/disables the confirmation of storing the action after saving/editing an action.
The Train Simulator features will be explained in this online manual in the future, for now check out the corresonding tutorials on YouTube.
VB-Script-SDK for advanced programming
To let a single Midi-Pad trigger a program and the next time, You press it again to trigger another program or stop the first one, there is a VB-script example
in the download-section.
Normally MidiKeyKey can only perform one program-action on one Midi-Key and another on a 2nd Midi-Key. In the given example everytime the same single script is executed.
It remembers it´s last state. The example can be used to
play a sound-file in the background via VLC and stops VLC when executed again. This saves Midi-Pads and can be used to trigger a bunch of different sound-files,
since the script takes the path/name of the soundfile to be played as an argument.
Possibly coming features
Thinking about this...