Hi Gasten, It was the miniAudicle. It was set for built-in in/out. 48000khz sample rate, 2 ch in, 2 ch out. They were same settings that I had used earlier that day, as far as I knew. I'm on a Macbook Pro Intel. I haven't ever seen it happen before or since and can't reproduce the effect on the command line. It was a troubling ten minutes, but it seems to have been fixed by restoring miniAudicle's default preferences, although they seemed to be defaulted already. There's really nothing to discuss about this until I can reproduce it, though. I'm not sure how to do that. It really took me by surprise. -Mike On Jan 20, 2008 5: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...

Cheers! mike

On Jan 19, 2008 12:23 PM, mike clemow 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 when this happened? mini or audicle? can you reproduce this behaviour on the command line? Version?

Thanks, Gasten

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

-- http://semiotech.org http://blog.deadlylittlepills.com http://www.murderkills.com http://shadowofaculture.blogspot.com

Yeah well, ok. But now we got it on record so we can do more testing next time someone gets here with this problem. peace, Gasten sön 2008-01-20 klockan 13:59 -0500 skrev mike clemow:

Hi Gasten,

It was the miniAudicle. It was set for built-in in/out. 48000khz sample rate, 2 ch in, 2 ch out. They were same settings that I had used earlier that day, as far as I knew. I'm on a Macbook Pro Intel. I haven't ever seen it happen before or since and can't reproduce the effect on the command line. It was a troubling ten minutes, but it seems to have been fixed by restoring miniAudicle's default preferences, although they seemed to be defaulted already. There's really nothing to discuss about this until I can reproduce it, though. I'm not sure how to do that. It really took me by surprise.

-Mike

On Jan 20, 2008 5: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...

Cheers! mike

On Jan 19, 2008 12:23 PM, mike clemow 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 when this happened? mini or audicle? can you reproduce this behaviour on the command line? Version?

Thanks, Gasten

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

I seem to remember.... but it's hazy.... that this is a error you get when ChucK's sample rate doesn't match the system's rate.

It seems that with both miniAudicle and the command line it doesn't seem to matter what I have my system sample rate set at. chuck --srate44100 foo.ck works as well as chuck --srate48000 foo.ck Currently my system is using 44100. Do I have the syntax right? Is chuck ignoring me or is my system ignoring Chuck? -Mike On Jan 20, 2008 2:40 PM, Kassen wrote:

On 20/01/2008, mike clemow wrote:

...

Hi Gasten,

It was the miniAudicle. It was set for built-in in/out. 48000khz sample rate, 2 ch in, 2 ch out.

I seem to remember.... but it's hazy.... that this is a error you get when ChucK's sample rate doesn't match the system's rate.

There are/were some more issues there, for example with systems that simply wait for what sample rate they get and adapt to whatever this is (some RME cards come to mind), the Mini had some issues there as well.

Maybe you could set it to be wrong on purpose and check whether you get the same error?

Hope that helps a little but don't attach too much value to it; I know I've seen the error before but can't remember for sure what the issue was.

Yours, Kas.

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

-- http://semiotech.org http://blog.deadlylittlepills.com http://www.murderkills.com http://shadowofaculture.blogspot.com

On Jan 20, 2008 4:50 PM, Kassen wrote:

Also, unless you are sure what you are doing and have a specific purpose for it I would stick to 44.1K. 48 is clearly better on it's own (it's more....) but the higher resolution isn't worth the artefacts of down-sampling if you ever decide to burn a CD of your work. Even established, professional and expensive packages often make of mess of that so I recommend sticking to CD quality and going to double or four times that if you need higher resolution for some purpose, and steering clear of 48 and it's multiples unless you are sure that's a good idea.

Well, that's good advice and I'll take that to heart, but mostly I was just befuddled by the error. It was also with miniAudicle, so I'm not sure about the extra '0's thing. I guess that if I encounter the issue again I'll pay more attention to what else is going on. It might have been that Audacity was also running, which may have monopolized the sound card. In fact I'll test that... Nope, that didn't reproduce the error. I tried setting the sample rate on both at different settings and times, and starting one before the other and vice versa. No dice. Audacity does make the Chuck VM hang, sometimes, however, so they clearly don't like each other. -Mike

Oh, well, let's hope it's gone now.

Kas.

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

-- http://semiotech.org http://blog.deadlylittlepills.com http://www.murderkills.com http://shadowofaculture.blogspot.com

Hi Mike, 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! spencer 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...

Cheers! mike

On Jan 19, 2008 12:23 PM, mike clemow 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 when this happened? mini or audicle? can you reproduce this behaviour on the command line? Version?

Thanks, Gasten

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