<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-06-04 2:46 GMT-03:00 Joel Matthys <span dir="ltr"><<a href="mailto:jwmatthys@gmail.com" target="_blank">jwmatthys@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><span class="gmail-">
<br>
<br>
<div class="gmail-m_8988267472488998947moz-cite-prefix">On 06/04/2017 12:35 AM, Alexandre
Torres Porres wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">It seems that when you have a phase
input to SinOsc, it'll only consider that input and disregard
any frequency input, is that possible?
<div class="gmail_quote">
<div><br></div></div></div></div></blockquote></span>
Yes, that is correct. IIRC, doesn't cyclone have some oscillators
that work that way as well?</div></blockquote><div><br></div><div>The only oscillator with a phase input in cyclone (or max) is cycle~</div><div><br></div><div>it has a frequency input in the left inlet and a phase input in the right inlet.</div><div><br></div><div>But sending a phase signal to drive cycle~ does not anule the phase input at all! And this is what I'm suspecting it's happening in Chuck, and what you seem to be confirming to me.</div><div><br></div><div><br></div><div>
<p class="gmail-p1">Phasor<span class="gmail-s1"> </span><span class="gmail-s2">p</span><span class="gmail-s1"> </span><span class="gmail-s2">=></span><span class="gmail-s1"> </span>SinOsc<span class="gmail-s1"> </span><span class="gmail-s2">osc</span><span class="gmail-s1"> </span><span class="gmail-s2">=></span><span class="gmail-s1"> </span><span class="gmail-s3">dac</span><span class="gmail-s2">;</span></p>
<p class="gmail-p2"><span class="gmail-s4">440</span><span class="gmail-s1"> </span>=><span class="gmail-s1"> </span>p.freq;</p>
<p class="gmail-p3">// 440 => osc.freq;</p>
<p class="gmail-p2"><span class="gmail-s4">1</span><span class="gmail-s1"> </span>=><span class="gmail-s1"> </span>osc.sync;</p>
<p class="gmail-p4"><span class="gmail-s4">4</span><span class="gmail-s2">::</span>second<span class="gmail-s1"> </span><span class="gmail-s2">=></span><span class="gmail-s1"> </span>now<span class="gmail-s2">;</span></p><p class="gmail-p4"><span class="gmail-s2"><br></span></p><p class="gmail-p4"><span class="gmail-s2">In the above code, I have a Phasor driving the oscillator, and the same result as if I had a SinOsc with the same frequency as the Phasor's frequency...</span></p><p class="gmail-p4">Now, if I uncomment the line "// 440 => osc.freq;", nothing changes! As if the frequency input is anuled or something.</p><p class="gmail-p4">Going back to cycle~, the two input are valid, and the result is that the output frequency is 880 hz (the sum of both inputs).</p><p class="gmail-p4">Now, that makes phase modulation extremely trivial and simple with cycle~</p><p class="gmail-p4">I know I'm close to doing it in Chuck, If uncommenting that line in the code did work, I'd be done with it, but I'm stuck...</p><p class="gmail-p4">Is it really impossible to set both a frequency value and a phase input from another Unit Generator? </p><p class="gmail-p4">If not, then adding a signal to the Phasor output has got to do the job. But how can you do that?</p><p class="gmail-p4"><br></p><p class="gmail-p4">cheers</p></div><div><br></div></div></div></div>