It is fascinating how some hardware manufacturers of #MIDI controllers and instruments no longer show the MIDI logo on the box or documentation, just to get around the requirement that the use of that logo and getting certified obligates them to publish a MIDI implementation chart for all the MIDI events it supports, including #SysEx messages.

Here's my first attempt at a quick primer on what #sysex (system exclusive #midi) data. Does it make sense? Anything I left out?

https://coffeeshopped.com/sysex

I'm going to be working on some scripts to send batches of #MIDI #sysex commands to a #novation bassstation2. It's probably going to be with #lua or #python , but please let me know if there's any other language or scripting environment that will speed up the task

https://mathr.co.uk/blog/2019-12-10_midi_network_between_linux_and_amiga.html #blog post about #midi #network between #linux and #amiga for #file #transfer over #SysEx

#RetroComputing

Researching #MIDI and #Amiga #serial port handler:

http://personal.kent.edu/~sbirch/Music_Production/MP-II/MIDI/midi_physical_layer.htm
https://wiki.amigaos.net/wiki/AmigaOS_Manual:_AmigaDOS_Additional_Amiga_Directories#Port-Handler
https://wiki.amigaos.net/wiki/AmigaOS_Manual:_AmigaDOS_Command_Reference#TYPE

Hoping I could use this command to #bootstrap a #network over MIDI:

TYPE SER:31250/8N1 TO outputfile BUFFER=bytes

I need to check if I can send raw data from Linux over my USB MIDI interface, and the SER: handler might not be performant enough, but if so then I can start working on a simple FTP-alike for transferring files (with consistency checksums and retrying failed chunks) over MIDI cables, using real 7bit #SysEx payloads if necessary.

I'd transfer only the first program binary(s) using the SER: method, would develop in FS-UAE emulator with easier internet access (via shared Linux host folder).

#RetroComputing