[L2Ork-dev] disis-munger~ latency

[Alberto Zin]

That makes sense. OTOH in a pure realtime setup, (I'm using a flute to
drive adc~) it has to be used carefully, I would say...
Best,
Alberto

Il 12/dic/2016 10:16 PM, "Ivica Bukvic" <ico at vt.edu> ha scritto:

> The latency depends on the window size. IIRC it is half of the full window
> size to allow for the desired data spread. E.g. by default it should be 1.5
> seconds on a 3-second buffer. Hope this helps.
>
> --
> Ivica Ico Bukvic, D.M.A.
> Associate Professor
> Computer Music
> ICAT Senior Fellow
> Director -- DISIS, L2Ork
> Virginia Tech
> School of Performing Arts – 0141
> Blacksburg, VA 24061
> (540) 231-6139
> ico at vt.edu
> www.performingarts.vt.edu
> disis.icat.vt.edu
> l2ork.icat.vt.edu
> ico.bukvic.net
>
> On Dec 12, 2016 15:38, "Alberto Zin" <alberto.zin at gmail.com> wrote:
>
>> Hello,
>>
>> a question not 100% related to pd-l2ork: I'd like to use disis-munger~
>> granular external in a live (i.e. realtime) setup, with adc~ as input to
>> it.
>> What is the latency introduced by the external? I suppose it should be
>> the internal buffer size. SInce I want to create crossfades between
>> dry/wet signals, latency compensation of the dry should be done with some
>> z^-n ...
>>
>> Thanks,
>>
>> Alberto
>>
>> --
>> http://sites.google.com/site/albertozin/
>> 47 41 4d 45 20 4f 56 45 52
>>
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> http://disis.music.vt.edu/listinfo/l2ork-dev
>>
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20161213/e8ca7ddd/attachment.html>