SUPER SIMPLE MIDI KEYBOARD DIY HOW TO 

Yes but also he could have made it a bit easier to remap later by assigning his channels and notes and velocities in variables before running the variables into the midi function.

agreed....ARDUINO FOR DUMMIES!! love it.

I know yall know he isnt an idiot and probably knows more about coding than he lets on....which is brilliant, really, considering he ends up making entertaining for everyone watching.

this bippity bop and this swirly thing 😂😂

it is ugly! hs but you know tried tomake it make sense like lego mindstorms ha

@@LOOKMUMNOCOMPUTER You're like a mad scientist without a dictionary. If you get the stuff done, it doesn't matter. Comments are great if you can remember them. Some of the functions are pretty intuitive. I don't know this program AT ALL, but took C++ back in the day, so I'm looking at the code and thinking, "oh yeah, this makes sense, I can read it!"

@@LOOKMUMNOCOMPUTER if you have a midi keyboard like the one you showed first if its already broken some keys couldnt you take all the guts out and build a interface like this and weld a button to each of the key you want.. and you can keep the faders and rotary aswell just change to another enclosure

@@fullfunk you could. Quite a faff but you should give it a go!

I dunno the names he gave them made sense to me

yeah!!! im glad newer products are ditching the midi over mini jacks and going back to 5 pin din! the mini jack midi is awful haha

@@LOOKMUMNOCOMPUTER nothing wrong with the mini jack, but they are asking like 20€ for (... or something around that) for a original Arturia jack to din converter. than the fact you can loose it.

They even made a nice MIDI 2.0 version in 2020 with better resolution and nice new options but keeping it backwards compatible with the old MIDI. I love these guys, nice simple standard without the BS.

I did basically this same kind of project with a set of organ pedals many years ago and found something interesting. I always wondered why the MIDI serial port rate was 31,250 baud - kind of a weird number. More typical would be 9600,19200, 38400... turns out 31,250 is the fastest baud rate you can send from a 20MHz 8051 (which is what I was using for my project). So I'm betting that is the original processor they used for the prototypes :)

@@VAXHeadroom that would mean they divided 20mHz by 640, not accounting for start and stop bit. but 640 is still a multiple of 10 and 8.

I'm a beginner straight up clueless. This man taught me a lot thanks dude.

Nice call. Also good for 8ve shifts

He would make a good teacher. (This coming from a Swedish/English teacher for senior high school in Sweden.)

he is coding in a potato, i am pretty sure of that =p

i have a qestion . Will be this program good when i want use it as midi for FL studio but i want use usb cabel for conect it?

@@adambalaz4833 you can send midi over serial and convert it on the computer side with midi loopback driver

I was literally *just* about to buy a Midi Fighter today, and then spotted this video. The coding was the part that intimidated me about going diy, but after seeing this I think I'll give it a shot.

The main weapon of the Spanish Inquisition.... :D

Kosmo

TB-303

Another lovely Jubbley project. I have been following you since around 2016 I believe and your stuff is getting more amazing all the time. Thank you for your mad scientist contributions; your work is highly inspiring and appreciated. Just wanted to take a moment to say keep up the good work!

Atari ST

An Arduino

Probably easier to use a load of I2C port expanders, you can put 4 or 8 on the bus depending on how many address channels they have and if you have a MEGA they have multiple I2C ports.

come visit the forum linked on the project page in the description! We can help.

He can make an input array and a midi notes array, or he can define the input int range and the range of the midi notes, or he can define the base offset between the input numbers and the notes.. Out there is a principle called KISS

Except that #define is super risky to use, if you accidentally use the defined string as part of another string it will still replace it. For example: if you do #define a 1, and then write digitalRead();, it will be interpreted as digit1lRe1d(); const gets compiled perfectly and does not take up more memory than #define, so go for const. And more importantly: int is fine for beginners. use int.

​@@DanielSimu Well, technically that's true, But if you use a more descriptive name than "a", something you should do anyway, it's just very unlikely that this will happen. And correct me if I'm wrong here, but the difference in memory use is that variables, const or not, are stored in RAM and literals, what preprocessor directives eventually become, won't. Every time you use a literal (as long as the number is small enough for a single word data type), it's taking up one word in flash and every time you're referencing a variable, the address also takes up one word in flash. So that's basically the same. So it depends on the question if you're running short on RAM while it won't help you much when you're running short on flash. Of course, that won't be much, but that's why I wrote it won't be a problem in smaller projects, so as you say, it's not a problem for beginners, but even beginners should start to learn good habits instead of unlearning what they've learned later. Even when I don't think about why this makes sense, I just look at how preprocessor directives are all over the place in Arduino itself at that they probably did it for a reason.

