Common Issues

This guide covers the most common issues you may encounter when using Kilowhat with your Yaeltex controller, along with solutions to get you back up and running.

Device Not Detected

If your controller isn’t appearing in the Devices dropdown, follow these steps:

Check USB Connection

1. Ensure the USB cable is firmly connected at both ends
2. Try a different USB cable (some cables are charge-only and don’t support data)
3. Connect directly to your computer rather than through a USB hub

Try a Different USB Port

• Switch to a different USB port on your computer
• Prefer USB ports directly on your computer over hub connections
• On desktop computers, try ports on the back panel as they often have better power delivery

Refresh Devices

1. Click the Refresh button in the Devices panel
2. If that doesn’t work, try unplugging and replugging the controller, then refreshing again
3. As a last resort, reload the Kilowhat web page entirely

Tip

You can work on a configuration in Kilowhat even without a controller connected. Save your configuration to a file and upload it to your controller later.

Browser Compatibility

Kilowhat requires a browser that supports the WebMIDI API. Recommended browsers:

Browser	Support Status
Chrome	Full support
Firefox	Requires WebMIDI extension
Edge	Full support
Safari	Limited support

Caution

Firefox requires the Web MIDI API extension to be installed for MIDI functionality.

Windows-Specific Issues

On Windows, each MIDI port can only be open in one application at a time. If your controller isn’t detected:

1. Close any DAW, MIDI utility, or other software that might have the controller’s ports open
2. Click Refresh in Kilowhat or reload the page
3. Try disconnecting and reconnecting the controller

MIDI Not Working

If your controller is detected but MIDI messages aren’t being sent or received correctly:

Verify MIDI Port Selection

Your controller may have multiple MIDI ports (USB and MIDI DIN). Ensure you’re sending to the correct one:

1. Open the component card you want to configure
2. Check the Output Port setting
3. Set it to USB for connection to your computer via USB
4. Set it to MIDI for connection via the 5-pin DIN connector

Check Device Selection

Confirm you have the correct device selected in Kilowhat:

1. Go to Preferences > Devices
2. Verify your controller appears in the dropdown
3. Select it if it isn’t already selected
4. Check that the Link indicator shows yellow (connected)

Confirm MIDI Channel Matches Your DAW

MIDI channel mismatches are a common cause of communication issues:

1. Note the MIDI channel configured in Kilowhat for your component
2. Verify your DAW is listening on the same channel
3. Most DAWs default to “All Channels” but MIDI learn features may lock to a specific channel

Tip

Use the MIDI Monitor to verify what messages your controller is sending. This helps identify channel or message type mismatches.

Use MIDI Monitor to Debug

The MIDI Monitor is invaluable for troubleshooting:

1. Enable MIDI Monitor via Preferences > Kilowhat Options
2. Move the control that isn’t working
3. Verify the message appears in the monitor
4. Check that the channel, CC number, and values are what you expect
5. If no message appears, the issue is with the controller configuration
6. If the message appears correctly, the issue is likely in your DAW settings

Encoder/Fader Values Jumping

When switching banks or when parameters change in your DAW, the physical position of your analog control may not match the current parameter value. Moving the control causes an audible “jump” in the value.

Configure Takeover Mode

Takeover mode prevents value jumps by controlling how analog components behave when their physical position doesn’t match the software value.

1. Go to Preferences > Controller Options
2. Find the Takeover Mode setting
3. Select the mode that best fits your workflow

Available Takeover Modes

Mode	Behavior	Best For
None	Incoming feedback values don’t affect component behavior; values may jump	Simple setups without bank switching
Pick-Up	Control won’t send values until physical position matches the parameter value	Precise control, avoiding any jumps
Value Scaling	Control sends values immediately but scales them to converge smoothly with the target	Quick response while minimizing audible jumps

Tip

Pick-Up mode is recommended for most users. It ensures you never accidentally jump a parameter value, though you’ll need to move the control to the current position before it responds.

Caution

Takeover mode is a global setting that affects all analog components on your controller. Choose the mode that works best for your most common use case.

Changes Not Saving

If your configuration changes aren’t persisting:

Send Changes to Device

Editing a component in Kilowhat doesn’t automatically update your controller. You must explicitly send changes:

1. Make your configuration changes in Kilowhat
2. Click Send to Device to upload the configuration
3. Wait for the transfer to complete before disconnecting

Caution

If you close Kilowhat or disconnect your controller without clicking Send to Device, your changes will be lost.

Save Configuration to File

For backup and portability, save your configuration to a file:

1. Configure your controller in Kilowhat
2. Use the Save function to export your configuration
3. Store the file in a safe location
4. Use Load to restore your configuration later

Benefits of saving to file:

• Backup before making major changes
• Transfer configurations between controllers
• Work offline and upload later
• Share configurations with others

LEDs Not Responding

If your LEDs aren’t lighting up or updating correctly:

Check Feedback Source Settings

The feedback source determines where your controller listens for LED update messages:

1. Open the component card for the LED that isn’t responding
2. Check the Feedback Source setting
3. Ensure it matches where your feedback is coming from:

Source	When to Use
Local	LED responds only to your direct interaction
USB	LED responds to messages from DAW via USB
MIDI	LED responds to messages from external gear via DIN MIDI
USB + MIDI	LED responds to either source (recommended default)

Tip

If your DAW is connected via USB, make sure the feedback source includes USB. Setting it to Local only will prevent DAW feedback from updating your LEDs.

Verify DAW Is Sending Feedback

Many DAWs don’t send MIDI feedback by default. To enable feedback:

1. Check your DAW’s controller/MIDI preferences
2. Enable MIDI output to your controller
3. Ensure the DAW is configured to send feedback on the same channel and CC your controller expects
4. Use the MIDI Monitor to verify feedback messages are arriving

Check Message Matching

For feedback to work, the incoming message must match what the component expects:

Setting	Must Match
MIDI Channel	Same as configured in feedback settings
Message Type	CC, Note, etc. must match
Parameter Number	CC number or Note number must match
MIDI Port	USB or MIDI must match the source

Common Feedback Issues

Symptom	Likely Cause	Solution
LEDs work when touched but not from DAW	Source set to Local only	Add USB or MIDI to source
LEDs respond to wrong controls	Parameter number mismatch	Match CC/Note numbers
LEDs respond but wrong color	Color mode misconfigured	Check Fixed vs Value to Color mode
LEDs respond but wrong brightness	Intensity settings	Check Value to Intensity configuration

Still Having Issues?

If you’ve tried the solutions above and still have problems:

1. Check firmware - Ensure your controller has the latest firmware
2. Try another computer - Rule out computer-specific issues
3. Factory reset - Reset your controller to default settings and reconfigure
4. Contact support - Reach out to Yaeltex support with details about your issue

Related

• Devices and Refresh - Device connection details
• Controller Options - Takeover mode and global settings
• MIDI Monitor - Debug MIDI messages
• Feedback - Complete feedback configuration guide