Post by lukesleepwalker on Sept 16, 2018 22:59:44 GMT
Great, thanks for this. In a situation where I'm using an XY pad and converting CC values to notes, is there a way to filter multiple notes that are generated by the width of a finger? That is, is there a smart way to calculate the middle value of incoming CC values and generate a single note that's roughly in the middle? Doesn't have to be precise...
Post by lukesleepwalker on Nov 11, 2018 19:47:47 GMT
Hi Nic, It has been a while, but I have read through the thread with Josef and it is going way over my head. I have a single axis that I am working on, which is essentially the X axis in Josef’s use case. I am successfully converting CC7 value to notes using this, as you suggested:
BX 07 = 9X X3 50 +C BX 07 = 8X X3 00 +C +D500
But, it sounds terrible because I get several notes at a time, as previously reported. Are you suggesting that I need a sub-array to create a single “averaged” note from the several that result from my fat finger on the X pad?
Hmm, this was from quite some time ago. I'll have to check, but I think we added code to ignore CC values 'close by' to the currently sounding note. Let me get back to you tomorrow and see if I can come up with a cunning plan for this.
Post by lukesleepwalker on Nov 11, 2018 23:46:07 GMT
Thanks for the quick reply, Nic. Is that supposed to replace everything I have so far? If so, it does nothing. I just get CC7. If added to the CC to note conversion, I can't detect much difference. Still get multiple adjacent notes. Copy/paste and install rules.
Post by lukesleepwalker on Nov 12, 2018 13:40:59 GMT
The great news is that this works and delivers predictable results! The only downside is that it creates a bit of a gated effect when holding a note and even when playing rapid notes. I'd like to play with the time interval but I'm afraid I don't see the interval stored in K1. Can you point that out to me?
Post by lukesleepwalker on Nov 12, 2018 16:34:43 GMT
Right on, thank you. Playing with the interval allows for different approaches to responsiveness with the pad, which is great! Two further questions:
1. Is there a way to easily constrain the note range? Right now I've got 127 notes so it's hard to get "precise". Is there an easy way to limit it to C1 to C2 (for instance)?
2. Is there a way to not get the arp/gated effect when I hold my finger on a note? It would be better if, when I held my finger down on the surface it sustained the note, rather than getting the arp'd/gated effect I'm getting now.
Thanks for your help. I'm certainly getting better results than I've ever gotten from this pad, so appreciate it greatly!
1. Yes, we can constrain the notes. We could scale the CC's value to a note range for example.
2. The gate effect is the fixed note length and a retrigger - if we knew when you released your finger that would help solve all of that... Does this pad generate a CC with zero value when you release your finger?