Hi, tried out the midi trigger option and OSC but there is no midi input or any OSc sources. Shut down Keyboard Maestro as well. No luck. Regards, Kim
Christian Scheuer @chrscheuer2020-09-29 19:30:38.142ZHi Kim,
Thanks for taking your question here :)
When using OSC, you have to specify yourself which port you'd like SoundFlow to listen on, and what OSC address string your script should react to.
For MIDI triggers, the device should be possible to select in the MIDI Device drop down here:
It sounds like you're saying this is empty for you. Is that true, or were you looking elsewhere?
What are the physical devices you have attached?
Kim Planert @Kim_PlanertThanks Christian,
Yes these are empty on my end. Midi hardware wise I have an MTP AV connected. The Lemur Daemon is virtual as is, Video Salve and an app called Patchboard. Interestingly Pro Tools sees Soundflow in it's Midi Input Enable dialogue.
My current goal is to operate Sound Flow from Lemur. I have many functions programed there that work thru Keyboard Maestro and CC faders. If I could use buttons here to launch specific Soundflow commands that would put it all on the one surface for me. Some function I can do with KM that I can't do with SF (yet) and visa versa. Either I get the trigger via midi or OSC happening.
Thank you!
Kim
Christian Scheuer @chrscheuer2020-09-29 21:18:58.227ZGotcha. Yea, of course, we'd love it if we could get you onto SoundFlow surfaces at one point (note, SF can also call out to KM) - but I understand your wish to integrate the other way round for the time being, if you already invested a lot of time in Lemur.
I can imagine virtual devices like Lemur wouldn't show up in SF as potential inputs. We haven't tested this. (Again, SoundFlow surfaces work without any need of manual routing. It just works. But yea you need to spend a lot of time to route Lemur stuff correctly)
I'd probably try to go through OSC.
Set an OSC trigger in SF and choose a port - say 9456.
Set the OSC address that the script should listen to - say/my/commandNow make your Lemur button send an OSC message to your macOS host on port 9456 with the address
/my/commandand it should run your script.Or, design your surface in SF today and you'll only have to deal with (the much easier) calling out to KM for those few scripts you can't do today in SF.
This would be my recommended approach - but of course, there may be reasons I haven't understood yet that would keep you from this.- Kim Planert @Kim_Planert
Thanks Christian,
The OSC way looks to complicated and untested. I am one of the users who has little interest in OSC or learning Java :-).
Now the Midi Devices were listed and I successfully triggered a command in SF via Midi and the Lemur Daemon from Lemur. That's fabulous!
It's great that SF can talk too KM. What holds me back from switching is that at the moment the Faders do not send independent Midi CC. Moving two or more faders at the same time is not possible. Did you manage to fix this issue yet? Also the fact that tabs are not supported yet. I read that's coming soon? I have more functions programed then fit onto the Samsung Galaxy screen. So tabs are great for grouping.
This current state allows me now to merge some of my old KM macros with what SF has to offer. Really cool!
- Christian Scheuer @chrscheuer2020-09-30 18:58:05.281Z
Great to hear you got it working :)