[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sc-devel] [Bug?] TempoClock queueSize problem?



The queue array has to store times as well as items, so for every single entity you schedule, two slots are used.

Sometimes I use this nifty little addition for debugging, if I'm not sure what's actually on the clock. Note that you have to clump the array by 2 in order to make sense of it.

+ TempoClock {
// for debugging purposes
// this will generate A LOT of information!
dumpQueue {
queue.clump(2).do({ |pair|
("\n" ++ pair[0]).postln;
pair[1].dumpFromQueue;
});
}
}


+ Function {
dumpFromQueue {
("Arguments: " ++ this.def.argNames).postln;
("Variables: " ++ this.def.varNames).postln;
this.def.dumpByteCodes;
}
}

+ Object {
dumpFromQueue {
this.dump
}
}


hjh

On Dec 24, 2007, at 4:15 PM, Tom Hall wrote:


Hello List

TempoClock's default queueSize is 256.
*new { arg tempo, beats, seconds, queueSize=256;
^super.new.init(tempo, beats, seconds, queueSize)
}

But the error msg "scheduler queue is full." occurs when the queueSize exceeds 128.


: H. James Harkins

: jamshark70@xxxxxxxxxxxxxxxxx

: http://www.dewdrop-world.net

.::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..:


"Come said the Muse,

Sing me a song no poet has yet chanted,

Sing me the universal."  -- Whitman