Envelope staying open after stopping everything

[kilgore]

hey nerds,
I tried to find this answer in the manual, but maybe I'm looking in the wrong place?

I have a CV going out from track one to an oscillator. Envelope 1 in the nerdseq automation screen is being triggered by Gate 1 and sent through the MOD1 output to a VCA. Pretty simple.

The issue: when I STOP the nerdseq, sometimes the VCA stays open, so the oscillator is droning. I have the envelope set to ONE SHOT. The thing is, it doesn't do this all the time. Sometimes I stop everything (SHIFT+STOP) and everything stops, some times the VCA stays open and I get a drone.

The only thing I was able to find in the manual is on page 86:

Possibly a VCA may ‘stay open’ depending on the offset level and any waveforms can still be audible after the release phase if the offset is not set to zero.

But there is no offset on the envelope, so it should just return to zero?

Changing the setting of the offset switch doesn't make a difference (except the drone is quieter if the switch is to the left).

Thanks!

[XORadmin]

hey nerds,
I tried to find this answer in the manual, but maybe I'm looking in the wrong place?

I have a CV going out from track one to an oscillator. Envelope 1 in the nerdseq automation screen is being triggered by Gate 1 and sent through the MOD1 output to a VCA. Pretty simple.

The issue: when I STOP the nerdseq, sometimes the VCA stays open, so the oscillator is droning. I have the envelope set to ONE SHOT. The thing is, it doesn't do this all the time. Sometimes I stop everything (SHIFT+STOP) and everything stops, some times the VCA stays open and I get a drone.

The only thing I was able to find in the manual is on page 86:

Possibly a VCA may ‘stay open’ depending on the offset level and any waveforms can still be audible after the release phase if the offset is not set to zero.

But there is no offset on the envelope, so it should just return to zero?

Changing the setting of the offset switch doesn't make a difference (except the drone is quieter if the switch is to the left).

Thanks!

Share the project and I can check the envelope. Why are you using the envelope with the automator?

[kilgore]

I think I'm confusing the terms, sorry. There is NO automation running. Just Envelope 1 from the envelope screen.

Attached is the project file. Thanks!

[XORadmin]

I think I'm confusing the terms, sorry. There is NO automation running. Just Envelope 1 from the envelope screen.

Attached is the project file. Thanks!

I guess you press SHIFT+STOP twice? This does stop the envelopes and the MOD for example stays at the current envelope position since it is not getting updated by the envelope anymore.
If I regular press stop the envelope seem to do the full release phase for me.

[XORadmin]

OK I think the issue is here that they are 2 commands with the 'NOW' attribute while one is the pattern order command which possibly jumps directly to another step defined by the pattern order.
I got to check how easy it is to have the clock command also as a 'pre-check' command to change the clock, without generating an unstable situation = keep everything in sync as good as possible.

[kilgore]

I think I'm confusing the terms, sorry. There is NO automation running. Just Envelope 1 from the envelope screen.

Attached is the project file. Thanks!

I guess you press SHIFT+STOP twice? This does stop the envelopes and the MOD for example stays at the current envelope position since it is not getting updated by the envelope anymore.
If I regular press stop the envelope seem to do the full release phase for me.

I think you're right! Out of habit I've been pressing it twice. So far that seems to work. Now I also understand why the MOD would continue putting out the output of the envelope position that I stopped at. Funny, even when closing the project and opening it agian, the MOD will continue to put output the same CV level I stopped it at.

---

OK I think the issue is here that they are 2 commands with the 'NOW' attribute while one is the pattern order command which possibly jumps directly to another step defined by the pattern order.
I got to check how easy it is to have the clock command also as a 'pre-check' command to change the clock, without generating an unstable situation = keep everything in sync as good as possible.

Hey! I think this reply was actually meant for my other topic (my fault for having two threads with the same example)

 But yeah, I also think the "random now" command was getting in the way. I even tried putting the clock command in the first FX column so it would hopefully get read first, but didn't work.

But while I was out this evening the solution came to me! In another project I was using the SPFX 00C command (random jump) to get a random pattern from a set of notes. This command does not seem to need to be updated in subsequent patterns. So using that command instead of of teh CBPB command cleared up this issue! Now I can jump between patterns and the clock changes correctly, and I get my randomness where I wanted it. So cool that there are multiple ways to get the similar result.