[PD] Delay (msec) option in audio properties
danomatika at gmail.com
Thu May 16 13:31:24 CEST 2019
Is this in the Pd Manual somewhere? Could be a good point to add to future questions.
> On May 16, 2019, at 12:00 PM, pd-list-request at lists.iem.at wrote:
> From: Mario Buoninfante <mario.buoninfante at gmail.com <mailto:mario.buoninfante at gmail.com>>
> To: Miller <msp at ucsd.edu <mailto:msp at ucsd.edu>>
> Cc: pd-list <pd-list at lists.iem.at <mailto:pd-list at lists.iem.at>>
> Subject: Re: [PD] Delay (msec) option in audio properties
> Message-ID: <prv0jfua425kbuby0250gq1e.1557925987966 at email.android.com <mailto:prv0jfua425kbuby0250gq1e.1557925987966 at email.android.com>>
> Content-Type: text/plain; charset=utf-8
> Hi Miller,
> Thanks a lot for the explanation.
> -- Electronic Musician, Creative Coder, QA Engineer https://vimeo.com/creativecodingsalerno <https://vimeo.com/creativecodingsalerno>http://mbuoninfante.tumblr.com <http://mbuoninfante.tumblr.com/> https://github.com/mariobuoninfante <https://github.com/mariobuoninfante> https://bitbucket.org/mariobuoninfante <https://bitbucket.org/mariobuoninfante>
> On 14 May 2019 5:39 pm, Miller Puckette <msp at ucsd.edu <mailto:msp at ucsd.edu>> wrote:
>> Rough explanation: Pd sets up two FIFOs, one for audio input and one for
>> output, and "delay" sets the length of those FIFOs. I/O is managed so that
>> (in theory at least) the sum of the number of sample frames in the input
>> and the output FIFOs add up to the "delay", plus or minus one 64-saple block.
>> So theoretically at least, the total delay from audio input to output should
>> be the sum of three things: this number, the OS's internal audio latency
>> (which depends on all sorts of factors) and the A/D/A devices.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list