Table clocking from automators

[Bleep bleep]

Im playing around with automator clocking of tables and im experiencing some issues here.

I would like to pass to the next step of a table with an envelope to transpose an oscilator every time it plays.

I have an envelope triggered by my oscilator already and routed to the volume of this oscillator,
but this one is not fast enough to retrigger the table when two notes play close one to each other .

So i created a second envelope, very short, in the automator with an offset. with my oscilator also as the same source
(this should work?)
 
because "envelope1 start" as source seems not to retrigger until the first envelope has reach the end.

Now i can get what i want to work but only if this second envelope is routed to modulate also the volume of my oscilator and this create a click in the sound. If set on something else it wont trigger.

Its weird that the same source cannot trigger two different envelopes unless they have the same destination.

I dont know if this is normal. 

Now i made another test, the second envelope is now a very slow triangle set to destination none, with the envelope1 start as source. It does trigger but when it cross to zero i would expect the table to jump to the next step but nothing happens.

Maybe it is related to the fact that the table clocking happens only on zero crossing? 

Perhaps it would be better to happen anytime the wave is going from a negative to a positive value? as now the noise lfos seems not to be usable for this purpose. 

Also an envelope divider in the automator settings might solve the problem(and its a free spot there).

I continue to investigate. 
Anyone else trying to do something similar? 

(if found a workaround already but i think it should work somehow with the envelope automators)

[XORadmin]

I guess you don't reset the gate of the oscillator (which is your envelope source)? Because then also the 2nd envelope sourced by the first one would follow that. So use a 'gate off' between your notes will take care for the retrigger of coupled envelopes.

I can actually see one bug and that is that the zero cross is not correct (which suppose to be the middlepoint of the automator being the zero cross.
It works but the main value has get slightly below the zero point and the 'off' value has to go much lower. This threshold is not correct and i got to fix it.
But you can simply work around that by adjusting the AMP and Offset. When you see the max value of your env passing the midpoint and the lowest value getting around the N of Envelope, then it triggers the table.

But generally of course, the table is not triggered by a new envelope, but by a automator. So if the envelope doesn't reach it's levels, then no trigger occours.
If the envelope doesn't match the needs for that, you can always use the SPFX instead to give the table tick.

[Bleep bleep]

Ok i understand better what happened here, 

Regardless of tables and automators, the point is envelope2 will not trigger if the decay phase of envelope1 is not finish when it retrigger. is this normal?

Just to be clear all this happens in audio track 1.

Envelope1 have "audio1" as source, and "volume1" as destination.
Envelope2 have"Envelope1 start" as source and"pitch1" as destination.
Both envelopes type on "oneshot"

You can see in the video, if i increase the decay of Envelope1, Envelope2 will not restart on the shortest steps.

https://www.youtube.com/watch?v=LVRr8p_I7os

Its kind of working tough if i put the attack, attack peak and decay to zero and use the sustain and release to shape the envelope.

i would expect the envelope2 to restart together with envelope1 wathever is the state of the envelope. 
Is it working like this on purpose?

[XORadmin]

Yes, if you connect it to envelope start then it would start with this envelope.
I see in the video that you are not using the gate off but note off. This will cut off the note. Use the gate off to release the envelope gate.

For the 4 lines below you could try the Retrig command with 0000, it suppose to retrigger also envelopes. However, i found out with testing today that this doesn't always work perfectly as advertised. I fixed that already actually. For now a little workaround might work: Use a retrigger 1x with some repeat values will take care that they are always triggered for now. Retrig0000 will work with the next update and gate off works anyway.

[Bleep bleep]

Ok im trying again now with gate off and retrig command but i dont get it to work better...

https://www.youtube.com/watch?v=FZnYOCM1QY0

I also cloned the pattern to see the difference and i have exactly the same results with or without the gates off and retrigs.

[XORadmin]

Ok im trying again now with gate off and retrig command but i dont get it to work better...

https://www.youtube.com/watch?v=FZnYOCM1QY0

I also cloned the pattern to see the difference and i have exactly the same results with or without the gates off and retrigs.

Not sure about the retrig ones as i hear more envelopes here?, but the gate off ones seem to work well.

Your envelope is at some voltage level, maybe in release and gets back to the attack phase from that level. It doesn't start at zero. Thats how it suppose to be. Also with retrigger. (They act like analogue envelopes)

[Bleep bleep]

Ok im shure now,

 "Envelope1 start" will not trig the envelopes that have it as source if it happens during attack or decay time of Envelope1. 
But it does on release.

By the way , Envelope1 gonna always reset itself if retriged, even during attack or decay, so both envelopes will not always behave the same way.

We can see it better here:

https://www.youtube.com/watch?v=3JKoIaIne2I

We clearly listen the sound fading every time, but the pitch dont change when the envelope is trigged during is attack or decay.

Good to know, it was confusing at first but its all fine now... 

So its better to build the attack/decay envelope as attack/release envelope if we want them to always trigger the envelopes they are linked to.

[XORadmin]

As i said, a fix is on the way, just waiting to collect more info about issues with the gamepad for some users with several controllers.

Actually about the Attack/Decay Vs. Attack Release. I would always only think of a Attack/Release if i want to have that curve. Attack/Decay would only be one half of the whole thing. Especially if you use AD-SR envelopes that would always make more sense.

[Bleep bleep]

Ok thank you!

[XORadmin]

Fixed in V1.23A