# GATE Sequencer suggestions **URL:** \ **Category:** DIY STUFF\ **Created:** [December 6, 2021, 2:01am UTC](https://lookmumnocomputer.discourse.group/t/gate-sequencer-suggestions/4342 "2021-12-06T02:01:09Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![analogoutput](https://yyz2.discourse-cdn.com/free1/user_avatar/lookmumnocomputer.discourse.group/analogoutput/32/29663_2.png) [@analogoutput](https://lookmumnocomputer.discourse.group/u/analogoutput)\ **Post date:** [December 6, 2021, 3:30pm UTC](https://lookmumnocomputer.discourse.group/t/gate-sequencer-suggestions/4342/5 "2021-12-06T15:30:58Z")
> [@Plop](#): > > Atmega’s (Arduino) are quite slow and only have one core so it’s not that good for sequencing and reading input in the same time, but bluepills or teensy are some good choice I’ve had my Nano based [G.E.A.R. sequencer](https://lookmumnocomputer.discourse.group/t/ao-g-e-a-r-sequencer-rhythm-generator/4332) running at up to a few hundred Hz clock speed — and it wasn’t maxing out then, although that was before I added some software switch debouncing that would limit that. I wasn’t working the controls in that test, so it didn’t have to process input and display it on the OLED, but it was reading five analog pins on each loop. Interrupts are used to handle clock events. Earlier I’d found the user interface bogging down the sequencer speed, but that was before I made some software improvements. In particular I ditched digitalRead and digitalWrite in favor of the DirectIO library and that seemed to make an improvement. --- _[View the full topic](https://lookmumnocomputer.discourse.group/t/gate-sequencer-suggestions/4342)._