Page 1 of 1

Midi "NOTE OFF" interpretation

Posted: Thu Nov 27, 2008 10:15 am
by zoophar
Hello there,
trying to do thing with MIDI and M8

but can't have a NOTE OFF signal... in M8

tried with pure data / then a MIDI hardware by Roland /
>while the midi Monitor.app shows me NOTE OFF
>M8 sees it as param['param2'] =0

How can i make M8 see the REAL: NOTE OFF msg to set a button OFF
(and not from the param['param2'])... beacause it's not the way we use to do it...

CHEERZ

Posted: Tue Dec 02, 2008 10:45 am
by zoophar
Hello myself how do i do?

It's like that...
it's the second way of sending NOTE OFF:
NOTE ON message with velocity 0

this method is legal by the MIDI specification....

have a nice day myself....

I have the same problem

Posted: Wed Apr 01, 2009 5:22 pm
by markvomton
Hello, i want to try Layer on/off via midi,(ableton live7) but i can not send midi note on with velocity 0.
How it is possible to make a layer off?

Posted: Wed Apr 01, 2009 7:31 pm
by zoophar
hello markvomton ;-)
this is a note concerning how some applications understands midi NOTE OFF..

I think you could just send a normal NOTE OFF from Ableton,
and see how it is understood in M8: you should see param['param2']=0 (this is the velocity)
>while the midi Monitor.app shows me NOTE OFF
>M8 sees it as param['param2'] =0


if you are mapping midi via the interface (menu map midi keys) you shouldn't care about anything.... m8 just takes all in charge...
1)in M8: just select the knob you want to map,
2)in Ableton: send your midi signal.. NoteOff and NoteOn are automatically handled... and you shoud see the channel/note written on the knob in M8...

hope i was understandable,
if not, just say it i will try another way to explain

PS: Have fun ;-)

Posted: Fri Apr 03, 2009 12:28 pm
by david
Hello Zoophar,

zoophar wrote:Hello myself how do i do?

It's like that...
it's the second way of sending NOTE OFF:
NOTE ON message with velocity 0


Modul8 is receiving the NOTE OFF midi message

A module that do (in DirectEvent) :
print type, param;

gives

MIDI {'timestamp': 14513855337059.0, 'channel': 1, 'param1': 2, 'message': 'NOTE_ON', 'rawEvent': 144, 'param2': 64}
MIDI {'timestamp': 14514003451505.0, 'channel': 1, 'param1': 2, 'message': 'NOTE_OFF', 'rawEvent': 128, 'param2': 64}

So you should be able to write a Module to handle this toggling issue (not supported by current MIDI mapping).

Best regards

Posted: Fri Apr 03, 2009 7:58 pm
by zoophar
thank you David,
for me it was ok since i answered to myself...
i wrote this because i discover (googling) it was legal to have a noteOff that is understood like: "noteOn with velocity=0"
it's maybe the device (or app) that sends the message that way,
(like french and suisse-romand: ex: 90 == nonante or quatre-vingt-dix... but's its the same...it just depends your sleng...)
in my case: Modul8 recieves messages from PureData...

i am now writing a module to monitor the midi signals:
':arrow:' see the incoming midi signals in a "view window"
a rect for each note in an XY table...

':arrow:'send some of the sgnals trougth sharedDict() (send the "mapped" notes, the wanted ones, they appear in a different color...)
(little Prob: dont' know how to clear the sharedDict() )

':arrow:' another piece of module
(more a brick of module to do wat you want...)
Get the selectionned sharedDict()message...
(selection is made trough a list of all the sharedDict() keys)
it could be something like a "esaySharedDict()" thing. to copy-paste in a module with a real function...

still in beat version,
if some of you want to test it or are interested, just drop an email ;-) and let's go !!!

just send some feedback please