From: owner-sc-users-digest@lists.io.com (sc-users-digest) To: sc-users-digest@lists.io.com Subject: sc-users-digest V1 #378 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 Friday, November 9 2001 Volume 01 : Number 378 ---------------------------------------------------------------------- Date: Wed, 07 Nov 2001 08:57:29 -0700 From: David Cottle <---@---.---> Subject: Re: Digi 001 input >> >> I already use these for sound out. I didn't realize input would work the >> same way. So is it correct that I don't even have to mess with the choices >> in the Sound control panel? That's just for system sound? > > I'm not at my studio to check it right now but I believe so. You might > want to make sure that the 001 is not selected in Sound Control Panel as > that might make it unavailable for SC. Works great. Thanks. It makes sense now that I think of it. There's no reason to select DIGI for the system sound. I think that's what was causing my lock ups. - -- ><><><><><><><><><><><> David Cottle, computer music, contra, cottle@cerlsoundgroup.org "Nothing is so boring as a merely well-rehearsed performance, well-rehearsed in the sense that nothing can be expected to happen except what was studiously prepared in advance." -Copland ------------------------------ Date: Thu, 08 Nov 2001 17:27:07 +0100 From: John Eacott <---@---.---> Subject: Re: Digi 001 input > I'm glad. How do you manage to have an enless supply of good quotes to put at the end of your mails? The current one reminds me of an article somone showed me recently about 'Wasi sabi' (I think) - the Japanese art of imperfection. John. > > > > > I'm not at my studio to check it right now but I believe so. You might > > want to make sure that the 001 is not selected in Sound Control Panel as > > that might make it unavailable for SC. > > Works great. Thanks. It makes sense now that I think of it. There's no > reason to select DIGI for the system sound. I think that's what was causing > my lock ups. > > "Nothing is so boring as a merely well-rehearsed performance, well-rehearsed > in the sense that nothing can be expected to happen except what was > studiously prepared in advance." -Copland - -- john eacott ======================================== composer - interactive sound design www.informal.org ------------------------------ Date: Thu, 08 Nov 2001 22:57:58 -0500 From: felix <---@---.---> Subject: Re: amplitude on 11/7/01 8:37 AM, Tim Sayer at timsayer@ntlworld.com said: > I am new to SC and I'm trying to record an array of markers from a buffer > containing some speech to detect where the words start and finish. I don't > know if it's possible to look at the amplitude of the signal in the buffer > without playing or if I have to track the amplitude while it's playing. > you could play it, analyse it with a ugen Amplitude.kr(speech) > threshold where threshold is a float value like 0.2 using > with a ugen (amplitude is a ugen) results in a BinOpUgen that basically asks the question "amplitude > threshold ?" every sample cycle. its output is a 0 or 1 can be used: Synth.collect({ var schedSynth; schedSynth = thisSynth; TSpawn.ar({ arg synth,i,spawn; // not this synth, its only just been born! schedSynth.beats.postln; // whenever this is triggered... nil // no audio output }, Ampltidude.kr(speech) > threshold); // the TSpawn is triggered by volume attacks // you can try setting the rise/fall time to match the speech // or possibly massaging the signal further // with Latch or Gate }); // returns a signal, but we're not using it you probably want to rig up some more complex triggering mechanism, like those expander gates that trigger at a different level than they release at. > I can't figure out how amplitude.kr works. I've tried passing it playbuf but > can't seem to trap the amplitude of the signal, if I put it in an if > statement it tells me it's not a Boolean expression. PlayBuf.ar should work 'if' can create a ugen. its input must be a boolean expression as i've done above. > > I suspect I have completely the wrong approach, if anyone has the time to > help I'd be very grateful > > TiM > > > ------------------------------ Date: Fri, 09 Nov 2001 14:07:41 -0600 From: matrix6k <---@---.---> Subject: error -37 my apologies if this has been brought up already, SC 2.2.11: after recording or writing a soundfile to disk I receive error -37 when attempting to save the SC document after changes. this is repeatable, and does not happen unless i write a soundfile first. i can 'save as' then 'replace' and re-type in the patch name, but not 'save'. - -michael _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ------------------------------ End of sc-users-digest V1 #378 ******************************