I used to be an IT guy and have been using MIDI for nearly 40 years, but watching your video is the first time I really understand what is going there. Dave Smith and Kakehashi Ikutaro were geniuses!
This video repeatedly mentions "127" voices, or cc messages, etc. There are actually 128. 2^7. The 127 comes from the numbering system being 0-based, so the first is 0, second is 1... one-hundred twenty-eighth is 127.
You should also add about the amazing Running Status feature of MIDI. Where - as long as the data bytes are still for same status message & channel (example key on ch 1) , then each individual status bytes does not need to be repeated, just the key and velocity. Given that MIDI was only 31,250bit/sec (3125 bytes per second). This greatly improved the available bandwidth. Truely amazing what they managed to cram into the microprocessor tech of the day.
What a tremendous video, I’ve been a guitar player for many years, and recently started playing 80s and 90s synths. While I learned practically how to daisy chain them, I always wanted to know how each instrument “knew” which channel was which. Thanks so much!
Thanks for watching! It's wild, huh? I'm actually just editing a new video on MIDI system messages, to show the messages that you can send to your *entire* daisy-chained system. Stay tuned!
Beautiful video :) Moments like this make me appreciate RUclips SO much. Thanks for creating it and sharing. I've used MIDI for years, been programming for years, but never really understood MIDI and always wanted a quick video at an appropriate level to dive into the protocol. This is it!
Great video. Learned all kinds of little nuggets. Ended up subscribing and started watching the Pure Data Tutorials. I've been experimenting heavily with generative plugins, so understanding the "why" seems to be the next logical step. Keep it up.
Thanks for taking time to make this. At 01:34 I'm confused though: in a DAW you might have one track per instrument articulation (legato, staccato, pizzicato etc etc) so can easily hit 50-100 tracks for an orchestral piece which is way more than 16 channels. So how is this is situation normally managed? I appreciate there's the key switch method also.
Good question. DAW tracks and MIDI Channels are different. A DAW isn't limited in the number of tracks it can have (well, unless it's limited by the manufacturer), it's not limited by the number of channels the MIDI protocol can represent. The MIDI protocol, though, can only represent these 16 channels though, so a DAW sending to an external synth could only send 16 channels to that external synth along that MIDI cable.
Hi, what is the function of the "Song Select" midi command. Status byte F3 (hex), followed by 1 data byte ? If I sent this to a synth, would it start playing the specified song??
Best executive overview explanation for foundational midi on the Internet :) Wanting to write an app to accept CC data from a generic midi controller using python
Really great video man. I have been wondering exactly what midi protocol looks like for a while now. I have a project in my microcontrollers class using a PIC24 microcontroller and MPLABX, and I am strongly considering trying to work with some amount of MIDI protocol. If I don't use it then, I'm sure ill try building something with it sooner rather than later
Thank you for such a clear and easily-followed breakdown! This perfectly clarifies some of the lingering confusion I've been puzzling over since the '80s... ;)
i know Im asking the wrong place but does any of you know of a method to get back into an instagram account..? I was stupid forgot the login password. I would appreciate any tips you can offer me.
@Turner Everett thanks for your reply. I found the site thru google and Im trying it out now. Seems to take a while so I will reply here later when my account password hopefully is recovered.
Hi Simon, I came across your video while looking for ways to transcribe MIDI Messages through Image Inputs I was slightly interested in understanding if some other triggers could be used to encode these messages (such as the RGB Data, and equating it with similar data bytes in a way?) This may allow people to sonically experience photographs. I'd love to hear your views and take on this.
I'm not sure I completely understand your question, but, in short. You can convert all data (including MIDI data) into another kind of data (like RGB values). Check out more here - ruclips.net/video/NHufvylg0Vw/видео.html
You clarified some very essential concepts I wasn’t able to grasp from a bunch of other video explanations. And your slides were super helpful. Very grateful for your time and effort in putting this out. Thanks again.✨
Thank you my friend! We're LUCKY to have access to knowledge/explanations like yours. I have 1 question if anyone has time to clarify: ...Is this dual functioning of the Data Byte's 1st Bit correct? 1) '1'xxxnnnn designates it as a Status Byte as opposed to Data Byte, and 2) The '1xxx'nnnn portion specifies the kind of message we're sending, i.e noteOff(1000nnnn), noteOn(1001nnnn), Polyphonic Aftertouch(1010nnnn), Control Change(1011nnnn), Program Change(1100nnnn), Channel Aftertouch(1101nnnn), Pitch Bend Change(1110nnnn), or System Exclusive(1111nnnn) I ask because I want to be sure the first Bit of a Data Byte serves two purposes. EDIT: spelling
Thanks for your message. I'm not completely clear on your question here. Maybe you're saying "Data Byte" when you mean "Status Byte"? I'm not sure. I do have another video about the bits and bytes here, which might answer your questions: ruclips.net/video/Ll6L7o42I-s/видео.html
@@SimonHutchinson thanks for the quick response, and yes - I meant Status Byte where the MSB is '1'xxx nnnn... I watched your other video as well, and I think it answered my question. Thank you!
Thanks for your explanation! It's very useful for a project I have, do you recommend any video where they use assembly to transmit these midi packets (bytes) through USART to the computer (with an Arduino Uno ATMega328P uController, but using the assembly code instead of the more easy high level programming) to assign some keys (push buttons) to different things in the DAW's (FLStudio, Ableton, whatever)? Because I found many videos they do this but with the C-like code that uses Arduino, importing libraries, I tried to debug the libraries themselves, but I did not find a good explanation of the bytes sent, as you did in this video, I saw the Note on and stuff but it was not that clear. Thanks in advance if you know some source! If not anyway thanks for the video is very clear ^^!
This is really a wonderful video. I have not found any video about MIDI with such a clear explanation as yours. It's really helped to systemes the bits and pieces of knowledge about MIDI that I had!
Hi Simon thanks tons for your videos ! can you tell me what using an inputhandler call back does that is different from the standard way midi apps handle inbound messages? - can you pretend I'm dumb as shit and explain accordingly because I don't get it at all? Thanks!
Hello Simon! I have one question about the 1111nnnn status bytes. I've read that some sustain pedals will only work to their full capabilities only with keyboards of the same brand. Could the be due to the use of this "1111" data? And, if so, could manufacturer data be "replicated" to make a keyboard believe a pedal is from its brand?
I don't think that's correct. Sustain pedals are supposed to be Control Change Messages on controller number 64. So they shouldn't have much to do with System Messages or the brand of the pedal/keyboard. en.wikipedia.org/wiki/General_MIDI#Controller_events
@@SimonHutchinson and could it also send that kind of data let's say in the first press? Another thing that confuses me is how sustain pedals use Jack audio cables as MIDI data cables.
@@SimonHutchinson Thank you! If you had the MIDI channel but wanted to work out the binary NNNN would you just have to look at the diagram or is there a formula you could use to work it out?
@@benparamoresound338 if you are using a programming language to get the channel from a byte, you can just do a byte AND 16 to mask off the rest of the bits to be 0. The remaining number is between 0-15, if you add 1 its the channel number between 1-16. Hope thats helpful
Super explanation but please leave out the music :( Although I really like weirdly sequenced ambient wavetable stuff, this makes it a bit hard to follow. But this may be my ADHD kicking in, so what do I know... Anyways, finally a clean explanation of MIDI I was waiting for for years haha
I used to be an IT guy and have been using MIDI for nearly 40 years, but watching your video is the first time I really understand what is going there. Dave Smith and Kakehashi Ikutaro were geniuses!
😆 I have a slide that I show to my class that just says “MIDI is Awesome”.
This video repeatedly mentions "127" voices, or cc messages, etc. There are actually 128. 2^7. The 127 comes from the numbering system being 0-based, so the first is 0, second is 1... one-hundred twenty-eighth is 127.
ruclips.net/video/Ll6L7o42I-s/видео.html
THE clearest explanation of MIDI protocol I've found yet!!! Thank you!!!!🙌🏾
Happy to hear it! Glad it was helpful!
Notes and Volts does a good job explaining it too.
I 100% agree. You have a gift. Glad I found your channel.
Awesome breakdown of digital elements of MIDI.
Clear and straightforward, no additional b...hits, exactly what I needed and was looking for. Thank you!
The design of midi was very forward thinking, it's 40 years old and still as useful today as ever! Thanks, great video 👍😎❤️
Thank you! Could you make a video about System messages?
Great suggestion!
You should also add about the amazing Running Status feature of MIDI. Where - as long as the data bytes are still for same status message & channel (example key on ch 1) , then each individual status bytes does not need to be repeated, just the key and velocity. Given that MIDI was only 31,250bit/sec (3125 bytes per second). This greatly improved the available bandwidth.
Truely amazing what they managed to cram into the microprocessor tech of the day.
This should have way more views! Leaned a lot from this, thanks!
Thanks! I appreciate it!
What a tremendous video, I’ve been a guitar player for many years, and recently started playing 80s and 90s synths. While I learned practically how to daisy chain them, I always wanted to know how each instrument “knew” which channel was which. Thanks so much!
Thanks for watching! It's wild, huh? I'm actually just editing a new video on MIDI system messages, to show the messages that you can send to your *entire* daisy-chained system. Stay tuned!
Awsome!!!
Thank you! Greatly appreciated!
Great info. Thx so much!
Glad it was helpful!
So, 2 to the 14th.. I'm not going to go through it :D
Beautiful video :) Moments like this make me appreciate RUclips SO much. Thanks for creating it and sharing. I've used MIDI for years, been programming for years, but never really understood MIDI and always wanted a quick video at an appropriate level to dive into the protocol. This is it!
Thanks so much for your kind comment! I appreciate it!
Great video. Learned all kinds of little nuggets. Ended up subscribing and started watching the Pure Data Tutorials. I've been experimenting heavily with generative plugins, so understanding the "why" seems to be the next logical step. Keep it up.
Thanks! Welcome!
Thanks for this! Very clear and helpful.
Thanks for taking time to make this. At 01:34 I'm confused though: in a DAW you might have one track per instrument articulation (legato, staccato, pizzicato etc etc) so can easily hit 50-100 tracks for an orchestral piece which is way more than 16 channels. So how is this is situation normally managed? I appreciate there's the key switch method also.
Good question. DAW tracks and MIDI Channels are different. A DAW isn't limited in the number of tracks it can have (well, unless it's limited by the manufacturer), it's not limited by the number of channels the MIDI protocol can represent. The MIDI protocol, though, can only represent these 16 channels though, so a DAW sending to an external synth could only send 16 channels to that external synth along that MIDI cable.
This channel is a gem for mathematically inclined and detail oriented folks like me
Awesome thanks a lot!
You're welcome!
Hi, what is the function of the "Song Select" midi command. Status byte F3 (hex), followed by 1 data byte ? If I sent this to a synth, would it start playing the specified song??
Check this out (timestamped link): ruclips.net/video/y5Sah0bJYkg/видео.htmlsi=PtGPPO2dvYavDutc&t=308
Best executive overview explanation for foundational midi on the Internet :)
Wanting to write an app to accept CC data from a generic midi controller using python
this was great, thank you!
Well done ! Thanks !
Really great video man. I have been wondering exactly what midi protocol looks like for a while now. I have a project in my microcontrollers class using a PIC24 microcontroller and MPLABX, and I am strongly considering trying to work with some amount of MIDI protocol. If I don't use it then, I'm sure ill try building something with it sooner rather than later
Just preparing my exam right here, my course was unclear and I needed to look for a visual explanation, you helped me a lot! Thank you so much!
Glad it helped! Good luck on your exam!
Super video 🙂👍
nice
Thank you for such a clear and easily-followed breakdown!
This perfectly clarifies some of the lingering confusion I've been puzzling over since the '80s... ;)
Glad it was helpful! The 80s, huh? The good news is it's not too late to finish up work on that synthwave album!
@@SimonHutchinson My trusty MSQ-700 cannot help but agree... :)
i know Im asking the wrong place but does any of you know of a method to get back into an instagram account..?
I was stupid forgot the login password. I would appreciate any tips you can offer me.
@Salvador Madden instablaster =)
@Turner Everett thanks for your reply. I found the site thru google and Im trying it out now.
Seems to take a while so I will reply here later when my account password hopefully is recovered.
best explanation on YT, THANKS!!
Super helpful video man. MIDI is such a fascinating and helpful tool.
Glad it was helpful!
Hi Simon,
I came across your video while looking for ways to transcribe MIDI Messages through Image Inputs
I was slightly interested in understanding if some other triggers could be used to encode these messages (such as the RGB Data, and equating it with similar data bytes in a way?)
This may allow people to sonically experience photographs.
I'd love to hear your views and take on this.
I'm not sure I completely understand your question, but, in short. You can convert all data (including MIDI data) into another kind of data (like RGB values). Check out more here - ruclips.net/video/NHufvylg0Vw/видео.html
Very well explained, thanks!
Glad it was helpful!
Thank you so much🥁💥
You clarified some very essential concepts I wasn’t able to grasp from a bunch of other video explanations. And your slides were super helpful. Very grateful for your time and effort in putting this out. Thanks again.✨
+1 SUBCRIPTION!!!
Thank you!
Please turn off the background music
Thank you my friend! We're LUCKY to have access to knowledge/explanations like yours. I have 1 question if anyone has time to clarify:
...Is this dual functioning of the Data Byte's 1st Bit correct?
1) '1'xxxnnnn designates it as a Status Byte as opposed to Data Byte, and
2) The '1xxx'nnnn portion specifies the kind of message we're sending, i.e noteOff(1000nnnn),
noteOn(1001nnnn), Polyphonic Aftertouch(1010nnnn), Control Change(1011nnnn), Program
Change(1100nnnn), Channel Aftertouch(1101nnnn), Pitch Bend Change(1110nnnn), or System
Exclusive(1111nnnn)
I ask because I want to be sure the first Bit of a Data Byte serves two purposes.
EDIT: spelling
Thanks for your message. I'm not completely clear on your question here. Maybe you're saying "Data Byte" when you mean "Status Byte"? I'm not sure. I do have another video about the bits and bytes here, which might answer your questions: ruclips.net/video/Ll6L7o42I-s/видео.html
@@SimonHutchinson thanks for the quick response, and yes - I meant Status Byte where the MSB is '1'xxx nnnn... I watched your other video as well, and I think it answered my question. Thank you!
How to get revive MIDI data ??
Nicee, this rocks! Was always wondering on how it works in the context I understand :D
Thanks! Glad to hear it was helpful!
Thanks for your explanation! It's very useful for a project I have, do you recommend any video where they use assembly to transmit these midi packets (bytes) through USART to the computer (with an Arduino Uno ATMega328P uController, but using the assembly code instead of the more easy high level programming) to assign some keys (push buttons) to different things in the DAW's (FLStudio, Ableton, whatever)? Because I found many videos they do this but with the C-like code that uses Arduino, importing libraries, I tried to debug the libraries themselves, but I did not find a good explanation of the bytes sent, as you did in this video, I saw the Note on and stuff but it was not that clear. Thanks in advance if you know some source! If not anyway thanks for the video is very clear ^^!
This is really a wonderful video. I have not found any video about MIDI with such a clear explanation as yours. It's really helped to systemes the bits and pieces of knowledge about MIDI that I had!
You're very welcome! Glad it was helpful!
Thanks to this. Well explained! You got a new subscriber.
Welcome aboard!
Hi Simon thanks tons for your videos ! can you tell me what using an inputhandler call back does that is different from the standard way midi apps handle inbound messages? - can you pretend I'm dumb as shit and explain accordingly because I don't get it at all? Thanks!
great video! helped me a lot :)
Glad to hear it!
Hello Simon! I have one question about the 1111nnnn status bytes. I've read that some sustain pedals will only work to their full capabilities only with keyboards of the same brand. Could the be due to the use of this "1111" data?
And, if so, could manufacturer data be "replicated" to make a keyboard believe a pedal is from its brand?
I don't think that's correct. Sustain pedals are supposed to be Control Change Messages on controller number 64. So they shouldn't have much to do with System Messages or the brand of the pedal/keyboard.
en.wikipedia.org/wiki/General_MIDI#Controller_events
@@SimonHutchinson and could it also send that kind of data let's say in the first press? Another thing that confuses me is how sustain pedals use Jack audio cables as MIDI data cables.
The pedal connects to the keyboard (analog) electrically with a 1/4 jack, and the keyboard is what converts that cable into MIDI.
I need your big brain a second! How do you work out MIDI channels from a Byte? Is there a calculation you can use or a formula?
So, the status byte is 8 bits: 1 (Status byte marker), XXX (Type of MIDI Message), NNNN (MIDI Channel).
Look at the NNNN. If it's
0000 - MIDI Channel 1
0001 - MIDI Channel 2
0010 - MIDI Channel 3
0011 - MIDI Channel 4
0100 - MIDI Channel 5
0101 - MIDI Channel 6
0110 - MIDI Channel 7
0111 - MIDI Channel 8
1000 - MIDI Channel 9
1001 - MIDI Channel 10
1010 - MIDI Channel 11
1011 - MIDI Channel 12
1100 - MIDI Channel 13
1101 - MIDI Channel 14
1110 - MIDI Channel 15
1111 - MIDI Channel 16
... I think I got that right.
@@SimonHutchinson Thank you! If you had the MIDI channel but wanted to work out the binary NNNN would you just have to look at the diagram or is there a formula you could use to work it out?
@@benparamoresound338 if you are using a programming language to get the channel from a byte, you can just do a byte AND 16 to mask off the rest of the bits to be 0. The remaining number is between 0-15, if you add 1 its the channel number between 1-16. Hope thats helpful
Super explanation but please leave out the music :(
Although I really like weirdly sequenced ambient wavetable stuff, this makes it a bit hard to follow. But this may be my ADHD kicking in, so what do I know...
Anyways, finally a clean explanation of MIDI I was waiting for for years haha
This is so fucking confusing 😕
Ha! Sorry! There are lots of resources on MIDI out there, though. I hope you can find one that resonates with you.
Confusing!? This has to be one of the most simple protocols I have encountered in my live!
Wonderful explanation!!!
What about bank change? Did you miss this one or its something different?
www.sweetwater.com/sweetcare/articles/6-what-msb-lsb-refer-for-changing-banks-andprograms/