MIDI Kinetics Forum

@Phil999
When using OSC I assume that all midi parameters used by the DAW can remain as is and that OSC uses a whole different set of communication. If I use midi with the DAW then all my DAW controllers are rendered kind of useless but if OSC uses different communication with the DAW this wouldn't be a problem. BTW, I use Ableton Live.
Thanks for all this great info
Alan

Ableton Live is able to send MIDI parameter feedback, so I don't see a problem with what you want to do. I'm not experienced with Ableton, I guess you have to set the remote MIDI output in the preferences, and your template should work bi-directionally.

Hey,

just an idea: have you opened the "plug in editor" in Ableton? That little button in the headline near on/off-switch of the plugin with the wrench-Icon... if activated you can see the plugin surface. The plugin editor have to be opened for sending Midifeedback in Ableton! I experienced that with good old "synth1" (love that synth!) - if not opened, no midifeedback. If opened, Midifeedback works fine! See a video here with Midifeedback on lemur on Programm change: http://youtu.be/89FZAKI2Eho?t=16s
I think, if old synth1 gives Midifeedback other plugins will do too.

Other possible problems:
Have you defined Midi-in targets on Lemur correct?
Have you activated Midiout in Live preferences for those targets?
If using variables on Lemur, Midifeedback is not working (like fader.x*fader.y)...well maybe with some scripting... but if you use controls direct it is woking fine.
Anyway.... Midifeedback is sloooow. On high traffic it can be a problem.
(btw: do not use same Midiport for in and out!)

Hope that helps
mat

Hi @mat

Being new to Lemur, not sure what you mean by defining midi-in target in Lemur. I have defined live preference control midi, etc in Ableton. Sounds like a good idea to play around with and explore.

thanks
Alan

Ah... I see!
For a bidirectional Midicommunication you need both: Midi in and out.

On Lemur:
- go to settings
- see your miditarget 0
- "From": set to a midiport installed on your system....e.g. maple 1 on PC
- "To": set to another Midiport...e.g. maple 2

In Abletons preferences:
- open track and remote (for Control change) input of maple 2
- open track and remote output for maple 1

Now you have a bi directional Midi control for Miditarget 0 on Lemur (you can add more targets, but 0 is standard)
Important: Do not use same port for in and out. This can cause a Midifeedbackloop which can crash your system (or at least your driver installation)

On Mac it is a bit different. That Midibus system (IAC) can handle bidirectional in one bus...however.... maybe a Mac-user can bring in some clarification???

enjoy
mat

@mat

Thanks for the info, I'll give it a try