Hi Charles,<br><br>Thank you for your reply. Indeed, the maximum number of partitions is set to 256. I'll try to inscrease it when i have time (and when i've learned how to compile externals!).<br><br>Cheers,<br><br>
Pierre.<br><br><div class="gmail_quote">2013/2/17 Charles Z Henry <span dir="ltr"><<a href="mailto:czhenry@gmail.com" target="_blank">czhenry@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Sun, Feb 17, 2013 at 4:54 AM, Pierre Massat <span dir="ltr"><<a href="mailto:pimassat@gmail.com" target="_blank">pimassat@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br><br>While readin Katja's website i discovered the [partconv~] object from Ben Saylor's library. I had actually used it long time ago with some IR reverbs, but I then judged the latency to big to be usable live. <br>
I gave it another shot this morning, and realized that the partition size could be set in [partconv~]. A lower partition size reduced the latency to something usable, which is cool, but it also cuts the tail of the reverb (it sounds very unnatural will low partition sizes). <br>
<br>Could somebody please explain to me whether it is possible to fix this behaviour ?<br></blockquote><div><br></div></div></div><div>I believe there's a maximum number of partitions set in the code. You could just increase the number and re-compile.<br>
<br></div><div>Chuck<br></div></div></div></div>
</blockquote></div><br>