athierauf

Hi, I know there have been many posts about tapin/out but so far I haven't found any that deal with my specific issue. When using tapin/out with adc~ I get a strange fuzzy noise, probably distortion? every 167 seconds or so. The first time I noticed this I was using several tapin/out objects so I assumed that I was just overloading the system or playing too loud so I tried it with just one instance of tapin/out and playing softly yet had the same results. I've been experimenting trying to find the possible cause, changing number of instances, having feedback/ not having feedback, scaling down the incoming signal, etc. No change, it always happens about every 167 seconds (sorry to be so obscure with the time but I was using a foot pedal to time it) Does anyone have any suggestions? I'm running on 4 gigs of RAM at the moment so that is probably the culprit...but I haven't tried it on another computer with more/ less RAM so not sure... but any other ideas? Thanks!

Hi, I know there have been many posts about tapin/out but so far I haven't found any that deal with my specific issue. When using tapin/out with adc~ I get a strange fuzzy  noise, probably distortion? every 167 seconds or so. The first time I noticed this I was using several tapin/out objects so I assumed that I was just overloading the system or playing too loud so I tried it with just one instance of tapin/out and playing softly yet had the same results. I've been experimenting trying to find the possible cause, changing number of instances, having feedback/ not having feedback, scaling down the incoming signal, etc. No change, it always happens about every 167 seconds (sorry to be so obscure with the time but I was using a foot pedal to time it) Does anyone have any suggestions? I'm running on 4 gigs of RAM at the moment so that is probably the culprit...but I haven't tried it on another computer with more/ less RAM so not sure... but any other ideas? Thanks!


tapinout-overloading

Something of a wild guess, but that's getting close to the point where the floating-point representation of time in samples can hit a precision barrier. Exactly where precision starts to become an issue depends on the sample rate and the size of the floating point representation. Are you using 32- or 64-bit Max? (And even if you're using 64-bit Max, there is a slight chance that the internal tapin~/tapout~ interface might still rely on 32-bit floats, although that seems less likely). And at 44.1 kHz you ought to get about double the value you're talking about before you hit a precision wall.

Maybe try a different sampling rate and see if that affects the delay you can use before getting that "fuzzy noise"?

Tapin~/out~ overloading