On 8/10/07, 2g <electriclightheads@gmail.com> wrote:
ah yes!
i didn't test it that way.

Well, then that's a important lesson in both programing and sound engineering; when something seems strange always try to pinpoint the issue in a simplified version of the situation. This will save you a lot of time in the long run.

Also; mute-buttons and typing "//" are very fast and easy.

 
i learned that the initiation of the SinOsc is important
if i want everything go correct from in the beginning

What I think is realy important in your code is that you should figure out what the lowest and highest frequency the random stuff can give are and try to tune them to make sure those are within the range of your speakers and ears.

 

am now even nervous to the order of this in the code

Don't be! The order of this code is definately very important but it's much better to be "adventurous" then it is to be "nervous", just relax and try things at a low volume and nothing can go wrong.

Kas.