@@asp95video Yes, "keep it simple, stupid", but I don't see how using preprocessor directives isn't as simple using variables. Using arrays might be the more elegant solution, but my comment was more about variables vs preprocessor directives in general than about this particular case.

@@juschu85 Feel free to keep on using #define, but I disagree that it is unlikely to happen. For example, in this video there was an int button1 and an int button1beans, if the first had been #define button1 you would have gotten issues with the second. On a recent memory limit approaching project I had a look at replacing all the consts with #define just to test, and the arduino compiler showed no difference, the sizes were exactly the same. Why would the compiler treat a const differently anyway?

I have found "ternary operators" are incredibly useful to remove annoying "if" statements, as it sets up a "true" / "false" argument that puts everything on one line. ? : ; I haven't tried it but would this code work? (digitalRead(button1) == HIGH) ? (MIDI.sendNoteOn(36,127,1) : (MIDI.sendNoteOff(36,127,1);

Aaah I remember us talking about you messing about with midi!

@@LOOKMUMNOCOMPUTER cheers Sam, great gig :) I have a denshi block kit in the garage somewhere that I’d like to donate to the museum. Will take a trip over when you’re open later this year. I remember most of those everyday electronics issues :) think I threw the mags away though.

ditto!

ofcourse, but almost everything has a resistor that has not been made by me so its ok haha. to be honest i usually never bother with opto couplers on the midi inputs haha. its just a digital signal stream, i have not come up an issue yet. obviously there can be issues but works for me :D. and when imake proper midi things i include optocouplers, but most of the time i just wire straight to midi socket on each sides

Yeah I was thinking the same. Agree you may not need it if you're just bodging your own projects together, but the issue here is that if you were to plug this into some proper synth you may blow up the optocoupler inside it if you exceed the max current of the LED :D.

​@@LOOKMUMNOCOMPUTER I agree that for my own circuits, I often don't do "MIDI at the electrical layer" and just connect RX to TX on microcontrollers, and just "MIDI at the software/protocol layer", but as this is being called a MIDI keyboard and has a 5-pin DIN socket it looks for all outward purposes to be for connecting to other equipment, so isn't there a real chance of overloading an input circuit with no resistors? I think the issue is that the MIDI spec works on the basis of assuming a 5mA current loop, and the circuits suggest three resistors to get it - two on the output side, one on the input side. I am not an electronics person, but as I understand things, with an Arduino driving a MIDI circuit at 5V, using two 220 resistors on MIDI out and one 220 on MIDI in (at the other end) gives you 5/660 = 7.5mA (well it will be less as I've not included the diode Vf). But with no resistors in the MIDI out and just the one on the MIDI in, the current is 5/220 = 23mA (again actually less) but is four times higher than the MIDI spec says is required. Some opto-isolators on input circuits will be fine with this (the H11L1 for example has an input current limit of 60mA I believe). However some might be marginal, the commonly used 6N138 might have an input current limit of just 20mA, so any more would strictly speaking be too much for it. As with many things, I'm sure there is margin for error and you'd hope expensive equipment has input protections, so it may be fine. And I'm sure it isn't as simple as I'm saying here anyway (as I say, I'm not an electronics person and there are voltage drops involved across the diodes and things too). I often leave out the suggested buffers on outputs, but for the cost and effort of soldering in two resistors, why take that risk? Or at least, don't call it MIDI or use a 5-pin DIN socket, as a reminder to your future self? Kevin

@@SimpleDIYElectroMusicProjects sure I’ll add a disclaimer to the site and the project. But the margin for error is pretty chunky. Having done this a lot plugging into things I haven’t had any bad experiences but then again maybe that’s luck. A 6n138 for me has been fine for a lot above that. I mean in one project.. the drum trigger sequencer there are no resistors at all anywhere technically it would have burnt out years ago but going strong haha. I probably won’t change my behaviour towards it but I’ll mention it on the project page.

@@rjgscotland as said to the other commenter I will add a note on the site about this.

Yeah al good tbh I was being lazy: I haven’t bothered so if someone is protective of their synth and I’m around with a midi controller I made don’t let me plug it in ha. I added 220r on the pic on the site when the vid went up al good

@@LOOKMUMNOCOMPUTER Excellent, man! Love all the hacky stuff to bits, just wanted to make sure nobody's equipment would get hurt.

What is it about people striving towards effficient code on simple stuff. It’s not like that in electronics

No doubt it can be but it’s written like that to make sense to people who aren’t one hand in doritos the other hacking the mainframe ha