RtMidi native library floods output console when internal message queue limit is reached

[basshelal]

If a ReadableMidiPort receives enough messages to fill its internal (RtMidi) queue (100 by default in RtMidi and also 100 in JRtMidi, ReadableMidiPort.DEFAULT_QUEUE_SIZE_LIMIT) then our console gets flooded with error messages saying MidiInAlsa: message queue limit reached!!.

Setting the queue size to 0 causes a segfault later and setting it to a large number actually allocates all that memory only for it to inevitably flood the console again once that limit is reached anyway.

I have already filed an issue with RtMidi about this here: thestk/rtmidi#236

But most likely, we will have to figure this out for ourselves by probably trying to suppress the output somehow.

I know this is somewhat of a minor nitpick, but the way I see it, the native library should only be printing to the console if we let it, ie some kind of debug flag in RtMidi.Config, otherwise, a Java application should only be seeing Java output on its console.

It's actually more annoying because it happens upon every new received message, so in some cases, "flooding" is actually an understatement, not good, especially for development and debugging, but also for production too, since a GUI-less application will also be flooded with this as well.