Cakewalk Setup & Troubleshooting: Impact GXP

Impact GX/LX Mini & GXP Support

Here are the steps you need to go through to get Cakewalk/Sonar up and running with your Impact GXP Controller:

Download ‘Impact_GXP_Cakewalk_Support…’ from your Account page after registering your product.

Run the ‘Impact_GXP_Cakewalk_Support…’ in that folder and follow the on-screen instructions.

  1. Plug in your Impact GXP and make sure it’s switched on (if you didn’t do so already).
  2. Launch Cakewalk/Sonar and open the Edit menu.
  3. Select ‘Preferences’
  4. In the MIDI category, select ‘Devices’ (image 1).
  5. Make sure the following ports are ticked (image 1):
    • Inputs: Impact GXP**
    • Inputs: MIDIIN2 (Impact GXP**)
    • Outputs: MIDIOUT2 (Impact GXP**)
  6. Click ‘Apply’.
  7. In Cakewalk/Sonar Preferences, now go to ‘Control Surfaces’ in the MIDI category.
  8. Click on the yellow star icon at top right corner.
  9. The Controller/Surface Settings dialogue box now appears (image 2).
  10. Make the following selections as per image 2.
  11. Controller/Surface: ‘Impact GXP**’
  12. Input Port: ‘MIDIIN2 (Impact GXP**)’
  13. Output Port: ‘MIDIOUT2 (Impact GXP**)’
  14. Click ‘OK’.
  15. Click ‘Apply’.
  16. Image 3 shows how the Control surface window should now look.
  17. Click ‘Close’.

That’s it, setup is now complete.

Note: ‘Impact GXP**’ where ** represents the Impact GXP keyboard model you are using.


If you find that your Impact keyboard does not appear in the ‘Controller/Surfaces’ list as shown in Image 2, you may need to install the Microsoft Redistributable Files for VS2013.

If you are using a 64-bit version of Windows, you will need to run both of these installers:

If you are using a 32-bit version of Windows, you only need to run the ‘vcredist_x86.exe’ installer.

Once you have done that, install the latest ‘Impact_GXP_Cakewalk_Integration’ installer again and reopen Cakewalk/Sonar.

Patch Changes
If you find that the [< Patch] and [Patch >] buttons don’t work when controlling a third-party plug-in, it’s likely because the plug-in uses it’s own patch browser. The Patch buttons on the Impact series control the patch navigation functions of the DAW, so you may need to save the plug-ins presets in your DAWs patch format, before you can use the Patch buttons on the Impact controller for patch navigation. You can find more information about saving patches in your DAW, in the documentation for that program.