Problems Assigning KeyStrokes to Pads

Hi everybody,

New to this forum here, and also to Bome, I've read all the stuff in the manual and Stray's post on this forum but I still can't seem to figure this one out;

Yesterday I set up two pads on my controller to send key-strokes "tab" and "shift + tab", and it worked beautifully!
However, today I experimented some more and suddenly I broke it somehow.
Now the first pad still does it's tab function, but the pad that should Shift+tab also does a normal tab function (Switching between session and arrange in Ableton)
It seems like it doesn't listen to the shift anymore, or that they are fired in the wrong order, I feel like I've tried everything but I can't seem to make it work.

I think one of the main reasons i'm having a hard time programming this is that the pads send all sorts of messages I don't want every time, like aftertouch.
I can only globally disable aftertouch on all of the pads, which I don't want, is there a way to filter these messages out with the "Rules" section, or should it not be a problem if I choose the correct note on message as input?

I've attached the preset that I made in the images, maybe someone can easily spot what I'm doing wrong, should I use a delay for the tab key maybe?
Come to think of it, it would be even better to have shift+tab with high velocity values and normal tab with values lower then 100.
Can i do that by just using rules? I read that it's often better to add more rules instead of translators but I'm still a bit unsure on how to use these.

Thank you all!
Jor

Hi jorgalad

We have all been seeing issues with keystroke combinations, unfortunately. There are ways to mitigate that, though, using timers. Instead of disabling aftertouch globally, which you don't want to do, can you remove velocity sensitivity on individual pads so they only trigger with a full velocity 127 message? If so we can make some easy translators which should pass data. If they are sending aftertouch, though, how does that message look? As far as I am aware, it should not trigger these translators.

The first step is to try to get rid of any extra messages being sent, and we'll use a timer for the Shift + Tab message. Let me know if this works.
Let me know if that works.
J

Hi J,

Thanks for the fast reply, and glad to hear I'm not the only one experiencing this problem (thought my MIDI controller was broken).
Unfortunately it is still not working, i've attached some screenshot again just to make sure there are no user errors involved.

I've set the velocity for that pad on a fixed 127 and did some testing, and it seems like there is some weird stuff going on, for example when I hit the pad very briefly it will send multiple note on of messages with one hit, is this normal?

Thanks again for the help!
Jor

The missing files

Allright, I've got it working now using a delay on the shift up key
I've used This website to see what the shift key does, this really helped me visualize the process.
Then I've set it up with 3 translators, one is the tab key, just a normal translator and the other two are for the shift.
So first I press the shift down, just like you would on a keyboard, and then I press the tab key (another pad).
The shift up automatically sends 1 second later, so this gives me 1 second to press the tab key, which is probably a bit too much, so i will change that to .5 seconds.

It's not a fancy solution but it works for now, if anyone has a better idea I'd be very happy to hear about it!