Greetings Jesse, greetings all,
Every time I finally figure out something that's had me stumped, I realize anew just how good, simple, stable and unproblematic (and worth a donation) SL is. But the devils in the details getting various things to work together ... you know the story. Anyway, each new level of complexity I add to my nascent setup poses new challenges. Which I guess is why we're all here.
So ... here's something weird:
As you see, I'm using SL in AULab, now fed by an RME FF400 (which replaced my reliable but very limited Edirol UA-25EX). This, in turn, is fed with MIDI from a Roland FC-300, which has its quirks but, with those accounted for, did quite well in my previous setup.
So the first thing I tried to do with the RME was basically replicate the simple setup that worked with the Edirol (at least I think that's what I'm doing). MIDI Monitor tells me everything's coming through fine (once I filter out the constant "active sense" messages, which I assume aren't the problem). So with an input and an output set up, I add a bus and insert AULab. I've moved the standalone version of SL to the right place, so the plugin version finds the GUI by itself ... so far so good. Then I go to the MIDI Effect Editor view in the bus window and ... it comes up blank. Simply blank. Despite the fact that I've connected the Bus with the RME's Port 1 in the "Midi Sources" area of the AULab studio view. So I go back to the SL plugin view, and nothing comes up anymore. No GUI and no option to start or find it. Again, just a blank window. The only way to get SL back seems to be to delete the plugin and re-add it. For the record: when I just go ahead and try to use the GUI after adding the bus and plugin, the MIDI messages I send do not reach it.
I'm not convinced that this has to do with the different audio interface. But as far as I can tell, that's the only significant factor that has changed.
Have any of you had a similar issue? And how have you solved it???
Many thanks for any and all input...!