-
Notifications
You must be signed in to change notification settings - Fork 3
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
make multi-channel spatialised synth modules #56
Comments
Okay, tell me more. We have approached this in the past with VBAP to calculate coefficients for outputgains, virtual sources for Spat, or HOA. Make separate modules for each, time permitting? |
…bstraction handling spat and panning in camu.synth.voice-8ch
Hi Aaron, this issue is meant for a (sub)module to be put into poly voices for multi-touch use or load-balancing.
|
Yes I think it is the same algorithm.
I have not found an issue if the unused poly~ voices are muted. Incidentally I have some similar design needs for my spatial filter example, which also requires poly~. For example I also need a module to send parameters to all mubu.concat~ objects at once since attrui doesn't work. So maybe we can compare / combine ideas. |
have a look at the |
It would be cool if we can use the azimuth value in the key-mixer and have that sent to a multichannel spatialization patch which takes speaker number/step as an argument and positions the grain |
Thanks. Trying to mute unused voices, I've awakened the devil of the details:
|
I would think option 3, using the busy state to pilot muting, would be the
best option to pursue...
…On Thu, Jun 2, 2022 at 11:19 AM diemo ***@***.***> wrote:
I have not found an issue if the unused poly~ voices are muted.
Thanks. Trying to mute unused voices, I've awakened the devil of the
details:
- when is an instance no longer needed and can be muted? for this we'd
need to know how long the last triggered grain will sound.
- And what about periodic play?
- Or is it possible to use the busy detection of thispoly to drive mute
?
—
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRYDC5NQJMNUHA6P4XWYGDVNB4CZANCNFSM5WEW7OZQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
The text was updated successfully, but these errors were encountered: