• Audio

  • Unexpected trigger in Pd

On a different note, I'm also having a strange issue when running my code on the bela. Something is triggering a hi hat sample that has no possible trigger and it plays indefinitely... after about 5 seconds the bela stops responding.

Hmm what do you mean "has no possible trigger" ? What does the part of the patch that would trigger it look like? What block size are you using?

Ah I realized I had adc3 routed somewhere leftover from when I was running it through a different interface so I've gotten rid of the sound. I also just checked my block size and its 16 and I've brought it up to 1024 which is what I run in pure data but it still is crashing... I also get flashing red purple blue light on the board

flashing red light indicates the same as underrun detected. If this happens occasionally, e.g.: in response to specific events, then it could be a matter of excessive peak CPU usage. If it happens continuously, it would mean excessive average CPU usage. Now, it could be that the triggering is the cause for the underrun, or it could be that it's a consequence of it. You need to analyze your patch to figure that out.

  • saia replied to this.

    Just got this
    CPU time limit exceeded
    make: *** [runide] Error 152

    giuliomoro Okay. I think its both because it freezes on run, and then when I trigger via contact mic it plays sound for a second and then shuts off and says that message I just sent about CPU

      Then you'll have to reduce the CPU usage of your patch.