<div>
Mike,
</div><div><br></div><div>We had run it with larger times at that point, and got the same result. That is just a part of a larger file, but we had narrowed down the failure to that spot.</div><div><br></div><div>I am thinking it is probably related to Kassen's idea of win/mac text copying. Problem is that I don't have a windows machine to test it on, so I have to send these suggestions to my student and have him try them out. It all works fine on my machine.</div><div><br></div><div>Funny thing is, the guy is a trombone student. He just mentioned that he wanted to explore some computer music, so we took off on a ChucK tangent.</div><div><br></div><div>-j</div>
<div><div><br></div>-- <br>Jeff Albert<br>PhD Candidate<br><div>Experimental Music & Digital Media</div><div>Louisiana State University</div><div>jalber4@cct.lsu.edu</div><div>(504) 315-5167</div><div>http://about.me/jeffalbert</div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, February 14, 2012 at 10:27 PM, mike clemow wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Jeff,</div><div><br></div><div>Is that the entire file or just a snippet? I've sometimes run into a</div><div>problem where my last line is some tiny amount of time (e.g. 1::samp</div><div>=> now) and the previous line is a spork ~ someFun(); or a</div><div>Machine.add() and the main code exits before the shred-spawning</div><div>function ever has a chance to return.</div><div><br></div><div>If your code is the entire file we're looking at, does it behave</div><div>correctly when the last line is 10::ms => now; ?</div><div><br></div><div>-Mike</div><div><br></div><div><a href="http://michaelclemow.com">http://michaelclemow.com</a></div><div><a href="http://semiotech.org">http://semiotech.org</a></div><div><br></div><div><br></div><div><br></div><div><br></div><div>On Tue, Feb 14, 2012 at 7:12 PM, Hans Aberg <<a href="mailto:haberg-1@telia.com">haberg-1@telia.com</a>> wrote:</div><blockquote type="cite"><div><div>On 15 Feb 2012, at 00:18, Kassen wrote:</div><div><br></div><blockquote type="cite"><div><div>Assuming that the filenames indicated are the actual ones then that's</div><div>not it, those should be legal under both, but Windows and Mac</div><div>potentially use slightly different non-printable characters for stuff</div><div>like the end of a line.</div></div></blockquote><div><br></div><div>I recall there was a bug in miniAudicle at Mac where it choked at UTF-8 characters in the beginning, even though they were in a comment. Maybe fixed by now, but perhaps not on all platforms.</div><div><br></div><div>So try what happens in 'chuck' at the command line.</div><div><br></div><div>Hans</div><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>chuck-users mailing list</div><div><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a></div><div><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a></div></div></blockquote><div>_______________________________________________</div><div>chuck-users mailing list</div><div><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a></div><div><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>