You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in #800 I added a bunch of voice termination on structural changes things
right now this just slams the voice closed. Would be nice if there was a fadeout but that means the voice has to go somewhere to fade and its zone is now no longer configured properly.
One thing we could do is, like, render the voice for 6 blocks into a voice buffer put the voice pointer in an engine wide 'orphaned voice winddown' list have engine process mix that in i guess but then we skip loads of things like processors and busses so it kinda doesn't work.
alternative is voice termination isn't instant; we mark a zone for move or delete n blocks later and so on and then have all the structural messages be async.
it's a hard problem.
The text was updated successfully, but these errors were encountered:
Handle a voice stealing API which, for now, steals only at
the hard limit, but has been tested at both hard and soft
limit at this commit with a different configuration. Closes
At the same time, add a voice termination fade for soft
terminates which keeps the voice alive for 8 blocks with
a fade during the period. Closessurge-synthesizer#801
in #800 I added a bunch of voice termination on structural changes things
right now this just slams the voice closed. Would be nice if there was a fadeout but that means the voice has to go somewhere to fade and its zone is now no longer configured properly.
One thing we could do is, like, render the voice for 6 blocks into a voice buffer put the voice pointer in an engine wide 'orphaned voice winddown' list have engine process mix that in i guess but then we skip loads of things like processors and busses so it kinda doesn't work.
alternative is voice termination isn't instant; we mark a zone for move or delete n blocks later and so on and then have all the structural messages be async.
it's a hard problem.
The text was updated successfully, but these errors were encountered: