That's the problem then. There is no way that a serial port sending ASCII codes can convey information about how long a key was pressed. I think a Leonardo could do it, because I believe it can emulate a USB PC keyboard, for which the up- and down-codes are sent separately.
Problem with that is that the Leonardo doesn't have enough analog pins.
Do you know how I can fix the issue where your code works flawlessly in the serial monitor but starts glitching when I turn on aac keys?
Not without using a Leonardo or other device that can emulate a keyboard that returns scan codes. How many analog inputs do you need, and why? The Leonardo has 12, and you can add more using an external ADC or analog multiplexer.
That's the problem then. There is no way that a serial port sending ASCII codes can convey information about how long a key was pressed. I think a Leonardo could do it, because I believe it can emulate a USB PC keyboard, for which the up- and down-codes are sent separately.
Problem with that is that the Leonardo doesn't have enough analog pins.
Do you know how I can fix the issue where your code works flawlessly in the serial monitor but starts glitching when I turn on aac keys?
Not without using a Leonardo or other device that can emulate a keyboard that returns scan codes. How many analog inputs do you need, and why? The Leonardo has 12, and you can add more using an external ADC or analog multiplexer.
I'm just wondering because it has that same issue when using it to print the letter a in a word document.
I need 13 analog pins. I want to go one full octave from c to c