sorry mas modulator and not carrier.<br><br>Thats right. It doesnt loop all the time. Only when the <u>modulator</u>
diverges in small amount from an intire multiple of the carrier
frequency, but that is FM matters, not [tabosc4~].<br><br><div class="gmail_quote">2010/1/26 mami music <span dir="ltr"><<a href="mailto:mami.music@gmail.com">mami.music@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all and thanks<div class="im"><br><br>2010/1/26 cyrille henry <span dir="ltr"><<a href="mailto:ch@chnry.net" target="_blank">ch@chnry.net</a>></span><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
mami music a écrit :<div><a href="https://mail.google.com/mail/?shva=1#inbox/1266c7380e4f9473" target="_blank">https://mail.google.com/mail/?shva=1#inbox/1266c7380e4f9473</a><div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey cyrille thanks for your answer. But it didn`t quite work.<br>
Im dinamicaly feeding the table with a signal,<br>
</blockquote></div></div><div class="im">
hum,<br>
you can sync this with bang~</div></blockquote><br>
yes yes!!! [bang~] was the object i was missing.<br><br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
so the 256th sample of the signal changes at block speed and the writing of the 257th and 258th sample is done at control speed. (please check attached patch)<br>
</blockquote></div>
if you change the table use by tabosc~, you should expect to have some click anyway.<br>
moreover, your table did not loop, so don't exepct a clean sound...</blockquote></div><div>Thats right. It doesnt loop all the time. Only when the carrier diverges in small amount from an intire multiple of the carrier frequency, but that is FM matters, not [tabosc4~].<br>
</div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I used an [until 44] to see if i could make up for the differences in the signal time, bit still not working<br>
<br>
Ill check the nusmuk external to see how it works, but definitely would be glad to make it in vanilla.<br>
</blockquote></div>
i can understand that.<br>
but delay~ is not in vanilla.<br></blockquote></div><div>wao wao!!! had always used it without checking its origin in the help file.... you ar absolutely right!!!<br><br><br>Another question rises now:<br>When the signal inside the array cant loop at the block~ frequency is there a windowing method any would recomend to try to smooth things out (obviously there would be distortion). <br>
Maby having two [tabosc4~] one with phase shift of 180 degrees in relation with the other with some sort of windowing... but i guess that would be equivalent as making the blocksize bigger....<br><br>Thanks again!!!<br></div>
</div>
</blockquote></div><br>