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

Fluencerator Force-restart? #19

Open
DoktorPlekter opened this issue Mar 8, 2022 · 1 comment
Open

Fluencerator Force-restart? #19

DoktorPlekter opened this issue Mar 8, 2022 · 1 comment

Comments

@DoktorPlekter
Copy link

Hey! I've been using the Fluencerator alot in my patches, and I absolutely love the beautiful and organic phrases it creates.

Correct me if i'm wrong about this, but there seem to be no way to force an instant trigger of the "Generate" button, so you always have to wait for the phrase to end before it can generate a new melody (f.eks in a new incoming scale).
This also makes it hard to properly sync the Fluencerator with other Fluencerators and melody-generators, which might be a problem when dealing with different musical scales..

I'd suggest there be some type of "Force generate" input or switch, so a new phrase will generate right away without having to wait :)

@NikolaiVChr
Copy link
Owner

Yes there is yet no way to start a new phrase before the current has played out.

There is 3 principles in it, that has to do with how humans perceive note sequences. Those can potentially be broken by starting a new phrase at a arbitrary point in time.

That being said, I understand the issue you have.

If you only use one of these modules, you could let the Fluencerator know when you want to change, and then let the NEW output from that module trigger the actual change in the other modules.
But that wont work for multiple Fluencerators. And it might not suit your patch to wait for that.

I will look into this. Probably add a second generate input that does it instantly.

PS. I just noticed that the Fluencerator manual, was still under Coming in v2.1.0 section. I just fixed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants