Hi there - <br><br>I&#39;m very new to ChucK so please be kind if I sound incredibly stupid,<br>and very angry because I am going nuts here. <br><br>(Kassen, I&#39;m here - we had a very brief exchange about ChucK with toplappers)
<br><br>I&#39;m writing my scripts using SciTE, and using the command-line VM. I have<br>tried some Chuck with tutorials, manual and helpful tips on forums, usually<br>by someone too good to be true like Kassen.I want to know what people really
<br>&nbsp;mean by OTF (on the fly) or by &quot;livecoding&quot; in Chuck.<br><br>If you prepare your files and code in advance and then just chuck the <br>shreds in and out of the VM, it really is a a bit like sequencing, rather
<br>than livecoding. And if I change the code in the file, save it, then the <br>effects don&#39;t appear live, do they? I really don&#39;t see how i&#39;m changing <br>the code &quot;while its running&quot; here. <br><br>
Maybe i&#39;m missing something freakin obvious, but I&#39;m so frustrated<br>having had to learn Csound, Chuck, SuperCollider and all sorts of <br>new languages just because Python did not provide me with a simple<br>audio processing module. All I wanted to do using Python was analyse the sound
<br>of a live flute playing and plot its frequency, and other characteristics, straight<br>off the audio port. <br><br>Now I&#39;m a newbie at all of the above, and thats really fantastic because<br>it hasn&#39;t solved a single problem. It has certainly added a few more. 
<br><br>What a royal mess. <br><br>-------<br>1/f&nbsp;&nbsp; )))<br>-------<br><a href="http://www.algomantra.com">http://www.algomantra.com</a>