cmdmp3 VS arduino_midi_library

Some things I built on the side, outside of my day job:

In the late 90's, I sold a command-line SMTP e-mailer for Windows. It was easy enough for folks to integrate e-mail transmission into their systems ... even 16-bit systems since spawning a copy of the shell would allow 16-bit systems to invoke my 32-bit mailer. Lots of folks had used these tools for all sorts of things. I got registration checks and cash from around the world before I started taking credit card payments.

I have an open source command-line MP3 player for Windows that folks still use and incorporate into their systems, JS libraries for node.js, ...etc.

https://github.com/jimlawless/cmdmp3

I wrote a command-line MP3 player in C for Windows. I just wanted to play with the media manger API's, but I've ended up using this to play MP3's in succession via a script.

https://github.com/jimlawless/cmdmp3

It doesn't work on all versions of Windows ... it depends on some configuration elements. This has been used in another developer's video game and I believe it's installed with an MP3 player library in node.js ( if you're running node.js under Windows. ) It also plays WAV files on Windows 10 (possibly 11) if you pass the name of a WAV file into the command-line.

I needed a command-line emailer that would send an email with a very simple one-line body for my Mac. I also wanted to exercise Go's SMTP libraries while experimenting with trying to build a minimal emailer application.

https://github.com/jimlawless/gsend

I use this regularly. I used to use it on MacOS, but I use it more frequently on Windows.

That makes me wonder how often one runs across a synth that doesn't support running status. I'm working on a MIDI controller myself, and that's a thing I probably ought to enable if I want the lowest latency.

It seems the standard MIDI libraries that Arduino uses don't enable it by default, but it's a configuration option you can turn on, along with a note not to try to use it with USB[1].

[1] https://github.com/FortySevenEffects/arduino_midi_library/bl...

take a look here

The Arduino MIDI Library [1]. Back in 2009, I learned C++ to build it and control my guitar effects pedals with custom electronics as part of my engineering degree.

[1] https://github.com/FortySevenEffects/arduino_midi_library

Your project can be broken up into a number of subprojects. For keyscanning you don't need additional hardware, just the pins from the ribbon cables going to the arduino's digital pins and ground. Since the keys are just switches (two per key, the time difference between the two switches closing giving the source of velocity), you could start with some examples from the Arduino MIDI library (https://github.com/FortySevenEffects/arduino_midi_library). To test MIDI sending you don't even need to start from the keybed just yet, and if you do, you can start with a single key. Once you've got that part figured out end to end (key press/release generates note on/off events) you can work on iterating through the matrix, CC controls etc. MIDI out can be done in different ways. With a 5 pin DIN plug you'd just need two 220 ohm resistors.

On an Arduino compatible platform the configuration of the baud rate at the bare metal layer is taken care of by the library when you call its begin() method. Looking at the example code included with the library it appears that there are no timer interrupts or anything like that required of you in order to use it. Another thing that jumps out is that the call to read() returns a non-zero value if anything has been received that you should use to predicate whether any further attention needs to be spent on it by your code. You may know this but it wasn't apparent from the loop() { MIDI.read\`() }` example that you gave above.

As i have started to combine this with Midi Implementation from FourtySevenEffects lib, i only have done a quick test with two/three strips and did discover follwing issue(s):

Using a library for the midi shield you can register two functions as callbacks. One callback for NoteOn(...) messages and one for NoteOff(...) messages. But thre is much more. In the end the source of truth should always be the docs for the library itself.

Click the link to github (second link in the article) and there's all the source code: https://github.com/FortySevenEffects/arduino_midi_library

Here’s a library that might work.