newbie help! Visual feedback!

[devilwidget]

Hello, and thank you in advance!
I am trying to do something I imagine to be incredibly basic, but failing...

I want to set up a series of pads or switches that light up when triggered by an external keyboard (easy enough) BUT then un-light when the key is released. I have gone through the manual and am now pulling my hair out. Surely it has something to do with making note on velocity retrigger the pad/switch light when it reaches 0... but what... arrgghhhh!!

Any help, and anyone who can point to any more useful tutorials than those on the lemur website would be forever a legend in my mind.

Thanks

Daniel

p.s. sorry if this topic has been asked elsewhere - I have looked but couldn't find it.

[Phil999]

the pad should 'un-light' automatically when the keyboard key is released. It should even light up according to the velocity level (didn't know that, what a surprise!).

Maybe you can post your template so we can see where the error might be.

[devilwidget]

Hello and thanks for getting back to me so quickly!
I have uploaded a test file.
If I press a g sharp from my keyboard this pad will light... but will stay then forever lit unless I manually press is again inside of lemur.
Any ideas what I'm doing wrong?
thanks in advance

Daniel

test.jzml

(2.38 KiB) Downloaded 119 times

[Phil999]

your template works perfectly fine. Maybe your keyboard doesn't send note-off? I'm using a Cakewalk A500s.

You can check the output of your keyboard with a useful tool called MIDI-OX. Also, does the Pad object reflect the velocity value (more velocity, more red)?

[devilwidget]

hi there

midi keyboard is sending both note on and note off. even tried it with a vst keyboard. Velocity shows up fine. Light just stays on if triggered externally (if triggered inside of lemur by touching pad it goes off as it should).
Do I need to manually set the note off value in lemur? Might there be a global setting that is getting in the way?
Thanks for all your help - as you can imagine, this is very infuriating!

Daniel

[Phil999]

yes, I don't understand it. I can't think of a 'global' or any other setting. In Lemur, only the keyboard input is needed, the output can be left blank.

Therefore it must be something with the computer, although I can't imagine what. Try to test your template with a different computer.

[Macciza]

Hi Daniel
I also have it working fine receiving midi data from Max, so can confirm that the project operates correctly.

What type of keyboard is it you are using? What connection method and software setup? What did you use to confirm it's output?

Please try the attached project ^^MIDI-MON and get back to me with the results.

For normal operation we would expect to see note on velocity and noteon velocity = 0 for note offs.
The pad is set to respond to note number 60 - note -some keyboards used to number there notes 1 octave differently

[devilwidget]

hi there
thanks for getting back to me so quickly.
Well, Lemur is receiving note off (I got note on: 60,79 and note off: 60,0). But when I release the key of my external controller, the light in Lemur stays lit at whatever velocity it was at.
I am using a akai mpk 25, and also have tried triggering it from abletons drum pads. I have tried connecting to Lemur through the midi in of a alesis io dock, and also over wifi-midi from ableton (both connections were stable and unproblematic, except for the note off issue).
The light is supposed to go off when it receives note off externally, right? I'm not just being an idiot and Lemur doesn't actually support two-way visual feedback?
Confusing!
I haven't used Lemur before, nor am I particularly proficient with scripting (though I have nominal experience with max/msp and supercollider).
Any ideas where I'm going wrong?

best wishes

Daniel

[Macciza]

Hi Daniel

Therein lies the problem - note_on velocity-0 is generally used for note-off which is what Lemur does
Note_off messages are implemented by some manufacturers to provide a measure of how quickly a key is released . . .
If you add a script under your Pad called say pad_off set to execute on MIDI , Note Off , MidiTarget same as the other, 60 to 60(note), 1 to 16 (channel)

if (MIDI_ARGS) x=0;

This should then turn the pad off when Lemur receives noteOff 60 any velocity . . .
This is proof of concept - there may be better ways of implementing it in larger projects

I will raise the issue with the dev team and see if there is any update solution possible for this
But basically the way the objects work is to respond to the midi message they are assigned to
To get it to also listen to note_off messages will create issues - all note_off vals?? only 0?

Hope that helps

MM

[devilwidget]

You Sir, are a blimmin' legend.
Working now, thanks for the advice, and sorry for my ignorance!
Best wishes

D x