From: owner-sc-users-digest@lists.io.com (sc-users-digest) To: sc-users-digest@lists.io.com Subject: sc-users-digest V1 #103 Reply-To: sc-users Sender: owner-sc-users-digest@lists.io.com Errors-To: owner-sc-users-digest@lists.io.com Precedence: bulk sc-users-digest Saturday, April 1 2000 Volume 01 : Number 103 ---------------------------------------------------------------------- Date: Wed, 29 Mar 2000 19:48:29 -0500 (EST) From: Paul Lansky <---@---.---> Subject: Re: iMacs I get 360 on an iMac DV special edition (400 MHz) paul lansky >James, > >The first oscillator benchmark test in the example files will easily run 300 >(and a few more) oscillators on a blue G3 MHz 350. In running the same test on >4 iMacs, I found that 250 oscillators will lock them up without fail ... which >seems odd since the iMacs are ostensibly faster than the 350 MHz G3. > >Have you (or others on the list) experienced anything similar to this with >iMacs? > >-Mark > ------------------------------ Date: Wed, 29 Mar 2000 19:59:04 -0600 From: James McCartney <---@---.---> Subject: Re: iMacs on 3/29/00 5:45 PM, Mark Polishook at polishoo@cwu.edu wrote: > James, > > The first oscillator benchmark test in the example files will easily run 300 > (and a few more) oscillators on a blue G3 MHz 350. In running the same test on > 4 iMacs, I found that 250 oscillators will lock them up without fail ... which > seems odd since the iMacs are ostensibly faster than the 350 MHz G3. > > Have you (or others on the list) experienced anything similar to this with > iMacs? I don't have an iMac. How do the caches compare? Cache is as important or more so than CPU speed. Shot in the dark: You should have 'allow processor cycling' turned off in the energy saver control panel. - --- james mccartney james@audiosynth.com SuperCollider - a real time synthesis programming language for the PowerMac. ------------------------------ Date: Thu, 30 Mar 2000 09:00:23 -0700 From: David Cottle <---@---.---> Subject: Tabs, Drift Hi, Is it possible to change the default tab size (and how would I do it)? I prefer them about half the size of what they are. One of my students put together a complicated patch with a small error someplace which causes the signal to drift gradually up or down in the final "add" value. For example, it acts like this: Synth.scope({SinOsc.ar(600, mul: 0.3, add: LFNoise1.kr(0.5, 0.5))}) He understands that it's a problem somewhere in his instrument design, but the instrument is quite complex and the precise cause eludes us, and in the interest of a pressing concert I wondered if there is a way to treat the symptom. That is, test the final output to see if the average is too high or low, and make an adjustment at that point. We know how to make the adjustment, but how would we test the output? ------------------------------ Date: Thu, 30 Mar 2000 10:44:16 -0600 From: James McCartney <---@---.---> Subject: Re: Tabs, Drift on 3/30/00 10:00 AM, David Cottle at lime@uiuc.edu wrote: > Hi, > > Is it possible to change the default tab size (and how would I do it)? I > prefer them about half the size of what they are. no, sorry. (If your nesting is getting too deep it probably means you could break up your functions into smaller pieces.) > > One of my students put together a complicated patch with a small error > someplace which causes the signal to drift gradually up or down in the final > "add" value. For example, it acts like this: > > Synth.scope({SinOsc.ar(600, mul: 0.3, add: LFNoise1.kr(0.5, 0.5))}) > > > He understands that it's a problem somewhere in his instrument design, but > the instrument is quite complex and the precise cause eludes us, and in the > interest of a pressing concert I wondered if there is a way to treat the > symptom. That is, test the final output to see if the average is too high or > low, and make an adjustment at that point. We know how to make the > adjustment, but how would we test the output? > Is he using a feedback delay line or some other process that is effectively integrating the signal? If so you may need to use LeakDC. - --- james mccartney james@audiosynth.com SuperCollider - a real time synthesis programming language for the PowerMac. ------------------------------ Date: Thu, 30 Mar 2000 10:16:21 -0800 From: Mark Polishook <---@---.---> Subject: problem with class def James, A problem with a class definition... Noise { *ar { var env; env = Env.perc(0.4, 5); ^TSpawn.ar({ Ringz.ar(WhiteNoise.ar(0.005), [50, 100].rrand(2000), 0.5, EnvGen.kr(env)) }, 2, nil, TabletButton.kr(2, 0, 1)); } } Compilation works. { Noise.ar }.play 'appears' to run (the patch starts and the status bar appears at the top of the desktop). But when I press the button on the stylus (the trigger for TSpawn), I get Error: Message 'ar' not understood ...but a class with a similar definition works fine...for example SineButton { *ar { var env; env = Env.perc(0.4, 5); ^TSpawn.ar({ SinOsc.ar([50, 100].rrand(2000), 0, EnvGen.kr(env)) }, 2, nil, TabletButton.kr(2, 0, 1)); } } What should I do to fix the Noise class? Thanks, Mark ------------------------------ Date: Thu, 30 Mar 2000 12:42:25 -0600 From: James McCartney <---@---.---> Subject: Re: problem with class def on 3/30/00 12:16 PM, Mark Polishook at polishoo@cwu.edu wrote: > James, > > A problem with a class definition... > > Noise { > *ar { var env; > env = Env.perc(0.4, 5); > ^TSpawn.ar({ > Ringz.ar(WhiteNoise.ar(0.005), [50, 100].rrand(2000), 0.5, > EnvGen.kr(env)) > }, 2, nil, TabletButton.kr(2, 0, 1)); > } > } > > Compilation works. > { Noise.ar }.play 'appears' to run (the patch starts and the status bar > appears > at the top of the desktop). > But when I press the button on the stylus (the trigger for TSpawn), I get > > Error: Message 'ar' not understood Works fine for me. You didn't name that file Noise.sc by chance? Then it would conflict with the file Common/Audio/Noise.sc . - --- james mccartney james@audiosynth.com SuperCollider - a real time synthesis programming language for the PowerMac. ------------------------------ Date: Thu, 30 Mar 2000 12:52:19 -0600 From: James McCartney <---@---.---> Subject: Re: problem with class def on 3/30/00 12:42 PM, James McCartney at asynth@io.com wrote: > You didn't name that file Noise.sc by chance? You must have. Here's what is happening. When you name a file the same name at a higher level folder, it means you want to replace all the definitions in the lower level file with the higher level one. This is why Common is an alias in the Default Library. It lets you replace any of the files in Common with your own without having to alter the files in the Common folder in any way. If you replace Noise.sc, then it does not know about the class WhiteNoise and cannot send it a .ar message. - --- james mccartney james@audiosynth.com SuperCollider - a real time synthesis programming language for the PowerMac. ------------------------------ Date: Thu, 30 Mar 2000 10:54:28 -0800 From: Mark Polishook <---@---.---> Subject: Re: problem with class def > > > Works fine for me. You didn't name that file Noise.sc by chance? > Then it would conflict with the file Common/Audio/Noise.sc . > .. ummmm....I'll change the name of the file to something other than Noise.sc ... Thanks, Mark ------------------------------ Date: Thu, 30 Mar 2000 11:58:22 -0800 From: Mark Polishook <---@---.---> Subject: Re: problem with class def James McCartney wrote: > on 3/30/00 12:42 PM, James McCartney at asynth@io.com wrote: > > > You didn't name that file Noise.sc by chance? > > You must have. Yes, I did...and have now renamed it and it works fine. Thanks for the explanation...which makes perfect sense. > Here's what is happening. > When you name a file the same name at a higher level folder, it means you > want to replace all the definitions in the lower level file with the higher > level one. This is why Common is an alias in the Default Library. It lets > you replace any of the files in Common with your own without having to alter > the files in the Common folder in any way. > If you replace Noise.sc, then it does not know about the class WhiteNoise > and cannot send it a .ar message. > > --- james mccartney james@audiosynth.com > SuperCollider - a real time synthesis programming language for the PowerMac. > ------------------------------ Date: Thu, 30 Mar 2000 20:32:50 -0500 (EST) From: Paul Lansky <---@---.---> Subject: feedback loop Hi I think I understand why the following is incorrect, but is there any way to accomplish this kind of feedback relation in SC? Synth.play({ y = WhiteNoise.ar(1); y = y + 0.9 * s; s = DelayN.ar(y,0.1,10/44100); }) thanks paul lansky ------------------------------ Date: Thu, 30 Mar 2000 21:14:04 -0600 From: James McCartney <---@---.---> Subject: Re: feedback loop on 3/30/00 7:32 PM, Paul Lansky at paul@silvertone.Princeton.EDU wrote: > > Hi > > I think I understand why the following is incorrect, but is there > any way to accomplish this kind of feedback relation in SC? > > > Synth.play({ > y = WhiteNoise.ar(1); > y = y + 0.9 * s; > s = DelayN.ar(y,0.1,10/44100); > }) > You can't have feedback loops smaller than the block size. You can set the block size to whatever you want. For feedback loops that are larger than the block size you can use DelayWr, Tap or DelayProcessN. Feedback loops will be better supported in a newer version I am working on. - --- james mccartney james@audiosynth.com SuperCollider - a real time synthesis programming language for the PowerMac. ------------------------------ Date: Sat, 1 Apr 2000 16:32:55 +0200 From: Joel Ryan <---@---.---> Subject: more Wacom Problems I just know you dont want to hear this, I've just transferred a couple of applications from a desktop G3 to a bronze powerbook G3 and experienced catastrophic Wacom complications. Im using an Intuos 12x18 pad with a serial interface (Wacom driver 4.5.1) and a Keyspan dual Serial to USB adaptor (usa28x. Keyspan driver 1.2) for my powerbook. The pad connects and behaves normally with only the usual Wacom startup thrashing, but SuperCollider 2.2.7 crashes in the initialization phase before I even load my program before any of compiler messages appear in its window. I get the same results with SuperCollider 1.1b8.7, it crashes as soon as the sc wincdows are drawn and before any init messages appear in the message window. Im also using USB for midi (midiSport) but even without , it crashes Otherwise there is nothing muche else in the system I tried with a stripped down as well as a normal fat system with no changes. not cool. /////////////////////// Joel Ryan STEIM :: Ballett Frankfurt :: Institute of Sonology Achtergracht 19, 1017WL Amsterdam +31 (20) 624-3886 +31 (20) 626-4262 fax http://www.frankfurt-ballett.de/joel.html http://www.steim.nl /////////////////////////////////////////// ------------------------------ End of sc-users-digest V1 #103 ******************************