Re: [sc-users] OSC Pattern Scheduling

[James Harkins <jamshark70@xxxxxxxxx>]

On 9/21/05, Esben Stien <b0ef@xxxxxxxxxxxxxxxx> wrote:
> James Harkins <jamshark70@xxxxxxxxx> writes:
>
> > OSCSched is kind of a superfluous class. Why not just do it all
> > directly in the routine?
>
> There would be too many calculations when I put in tsched doing it
> like this.

Why do you need tsched? I can't see any concrete benefits of it over
the scheduling methods in SystemClock and TempoClock.

The only really distinctive feature of BeatSched that I can see is
xsched, with the ability to cancel messages in the future. I played
with that a couple of years ago and found it pretty crashable. Maybe
it's improved since then.

In your example you have two clocks -- the system clock running the
routine, and the beat scheduler which uses TempoClock. That means you
have potential problems with coordinating the two clocks. I'm
suggesting simplifying it and doing it all on one clock. It will be
easier to understand, debug, and you'll be happier. Occam's razor
applies here, I think.

Could you clarify what you mean by "too many calculations"?

Oh, and...

(
d = Routine({
   var c = thisThread.clock;
   20.do({
           c.sched(1.0, {Synth("tutorial-sine",[\gate,1]); });
           c.sched(3.0, {Synth("tutorial-sine",[\gate,1]); });
           c.sched(5.0, {Synth("tutorial-sine",[\gate,1]); });
           8.0.wait;
   });
});
SystemClock.play(d);
)

Something like that?

hjh

--
James Harkins /// dewdrop world
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