It’s been a while since I last used my Stream Deck and today I started preparing it to make some midi programming easier.
For clarity: I’ve already changed to Windows Midi Services and created the loopbacks. (Microslop sneakily breaking most of my midi stuffs with that update forced me to do so to use at least most of my setup again though lost bunch of features on hardwares.)
Apparently, for whatever reason, the Midi plugin doesn’t seem to be actually sending any data through the loopbacks whatsoever, tested note-on/offs, CCs and Mackie Control.
First I tried sending CCs to QLC+ but it indicated no incoming data. I double-checked via Reaper-QLC+ loopback to see if QLC+ was bugging but that transferred midi data normally from Reaper to QLC+. To make sure it wasn’t just one loopback messing up, I tried setting another. Still no incoming data in QLC+.
Next I tested if Reaper indicated any incoming midi data by setting a stream deck button to send note-on to Reaper via “QLC to Reaper”-loopback (That I don’t actually use for that so good for testing). Reaper indicated no incoming midi data either after pressing the button 4 times with extended logging enabled and I even turned on MIDI logger plugin in Reaper but shows no incoming data whatsoever.
To check that I had set the track to record midi correctly, I double-checked by playing some notes on my midi keyboard. Midi logger recognized them normally.
I also tried setting up Mackie Control. No response.
So, having done those double-checks, the issue seems to be on midi plugin.
Also, to check if there was an issue with Stream Deck itself, I tested changing some scenes in OBS and using Reaper OSC to press Play. Those worked normally.
Unfortunately I haven’t figured out the best way to test incoming data in Stream Deck plugin, just the outgoing, so dunno if that’s also affected.
Please follow the procedure in the last item on the FAQ page to create and upload a log file (please press the upload button, don’t attach the log file here). That way, I get hard evidence of what’s going on in the plugin and can provide better support.
Tested again: Turned extended logging on, quitted Stream Deck.exe and started it again to log possible stuff happening on start up, then pressed the note on 60 button 4 times and turned off extended logging.
Log says that the messages are being sent successfully but Reaper doesn’t see any incoming MIDI.
Also, after that, tested sending midi from another track via same loopback to same track as I used for test-logging and the loopback itself works properly. legacyMidi is written in the Advanced Settings field.
You should check the MIDI port assignments because I don’t think they are correct. As you have seen in the log file, the plugin successfully sends the MIDI commands. If they don’t arrive at the destination, there’s something wrong with the port configuration.
You have several MIDI 2.0 ports named as MIDI 1.0 ports, with directions in their names, even though MIDI 2.0 ports are bidirectional. The ports will, of course, function as MIDI 2.0 ports regardless of the names, but I find it confusing to have directional names for ports that go both ways.
The ports used for the button are NOT named as MIDI 2.0 ports, but they are used as MIDI 2.0 ports, which causes a feedback loop.
I don’t know what the port abbreviations mean, but if “QLC to Reaper” and “Reaper to QLC” are MIDI 1.0 loopback ports (which they appear to be based on the names), the plugin cannot have “QLC to Reaper” as both an input and output port.
Assuming the “QLC” is the plugin, you should set “QLC to Reaper” as the output port and “Reaper to QLC” as the input port for the plugin. And similarly, assuming that “Reaper” is …ehh…Reaper, it should have “Reaper to QLC” as the output port and “QLC to Reaper” as the input port.
Figured the stuff out. So, I was basically using them one-way, setting Reaper DAW to output midi to QLC+ lighting software of that same port name. Midi 2.0 loopbacks apparently like to come in A-B pairs when set up, so to keep it simpler for myself, I indeed named the old way “one-directional” as I would’ve used the A part to move data one way and B part the other way while ignoring the input/output that wasn’t being used.
But to the root of the problem: apparently QLC+ lighting software and Reaper DAW don’t seem to understand how to deal with Midi 2.0 loopbacks yet as their settings still use the Midi 1.0 loopback style…and function.
So I today google’d further and got the WIP midi 1.0 loopbacks plugin from the Midi 2.0 github and set that up and by creating the ol’ good midi 1.0 loopbacks with it, both the connection between my softwares and between them and my Stream Deck XL work again as normal. Thus solved for now. (And hoping they don’t break the midi 1.0 loopbacks with next iterations.)