TimeIndexSound behaviour

Question

Hi there,

When gating the TimeIndexSound it behaves as expected but when I use a trigger it changes instantly into release stage no matter where I am in the timeindex. It is quite confusing in general ;)

A little example using the following parameters:

Start: 0, MarkAtkEnd: 0.1, LoopStart 0.2, LoopEnd: 0.5, ReleaseStart: 0.8, End: 1

Gated

on

0 - 0.1 scaled by AtkScale

0.1 - 0.2 not scaled

0.2 - 0.5 scaled by susScale and loop

off

0.5 - 0.8 not scaled

0.8 - 1 scaled by relScale

Trigger

on

0 - off (so just the time the button is pressed) scaled by AtkScale

off - 1 scaled by relScale

 

Why isn't the timeIndex behaving like gated except it doesn't loop? I just realised that I haven't tested releasing the gate before the loop stage. But I think it doesn't go into release stage immediately?

Also why is there a Duration and a Rate field? Usually kyma handles this with only duration and one can optionally use !Rate to scale. 

I only like to notice that there's a hierarchy in the markers/loopPoints. That's fine but it isn't mentioned in the documentation. MarkAtkEnd := MarkAtkEnd vmin: LoopStart. LoopEnd := LoopEnd vmin: ReleaseStart.

Aaaaaand: I'd really love a parameter in the SampleWithTimeIndex to apply a short fade in/out when there's some discontinuity in the timeindex to avoid clicks :)

Thanks!

Comments

Thanks for making an analysis. This TimeIndex is quite unintuitive for me too. I have also experienced odd click behaviour with LoopEnd and ReleaseStart .. it would  be really cool to have the LoopFade feature of the Sample prototype somehow integrated. But of course, this is related to Amplitude modulation (Product or Envelope) not TimeIndex as such. Although when windowing another signal, you could use TimeIndex to calculate precisely when it is looping so as to place the tiny fade ins or outs.

---

I just tested and indeed the timeindex does immediately jump into release state when closing the gate.

Answer 1

From your description the TimeIndex is working as expected in response to a trigger.  If you trigger (rather than gate), then it should have no duration.  Thus it makes sense that the index should jump immediately to the release stage.

Comments

Ok, I see. I'll work my way around, thanks!