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

Quantize vs Loop Length #16

Open
wraybowling opened this issue Sep 9, 2020 · 2 comments
Open

Quantize vs Loop Length #16

wraybowling opened this issue Sep 9, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@wraybowling
Copy link
Member

A quantized beat is also a less lengthy one. Perhaps Quantize and loop length can live on the same knob as opposites by somehow organizing the selection of beats in the grid creatively. Something like a bayer dithering pattern comes to mind..

@wraybowling wraybowling added the enhancement New feature or request label Sep 9, 2020
@wraybowling
Copy link
Member Author

A Bayer dithering pattern would place beats like so

1-------
1---2---
1-3-2-4-
15362748

but to quantize effectively, it's much easier to iterate sequentially

12345678

because detecting a beat is a comparison of all the slots within a range. I'll need to think about this more.

@wraybowling
Copy link
Member Author

Also, writing 1–8 was easy as a thought experiment, but there are actually 24 slots for every quarter note so the divisions would not be as simple as a bayer pattern because 24 is not a a 2^n number.

wraybowling added a commit that referenced this issue Sep 11, 2020
initially set to 4. the max is 3 however. All values are reduced by 1 which also deminishes old beats.
Also includes preliminary work for #16 quantizing and does not build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant