Author |
Topic: 2 arguments for a event (Read 824 times) |
|
Jens_H
New Member

 MIDI-OX Rules!
Posts: 1
|
 |
2 arguments for a event
« on: Jan 9th, 2005, 1:42pm » |
Quote Modify
|
I need this: Then a#2 is note on, and controller #4 = 0-20 then note on A3 Then a#2 is note on, and controller #4 = 20-40 then note on B3 and of cource note off again, (remember that the controller #4 may change value then the noteoff come, but it will be acceptable if both A3 and B3 gets note off every time A#2 note off accurs. It's for control off hihat pedal to differrent samples, and stil have velocety for each samples.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: 2 arguments for a event
« Reply #1 on: Jan 9th, 2005, 4:46pm » |
Quote Modify
|
What you are requesting would require MIDI-OX to have a state history of all received events at the low-level mapping stage. Unfortunately it does not. The best you might do is to have CC #4 actually trigger A3 and B3.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
Peter L Jones
Expert
    

Hit it
Gender: 
Posts: 978
|
 |
Re: 2 arguments for a event
« Reply #2 on: Jan 9th, 2005, 7:39pm » |
Quote Modify
|
A good sampler - say, rgc:audio's sfz - has this kind of thing built in. You can use the CC value to pick which sample is triggered for the note (as well as velocity sensitivity).
|
|
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
|