Atte, Sincerest apologies on not getting back to you sooner... us princeton- ites were pretty swamped with ICMC madness this past week. To be honest, Im stumped. I guess it would be good to be absolutely certain that the exact same chuck that miniAudicle links to does not produce the same bugs. Additionally, try playing around with buffer sizes if you haven't already (miniAudicle accepts most of the same command line arguments as chuck, including --bufsize###). Also, do the same bugs pop up when you write the output to a file with WvOut? If it comes down to it I would be willing to do a remote debugging session to get a closer look at what might be going wrong, if you are up for that. spencer On Nov 12, 2006, at 2:25 AM, Atte André Jensen wrote:
Atte André Jensen wrote:
Spencer Salazar wrote:
That's a pretty baffling issue. Could you perhaps forward the console log output when starting the virtual machine in miniAudicle?
Sure. Seems clean to me...
Another finding in blit.ck: If I remove the line ".5 => s.gain;" I get sound but no reverb. Maybe that's an additional clue to knowledgeable people...
Any idea on this? Things I should try out?
-- peace, love & harmony Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users