Your descriptions of your code and the ideas behind it were very clear and well laid out. I appreciate you taking the time to make this video, which in itself is no small thing. Since I know very little about the mechanics of woodwind instruments I'm finding your content on them fascinating. Keep up the great work!
I did promise a part 2, didn't I? 😐 There's a lot of stuff going on in the lab besides UA-cam, so some things get put on the back burner, sorry. My plan for the next code class hasn't changed, but this kind of video is basically the most workload intensive of everything on the channel, so I'll get to it once I resolve about 50 other things. 😅 Appreciate your comments though, thanks for the support 🙏
Yes it's possible. Lots of conceptual, mechanical etc issues to solve, but it can be done. I don't have any plans to make one, but you should give it a try!
@@guilhermedagaita675 Sure. The Teensy is great, because it's easy to make capacitive keys, but use whatever microcontroller you have. If you can make it, then you can make it without the Teensy
I have been experimenting with capacitive touch sensing on the arduinos sadly I haven’t been able to get it working on the Micro (which is the only one small enough to fit on a breadboard) but I have been able to get it working on the Leonardo, Uno, and Mega. Still it is in no way easy or “built in” like it is in the teensy. I like building my own keys from scratch to emulate playing a real woodwind and for that I can really just make push buttons from copper tape and pen springs.
I want to build a digital concertina - complete novice when it comes to Arduino and MIDI, but I'm going to give it a shot - what kit should I start with?
Hi Johan. I think the Teensy is one of the best Arduino compatible options for making instruments, so start with one of those. Of course you'll still have to figure out everything else you need for the concertina. Quite a project!
Cool to see how you've done this, and how I've ended up doing the same thing in a different way! I've got all the key combinations that make a note stored in an array, where each combo is {pitch, pressed, not_pressed}. "pressed" is the keys which must be pressed for this note, and "not pressed" is the keys which must not be. Each of those is a 16-bit binary value, e.g. 0b0000000000000001 would mean only the last button is pressed. That's handy because it means I can represent the state of up to 16 buttons with just one number. I'm not sure whether it's more or less readable than your way though! I then just iterate through all the note combinations, and check whether the pressed and unpressed keys match, using a single bitwise AND operation for each. I think it's quite neat but it's definitely harder to explain. Let me know if you'd like to see the code - I don't think I can post a link in a youtube comment.
Hi George. Nice! :) Thanks for sharing. I’ve talked to other people as well, who have independently ended up with something quite similar. It’s like I say in the video, that’s just how woodwind keys work. Whether your binary way is more or less neat than mine, I can’t say. But I suspect that it executes faster, while being harder for an outsider to read. Readability was certainly an important point for me while putting this together, and speed isn’t really a concern with a Teensy board at this level of complexity. The important question then becomes, “what’s the mental process for defining each array?” Deciding which keys absolutely have to be “not pressed” and which can be safely ignored can have important consequences when playing. I’ll get into this more in the next “Woodwind Algorithm” video. And there’s a whole other dimension of possibilities to this, which I explored long ago with my original Open Horn MIDI system, which is to use those “ignored” keys to apply effects like timbral distortion, or microtonal adjustments, like you sometimes get with acoustic instruments. In my code this introduces a third “keyPhase”, and it hugely complicates things, but I might get back to it at some point.
Your descriptions of your code and the ideas behind it were very clear and well laid out. I appreciate you taking the time to make this video, which in itself is no small thing. Since I know very little about the mechanics of woodwind instruments I'm finding your content on them fascinating. Keep up the great work!
Thanks Jeff. Much appreciated!
I don’t mean to come across as urgent, or impatient, but I would LOVE to see more of these code class videos 🥹🥹🥹🥹🥹
I did promise a part 2, didn't I? 😐 There's a lot of stuff going on in the lab besides UA-cam, so some things get put on the back burner, sorry. My plan for the next code class hasn't changed, but this kind of video is basically the most workload intensive of everything on the channel, so I'll get to it once I resolve about 50 other things. 😅
Appreciate your comments though, thanks for the support 🙏
Is possible,make a accordion with air sensor and Teensy?
Yes it's possible. Lots of conceptual, mechanical etc issues to solve, but it can be done. I don't have any plans to make one, but you should give it a try!
Thank you!But,i can make without teensy?
@@guilhermedagaita675 Sure. The Teensy is great, because it's easy to make capacitive keys, but use whatever microcontroller you have. If you can make it, then you can make it without the Teensy
I have been experimenting with capacitive touch sensing on the arduinos sadly I haven’t been able to get it working on the Micro (which is the only one small enough to fit on a breadboard) but I have been able to get it working on the Leonardo, Uno, and Mega. Still it is in no way easy or “built in” like it is in the teensy. I like building my own keys from scratch to emulate playing a real woodwind and for that I can really just make push buttons from copper tape and pen springs.
I want to build a digital concertina - complete novice when it comes to Arduino and MIDI, but I'm going to give it a shot - what kit should I start with?
Hi Johan. I think the Teensy is one of the best Arduino compatible options for making instruments, so start with one of those. Of course you'll still have to figure out everything else you need for the concertina. Quite a project!
Cool to see how you've done this, and how I've ended up doing the same thing in a different way!
I've got all the key combinations that make a note stored in an array, where each combo is {pitch, pressed, not_pressed}. "pressed" is the keys which must be pressed for this note, and "not pressed" is the keys which must not be. Each of those is a 16-bit binary value, e.g. 0b0000000000000001 would mean only the last button is pressed.
That's handy because it means I can represent the state of up to 16 buttons with just one number. I'm not sure whether it's more or less readable than your way though!
I then just iterate through all the note combinations, and check whether the pressed and unpressed keys match, using a single bitwise AND operation for each. I think it's quite neat but it's definitely harder to explain. Let me know if you'd like to see the code - I don't think I can post a link in a youtube comment.
Hi George.
Nice! :) Thanks for sharing.
I’ve talked to other people as well, who have independently ended up with something quite similar. It’s like I say in the video, that’s just how woodwind keys work. Whether your binary way is more or less neat than mine, I can’t say. But I suspect that it executes faster, while being harder for an outsider to read. Readability was certainly an important point for me while putting this together, and speed isn’t really a concern with a Teensy board at this level of complexity.
The important question then becomes, “what’s the mental process for defining each array?” Deciding which keys absolutely have to be “not pressed” and which can be safely ignored can have important consequences when playing. I’ll get into this more in the next “Woodwind Algorithm” video.
And there’s a whole other dimension of possibilities to this, which I explored long ago with my original Open Horn MIDI system, which is to use those “ignored” keys to apply effects like timbral distortion, or microtonal adjustments, like you sometimes get with acoustic instruments. In my code this introduces a third “keyPhase”, and it hugely complicates things, but I might get back to it at some point.