-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ge, Thanks for the response. Changing the sample rate did indeed work for me using jack, and that's all I need. It didn't solve the problem with alsa, however, and neither did restarting alsasound. I'm running gentoo linux using kernel 2.6.8-r3. My system is fine now, but I'm happy to do anything you need to help figure out the alsa problem. matt Ge Wang wrote: | | On Sep 11, 2004, at 9:04 PM, Matthew Shanley wrote: | |> Hi guys, |> |> I'm on a fresh linux box, and when I compile chuck 1.1.4.8 for either |> alsa or jack, it compiles fine but when I go to run it I get: |> $ ./chuck -l |> RtApi: no devices found for given stream parameters. |> [chuck]: cannot initialize audio device (try using --silent/-s) | | | I don't think the audio interface code has been updated anytime | recently. several things to try: | | 1) try different sample rate: | | > chuck --srate48000 -l | or | > chuck --srate44100 -l | | 2) make sure ALSA is running, the best way (I know of) is just to restart: | | (as root) | > /etc/init.d/alsasound restart | | and make sure the levels are set right | > alsamixer | | 3) if the above no work, there could be another incompatibility that we | should track down. | | What linux are you running? | | Best, | Ge! | | _______________________________________________ | chuck mailing list | chuck@lists.cs.princeton.edu | https://lists.cs.princeton.edu/mailman/listinfo/chuck | . | - -- Matthew Shanley E-mail: mshanley@alum.rpi.edu GnuPG Public Key ID: 0x71BB0EC1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBRjyeMk//EXG7DsERArqCAKClJuAvaDN+m1h8wAF57yozKN7HMACgia6W XIBIgxKnWniOkLNGmeF8EEc= =HgdP -----END PGP SIGNATURE-----

adc => dac; while(true) 100::ms => now;

the shred will stop but the mic input will not, until I kill chuck:

Ah, yes. Thank you for finding this. I will enter this into our bug tracker. The assertion fail has been fixed shortly after 1.1.4.8, but the persisting adc => dac is still there. It is due the shred-specific ugen reference counting. since adc is global, when the shred leaves, the adc connection does not. In the current rewrite of the type system to include objects/array/event, we are going to fully address this issue. In the meantime, we will synthesize a work-around... Heh. A pre-work-around is to do the following hack: adc => gain g => dac; removing the shred will disconnect g, effectively but very inelegantly disconnecting adc from dac. Also, the assertion correction is in CVS - you can also email me for a tarball. Thank you once again for bring this up. Fix on the way. Best, Ge!