• drdoom

    My pd's a bit rusty, so bear with me. I tried searching, but the results didn't help much.

    I want to monitor numbers coming off the audio input. How can I go about getting some kind of volume reading from the [adc~]?

    ie I want to have the input levels from my [adc~] open a spigot if they exceed a certain value.

    Thanks!

    posted in technical issues read more
  • drdoom

    I did a search on this, didn't seem to turn up anything. Forgive me if I missed it.

    I'm having trouble getting pd to read from my microphone jack. Every time I switch it from portaudio to jack, it crashes.

    I'm on a MacBook Pro with OSX 10.5.4 and pd 0.40.3.extended.

    Any help would be appreciated.

    posted in technical issues read more
  • drdoom

    Is there a way to keep track of how often the peaks from a .wav file read from a table from a [soundfiler] reach or exceed a certain value? (i.e. finding drum hits)

    posted in technical issues read more
  • drdoom

    I had the same problem, used pix_texture to fix it.

    However, I have a related question, how can I get the geometry to automatically size itself to the image? I saw somewhere in the help to try using zero, but that didn't seem to help... I feel rather silly for asking this, but at the moment, I'm stumped. (I've tried both [rectangle] and [square]).

    If it helps, my image is a large, long rectangle, 2415 x 311.

    posted in pixel# read more
  • drdoom

    Yes for both. It crashes no matter what. It seems to be a system error and could very well be no fault of Pd. (I'm mainly a PC guy so any system fix tips would also be helpful although I know this is the wrong place for it.)

    posted in technical issues read more
  • drdoom

    Looks like [bonk~] might do what I need. The input seems straight forward, but I'm a little hazy exactly how to use it's outputs to get it to count the number of hits in a given time frame. I assume that I would use the raw output? Is there a way I could get it to bang a number every attack?

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!