Also, respectfully, if you're opening PDF files or running other programs while trying to do live ChucK performance, then you deserve to get clix :-) Seriously, though, boosting priority is indeed a good idea. We believe that ChucK should be the highest priority process. PRC On Thu, 20 Apr 2006, Ge Wang wrote:
Hi All,
I was running the stk/clarinet.ck example. No soundfiles involved at all. It was usually only in creating and destroying shreds that there was a problem. Actually, now that I think about it, glitching also occurred when I would change focus to another program and carry out some action, i.e. scrolling through the chuck manual in Adobe Reader. This is on an Intel with Pentium M, running Windows XP Pro with SP2.
Same thing here with the PDF file, and I also noticed it when switching to programs like Firefox or N.
Interesting that it seems likely to occur on fast machines running XP SP2, but not not on a PIII. I was also able to reproduce the same type of glitches changing windows on my XP SP2 Pentium M 1GB RAM laptop.
So, XP users, let's try this - run chuck with the --level10 flag, which should internally boost chuck's priority:
> chuck --level10 foo.ck ...
For me this got rid of the glitches. If this works in genereal, we can make this a default. Also feel free to try other values.
Let us know!
Best, Ge! _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users