Troubleshoot

I have issues to configure KordsKontrol to work with my controller!

The first time you launch the program, you are invited to select 3 MIDI ports that will be used by KordsKontrol to communciate, on one hand, with your controller, and on the other hand, with your destination instrument. Please refer to “How does it work” for further explanations.

The first 2 ports are used to communicate with your controller. The MIDI messages coming from your controller (“fromCT”) are considered as an Input; while the MIDI messages sent to your controller (“toCT”) are considered as an Output.

Usual ports used by the Korg padKONTROL are:

Input: “MIDIIN2 (padKONTROL)” or “padKONTROL (1) PORT A”; Output: “MIDIOUT2 (padKONTROL) ” or “padKONTROL (1) CTRL”

Usual ports used by Native Instruments MASCHINE  MK I are “Maschine Controller In” or “Maschine Controller Virtual Input » and “Maschine Controller Out” or “Maschine Controller Virtual Output »

Usual ports used by Native Instruments MASCHINE  MK II are “Maschine MK2 In” and “Maschine MK2 Out”.

Etc…

The third port used by KordsKontrol corresponds to the MIDI ouput to the destination instrument (hardware or via a virtual MIDI cable) that you want to use with KordsKontrol (“toOUT” port).

Once the intial setup is done, these 3 MIDI ports names are saved in the settings.ini text file saved by the application in the KordsKontrol folder generated in your system default user folder.

If you wish to manually modify the name of the MIDI ports in the settings file, please kindly make sure that the MIDI ports names are correct, including uppercase if any. Please also ensure that you write the port name just after the “=” in the text file, and don’t add any space at the end of it.

If you want to select the MIDI ports again, please simply delete the settings.ini file

Please refer to User guide for more information.

These ports shall not be used by any other application to avoid conflicts. It is therefore recommended to disable it in all the music software (DAW, …) you use, or, at least to start KordsKontrol before any application that may request access to it.

Also, KordsKontrol has to be exitted properly to ensure MIDI resources are freed up. Never kill the application, otherwhile you may have issues when you launch application again (ports not freed, requiring a system reboot).

For the Korg padKONTROL, please also make sure that the USB drivers are properly installed.

http://www.korg.com/us/support/download/product/0/161/

On Mac OS, please make sure that you are using the CoreMIDI4J version of the Midi ports, otherwhile it will not work! (see User guide for more details)

For Native Instruments MASCHINE, please ensure that both the Controller Driver and the Controller Editor software are up to date.

https://www.native-instruments.com

The controller must be placed in MIDI Mode, with the KordsKontrol template corresponding to your device loaded.

Please visit Downloads page to get the right Controller Editor template.

For details concerning Controller Editor and the Controller MIDI mode, please refer to Native Instruments documentation.

https://support.native-instruments.com/hc/en-us/articles/210264145-How-to-Use-Your-Native-Instruments-Controller-in-MIDI-Mode

KordsKontrol has been tested only with Maschine MKI controller until now; if there is any issue with the templates, please don’t hesitate to let me know!

If the issue persists, try to reset your controller (OFF-ON), or restart your computer.

Additionally, the latest version of JAVA must be installed on your computer (minimum JavaSE 1.7, jre 1.8.0_31)

https://www.java.com/fr/download/

And finally… please be patient :). The application generates a huge amount of data in the Chords database, which may take a few seconds.

My destination instrument is not playing!

First of all, you need to ensure that the selected output port “toOUT” is not be locked or used exclusively by another application, so that KordsKontrol can use it to send MIDI out.

If you are targeting Virtual Instruments in a DAW or Standalone, you must ensure that the “toOUT” port is properly configured as a MIDI input in your application, and that it is enabled for receiving MIDI events.

Please also check if you need a Virtual MIDI port. You need either a third-party Virtual MIDI port (Windows), or a IAC Driver Virtual MIDI port (Mac OS) – See the User guide  for more details.

If you are targeting an external Hardware Instrument, you must select for “toOUT” the input MIDI port of the instrument, or direct “toOUT ” to a MIDI OUT connected to the instrument.

For further explanation regarding MIDI routings, please refer to the User guide.

Last but not least, KordsKontrol is a 16 MIDI channels application. Some of the notes played are directed to MIDI channel 2, 3….. Please check that your destination is configured to receive MIDI from another channel than 1, or change the MIDI channels used by KordsKontrol in the settings file.

I have some issues with the sustain pedal of my destination instrument!

Some instruments may encounter issues with the automatic Sustain Pedal management (when a Sustain Pedal Off message is followed by a Sustain Pedal On message too quickly, the Pedal Off message is sometimes ignored) . The settings file allows to adjust timers parameters to enhance compatibility on this point. For further explanation, please refer to the User guide.

I have some audio jitters while using KordsKontrol!

KordsKontrol is able to generate a huge amount of MIDI data on its output MIDI bus. In some cases, a bus overload could lead to some audio jitters.

KordsKontrol is able to generate a huge quantity of notes simultaneously. In a virtual instruments multi channel configuration, KordsKontrol can easily overload your system computing real time audio rendering capabilities, especially when each MIDI channel is affected to a dedicated plugin, each of them consuming your system resources. In that case, adjusting the sample buffer size of you Audio device is recommended (the drawback being an increased latency).

Please also keep in mind that KordsKontrol is managing automatically the sustain pedals for all the 16 channels (up to 6 channels for chords, 1 channel for Drums, 1 channel for Scale notes, 8 channels for Arpeggios). So, please avoid to direct all the channels to a single destination target: this instrument will receive simultaneously a lot of sustain pedal messages coming from the different channels.

Please refer to user guide for more information on the MIDI channels configuration.

Last but not least, it will be a great pleasure to support you if you still meet issues to start the application. Don’t hesitate to ask!