EP-133 PLAY and STOP respond late while connected to a computer
A common report: with the EP-133 K.O. II connected to a computer, STOP or PLAY takes effect seconds late, and the small computer icon on the display blinks. Without the computer it reacts at once. Here is what we measured on OS 2.5.1.
In short
After every read of a whole project, the EP-133 ignores its buttons for 3.0 seconds. Run backups and syncs while it is stopped, and turn off app features that read the project during playback.
What causes it
- Any app that reads whole projects should cause it: backups and project editors do, and the EP Sample Tool reads projects the same way (we haven't timed it there).
- Small status requests (which project and group are active, about 2 ms each, several a second) caused no delay.
- While a file transfer runs, hits on the pads are muted. The sequencer's own playback isn't: it keeps playing through a read.
- Notes sent from the computer to the EP-133 over MIDI aren't delayed by file traffic: we measured the same timing with and without reads.
What to do
- Transfer while stopped. Don't run backups, sample transfers or project syncs while you perform.
- Turn off live following. In any companion app, switch off features that read the project while the EP-133 plays (following knobs or patterns).
- Don't press twice. If STOP seems ignored, it isn't: it takes effect when the 3 seconds are over.
In Padwork
Since 5 November 2026 Padwork reads nothing while the EP-133 plays. A pattern you pick on the device shows after you press STOP.
For developers
Read each transfer back to back, to the end. We also measured that a pause of 20 ms between the pages of one read made the EP-133 stop answering and restart itself, and reading only some pages of a project showed ERR 820 and dropped the device off USB (both on OS 2.5.1).