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.

rs

On Thursday, October 30, 2014, Robert Poor <rdpoor@gmail.com> wrote:

> Recently, i found that I have to turn audio on, otherwise the timing runs way too fast.

That's a feature, not a bug! :)  What's going on is that ChucK uses
the DAC's clock for timing.  When you run without audio, ChucK simply
runs as fast as possible, which is great, for example, when you're
writing complex audio to a sound file.

- Rob


On Thu, Oct 30, 2014 at 7:28 AM, Ryan Supak <ryansupak@gmail.com> wrote:
> Recently, i found that I have to turn audio on, otherwise the timing runs
> way too fast. (Only an issue, I guess, if you're needing it to be accurate
> and not just fast.)
>
> rs
>
>
> On Thursday, October 30, 2014, Forrest Curo <treegestalt@gmail.com> wrote:
>>
>> As I understand it, you send some number to 'now'
>> and for that length of time the confuser will continue to run whatever
>> oscillator instances you've started, then go on through your code.
>>
>> So if you only used it to generate values to trigger voices and changes in
>> other software, you could run Chuck without much overhead?
>>
>> Is this right, and how can I minimize that overhead?
>>
>> [Forrest Curo
>> San Diego]
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users@lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users