-
... numFrames, sr, i; sf = SoundFile.openRead(path.standardizePath); if(sf.isNil) { Error("ATSAnalyzer: could not open file: " ++ path).throw; }; numChannels = sf.numChannels; numFrames = sf.numFrames; sr = sf.sampleRate.asInteger; // Read all ...
-
... ame shapes, so subtracting should give zero. // Of course there's some rounding error due to floating-point accuracy. var tests = Dictionary[ ////////////////////////////////////////// // Ramp generators: "Line.ar can match LFSaw.ar" -> {Li ...
-
... all at least once before saving automation // otherwise will get not understood errors on load } prCheckConversion { | loadArgs | var newSynth, curentSpat; #newSynth, curentSpat = loadArgs; if (newSynth) { // evaluate before launching a new ...
-
... value( 0, "missing port in message" ); }; }), OSCresponderNode( nil, '/minihive/error', { |t,r,msg,addr| // from minihive verbose.value( 1, msg ); if ( msg.size > 1 ){ addr.port = msg[1]; this.errorFromHive( addr, msg[2], msg.copyToEnd(3) ) ...
-
... class is accessible. You should not do that. This will at some point become an error worthy of compilation failure. Catching methods that are not explicitly defined It is possible to catch calls to methods that are not explicitly defined i ...
-
... s).value_(active); }); cBox; }; midiConnectAll = { try { MIDIIn.connectAll } { |error| error.postln; "MIDIIn.connectAll failed. Please establish the necessary connections manually".warn; } }; switch(GUI.id, \cocoa, { modsDict = KeyDownActio ...
-
... || (char == $\r) || (char == $\n), { // enter key if (keyString.notNil,{ // no error on repeated enter value = interpretFunc.value(keyString, value) ? value; this.prClipValue; keyString = nil; action.value( this, value ); stringColor = nor ...
-
... l be 2 inNumChannels = in.numChannels; if(inNumChannels != stereoNumChannels, { Error( "[BlumUGen] In number of channels (%) does not match expected numInputs (%).".format(inNumChannels, stereoNumChannels) ).errorString.postln; this.halt }) ...
-
... ire('safer-buffer/dangereous')`. ## But isn't throwing bad? Not really. It's an error that could be noticed and fixed early, instead of causing havoc later like unguarded `new Buffer()` calls that end up receiving user input can do. This pa ...
-
... r's child patterns must be event patterns. Using value patterns in a Ppar is an error because value patterns contain no duration data. A Ppar is done when all of its subpatterns are done. ( Ppar([ Pbind(\dur, 0.2, \midinote, Pseq([62, 65, 6 ...