-
Notifications
You must be signed in to change notification settings - Fork 2
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
using 64 grids #16
Comments
yeah! that sounds great. it should just work I believe, the shading of the buttons will be weird of course but I would definitely love to have a PR if you want to make one! |
Most of the changes have looked straightforward enough, though there are a few changes I'm not sure about, for example
Is it safe to leave this line as is though my beat resolution on the 64 grid is half beats, rather than quarters like on the 128 grid (I may be totally misunderstanding this!)? There are a couple of other things, like midigrid 64 support and possibly supporting switching grids on the fly that I need to think about some more, all those are still TODO in the ggrid file. Thanks for making your script so accessible! |
yeah that should be safe! |
Hello, I've been using paracosms since release and it's great, thanks for an amazing script.
Up to now I haven't used the grid much but I'm starting to get into that more lately, however I have a 64 grid. It's workable but I was thinking of having a go at improving the experience a bit, if you don't mind I have some questions.
It seems all the grid functionality (other than loading the grid in
lib/paracosms.lua
) is in theggrid
file, is that correct?My plan would be to reduce the available sample slots on the grid to 56 (you could still access sample slots greater than 56 on the norns), clamp any loading of samples so there's only 8 per row, and decrease the time scale of sample start/end/duration. Assuming I get the math right in the relevant functions (famous last words), would there be any other gotchas with a plan like that?
Thanks!
The text was updated successfully, but these errors were encountered: