General
Custom MIDI messages are way cool
Started by cliffman on .
Sign in or create an account to join the conversation.
I just realized I could replace a bunch or scripting, and change MIDI channels and CC numbers on the fly,
the Custom MIDI stuff is just super useful......
Updated the Kenton Pro template in the Templates Forum.
Oh my duck, i am so liking this stuff...
the Custom MIDI stuff is just super useful......
Updated the Kenton Pro template in the Templates Forum.
Oh my duck, i am so liking this stuff...
Hi
It is important to remember that a variable assigned to a Custom Midi can output data but will not react to the corresponding incoming message.
Custom MIDI messages ar e NOT bi-directional . . . (Sect 9.4 in the manual)
Cheers
MM
It is important to remember that a variable assigned to a Custom Midi can output data but will not react to the corresponding incoming message.
Custom MIDI messages ar e NOT bi-directional . . . (Sect 9.4 in the manual)
Cheers
MM
I SO much wish that this fact would change - too! I would LOVE to have feedback for Custom MIDI messages. PLEASE. i wanted this ever since I had the hardware Lemur.
Hi
You can ofcourse still write scripts to deal with the return info - it just does not do it auto-magically
Cheers
MM
You can ofcourse still write scripts to deal with the return info - it just does not do it auto-magically
Cheers
MM
I've setup a multislider sending some distinct CC from a custom midi message to control Live's track Levels.
I've also succesfully managed to to have feedback from Live with an OnMidi script and and update the sliders.The problem that I have now is that because of the feedback that is caused the sliders do not respond easily to my touch. They stutter. Same goes for Live when I try to manipulate the track faders.
Any ideas how you can avoid the feedback.
In my script I assign the second value from the midi_args to the multislider.x value.
I've also succesfully managed to to have feedback from Live with an OnMidi script and and update the sliders.The problem that I have now is that because of the feedback that is caused the sliders do not respond easily to my touch. They stutter. Same goes for Live when I try to manipulate the track faders.
Any ideas how you can avoid the feedback.
In my script I assign the second value from the midi_args to the multislider.x value.
Hey guys,
i'm so sorry. i'm new to Lemur and i ask myself: what is a 'general midi message'.
there is not much explanation in the manual and the example they give in the manual doesn't work on my iPad.
i'm totally confused. seems that it's something great and i can't grab it
please help me.
can u tell me what it is and how it works and maybe a little example patch for Lemur? or some links which help?
i'll continue my google search simultaneously.
thank u so much
i'm so sorry. i'm new to Lemur and i ask myself: what is a 'general midi message'.
there is not much explanation in the manual and the example they give in the manual doesn't work on my iPad.
i'm totally confused. seems that it's something great and i can't grab it
please help me.
can u tell me what it is and how it works and maybe a little example patch for Lemur? or some links which help?
i'll continue my google search simultaneously.
thank u so much
you gave the answer to your question already. Simply research MIDI and General MIDI.
Even though kraft's post is old, for those having the same problem
(custom MIDI output - scripted custom MIDI feedback causes stuttering of the object when used in Lemur)
...the solution is to make the script provide feedback back into the object ONLY when it is not touched.....therefore by using the z expression which is now, available to more objects than it was back then.....
For example the "feedback" script should be included in a "if" statement of this form:
A similar method can be applied to eliminate the software mapped control stuttering (caused by "delayed" custom MIDI message generated from the script feedback that moved the object in Lemur) by creating a custom expression which be used as "trigger" in the custom MIDI output which will be (if we want to map the x expression of the object):
(custom MIDI output - scripted custom MIDI feedback causes stuttering of the object when used in Lemur)
...the solution is to make the script provide feedback back into the object ONLY when it is not touched.....therefore by using the z expression which is now, available to more objects than it was back then.....
For example the "feedback" script should be included in a "if" statement of this form:
if (ScriptTargetedObject.z==0)
{
//feedback script here
}A similar method can be applied to eliminate the software mapped control stuttering (caused by "delayed" custom MIDI message generated from the script feedback that moved the object in Lemur) by creating a custom expression which be used as "trigger" in the custom MIDI output which will be (if we want to map the x expression of the object):
t = z!=0?x:t