Bazille - sequencer>Env?

[hakey]

I've RTFM and followed the instructions for triggering an envelop with the sequencer but can't quite figure out what's going on.

Why does the env only trigger if the sequencer tap is wired to an arbitrary input?

Why does the env only trigger if the first slider is not at zero?

Why does the envelop trigger twice per measure if sliders 1 and 3 are not zero, but only once if 1,2 and 3, and not at all if 1,2,3 and 4?

Why aren't the envelop clicks of uniform loudness?

More generally, how does the whole thing work?

[hakey]

Here's another - why does releasing the second note of a two note chord sometimes stop the sequencer for both notes?

[lectrixboogaloo]

I have to look at the manual myself, but if you are controlling the env via cv on the amp mod for the envelope, then you are not actually 'triggering' the envelope only changing how much it changes the amplitude (which would cause behavior similar to what your description sounds like to me...) the only triggering comes from midi notes.

Unless you choose mod seq as env trigger on the tweaks page. Then it works as a sequencer sending voltage and triggers so it triggers the envelope for every slider at nonzero. But it still starts working very strangely after a bit for me...

I have had issues with the sequencers 'stopping' for no reason apparent to me, though. I wonder why?

(I should look at the manual )

[hakey]

Unless you choose mod seq as env trigger on the tweaks page.

Yep, that's what I'm talking about (as per the instructions in the manual).

Then it works as a sequencer sending voltage and triggers so it triggers the envelope for every slider at nonzero.

In which case it ought to trigger four times if all four sliders are up, but it doesn't.

[lectrixboogaloo]

I see what you mean. Seems to work fine for a couple measures then seems to... i dunno...

(now working fine again... wtf? am i doing wrong now )

Yup, you're right, seems to have to have step one on or it doesn't work as I expect it to. Even though sometimes it works anyway. Don't know why, that.

[hakey]

Ignoring the env triggering, put the first slider up and all others at zero, connect the first tap to OUT1, set Volume to Gate, press a key and note that the sequencer sends two blips, one at at position 1 (first slider) and one at position 2, which is set to zero, so shouldn't do anything.

[lectrixboogaloo]

I think the sequencer is midi controlled and if midi isn't triggering the sequencer at the right time the sequencer won't step and thus won't control anything. I guess I expected it to work more like a normal voltage control source. It seems a midi note and a nonzero step have to occur at the same time to get the sequencer running? Apparently I just been lucky with it until you got me curious about it.

[hakey]

Surely that's determined by the sequencer's Sync setting - free/sync/retrigger ?

[lectrixboogaloo]

Ignoring the env triggering, put the first slider up and all others at zero, connect the first tap to OUT1, set Volume to Gate, press a key and note that the sequencer sends two blips, one at at position 1 (first slider) and one at position 2, which is set to zero, so shouldn't do anything.

Right. But, in this case, are you sure we are not just hearing the 'voltage' turn on and then off? A voltage offset would make a sound when turned on suddenly and then another when turned off.

[lectrixboogaloo]

Surely that's determined by the sequencer's Sync setting - free/sync/retrigger ?

Assumed so, but that's not how it's acting to me. Maybe midi notes just turn the sequencer on and off while the sync settings only determine time division (erhm, i mean how the stepping is done in relation to midi timing- just a sync method and not a different mode of operation in the sense of free running lfos and such things)?

Surely someone who knows for sure will clear it up sooner or later.

[hakey]

in this case, are you sure we are not just hearing the 'voltage' turn on and then off?

Yeah, that's likely it.

[hakey]

Surely someone who knows for sure will clear it up sooner or later.

Maybe no one knows...

[Howard]

Why does the env only trigger if the sequencer tap is wired to an arbitrary input?

Because the 'ModSeq' gate options in the envelopes are defined by *used tap*.

Why does the env only trigger if the first slider is not at zero?

Does here. Maybe the next question/answer can help...

Why does the envelop trigger twice per measure if sliders 1 and 3 are not zero, but only once if 1,2 and 3, and not at all if 1,2,3 and 4?

They're not envelope triggers, they're envelope gates. Once a gate is opened by setting a positive value, it needs to be *closed* again (by a zero or negative value) before you can 'retrigger'. For a tie, simply don't ungate . Do you have the latest manual, hakey? If so, does the explanation need to be significantly expanded, with examples? (guessing it does!)

Why aren't the envelope clicks of uniform loudness?

Dunno - worth looking into (although I personally like those clicks).

More generally, how does the whole thing work?

Beats me!

[hakey]

Do you have the latest manual, hakey?

I do now. (the completed explanation in the manual is fine - no need to elaborate)

Why aren't the envelope clicks of uniform loudness?

Dunno - worth looking into (although I personally like those clicks).

I think the variable clicks I'm hearing are due to varying oscillator phase when the envelop retriggers (oscillators only retrigger at midi note-on).

[lectrixboogaloo]

I know I was a bit confused looking for a gate time switch but figured I would stumble across it eventually.

Makes sense now to me, I just think it is difficult to realize the sequencer treats v-trigger/gating in a different (but interestingly flexible) way.