Hi Chris,
I know this is mentioned by Rob but I thought it best to start a thread only for keyboard commands.
Currently keyboard controls don’t function. The only way to start/stop, etc, etc is by using the mouse. I can’t currently test midi but will be doing that as soon as possible.
Navigation key combos still work, for example CTRL + 5 for speed etc.
This is tested on an Intel Mac Mini running Sequoia 15.3.2 as well as my Macbook M1 Pro also running Sequoia 15.3.2.
Wow, OK—so this is why we do beta builds. 
When you press the spacebar or another key that isn’t working for you, do you hear the macOS system alert/beep sound, or does nothing happen at all in Capo?
Either way, I need to get some debug logs from you. Launch the Terminal app, copy/paste the following command, and press the return key to run it. When prompted, enter your login password[1]:
sudo log stream --debug --predicate 'subsystem=="com.supermegaultragroovy.capo.CapoRemoteControl"'
Then, return to Capo and press some of those keystrokes—spacebar, command-arrows, etc. Back in the Terminal app, you should ideally see messages that look like this[2]:
2025-03-31 10:08:00.235256-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: togglePlayback()
2025-03-31 10:08:00.340876-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] No commands for message: keyUp(space)
2025-03-31 10:08:01.471461-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToSongBoundary(beginning)
2025-03-31 10:08:01.542247-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] No commands for message: keyUp(command leftArrow)
2025-03-31 10:08:02.366250-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: togglePlayback()
2025-03-31 10:08:02.474421-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] No commands for message: keyUp(space)
2025-03-31 10:08:02.955027-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.200510-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.235381-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.267735-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.300570-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.334141-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.368339-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Dispatching: goToNext(entry: bar)
2025-03-31 10:08:03.383807-0400 0x41ade13 Debug 0x0 11232 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] No commands for message: keyUp(rightArrow)
Please copy the messages and then paste them in here for me to take a look at.
If nothing appears in the Terminal while you press keys, try quitting and re-launching Capo while the log messages are still running. At the very least, you should see the following messages (or something like them) on launch:
2025-03-31 10:11:37.389590-0400 0x41d8470 Info 0x0 14404 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:First-Time Initialization] First-time initialization already completed
2025-03-31 10:11:38.119404-0400 0x41d8357 Info 0x0 14404 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Bindings successfully initialized
2025-03-31 10:11:38.778057-0400 0x41d8357 Debug 0x0 14404 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CoreMIDIMessageProvider] Successfully created MIDI client
2025-03-31 10:11:38.782294-0400 0x41d8357 Debug 0x0 14404 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CoreMIDIMessageProvider] Successfully created MIDI input port
Let me know if even these messages aren’t showing up for you. Thanks!
Hi Chris,
No sound from the keyboard. I’ll get the logs for you tomorrow 
Hi Chris,
A correction wrt system sounds. The space bar does produce the standard Mac ‘blip’ sound but is usually delayed or the first few key presses don’t make any sound. It feels like it’s being buffered. This is particularly noticeable if I press one of the arrow keys a few times and then the space bar. Then it can take a few seconds before the blip sound.
The arrow keys also produce the system blip.
Logs - nothing shows on the screen but when I quit and restart I get the following:
Last login: Tue Apr 1 10:58:27 on ttys000
Filtering the log data using "subsystem == "com.supermegaultragroovy.capo.CapoRemoteControl""
Timestamp Thread Type Activity PID TTL
2025-04-01 10:59:10.694848+0100 0x69813b Info 0x0 34818 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:First-Time Initialization] First-time initialization already completed
2025-04-01 10:59:10.701299+0100 0x698129 Info 0x0 34818 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CapoRemoteCommandDispatcher] Bindings successfully initialized
2025-04-01 10:59:10.712348+0100 0x698129 Debug 0x0 34818 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CoreMIDIMessageProvider] Successfully created MIDI client
2025-04-01 10:59:10.756458+0100 0x698129 Debug 0x0 34818 0 Capo: (CapoRemoteControl) [com.supermegaultragroovy.capo.CapoRemoteControl:CoreMIDIMessageProvider] Successfully created MIDI input port
Regards,
James
OK, thanks for the confirmation. I’ve not yet determined why the keyboard events aren’t being fed into the remote system on your machines, and I might have to produce another build (maybe with updated log-gathering instructions) that spits out more debug information.
At the same time, I’m going to try and reproduce this on my test hardware [Update: My test machine is also not working!]. That should make this go much more quickly.
I have found the source of the error and released a new build (3090.1) that should now work correctly with keyboard bindings.
Keep an eye out for the release—once it passes through beta app review, you should get notified about the updated build.
Nice it’s working with the new version! 
