Troubleshooting: 'Go' command trigger issues

You press Go and nothing happens; KTPlayer isn't receiving the trigger. Work through the section for your trigger method, keyboard or MIDI.

Spacebar (or other keyboard command) GO not working

1. Is KTPlayer the focused app?

Key commands only fire when KTPlayer is the focused window.

1. Click anywhere in the KTPlayer window.
2. Confirm the KTPlayer window has the standard active-window styling.
3. Try Go again.

2. Is the key command still assigned?

If the Go key command got cleared or assigned to a different key, the default Space   won't trigger anything.

1. Open Preferences → Assignments (⌘,  ).
2. Find Go in the command table (it appears first).
3. Confirm the Key column shows Space   (or your preference).
4. If empty or wrong, click the Reset button beside the Key field to restore the default.

MIDI GO (pedal, button, or similar) not working

If your MIDI trigger isn't firing Go, work through Troubleshooting: MIDI assignment not working first. It covers device recognition, Listen, assignment, and the message-mismatch case in detail. The checks below are the GO-specific extras.

1. Is the MIDI device sending the message KTPlayer expects?

1. Open Preferences → Devices → MIDI devices.
2. Confirm your MIDI device shows in the list with Listen ticked.
3. Open Preferences → Assignments. Find Go.
4. Confirm the MIDI column shows your assigned message. If blank, re-assign with Learn.

2. Is "Prevent a second GO" too high?

KTPlayer has a guard against accidental double-fires. If two presses arrive within a defined window, the second is ignored. A footswitch that sends a "noisy" press (multiple messages in quick succession) can look like a missed trigger.

1. Open Preferences → Behavior.
2. Find Prevent a second GO within. Default is 100 ms  .
3. If it's been pushed up (say 500 ms  ), reduce it.

GO is delayed

If Go fires but lands late, there are two usual causes:

1. Quantisation is on. With Quantize GO to next bar enabled, a queued Go waits until the end of the current measure before firing, so it can feel delayed when you press mid-measure. This is expected behavior, not a fault. See How to use quantised cue triggering.
2. System load. If the Mac is under heavy CPU or memory pressure, triggering can lag. Close other apps, and if playback is also crackling, check the buffer size. See Troubleshooting: Audio distortion and playback quality issues.

Still no trigger?

1. Restart KTPlayer.
2. Restart the Mac.
3. Test with the default key command (Space) and the default MIDI assignments, which isolates whether the customization is the issue.

If still broken, contact KeyboardTEK (support@keyboardtek.com) with the show file name, your macOS version, the trigger method (keyboard / MIDI), and the exact key or MIDI message you're using.