![]() ![]() Here’s an example for registering keyboard key “A” to MIDI virtual button “24” (that’s Octave 0, C note): Īll I had to do was to batch-replace “DeviceConfigurationGuid” for input and output devices and the Rii mini profile was ready to be used. ![]() Transferring mappings from yesterday’s Logitech keyboard to today’s Rii mini was a matter of minutes as I duplicated the profile’s XML text and then replaced the device IDs in URC’s “content.xml” file (where the app stores everything). The rest of the MCDU buttons (such as FPLN, IDX, LEGS etc) I’ll either map in F1-F10 keys of Rii mini, or I’ll just leave them in Elgato Stream Deck. I’ve essentially mapped everything that can be used for typing in MCDU: dot, plus/minus, spacebar, slash, delete and I’m using Enter as EXEC. I’ve set up the alphanumeric keys of Rii mini to do the obvious: each letter or number is the respective A-Z and 0-9 button in WT CJ4 and CRJ. Otherwise buying a Novation Launchpad mini at anywhere between 60 to 95 Euros can be a preferable solution (not for me, as I’d then have to label the MIDI pad buttons, whereas with a keyboard I already know which key does what if I only use it for MCDU alphanumeric input). If you already own a device such as RealSimGear GCU47X for X-Plane & P3D - then you won’t care about lame MIDI workarounds. use numpad or other right hand side keys for specific tasks and leave the rest intact.Īlso this is obviously targeted to those who already have spad.next and don’t want to spend any money at all for any additional peripherals. Instead use half your keyboard as standard input for Windows (not map anything, not block any keystrokes) and then block the rest and map it to MIDI commands. very specific MSFS controls via spad.next)įor example an option would be to not use two keyboards. Pretty sure others have thought of all that a few dozen years before I did, so I’ve only tailored my solution to fit my exact needs (i.e. Yes, using a standard keyboard as a MIDI controller may have lots of potential for lots of different uses. Launch UCR, create a new profile and set your secondary keyboard as input and LoopBe as the MIDI output: We will need this as the output for UCR and also the MIDI input device for SPAD.neXt. Install LoopBe1, which is free software (as long as it’s not used for commercial reasons) which adds a MIDI device in Windows. The installation instructions are as follows: “Extract the 3 DLL files and place Core_Midi.dll in UCR’s /Providers/Core_Midi/ and the other two files in /Plugins/UCR.Plugins/”. The DLLs are essentially plugins which will add MIDI mapping features to UCR and will allow us to map keyboard buttons to MIDI commands. Enabling the blocking feature is as easy as updating the value of “BlockingEnabled” config item found in “UCR_v0.9.0\Providers\Core_Interception\Settings.xml” from False to True.Īdd 3 DLL files to UCR, found in a plugin called MapToMidi.zip and downloaded from here. This will effectively result in the second keyboard sending only MIDI commands to MSFS and nothing else (so we’ll avoid any key conflicts). Sounds fishy but it seems to be legit software, has been around for years and is well known to the community.Įnable Core Interception’s blocking feature, which allows UCR to prevent our secondary keyboard’s keystrokes from registering in Windows as standard input. All we need is to run executable “\Interception\command line installer\install-interception.exe” (as admins via command prompt) and reboot. Install UCR’s Core Interception software, which is essentially a driver which captures our secondary keyboard’s keystrokes before they reach Windows. In the worst case scenario, you will need to use the power button on your PC to reset it.ĭownload UCR, which enables us to map any device input to any device output. If this happens then try killing UCR via CTRL+ALT+DEL and Task Manager. The solution can scale up to as many additional keyboards as we want to.ĭISCLAIMER: Best to try this with TWO keyboards connected to your PC, otherwise you may end up locking your input if you are only using one keyboard. So what if I could use a secondary PC keyboard as a dedicated input, masking it as a virtual MIDI device? I would effectively have as many keys as I wanted for free (except the initial purchase of SPAD.neXt). In particular to control things that cannot be mapped directly via in-game settings, for example all L:VAR/H:VAR variables which are very common in 3rd party aircraft (WT CJ4, Piper P28R, CRJ and so on).Īlthough a full blown MIDI controller with dozens of keys and knobs would be ideal, they also don’t come cheap. The idea is simple: I’ve been using the full version of SPAD.neXt which includes MIDI support and, as such, can utilize devices such as Behringer Xtouch Mini or Novation Launchpad Mini to control MSFS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |