Mike;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
we ran the 2pm show with some difficulty. mixing all the files to<br>
mono and pre-loading everything worked (using almost 1gb of RAM).</blockquote><div><br>Oh, well, that's what the RAM is there for :-).<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
the<br>
mono bounces were all clipped.<br></blockquote><div><br>Whoopsie. It happens.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
of course, it's supposed to be a 4-channel piece... ;-)<br>
<br></blockquote><div><br>:-)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
we had some sensor and code issues. We stopped and started over a<br>
couple of times. but basically the ChucK part worked perfectly. :D<br>
<br></blockquote><div><br>For all of it's crash-prone-ness I do find that ChucK is quite predictable; once you have your code working it'll keep working. I don't think I ever had a crash or glitch on stage (aside from livecoding).<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks SOOOOO much for all your help, everyone. I think that the 8pm<br>
show will be better.<br></blockquote><div><br>No problem; I enjoy this kind of thing. If any pictures or recordings materialise do post; I'd like to see what you've been up to but don't stress for my sake.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Kas, I was using buf.chunks(1024), but it looked in Activity Monitor<br>
like it was loading the whole file anyway. hrm...<br>
<br></blockquote><div><br>Lovely! Another bug found. We need to keep Ge on his toes; I hear he eats quite a lot, let's keep him busy to compensate ;-). I have actually been working on a similar problem lately ( <a href="http://bottomfeeder.ca/top/?p=71">http://bottomfeeder.ca/top/?p=71</a> ). It's quite hard. I said it before but I feel that ChucK could use a syntax for "load this file as quickly as you can without glitches but no quicker". The matter has been debated on the wiki with regard to fileIO but I still feel that the interaction between the highly abstracted ChucK syntax (that assumes a infinitely fast computer even while meant to facilitate a good trade between sound quality and CPU usage) and the finite resources of the underlying system could use some attention.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
More soon!<br><br></blockquote><div><br>Good luck!<br>Kas. <br></div></div>