Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 20, 2020 0:02:02 GMT
Hi All
Has anyone had any issues with the gate outputs on the SEQ16? I normally have it clocked to an LFO, and logically it should open the gate on and off for each step. However it seems to acting very intermittently at the moment.
A potential hardware issue? Or could it be something else?
Ryan
|
|
|
|
Post by slowscape on May 20, 2020 0:08:48 GMT
Are you using the LFO pulse? Perhaps it's an issue of the signal not being high/long enough for SEQ16 to read?
|
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556 
|
Post by Lugia on May 20, 2020 10:24:47 GMT
Could also be a waveform purity problem, too. Things that use timing pulses (gates, triggers) like to see hard leading edges on their clock signals. If there's a little bit of skewing on that, it could also cause a problem. I'd suggest outputting the LFO in question here to an oscilloscope (or something similar, like a waveform display in your DAW) to see if that leading pulse edge is vertical. If not, a bit of tweaking might be needed.
|
|
|
|
Post by Gaëtan on May 20, 2020 11:00:06 GMT
What is happening exactly ? Does the SEQ16 not advance steps on every pulse ? Or does it do it but the gate sometimes isn't fired ?
|
|
namke
wonkystuff
electronics and sound, what's not to like?!
Posts: 686
|
Post by namke on May 20, 2020 13:36:45 GMT
Hi, I noticed this yesterday too — feeding the seq16 with the square output of the LFO I found that the gate output of the sequencer was ‘tied’ to the next note; so you get a slur between notes rather than an expected staccato pattern. It didn’t seem predictable. In a way it ‘humanises’ the output, but that’s probably something that a performer wants to build in rather than having creative input from the machinery  …it just seems that the output gate is not always following the trailing edge of the input gate. The sequencer does advance on every input gate pulse |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 20, 2020 21:22:06 GMT
What is happening exactly ? Does the SEQ16 not advance steps on every pulse ? Or does it do it but the gate sometimes isn't fired ? It wasn't a gate issue, I've figured out the problem. I was using the square output to use as the clock source for the SEQ16. However as Lugia mentioned, it could have been out of phase when triggering each step. Once I used the L output instead, this seemed to solve the problem. What does the L on that particular output mean anyway? |
|
|
|
Post by admin on May 20, 2020 23:04:29 GMT
What does the L on that particular output mean anyway? I'm glad you got it sorted! The "L" isn't actually a letter but a graphical representation of a pulse, a short spike in voltage, as opposed to a rectangular wave. I understand it as a rectangular wave with a very very short pulsewidth. |
|
|
|
Post by robertlanger on May 21, 2020 7:56:55 GMT
Hi guys,
the "L" is a pulse where pulselength is set by the pulsewidth pot, indicated by the yellow LED. Sorry that the printing is not clear so it looks like an L !
Usually, the LFO square output works fine for the SEQ16 clock, but only when LFO is in triangle mode. If the LFO is in sawtooth mode, the pulse output (top one) is very short and maybe not sufficient / precise as clock for the SEQ.
|
|
|
|
Post by admin on May 21, 2020 22:29:27 GMT
|
|
