<div dir="ltr"><span style="font-size:12.8px">&gt; But sending a phase signal to drive cycle~ does</span><div><span style="font-size:12.8px">&gt; not anule the phase input at all! </span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I meant to say it does not anule the FREQUENCY input at all!</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-06-04 3:22 GMT-03:00 Alexandre Torres Porres <span dir="ltr">&lt;<a href="mailto:porres@gmail.com" target="_blank">porres@gmail.com</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">2017-06-04 2:46 GMT-03:00 Joel Matthys <span dir="ltr">&lt;<a href="mailto:jwmatthys@gmail.com" target="_blank">jwmatthys@gmail.com</a>&gt;</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="m_-1110496163877080299gmail-">
    <br>
    <br>
    <div class="m_-1110496163877080299gmail-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&#39;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&#39;t cyclone have some oscillators
    that work that way as well?</div></blockquote><div><br></div></span><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&#39;m suspecting it&#39;s happening in Chuck, and what you seem to be confirming to me.</div><div><br></div><div><br></div><div>







<p class="m_-1110496163877080299gmail-p1">Phasor<span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s2">p</span><span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s2">=&gt;</span><span class="m_-1110496163877080299gmail-s1"> </span>SinOsc<span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s2">osc</span><span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s2">=&gt;</span><span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s3">dac</span><span class="m_-1110496163877080299gmail-s2">;</span></p>
<p class="m_-1110496163877080299gmail-p2"><span class="m_-1110496163877080299gmail-s4">440</span><span class="m_-1110496163877080299gmail-s1"> </span>=&gt;<span class="m_-1110496163877080299gmail-s1"> </span>p.freq;</p>
<p class="m_-1110496163877080299gmail-p3">// 440 =&gt; osc.freq;</p>
<p class="m_-1110496163877080299gmail-p2"><span class="m_-1110496163877080299gmail-s4">1</span><span class="m_-1110496163877080299gmail-s1"> </span>=&gt;<span class="m_-1110496163877080299gmail-s1"> </span>osc.sync;</p>
<p class="m_-1110496163877080299gmail-p4"><span class="m_-1110496163877080299gmail-s4">4</span><span class="m_-1110496163877080299gmail-s2">::</span>second<span class="m_-1110496163877080299gmail-s1"> </span><span class="m_-1110496163877080299gmail-s2">=&gt;</span><span class="m_-1110496163877080299gmail-s1"> </span>now<span class="m_-1110496163877080299gmail-s2">;</span></p><p class="m_-1110496163877080299gmail-p4"><span class="m_-1110496163877080299gmail-s2"><br></span></p><p class="m_-1110496163877080299gmail-p4"><span class="m_-1110496163877080299gmail-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&#39;s frequency...</span></p><p class="m_-1110496163877080299gmail-p4">Now, if I uncomment the line &quot;// 440 =&gt; osc.freq;&quot;, nothing changes! As if the frequency input is anuled or something.</p><p class="m_-1110496163877080299gmail-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="m_-1110496163877080299gmail-p4">Now, that makes phase modulation extremely trivial and simple with cycle~</p><p class="m_-1110496163877080299gmail-p4">I know I&#39;m close to doing it in Chuck, If uncommenting that line in the code did work, I&#39;d be done with it, but I&#39;m stuck...</p><p class="m_-1110496163877080299gmail-p4">Is it really impossible to set both a frequency value and a phase input from another Unit Generator? </p><p class="m_-1110496163877080299gmail-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="m_-1110496163877080299gmail-p4"><br></p><p class="m_-1110496163877080299gmail-p4">cheers</p></div><div><br></div></div></div></div>
</blockquote></div><br></div>