[sc-users] Re: [sc-dev] Re: calling the stream upon EventStreamPlayer-stop

[James Harkins <jamshark70@xxxxxxxxx>]

On 1/4/06, ronald kuivila <rkuivila@xxxxxxxxxxxx> wrote:
> I could use your argument  to insist that note events
> should not rely on scheduling a separate "gate" message but should
> instead
> send  "sustain" as an argument to synth(s) it creates.

But I said... "any resource defined outside the pattern constructor
**that needs to be maintained across events**." The gate message is
contained within the event and will still execute if you stop or pause
the stream. A Pmono synth needs to be accessible within multiple
events, hence the problem.

> (After all, the clock could be stopped.)

That's the kind of exception that proves the rule, methinks. :)

> My way of thinking of this is that Patterns are "scores",
> eventstreams are "performances"
> Early termination of a stream (whether by user intervention or a time
> control pattern) is
> a "performance" decision.

I'm not convinced by the analogy. A stream is more aptly described as
a performER, not a performANCE, and it's a pretty dumb performer at
that. It knows how to do only one thing: next... next... next... My
argument is that for Pmono, you're asking a stream to do something it
isn't smart enough to do without being whipped over the head with a
stick. We could meet both your requirements and mine with a smarter
stream, one that understands .next and .releaseResources -- but the
implementation there is the tricky part.

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