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 continuous patterns with control busses needs segment to work properly #806
Comments
You can do |
You have to end up with a discrete pattern, to be able to events over a network. We could look at setting a default control rate if a continuous pattern reaches a bus. 30 per cycle? We could do the same for 'normal' events, e.g. |
but wouldn't it be better to use a function like |
Yes true, it doesn't really make sense to send a continuous signal to an event bus. A tradeoff between doing something approximating what a beginner expects but which might sow seeds of misunderstanding, and not doing anything. |
Beginners may also get confused. I'd be surprised to get more than one beat from |
Looking a bit closer, I see that e.g.
This does send the bus value at 20Hz, but always sends 0.5. If you send this:
The sinewave will be sampled and sent at 20Hz. So this always sends 0.5, because it's being combined with the 'sound' which is only taking one value:
This sends the sine to the bus at 20Hz, but no sounds are triggered at all:
So I was thinking this would both send the
However no, nothing gets sent then.. Combining discrete and continuous patterns together is not well defined, I guess.. This could probably be fixed. |
it looks like that using continuous pattern with control busses just applies one value, i.e.
A workaround is to segment the continuous function like:
But this does not look correct, because one advantage of control busses is that you don't have to segment your pattern with
chop
,split
orsegment
, I guess.The text was updated successfully, but these errors were encountered: