Skip to content

/ ansible

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kria: ratcheting glitch w/ ext clock + reset gate #37

Open
fourhexagons opened this issue Jan 1, 2019 · 1 comment
Open

Kria: ratcheting glitch w/ ext clock + reset gate #37

fourhexagons opened this issue Jan 1, 2019 · 1 comment

Comments

@fourhexagons
Copy link

@fourhexagons fourhexagons commented Jan 1, 2019

I just updated to 1.6.1 and I'm loving the new features. I noticed a glitch with the Trigger Ratcheting feature when externally clocking Ansible and also feeding a gate to the RESET input. I'm using Pamela's New Workout to clock and also provide a run gate to the RESET input so that my sequences start in phase.

What happens is that if I have ratcheting on step 1 and I stop/start Pam's, ratcheting doesn't happen on step 1 and then it adds triggers to empty steps. Here's a video demonstrating the issue. I'm not as snappy as I usually am in my Lightbath videos, but hey, it's NYE 🎉
@csboling csboling mentioned this issue Aug 17, 2019
Merged
@csboling
Copy link
Contributor

@csboling csboling commented Dec 2, 2019

Possibly resolved by #71, please try out the build in this post if you get a chance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@fourhexagons @csboling