12 ms·
How will MIDI 2.0 change music? (2020)
- prox 5y agoOf all technologies, I believe MIDI has been the most plug and play experience for me. Plug a midi cable in, boot up a sequencer and you are good to go. Really interesting to see what can be done with MIDI 2.0
- wtfrmyinitials 5y agoI was trying to write a program using midi last year and was surprised by the lack of any libraries to work with it. Then I looked up the spec and was able to get all the functionality I needed with 10 lines of code interacting with /dev/midi. Incredible how powerful such a simple interface is.
- deleted 5y ago[deleted]
- throw_m239339 5y agoThat's all good up until you try to synchronize different MIDI devices with their own sequencers. Even "voltage triggering" is more accurate...
- em3rgent0rdr 5y agohave you tried using https://en.wikipedia.org/wiki/MIDI_beat_clock https://en.wikipedia.org/wiki/MIDI_beat_clock
- TheOtherHobbes 5y agoThe clock is not very accurate and devices have to interpolate it. Which is something they all do slightly differently, especially if the tempo changes - which doesn't happen much in pop, but happens regularly in media composition. If you're lucky the result will be in-time-ish, but it's never going to be sample accurate. This actually matters for some applications, including sound design. If you trigger two samples with a variable offset you can get phase cancellation and other easily audible effects. DAWs are sample accurate now, but 5-pin DIN MIDI 1.0 really isn't.
- em3rgent0rdr 5y agoMidi can plug-and-play so easily because there is no handshaking. Every midi capable device has already agreed upon the 31,250 serial baudrate and 8-bit data + 1 stopbit format and the commands. The only occasional problem I'll experience with midi is if I unplug before sending a note-off for a note, then that note might forever be stuck on.
- romwell 5y agoAnd even that is not really a protocol problem. It's trivial for a device to implement "reset-on-disconnect".
- squarefoot 5y agoThe problem is that there is no such thing as a disconnect signal, so a device can't know a cable has been pulled or something in between has been powered off; if it happens then the device is left hanging with a note on, and one must find a way to send the relevant note off or the all notes off message when communication is restored. Adding such controls (aside the simple reading of the current loop value that doesn't solve all problems) would require one more layer which would translate in more complexity and more latency. If I had to implement such things on top of an improved protocol, I would likely also ditch the serial link, ignore completely USB, and jump straight to Ethernet, which is damn fast, near realtime, supported pretty much everywhere (Ethernet switches would essentially work as MIDI Thru boxes) and free of royalties. Devices in the same local network wouldn't even need the transport and above layers to work, so latencies would be extremely low, but adding more IP stack layers would allow to remote things easily.
- romwell 5y ago>There is no such thing as a disconnect signal Incorrect :) MIDI OUT provides power. No power = disconnect. That's not to mention that you don't need a signal for *physical disconnect Your stereo knows when you unplug headphones.
- 5y ago
- romwell 5y agoAs long as it's 100% backwards compatible, including the 5-pin DIN connectors, I'd be on board. No 5-pin, no game. More on this below. ---------------------- USB midi is one of the worst thing that happened to MIDI. If I have a synth with USB midi and a controller with USB midi, I can't connect them to each other, which is idiotic and frustrating. The original MIDI spec had its drawbacks, but the biggest have been addressed by MPE. As for latency, jitter, granularity — as a gigging musician and producer, I've never had any issue with it. It's good enough. And most of the music you hear today is a reflection of that. What's not good, it's that some manufacturers are ditching the 5-pin MIDI jack for USB or Bluetooth. Thanks, nobody asked. Same for losing the THRU port. Because what musicians love is setting up their computer on stage while everyone is waiting, right? Bidirectionality with MIDI can be achived by replacing the dual 5-pin MIDI with the mini-DIN (yes, the same connector the old PS/2 mouse used). Yamaha Tenori-On and and Reface series do that (though again, nobody asked). And the entire NRPN space of MIDI is unused because it's unstandardized. So simply agreeing on how MIDI 1.0 should be used would address most of the problems that MIDI 2.0 claims to solve. That's what MPE does, by the way, and that's why it has been silently becoming the de-facto standard. The examples I see in promotional videos show a computer talking to MIDI 2.0 devices. We've had enough of that. What made MIDI 1.0 work is the simplicity of device-to-device connectivity, regardless of what the devices are (and whether one of them is a PC). Think of this magic: if I have just ONE type of cable, I can connect ANY device to ANY OTHER device. That means my Yamaha MX-88 I bought new last year can talk to Korg Poly-800 made before I was born. I could have bought the cable in the 80s or yesterday, it's the same cable. What MIDI 1.0 gave people is less thinking about how to connect devices, and more about making music. USB midi did the same thing for devices connected to a computer, at the expense of being usable in a setup that does not have a computer. That implicit assumption — that everything will involve a computer — was flawed. WTF, I want to use my ROLI to play my Yamaha — and I can't, because ROLI is too "modern" to talk to any hardware synth made the same year. I hope that MIDI 2.0 avoids this fuckery, but I can't tell yet. Bidirectionality looks sus. My litmus test is: if a device doesn't come with a 5-pin MIDI jack while having space for it, it's a gimmick (Teenage Engineering being an exception, because they make up for it with analog control: my pocket operators sync with my Korg Monologue via pulse, and Korg syncs with Yamaha over 5-pin MIDI). And if Korg Volca could do it, so can pretty much everything else (hint: don't put it on the side, put it on the front panel if you want that slim look). MIDI 2.0 can be a huge success if you wouldn't be able to tell a MIDI 2.0 device from a MIDI 1.0 at a glance; i.e. same connectors, same interoperability. Then it would be truly an upgrade, a 2.0, and not "thing that works like MIDI in some cases, but have fun buying dongles to connect old equipment to new gear". MPE works on that model; and connectors aside, any multitimbral device is MPE-compatible.
- wackget 5y agoWhen XHR requests are blocked, the OP's URL returns a 404. "Interesting" website design.
- dang 5y agoSome past related threads: MIDI 2.0 Specifications Available for Download - https://news.ycombinator.com/item?id=22411765 https://news.ycombinator.com/item?id=22411765 - Feb 2020 (35 comments) MIDI 2.0, first major overhaul to music interface standard from 1983 - https://news.ycombinator.com/item?id=22180731 https://news.ycombinator.com/item?id=22180731 - Jan 2020 (105 comments) Details about MIDI 2.0 - https://news.ycombinator.com/item?id=20007638 https://news.ycombinator.com/item?id=20007638 - May 2019 (147 comments) MIDI 2.0 Prototyping announced - https://news.ycombinator.com/item?id=18946222 https://news.ycombinator.com/item?id=18946222 - Jan 2019 (195 comments)
- sillysaurusx 5y agoI just wanted to say, the next and prev links on comments are a brilliant feature. Thanks!
- frosted-flakes 5y agoAnd the "root" link. But since they are plain links they pollute the History stack, which is a bit annoying.
- dang 5y agoWe're thinking about handling them in JS to avoid that. But other users want it the other way. Might have to do a poll.
- odiroot 5y agoNever mind what new features will come, I hope it'll always be backwards compatible with MIDI 1.0. MIDI today is so universal and so easy to understand, even on the very low hardware level.
- pknopf 5y agoI don't know how it would be if they are switching from 8 bit to 32 bit. I imagine most devices that come with MIDI 2.0 will have an option to run in either 1 or 2.
- Rochus 5y agoThe physical layer is completely different; Midi 1.0 was a current loop with DIN five-pin connectors; Midi 2.0 uses Ethernet and Wifi.
- LegitShady 5y agoThe physical layer is the easiest thing to get an adapter for. It's the logic and processing that is hard to make cross/back compatible.
- Rochus 5y agoI don't think that the new 32 bit packet based protocol will run over the 31kBit/s current loop.
- romwell 5y ago>The physical layer is the easiest thing to get an adapter for Oh really? Riddle me this, then: a MIDI controller has a USB port. A synth has a USB port. Connect the two without using an external power source for the adapter (Hint: you can't).
- LegitShady 5y agoYou're actually proving my point, rather than disproving it. Thanks, I guess?
- rutierut 5y agoThere are a lot of claims in this article about MIDI1.0 that are misleading at best, it makes it sound more limited & crude than it is. Still it's indeed very nice to see some improvements here, especially since some were transitioning to proprietary communication protocols over HID.
- supernovae 5y agoMIDI 2.0 is going to have a tough road ahead of it to get any adoption. MPE solved some expressiveness and didn't break the world...
- elihu 5y agoYeah, I think that's the big problem with MIDI 2.0: it's complicated, and most manufacturers are probably only going to implement the parts they care about. MIDI 2.0 has been out for awhile and as far as I know there aren't any mainstream products that use it. (Maybe one or two companies have dipped their toe in the water.) That doesn't bode well for the future of the protocol. Something like the Expressive-e Osmose one would think would be exactly the kind of instrument MIDI-2.0 is for, but nope, it's MPE. If you want an expressive controller, there's the Haken Continuum, the Linnstrument, the Roli Seaboard, the Osmose, etc... and they all work work with MPE. https://www.expressivee.com/2-osmose https://www.expressivee.com/2-osmose https://expressivee.happyfox.com/kb/article/162-will-osmose-support-midi-20/ https://expressivee.happyfox.com/kb/article/162-will-osmose-...
- throw_m239339 5y agoNo, because most MIDI capable devices couldn't be bothered to implement the first version of the spec correctly even today.
- spicybright 5y agoDo you have examples?
- sharklazer 5y agoMIDI 2.0 has USB as a pre-req. I’m not sure how this improves things. One of my chief complaints, and why I moved away from USB to an all-midi setup is how interrupts are handled, making USB sometimes unreliable, especially with large setups like mine. MIDI just works and is pretty easy to implement. I’ve never experienced a real limitation. Resolution has its workarounds but honestly isn’t all that limiting. What does 2.0 offer me that 1.0 doesn’t? I know it has new features, but I want a good argument for those features actually being useful.
- jcal93 5y agoI'm in your camp on this one. The new features are neat, but MIDI 1.0 being stupid-simple is its killer feature to me. Plus everything from the last 30yrs supporting it is a big plus. I love that I can take my 1980s SuperJX and fit it right into my setup with brand new stuff, and a brand new DAW, and everything just works.
- md8z 5y agoI don't know if I would call MIDI 1.0 simple in practice. It has a lot of really confusing idiosyncrasies, it's definitely got that feel of being a simple base that was organically developed and had tons of things piled into it over the years. The packet structure in MIDI 2.0 is a lot more... consistent, I guess is what you could say? I don't think you even need a state machine to implement it beyond the initial handshake.
- sova 5y agoMidi 1.0: 127 steps Midi 2.0: 4,294,967,296 steps https://www.midi.org/midi-articles/details-about-midi-2-0-midi-ci-profiles-and-property-exchange https://www.midi.org/midi-articles/details-about-midi-2-0-mi...
- romwell 5y agoNumber big, protocol better! Ever heard of NRPN, my friend? There's a reason why this part of the MIDI spec is rarely used. And the reason is that the musicians don't need it. If you can hear stepping on your pitch bend or filter, it's not because MIDI, it's because the implementation on your device is stupid.
- SeanLuke 5y agoI know that this article is meant for the general masses, but it's rather misinformed in nearly every sentence it utters regarding MIDI 1.0. That's a shame. I'm pretty bummed out about MIDI 2.0's prospects. The protocol has been very slow to come out, and its design is ugly, overcomplex, lumbering, and kitchen sink. It is nothing like its predecessor. MIDI 1.0 was pushed by a single person with a small coterie of contributors, and has the design elegance and simplicity of such. But MIDI 2.0 has been wasting away for years in a large committee, and reeks of it. MIDI has only a few, fairly easily dealt with problems: - It's too slow and has a fixed rate. - Its time sychronization mechanism is primitive. - Its data model is too low resolution both in value and parameter space, and workarounds (NRPN etc.) unacceptably trade off speed to fix this. The model also does not define constraints, such as min/max values or categorical labels for values. - Its parameters are global rather than per-note (resulting in workarounds like MPE). - Its escape mechanism (Sysex) is too flexible and leaves too many nonstandard design choices to the manufacturer. Because the CC/NRPN data model is bad, manufacturers often have resorted to layering custom and proprietary protocols on top of sysex, many of which are very, very badly designed, and all of which are different from one another. Indeed, some manufacturers have lately treated their corner of MIDI Sysex as a trade secret, using non-documented protocols (ahem Arturia) or profoundly stupid and lazy sysex protocol designs (I'm looking at you, Roli). This stuff is easy to fix. But 2.0 goes far further, dumping in two-way communication protocol options, device queries, ties to existing, non-peer-to-peer protocols (USB) and lots of data models that do not appear to be separable from the basic stuff. What a hairball. Will anyone want to implement this?
- romwell 5y agoYes to all of this. MPE is good enough.
- moomin 5y agoI wouldn’t hold your breath on MIDI 2 guitar controllers being better than MIDI 1. The fundamental problem is pitch resolution and that isn’t really addressed by having a better protocol for representing pitch and intonation.
- rnestler 5y ago> The fundamental problem is pitch resolution and that isn’t really addressed by having a better protocol for representing pitch and intonation. But having 32 instead of 7 bits for pitch will give better pitch resolution, no? Or am I misunderstanding something?
- elihu 5y agoMIDI 1.0 has 14 bit (per channel) pitch bend, which is probably fine. What MIDI 2.0 adds is per-note pitch bend, so you don't have to dedicate a separate channel for every string, which is awkward and un-idiomatic. (MPE at least standardized how multiple-channel instruments should behave, but that was a relatively recent development.)
- PaulDavisThe1st 5y agoMPE uses channel-per-note which is equally unidiomatic.
- elihu 5y agoOh I agree. MPE is kind of horrifying when you think about how it actually works. But, it gets the job done, and it's a standard. If you want to do electronic music with expressive instruments right now, MPE is what you would use. I don't think MPE is the end of the road, though. It'll probably be replaced eventually by something that was designed from the start to do the kinds of things that MPE is for. I'm not entirely convinced that MIDI 2.0 is the MPE replacement I'm looking for. Maybe someone will just invent something entirely new. (I have some thoughts in that direction that I plan on publishing eventually, not so much in the "hey look, here's a new protocol everyone ought to use" sense, but more like "if you were going to design a music protocol to do what MPE does but better, this is an example of what it could look like".)
- 112233 5y agoWhat happened to OSC?
- diskzero 5y agoWhat happened, as in why isn't OSC "MIDI 2.0"? The short story could be that the members of the MIDI Association chose to pursue their joint specification to be the next version of MIDI. The actual story will have to be answered by someone who attended all of the various meetings that have occurred over the last three decades about what the MIDI 2.0 spec will be. I was only at a few.
- romwell 5y agoThe same thing that will happen to MIDI 2.0, I feel :D
- spacechild1 5y agoOSC hasn't really been designed as a replacement for MIDI, I think. It is really a generic data communication protocol. They only specified the syntax and omitted any semantics. As a consequence, each application has to specify their own OSC messages. And that's what digital mixing consoles, lighting consoles, DAWs like REAPER or computer music programs like SuperCollider do. There really is no common ground between how these applications use OSC. To make OSC a suitable replacement for MIDI, you would have to come up with a set of OSC messages everyone can agree upon. That's not likely to happen...
- em3rgent0rdr 5y agoIt is a shame OSC didn't specify a minimum standard set of message names to use. I'm looking up and found a proposal for a standard namespace [1] though I'm not sure that even caught on. [1] https://github.com/fabb/SynOSCopy/wiki https://github.com/fabb/SynOSCopy/wiki
- em3rgent0rdr 5y agoMIDI Manufacturers Association should have come up with a standard "Official MIDI™" namespace for naming OSC messages and which works nicely with regular "MIDI" devices. Instead of trying to make their own new spec (that is unlikely to be widely adopted and which is not physically compatible with "MIDI" anyway).
- nyanpasu64 5y agoReplying to a past comment (https://news.ycombinator.com/item?id=22188146 https://news.ycombinator.com/item?id=22188146): > - Violins come last, and it doesn't really matter because they're lazy and they'll take a few hundred milliseconds to really kick in anyway. I think the assumption that violins don't need strong staccato/marcato attacks is wrong. I've needed it in the past, and was unable to get it from soundfonts which only have slow-attack samples. This issue is omnipresent in off-the-shelf soundfonts, and I've also sometimes seen poor articulation in music I've heard made using commercial sound libraries (which I've never purchased or pirated so I can't judge myself). As an example of a piece suffering from slow attacks, https://www.youtube.com/watch?v=ua5VJt6jkaU https://www.youtube.com/watch?v=ua5VJt6jkaU is a nice remix, but feels sloppy because the flute, strings, and violin's 32nd notes are barely audible (goes from attack to release without reaching full volume) and smeared together.
- bonestormii_ 5y agoYeah, articulation should be standardized in the midi specification. It's always a custom mapping to control it even when proper articulations are available. "Oh cool, custom mapping?!", you might say. Wrong. It sucks, because it tends to make old old scores utilizing articulation unusable because the mapping was stored in some obscure plugin configurations divided amongst many plugins. It would be great if articulation messages were standardized, and then you could just expect them to be there, and if they are absent, the soundfont can simply fall back to the closest thing available. That kind of helpful logic is not possible with custom mappings.
- nyanpasu64 5y agoOff-the-shelf .sf2 files containing full-GM instrument banks simply don't have sharp attack samples. I hope they will start having them, but I don't know what it takes. Are single-instruments (or .sfz files) more likely to have them? Adding support in soundfont players for selectable articulation? MIDI 2? "Just buy a commercial plugin?"
- PaulDavisThe1st 5y ago
- iainctduncan 5y agoIt won't. It will make certain small elements of music making a little easier, but there's nothing in Midi 2.0 that will fundamentally change what we can or cannot do in a way that will be noticeable in music in a broader sense. Compared to something like the advent of cheap digital recording, VST plugins, of fast computers, midi 2.0 is a drop in the bucket. That said, I'm definitely looking forward to having it reduce the number of hacky workarounds we currently deal with to get high resolution data in convenient forms. Honestly to anyone not deep into the weeds on this stuff it will be meaningless.
- timc3 5y agoYou hit the nail 100% on the head there. I Couldn’t agree more with what you have said hence the comment and not just an upvote.
- IAmGraydon 5y agoYeah I mean the feature that matters most is high resolution MIDI CC so we can finally avoid stepping. It’s great, but long overdue and not really a game changer.
- iainctduncan 5y agoExactly. It means we can stop using so many midi busses to work around the fact that we get one 14 bit per cc per channel right now (pitch bend), that kind of thing.
- musicale 5y agoExactly. Though with MPE we may see more controllers that support polyphonic expression. Personally I'm happy that ASM is making keyboards with polyphonic aftertouch.
- elihu 5y agoPer-note pitch bend is a big deal, and it could impact the kinds of music people use MIDI for. Right now, it's pretty awkward to use MIDI with controllers that aren't piano-like or to play music that isn't in twelve-tone equal temperament. That said, I'm kind of pessimistic about MIDI 2.0's prospects. Maybe it'll be adopted by most of the manufacturers, but it's not looking like anyone is in any great hurry to start making compatible hardware. There are also some problems that MIDI 2.0 just doesn't address (as far as I know), like the limitation of 128 notes per channel, or the difficulty of expressing a volume swell in a way that a synthesizer will play in a predictable way.
- rkagerer 5y agoMy biggest problem with MIDI is the latency & jitter introduced by USB adapters (many computers these days lack a dedicated sound card or even the space for one). Does the new spec do anything about that?
- em3rgent0rdr 5y agoAnd to be pedantic, USB is not officially part of the MIDI spec, so that problem introduced by USB adapters isn't really a problem with MIDI per se. If you really want to interface MIDI with a computer in a fashion consistent with the original MIDI specs, then you can use an actual Serial port at MIDI's 31,250 baud rate, which is possible to do on a Raspberry Pi for instance (or on a computer which you could set your baud rate to that). Then you can get interrupts precisely when the MIDI notes arrive.
- bitwize 5y agoIf you want MIDI without latency or jitter, you pretty much need an old Atari ST. USB isn't the only source of latency (and I believe MIDI over USB runs in a special mode that minimizes latency).
- strenholme 5y agoNow, I agree that MIDI 1.0 was designed for keyboard based synthesizers, and I know that complaints about MIDI latency have been around about as long as MIDI has been. So, yes, it has always been imperfect. However, the nice thing about MIDI is that it allows me to hook up my 2020/2021 synthesizer (a Behringer 2600) to a 1987 sequencer (a Yamaha QX5), a 2015 synth (a Roland JD-Xi), or pretty much any piece of pro synth gear made since 1983. Now, with MIDI-over-USB or what not, we lose something which makes MIDI very nice: We can connect a hardware keyboard to a dedicates sound module without having to have a computer involved. While there are USB host synths which one can connect a MIDI-only-over-USB keyboard to directly, they are few and far between (my JD-Xi has USB, as does my 2600 and Arturia Keylab controller, but all three can only be hooked up to a computer with USB) Until MIDI 2.0 has a way to allow synths to be connected to each other without involving computers, and there is a standard way to do that (I think USB-C would probably be best for this), DIN MIDI 1.0 will be a part of pro and bedroom recording studios.
- ssalazar 5y agoAgreed- though for MIDI 1.0 Kenton has some helpful boxes that act as a USB MIDI host to DIN MIDI converter.
- rektide 5y agothe converters are great& easy. this protest that we must conserve an over 30 year old standard& never ever update it is a breed of conservativism that makes me shudder. basic USB is available on a vast vast range of micros, including a huge range of under $1 ones. if you do want to use old gear, great, the are options.
- xyzzy123 5y agoI will shill for the retrokits rk006 all day long (I am not involved and do not benefit from the project). https://retrokits.com/shop/rk006/ https://retrokits.com/shop/rk006/ It's a midi usb host and multi-port thru-box that even boosts succulent growth while you make DAW-less jam. It's particularly good for bridging USB and DIN midi.
- 999900000999 5y agoThe only issue I've noticed, and this might just be an iOS thing is devices would randomly disconnect, I know it's not good for my iPad but one day I found myself incessantly plugging in the adapter over and over again to try to get it to work. It's at the point where I'm tempted to go Bluetooth midi only when using my iPad from music Creation. Which prevents me from using my full size piano, first world problems
- matchagaucho 5y agoThe article fundamentally speaks to how industry standards led to a proliferation of synthesizers and collaboration within the music industry. The Metaverse, coincidentally, is at nearly the same crossroads as MIDI in the early 1980's. Each vendor built their own hardware and defined their own protocols. When Roland open sourced the MPU-401 chipset and gave away the MIDI specs, the industry blossomed. Anyway, a lot to learn from MIDI... if Meta can similarly align an industry around basic hardware, APIs, and formats.
- filoleg 5y agoI've never thought of it this way until I've read your comment, but now I cannot shake it off, because the comparison seems so clear and obvious in hindsight.
- coretx 5y agoMIDI 1.0 is designed for musicians. MIDI 2.0 is designed for rights holders.
- thrusong 5y agoDuplicate that I shared last night: https://news.ycombinator.com/item?id=29045277 https://news.ycombinator.com/item?id=29045277
- rektide 5y agogonna take way too long before we get webmidi2. meanwhile the usual suspects are screaming hell that no it's too risky to do midi, we must protect the user, God forbid the web get good.
- robbrown451 5y agoI wonder when Firefox will support MIDI 2.0, since they still haven't supported MIDI 1.0. (chromium and other browser engines have had MIDI support since maybe 2014) https://bugzilla.mozilla.org/show_bug.cgi?id=836897 https://bugzilla.mozilla.org/show_bug.cgi?id=836897 Yes, cool things can be done with MIDI in browser, some that can't easily be done outside of browsers (such as synchronizing and overlaying on top of 3rd party videos, such as from YouTube). Here's some of the stuff I've been working on, mostly targeted at my kid, but adults love it too: https://www.youtube.com/watch?v=khU5A6Y1dk4 https://www.youtube.com/watch?v=khU5A6Y1dk4 (this one doesn't play on youtube because contentId flags it, but the app itself overlays on 3rd party YouTube videos and it is not a problem) https://www.karmatics.com/video/pianoplydemo.mp4 https://www.karmatics.com/video/pianoplydemo.mp4 https://www.youtube.com/watch?v=p1TcyDZiuyI https://www.youtube.com/watch?v=p1TcyDZiuyI https://www.youtube.com/watch?v=Gj2rlytbDsY https://www.youtube.com/watch?v=Gj2rlytbDsY
- snvzz 5y ago>how will MIDI 2.0 change music By breaking compatibility. Everything used to just work, now a layer of complication is added to the mix. This is why we can't have nice things.
- jdkee 5y agoJust use control voltage.