I’m experiencing an issue with MIDI input when trying to use MIDI controllers with Technobear’s plugins (including the newly developed Grid plugin).
I should mention that I am receiving MIDI input via the Percussa MIDI module with my controllers, so the issue is not related to Synthor/OS, the controllers, USB port or the cables!
I’m running ssp-sdcard-130720221320, where I have deleted the included Synthor file and replaced it with Technobear’s modified version of Synthor and the plugins from this download link:
I’m unable to get MIDI learn working in Technobear’s plugins. I can select the controller in the MIDI IN/MIDI OUT fields, but after exiting the settings and returning, the controller field resets back to “NONE.”
So the plugins sees the Controllers but maybe the connection is terminated when exiting the setting panel?
I’m really hoping to find a solution to this, so any suggestions or help would be super appreciated!
so, I assume you installed the above plugins recently, as I updated them on 03/04/26.
(please double check this… as the previous release had quite a few ‘quirks’, that could lead to confusion)
I did go check the tbplugins on my ssp, it it working fine…so no ‘release’ issue.
and Ive a number of midi devices that work fine.
the fact you can see them is a good sign. I assume they dont have an * against them?
(which would indicate they are disconnected) but it only shows that it can be ‘enumerated’, rather than be connected to.
hmm, hard to know where to start really…as Ive never had an issue with the controllers I have.
and the fact it works with synthor midi, indicates alsa/linux has no ‘issue’ with it.
so frankly, alot of this is speculative at best, because it should work
first lets get some details, what device are we talking about?
is it usb bus power, or external ,
always good to try external power, as some devices can consume a lot of power…
is this on a NEW patch, shouldn’t matter but always a good start.
just connect midi in
just in case theres a wierd midi feedback loop going on!?
have you tried other midi controllers?
this would be very useful, so we can see if its controller specific.
its perhaps not ‘odd’ that you see it on the list, and then it goes back to none…
seeing it on the list , just means it ‘enumerates’ correctly, it does not prove it can be connected to.
my guess is, it failes to actually connect to it… and whilst I store ‘disconnected’ devices, I likely only do that if it manages to connect to it the first time.
( I cannot prove this, as I dont have a midi device that wont connect)
frankly , the only thing I can think of is… this device for some reason, only allows ONE exclusive connection to it, and so SYNTHOR grabs it, and then nothing else can connect to it.
but, this is NOT a behaviour Ive seen, synthor always grabs the first midi device, so 90% of the time, Im connecting to the same device as synthor is… and Ive just double checked here, that is still ok.
do you have other midi controllers? this would really help us tie it down to controller specific (which I think is most likely) hence, why I and others have not seen this.
lets dig into this…
ok, agreed, its not usb port or cables.
controllers… if you are talking multiple different controlles Id agree, seem highly unlikely, as it works with all controllers ive tried on my ssp
BUT one specific controller - yes, the OS and Synthor could have particular issues with.
OR more specifically ALSA could e
.g. if there was some kind of ‘exclusivity’ for that controller, this is what we could see.
(both synthor and my plugins use ALSA to talk to midi devices, so yeah, if it works for one it should work for the other)
the annoying bit is Synthor grabs the controller regardless of if you use MIDI or not, so its always going to get it first, even before synthor loads my plugins
again, its back to the beginning really, I likely don’t have your controller, so its impossible for me to test that specific combo. I can only test with what I have, and the ones Ive tried worked fine.
I’ll see if I can find some time and other midi devices to test with, but I’ll be honest, Im not ‘hopeful’ that this will yield any light… but its all I can think of from my end to narrow it down.
i thought that too , but the OP says “MIDI controllers” / “the controllers”, so plural…
its important to find out if its ONE specific controller (type) or all/many controllers.
as I said, one controller, whilst I’ve not see one fail, it would not be a huge suprise.
but multiple would lean towards a more general pattern.
anyways, Id like to know which contoller/controllers - we are talking about here.
as, from my testing, I know at least my controllers work, so need to narrow things down a bit.
so, I went around my studio checking various controllers, and bingo… I found one with similar behaviour. which is great, as it means I can have something to test a dev build against.
its kind of odd, there is nothing in the log saying its connecting, or failed to connect - its like its not even attempting to connect to it - but no idea why…
(comparing against a device that works where the log looks entirely as expected)
so, Im now creating a test build to see if I can determine what is going on,
hopefully more news soon!
ok, Ive identified the issue, and have a ‘quick fix’.
however, Ive spotted another corner case for some devices, which is a little move involved but makes sense to address at the same time…
hopefully will have something released in a few hours.
edit: ok, got it all done, just building the release - will test that before uploading.
@thetechnobear, I can confirm that the bug has been resolved! Midi Learn is functioning as intended, and when using the Midi Monitor, I receive all the necessary information. I genuinely appreciate your efforts in fixing this issue. I’m really looking forward to using the matrix mixer in conjunction with a 4x4 encoder MIDI controller
@kuttor, I’m afraid that the issue persists in the Grid plugin version 2.4.4. However, I hope that TB’s fix will provide guidance on how to resolve it in Grid.
