# Aftertouch problem

**URL:** <https://forum.cabbageaudio.com/t/aftertouch-problem/699>\
**Category:** Csound Noobs\
**Created:** [6 September 2017 15:14 UTC](https://forum.cabbageaudio.com/t/aftertouch-problem/699 "2017-09-06T15:14:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![iainmccurdy](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/i/8baadc/32.png) [@iainmccurdy](https://forum.cabbageaudio.com/u/iainmccurdy)\
**Post date:** [6 September 2017 16:09 UTC](https://forum.cabbageaudio.com/t/aftertouch-problem/699/3 "2017-09-06T16:09:07Z")

</div>

I haven’t used aftouch in a long time but I give it a go when I get to a keyboard with aftertouch.  
An alternative approach would be to read the data in using midiin and filter into the aftertouch data by using its status byte and channel (I can’t remember what the status byte for aftertouch will be but you could easily test to find out what this is by using midiin and print messages.

The status byte value appears to be 208 so you can try this and see if it works any better:

```
 kstatus,kchan,kdata1,kdata2	midiin
 if (kstatus==208 && kchan==1) then
  kAftouch	=	kdata1
 endif
 printk2	kAftouch
```

---

_[View the full topic](https://forum.cabbageaudio.com/t/aftertouch-problem/699)._