Skip to content
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

`IN` reading is delayed #132

Closed
scanner-darkly opened this issue Nov 16, 2017 · 2 comments
Closed

`IN` reading is delayed #132

scanner-darkly opened this issue Nov 16, 2017 · 2 comments

Comments

@scanner-darkly
Copy link
Member

@scanner-darkly scanner-darkly commented Nov 16, 2017

Please describe the bug.

IN returns a cached value, not the actual value at the input when the command is executed

Please include the hash displayed at startup and the release of the software (e.g. "Teletype v2.0.1 5f838c9")

Teletype v2.0.1 5f838c9 ad358cd

What steps are required to reproduce the bug?

  1. connect a sequencer to teletype, CV to CV input, gate out to trigger input 1
  2. set script 1 to TR.P 1; CV 1 IN

expected result: CV 1 outputs the incoming CV
actual result: CV 1 outputs some previous CV

this is due to the fact that the input is being read from a timer which runs every 61ms.

@scanner-darkly
Copy link
Member Author

@scanner-darkly scanner-darkly commented Nov 16, 2017

@scanner-darkly scanner-darkly mentioned this issue Nov 17, 2017
0 of 2 tasks complete
@scanner-darkly
Copy link
Member Author

@scanner-darkly scanner-darkly commented Dec 20, 2017

this was fixed/merged, closing

@scanner-darkly scanner-darkly mentioned this issue Jan 24, 2018
2 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant