-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature Request: Structured randomization #10
Comments
Hi cladelpino. That sounds cool! We can add that in. "Random" seems to be a popular feature. BTW, you seem to be catching on to C++ quickly (nice PoC)! |
jaja yes, more like "never wrote c++", I am not new to programming or OOP :). If you'd really consider this feature how would you implement it ? Just 2 comments from my point of view: 2- I'm not sure from a user story POV what could be a nice way to piece this. Specially at the degree of user control where of course the more you give, the more you have to intervene the GUI + runtime.
|
Yes, I think it would be optional (keeping the traditional 'full' random as an option). For the degree of user control, probably to start just "Minimal user control" as the option. And then the "High" option either at the same time or at a later release. For the "High" level, I think the easiest thing to implement would be to have a text box in the context menu [if this is possible, I think I could add a text box as child of a menu item, but I've never tried] where you can define your own and underneath that text box, the menu items would enumerate the list of predefined pattern structures you could chose. If we allow users to add to the list I have to save these values and also implement delete/edit functionality, which while doable, for our time efforts, I'm not sure it would get higher priority over other items. [i.e. it may happen, but no promises]. What do you think? Would just having a Minimal and a 'non-saving' High work for your purposes? And are there any patterns you would like as part of the default list (besides 'A', 'AB', 'ABBA', 'ABAC')? |
First, thanks again for letting me contribute, again I think this is a very good project, and its nice to see its being developed by ambitious yet open devs. For me, what I termed "minimal" is more than enough. I think that if the patterns are "hardcoded" at build time from a file in github (I say this without knowledge of the module building process), I can contribute a bunch of them to that file. From the global project viewpoint, I also think that starting with "minimal" is the way to go. If in the future someone else appreciates this feature and requests more user control perhaps some effort can go into other options. |
Thanks for the great ideas. Sorry we haven't gotten back sooner. Life is busy. The "Minimal" version has been added in this 0.5.5.2 release. If we have time, I would like to add your High version too. If you want to add more patterns for the predefined mode, look in: and then
Of course, feel free to implement anything else you desire. There may be a lot of spaghetti in my code, but I think you'd figure it out. |
Ok, just made a PR with some other patterns, let's see how that works !! Off to try your new version :) |
Hi, first, amazing work on the modules ! thanks for it 👍
I'm using chained voltSeqs in pattern mode for procedural composition, and would love to see an optional feature where randomization comes from a randomly chosen "structure" i.e. "A" (just one value repeating), "AB" (two values alternating) "ABBA", etc.
I'm totally new to c++ so for now implementing this myself would be a bit burdensome. Nevertheless I've put together a small proof of concept, where voltSeq::randomize() would call the StructGenerator.getValue(step) function:
https://onlinegdb.com/rJ4_JAVLf
I'd love to hear thoughts on this. Thanks again for the amazing work !!!
The text was updated successfully, but these errors were encountered: