Jeremie

That should be really easy but I'm stuck for hours :

I receive int numbers from a midi keyboard.

I just need a bang when I receive 24. I tried select 24, route 24 and if $i1 == 24 then bang, but every time that bang for every number.

There is no difficulties, I really don't understand what's wrong...

Hi,
That should be really easy but I'm stuck for hours :
I receive int numbers from a midi keyboard.
I just need a bang when I receive 24. I tried select 24, route 24 and if $i1 == 24 then bang, but every time that bang for every number.
There is no difficulties, I really don't understand what's wrong...
Thanks for your help.


bang-when-int-24

Thanks but I've already try sel and that don't work.

I think the problem come from midiselect because I have the same problem with sel, route and if (bang for every value)

However, midiselect seems to send normal int values...

Hi,
Thanks but I've already try sel and that don't work.
I think the problem come from midiselect because I have the same problem with sel, route and if (bang for every value)
However, midiselect seems to send normal int values...
I dont understand.


[sel] works perfectly. You attached nearly empty patch (there is only one numberbox in it...), so we can't help you... but... if you are using [midiselect] you have to handle lists (not single ints) from outlets 1, 2 and 3.

Your patch works fine on my computer. I sent some MIDI notes from external sources and note 24 (C0) on channel 3 is triggering bangs (via if, sel and route). Are you sure, you are really sending MIDI notes on channel no. 3 to your patch?

Your patch works fine. Your mistake is the connection from the [umenu] to [midiin].

You should connect the middle outlet of [umenu] to [midiin], else the [umenu] send just a number which the [midiin] doesn't understand.

[midiin] works with names of the midi devices, not indexes.

Your patch works fine. Your mistake is the connection from the [umenu] to [midiin].
You should connect the middle outlet of [umenu] to [midiin], else the [umenu] send just a number which the [midiin] doesn't understand.
[midiin] works with names of the midi devices, not indexes. 

Thank you for your answers but it still doesn't work...

I have a session in Live 9 which send me 4 values : 24, 26, 24 and then 36.

the second 24 bangs the oulets 1 and 2 (!!)

When I change the values from Live, I faced similar problems.

Thank you for your answers but it still doesn't work...
I have a session in Live 9 which send me 4 values : 24, 26, 24 and then 36.
[If] bang every time.
For [Selet 24 26] and [Route 24 26]
24 bangs the oulets 1 and 3
26 bangs the oulets 1 and 2
the second 24 bangs the oulets 1 and 2 (!!)
36 bangs the oulets 1 and 3

When I change the values from Live, I faced similar problems.


It means that besides expected noteon/noteoff messages your session is sending something else. Print upcoming MIDi data to console to investigate the problem.

Well seen : Live send me 2 values simultaneously, the new and the older.

Messages box just show me the new value but when I print, I can see that.

Well seen : Live send me 2 values simultaneously, the new and the older.
Messages box just show me the new value but when I print, I can see that.
I'm going to look for what's going on.
Thanks a lot.


But this is very strange... are you sure, this is not something related to noteon/noteoff pair?

bang when int = 24