ssalazar at CS.Princeton.EDU
Sun Jan 20 20:18:59 EST 2008
Indeed, if you could provide console log + chuck --probe information
when this happens in the future, thats the best way to get to the root
of the problem-- saving other folks from this bug and helping
developers get to the bottom of it.
miniAudicle does have some intermittent issues properly starting the
audio subsystem, that are cured by opening the preferences window and
then closing it. These issues don't affect chuck proper, because the
bug is in miniAudicle code. Given the existence of previous bug
reports of this nature, and without any additional information on your
particular issue, I would reckon that you are seeing this very
problem. Anyways sorry that this affected you at such a crucial
moment, and glad you got it fixed!
On Jan 20, 2008, at 2:24 AM, Martin Ahnelöv wrote:
> lör 2008-01-19 klockan 12:26 -0500 skrev mike clemow:
>> Fixed, although I have no idea how. I reset the preferences to
>> defaults, but the sound card (built in mac in/out) is the same as it
>> was. Nothing changed.)
>> That's a very strange glitch...
>> On Jan 19, 2008 12:23 PM, mike clemow <gelfmuse at gmail.com> wrote:
>>> I'm suddenly, for no apparent reason, getting this error:
>>> [Untitled]:line(1): ugen's of type 'DAC' have no input - cannot =>
>>> from another ugen
>>> my patch is:
>>> SinOsc s => dac;
>>> 2::second => now;
>>> Any hints here? This is... just... wrong.
> What kind of card/mac do you have? how were the settings configured
> this happened? mini or audicle? can you reproduce this behaviour on
> command line? Version?
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users