Many times in my patches I have had gates remain high after stopping the clocks. I’m using Impromptu Clocked i to Polygene, among other things. I have deselected “Outputs high on reset when not running”. To me, stopping the clock running should also stop the gate outs, or the reset should, but neither seems to, leaving me with open VCA’s when it should be silent. Am I missing something? Insights please, and/or fixes
Uuups, i have to correct myself: i ignored the sentence - I have deselected “Outputs high on reset when not running” - from btrbcomposer
When the deselection is done the clk output is low after stopping.
1 Like
Nice try, but it does not solve the problem. I just tested with impromptu CLKD all 4 settings checked: when the Run button is hit on a high state of an CLK output it stays high.
What now?
So the order of your posting is mixed up and the problem solved ?
Yup, problem is solved. Order of the postings is flipped, i think because of the bloody approval process.
Thanks a lot!
1 Like
I have those all checked, and it still leaves gates high
Are you sure you have the gates high when not running turned off ?
and
1 Like
First thing I tried, and always check in a new patch
So do you have a patch that shows your problem, for me to test ?
Euclidean melody.vcv (15.6 KB)
This is the current project
I found part of the problem. The Polygene is holding when in gate or hold modes, but not in pulse mode. It’s still getting the signal from the clock as high. I’ve inserted trigger to gate modules (Bogaudio DGate) between it and the manifold as a quick fix.
1 Like
Yes it’s polygene it produces gates even when the clock is stopped. Your workaround is changing the gate lengths polygene is producing, as an alternative you could mute the gate output when the clock is not running, like f.i.
The run output of the clock is flip/flopping the moots (set to “use trigger for control” via the push trigger.
1 Like