[PD] So [bang~] can't "bang" in less than 64 blocksize, huh?

Alexandre Torres Porres porres at gmail.com
Sat Mar 14 15:52:10 CET 2015


"*I assume that's what bang~ was designed for. It is not an 'audio rate*

*bang' but something that lets you get timing information from audio*
*blocks*"

but it doesn't work for blocks lesser than 64... can't bang at each 32, 16,
8, 4, 2, 1 block samples... this was unexpected to me and what made me
wonder about similar/parallel behaviours from other objects, which I also
found to exist.

cheers


2015-03-14 6:18 GMT-03:00 Peter P. <peterparker at fastmail.com>:

> * Alexandre Torres Porres <porres at gmail.com> [2015-03-14 06:02]:
> > I was trying to get a bang at every sample and found out that the minimum
> > time bang~ works is at the 64 blocksize, check attached patch.
> I assume that's what bang~ was designed for. It is not an 'audio rate
> bang' but something that lets you get timing information from audio
> blocks, eg. deriving a video playback frame rate in sync to an audio
> stream.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150314/b0bac7e1/attachment.html>


More information about the Pd-list mailing list