Hi, I see your point, but I was really only doing two things:<br><br>1. Editing chuck files in a text editor and<br>2. Reading the manual to assist with number 1<br><br>Number 2 wouldn't happen in a performance, but number 1 certainly would occur, and would seem essential for live coding, at least until audicle reaches a really stable point in its development.
<br><br>~David<br><br><div><span class="gmail_quote">On 4/20/06, <b class="gmail_sendername">Perry R Cook</b> <<a href="mailto:prc@cs.princeton.edu">prc@cs.princeton.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Also, respectfully, if you're opening PDF files or<br>running other programs while trying to do live ChucK<br>performance, then you deserve to get clix :-)<br><br>Seriously, though, boosting priority is indeed a good<br>
idea. We believe that ChucK should be the highest<br>priority process.<br><br>PRC<br><br>On Thu, 20 Apr 2006, Ge Wang wrote:<br><br>> Hi All,<br>><br>>>> I was running the stk/clarinet.ck example. No soundfiles involved at
<br>>>> all. It was usually only in creating and destroying shreds that there<br>>>> was a problem. Actually, now that I think about it, glitching also<br>>>> occurred when I would change focus to another program and carry out
<br>>>> some action, i.e. scrolling through the chuck manual in Adobe Reader.<br>>>> This is on an Intel with Pentium M, running Windows XP Pro with SP2.<br>>><br>>> Same thing here with the PDF file, and I also noticed it when
<br>>> switching to programs like Firefox or N.<br>><br>> Interesting that it seems likely to occur on fast machines running XP SP2,<br>> but not not on a PIII. I was also able to reproduce the same type of
<br>> glitches changing windows on my XP SP2 Pentium M 1GB RAM laptop.<br>><br>> So, XP users, let's try this - run chuck with the --level10 flag, which<br>> should internally boost chuck's priority:<br>><br>
> > chuck --level10 <a href="http://foo.ck">foo.ck</a> ...<br>><br>> For me this got rid of the glitches. If this works in genereal, we can<br>> make this a default. Also feel free to try other values.
<br>><br>> Let us know!<br>><br>> Best,<br>> Ge!<br>> _______________________________________________<br>> chuck-users mailing list<br>> <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu
</a><br>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>><br>_______________________________________________<br>chuck-users mailing list
<br><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
</a><br></blockquote></div><br>