Wonderfull !! I love the way you explain all that ! Hope you will talk one day about a midi controlleur with force sensitive button (commercial or diy) for sending differents velocities in real time
Oi Gustavo! I find your YT channel very interesting and inspiring - thanks for the tutorials! I’m considering building 8 octave midi keyboard for GarageBand using Arduino Leonardo and 6 multiplexers. Could You be so kind to prepare tutorial on multiplexers in your MIDI Program for the Arduino series?
May I suggest an idea for a video..? You could take an existing device like a Volca Drum, Mother 32, or any other well documented device that has midi-in, and show the process of mapping a DIY controller to a spec given by the manufacturer. I think this would be so super valuable to your community (and yes I ask selfishly as I am trying to do this currently and having issues lol). Just a thought, keep up the great work ;)
I noticed something in your example Serial testing display 31:43 The first time we click a new button, it doesn't register the "on" but it does register the first "off" signal. Then after the first time a button is pressed, both "on" and "off" register. My tests have the same behavior. EDIT: I tested with pin 13 led and initial button press doesn't turn on the LED. I set the debounceDelay = 0 and the error went away. I'll work on a solution and post here when done.
OK the solution I came up with (with chatgpt help) is to add a bool so first press is always true and bypasses the debounce delay restriction. I did this by // First, I adding // Track if it's the first press bool *firstPress; //Next, under the void setup I added // Make firstPress recognize all buttons firstPress = new bool[N_BUTTONS]; for (int i = 0; i < N_BUTTONS; i++) { firstPress[i] = true; } // Finally, at the end of the void loop I added // Set first press to false after the first press firstPress[i] = false; Thoughts??
Actually I think it's a bug not related to the deboucing parameter but to the fact that he initialize buttonState and buttonPState both with 0. The way he set things up, the first time you press the buttons, the condition buttonState != buttonPState will always be false, hence the code is skipped.
É uma pena que nos vídeos você não precise traduzir para o espanhol, compre o curso e não tenha a opção....... It is a pity that in the videos you do not have to translate into Spanish, buy the course and you do not have the option
