<div dir="ltr">Stefan: kinda what I figured at any rate (lol). Turning on the soundcard worked fine for me in the end.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 10:48 AM, Stefan Blixt <span dir="ltr"><<a href="mailto:stefan.blixt@gmail.com" target="_blank">stefan.blixt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>If you have ever tried implementing some kind of stable timing in programming languages like Java, you may have gotten a feel for the kind of black magic that is needed to get that sort of thing to work. The clocks in a computer that don't deal with audio are either too imprecise for music purposes, or hidden inside hardware that is keen to keep its clock private so it will work properly.<br><br>One of the great features of ChucK is that it hardwires its timing system to the audio interface clock, making it as stable as possible. It's probably too much work and out-of-scope to implement timing without available audio hardware in ChucK.<br><br></div>/Stefan<br><div> </div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 3:57 PM, Forrest Curo <span dir="ltr"><<a href="mailto:treegestalt@gmail.com" target="_blank">treegestalt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Umm, if I left audio 'on' but simply didn't generate any of it through Chuck?<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 7:33 AM, Ryan Supak <span dir="ltr"><<a href="mailto:ryansupak@gmail.com" target="_blank">ryansupak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There you have it. :) Would love a flag or option that doesn't force me to have a sound card to get accurate timing though.<span><font color="#888888"><div><br></div></font></span><div><span><font color="#888888">rs</font></span><div><div><span></span><br><br>On Thursday, October 30, 2014, Robert Poor <<a href="mailto:rdpoor@gmail.com" target="_blank">rdpoor@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Recently, i found that I have to turn audio on, otherwise the timing runs way too fast.<br>
<br>
That's a feature, not a bug! :) What's going on is that ChucK uses<br>
the DAC's clock for timing. When you run without audio, ChucK simply<br>
runs as fast as possible, which is great, for example, when you're<br>
writing complex audio to a sound file.<br>
<br>
- Rob<br>
<br>
<br>
On Thu, Oct 30, 2014 at 7:28 AM, Ryan Supak <<a>ryansupak@gmail.com</a>> wrote:<br>
> Recently, i found that I have to turn audio on, otherwise the timing runs<br>
> way too fast. (Only an issue, I guess, if you're needing it to be accurate<br>
> and not just fast.)<br>
><br>
> rs<br>
><br>
><br>
> On Thursday, October 30, 2014, Forrest Curo <<a>treegestalt@gmail.com</a>> wrote:<br>
>><br>
>> As I understand it, you send some number to 'now'<br>
>> and for that length of time the confuser will continue to run whatever<br>
>> oscillator instances you've started, then go on through your code.<br>
>><br>
>> So if you only used it to generate values to trigger voices and changes in<br>
>> other software, you could run Chuck without much overhead?<br>
>><br>
>> Is this right, and how can I minimize that overhead?<br>
>><br>
>> [Forrest Curo<br>
>> San Diego]<br>
><br>
><br>
> _______________________________________________<br>
> chuck-users mailing list<br>
> <a>chuck-users@lists.cs.princeton.edu</a><br>
> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
><br>
_______________________________________________<br>
chuck-users mailing list<br>
<a>chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
</blockquote></div></div></div>
<br>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Release me, insect, or I will destroy the Cosmos!
</font></span></div>
<br>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br></blockquote></div><br></div>