How to make an 8x8 Pad to behave like a keyboard but remappe

[electrofux]

Ha, Softcore was right. changing Pitch from x*layout to layout did the trick. I still havn't really understood why but now it is working.
Sweeet.

[electrofux]

Working like a charm now. Thx guys, this just saved me 14% space of a 104% template.

[Macciza]

Hi
There does seems to be some weirdness going on with the array . . . .
I was able to end up with your problem but not sure how or why . . .
Somehow the notes array ends up reporting 0's instead of the correct values hence improper response

The difference between layout and x*layout should not affect the end result ....
Glad you got it going, you can always enter the array straight into pitch field as well
Have sent in a report on the issue ...
MM

[Softcore]

@macciza

case 1: pitch = x * layout

Consider user tapping at pad x[3].....the pitch x[3] * layout[3] = 1 * layout[3] = layout[3] (intended note on) is send as note on. (all the rest pitches of "x * layout" are not triggered, because the x triggers heave steadily remained 0 - NOTE: NOT because xs are 0, but because they remained so, during the process)

Consider the user letting go of x[3] the pitch x[3] * layout[3] = 0 * layout[3] = 0 (!= layout[3], NOT intended note off) is send as note off. (x[3] previously being 1, now goes to 0 so it triggers)

case 2: pitch = layout

Consider user tapping at pad x[3].....the pitch layout[3] (intended note on) is send as note on. (all the rest pitches of "layout" are not triggered, because the x triggers heave steadily remained 0)

Consider the user letting go of x[3] the pitch layout[3] ( intended note off) is send as note off. (x[3] previously being 1, now goes to 0 so it triggers)

Cancel your report - works as designed!

[Macciza]

Hi
It worked fine for me with it like that to start... but i follow what you say

There is still some sort of error with arrays which can give failure even using layout array
Report stands its just not what you think it is....

Also had to raise a report from Editor weirdness discovered via the LiveKnobs project
Have also picked up one or two other strange Canvas behaviours . . .

cheers
MM

[electrofux]

I found i would like to get the output of the Padgrid in a (to be programmed) arpeggiator. I think to be able to do this, i must convert the custom Midi to a common script with noteout(). And there the problems start again, since i can't just translate the values of the custom midi fields (Pitch:layout, (notrigger), Velocity: Pads.x (notrigger), trigger:x (any)) to a normal noteout message. At least that doesnt work.
Any good ideas how to do this in a lean way?

[electrofux]

Wow, this blows my mind . fourth version of the noteon script and something is always going wrong and i haven't even cared for the noteoff.
These arrays are tricky to tackle.
In one version i had the script spitting out the newly pressed key of any number of pressed keys and i thought i made it but when i hit keys simultaneously everything was garbage.

Damnit, got the noteoff right until i found out that when you swipe notes, no pad release is triggered :/

I give up for today