# Non-responsive pads and clipping audio

**URL:** <https://backstage.polyend.com/t/non-responsive-pads-and-clipping-audio/16246>\
**Category:** Archive\
**Tags:** synth, needs-info\
**Created:** [November 23, 2024, 11:59pm UTC](https://backstage.polyend.com/t/non-responsive-pads-and-clipping-audio/16246 "2024-11-23T23:59:07Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![Sandroid](https://backstage.polyend.com/user_avatar/backstage.polyend.com/sandroid/32/172_2.png) [@Sandroid](https://backstage.polyend.com/u/Sandroid)\
**Post date:** [December 6, 2024, 1:25pm UTC](https://backstage.polyend.com/t/non-responsive-pads-and-clipping-audio/16246/20 "2024-12-06T13:25:36Z")

</div>

I think we should change this bug report to focus on the non-responsive pads.

As @charlesreeves, mentioned we have a lot of detail regarding audio distortion/clippin in that **[other report](https://backstage.polyend.com/t/synth-audio-drops-out-in-what-sounds-like-bit-rate-distortion/16535)**.

I’m still trying to find a reproducable case regarding pads not becoming responsive.

I can confirm that this has happened to me before as well, but i’m unable to reproduce this reliably. I thought at first it was a idle time _thing_. So yesterday i left the device running for 5+ hours to see if it would become unresponsive at some point. But no dice.

Does anyone else have something reproducable?

---

_[View the full topic](https://backstage.polyend.com/t/non-responsive-pads-and-clipping-audio/16246)._