[sdiy] Handling MIDI Running Status from Power-up

[Tom Wiltshire]

> On 14 Nov 2019, at 22:14, Pete Hartman <pete.hartman at gmail.com> wrote:
> 
> 
> 
> On Thu, Nov 14, 2019 at 1:57 PM Tom Wiltshire <tom at electricdruid.net <mailto:tom at electricdruid.net>> wrote:
> 
>> On 14 Nov 2019, at 18:37, Next Expanse <nextexpanse at gmail.com <mailto:nextexpanse at gmail.com>> wrote:
>> 
>> The right way to solve this would be to have a bidirectional protocol, some sort of way for the receiver to detect when it’s been disconnected, and to have a way for the module to query the controller’s state. Nothing else will fix the problem, so unless there are some serious changes, we have to live with it.
>> 
> 
> The “right way” depends on the technology, and a bidirectional protocol would have been much too much overhead at the time MIDI was invented. Instead they did something simpler and it actually worked the vast majority of the time. Ok, there were “stuck note” problems, but everyone soon worked out how to fix that, and MIDI input devices started providing "MIDI Panic” functions that killed everything in an emergency.
> 
> The fact that we’re still here thirty+ years later discussing it shows exactly how much of a success it was. I can’t think of any other consumer/professional technology standard that’s lasted as long aside from the 1/4” jack!
> 
> TCP/IP/Ethernet
> 
> Ethernet itself was created in 1973, and the TCP/IP stack was created by DARPA to make use of it.  The physical medium has changed a lot over the years, and the protocol extended to handle ever faster speeds, but at it's core it's the same thing.
> 
> :-D

Yeah, nice example. Definitely another long-term success story. Thanks.

Tom

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20191114/31b1fdf5/attachment.htm>