rtmidi | common API for realtime MIDI input | Audio Utils library

probably a bit of a noob question so bear with me.

What do I want to do? I have a c++ class called main.cpp and with that I want to add the external classes of RtMidi. I can just move the RtMidi classes into the same folder as my main.cpp and include them from there, but it feels a lot cleaner if I can keep them in a sepperate folder.

The RtMidi folder comes with its own Cmake file, and my assumption is that I can build that folder first to create a library that I then can link to. Is this correct? I'm new to c++ and not 100% sure if this is the way you want to add external classes.

When trying to build my project RtMidi is built, but I'm getting a warning that the main.cpp file can't find the include.

I'm building this on a mac with Visual Studio Code and clang as the compiler if that's any help

main.cpp

I want to use Rtmidi to get input from launchpad. However, despite connecting the launchpad, 0 pods are available. "MidiInDummy: This class providers no functionality." There's also this phrase, so something seems to be wrong.

Source:

I am trying to use python-rtmidi with Flask and trying to display all available MIDI ports on the browser. And noticing two issues while the function gets called from views.py.

• MidiIn().get_ports() : doesn't recognize a new ports that opened after the flask server started.

• If a port reopened after it was closed (ex: VMPK Output) calling the same function MidiIn().get_ports(), it wouldn't recognize the new port.

• Calling MidiIn().get_ports() from any module works fine. It just whenever it gets called from views.py, the above issues occured.

• A similar code works totally fine in Quart framework.

Any idea why it happens with Flask and would appreciate if you could shed some light on a workaround.

I want to write a script on my Raspberry Pi Zero W, that sends MIDI to my computer whenever I make a specific connection on the GPIO board.

The hardware stuff is already taken care of, it can recognize unique button presses. But it won't seem to send any data to my computer. I've tried multiple python modules (like rtmidi-python, python-rtmidi, mido), but none of them work as I would want them to.

Trying to solve this issue, I've set up my Raspberry to power from the power port, so the USB port remains empty, and when it boots up, I connect the cable to my PC. I even wrote a script, that perpetually shouts the same note (note off included) over and over, since I couldn't find any "setup protocol". While browsing various forms, I noticed that all of them were pretty old. The newest is rtmidi-python on GitHub, but that doesn't seem to have any setup stuff.

It very well could be, that i just looked the wrong way all along, or that the signal doesnt even come through the USB cable, or it doesn't need a setup either. If so, would you mind letting me know, or showing me how to do it correctly.

I made my Raspberry into a "MIDI function" (this is how). My PC, and FL studio recognizes it as well. However, still no action, when I try to play a note. This port probing scripts

I'd like to create a python3.6 env with default anaconda packages. The manual and many online resources say the command is conda create -n py36 python=3.6 anaconda. On other computers that works, but on one particular computer it only installs very few packages. I can't figure out why. I've checked $HOME/anaconda2/env and there's nothing in there. (ubuntu 16.04, installed from anaconda, not miniconda)

In my program, I am using a sqlite3 database.

In order to handle the Ctrl-C signal and gracefully terminate the program by closing the database and closing all Midi ports (my program uses RtMidi), I need to set up a global object that stores them. I have made a class:

I'm writing a simple C++ command line utility to send MIDI messages from my Mac (MacOS 10.12) to a Behringer Powerplay P16-M audio mixer via a Roland UM-One Mk 2 USB interface. I'm using the rtmidi realtime MIDI API.

When I send two consecutive MIDI messages to the same channel, the two messages seem to get garbled by the mixer. When I send two consecutive messages to alternate channels, it works fine.

For example, in order to set channel 1 level to midi 0 (-51dB) and channel 1 pan to midi 64 (centered), I understand that I should send these two messages: 0xB0 0x07 0x0 and 0xB0 0x0A 0x40. When I send those messages one after the other, the LEDs on the mixer unexpectedly indicate that channel 1 level is about 64 and the panning is unchanged -- just as if I'd sent the single message 0xB0 0x07 0x40. If instead I intersperse the two messages with a message for another channel, or with a ridiculously long sleep (anything over about 900 milliseconds does it), the LEDs indicate the expected settings: level at zero, pan centered.

What am I doing wrong? Why can't I send two consecutive messages to the same channel? Am I sending the messages too fast? Is this is an rtmidi issue? Is it an issue with the mixer?

Here's a minimal but complete working example that demonstrates the problem. (I compile it in XCode against the CoreMIDI, CoreAudio, and CoreFoundation frameworks.)

I can't find a related solution so i finally post here. I have a very small program that uses the RTMidi library to map the controllers keys as hotkeys. Everything works fine in debug mode and releasing the app doesn't give me any errors either, but the RTMidiIn class isn't finding any Ports in the release version.

This is my code