We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
0
Since #1278 , when rand is sampled at the start (cycle 0), it always returns 0.
rand
Now, every number is as likely as any other, but this seems a little bit implausible. It means that for example
sound(wchooseCycles(["bd", 0.0001], ["sd", 1000000000]))
starts with a very unlikely kick.
Not sure how best to fix this, maybe just return 0.5 if the onset is 0?
The text was updated successfully, but these errors were encountered:
timeToRand
Successfully merging a pull request may close this issue.
Since #1278 , when
rand
is sampled at the start (cycle 0), it always returns 0.Now, every number is as likely as any other, but this seems a little bit implausible. It means that for example
starts with a very unlikely kick.
Not sure how best to fix this, maybe just return 0.5 if the onset is 0?
The text was updated successfully, but these errors were encountered: