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
{{ message }}
This repository was archived by the owner on Jun 7, 2026. It is now read-only.
This is a quality of life idea that I came up with. Currently you can only have one output node
that transports the sound from the internal engine to the VST plugin. Multiple nodes will not
crash the VST, but will lead to undefined behavior (thankfully not UB that’s memory unsafe, just
that we haven’t defined what happens in that case). The proposed fix is defining a behavior of
just mixing the inputs to each output node together which should be sufficient. This should not
be too hard to implement, but might take extra time so I feel like 1 hour is a comfortable
estimate.
This is a quality of life idea that I came up with. Currently you can only have one output node
that transports the sound from the internal engine to the VST plugin. Multiple nodes will not
crash the VST, but will lead to undefined behavior (thankfully not UB that’s memory unsafe, just
that we haven’t defined what happens in that case). The proposed fix is defining a behavior of
just mixing the inputs to each output node together which should be sufficient. This should not
be too hard to implement, but might take extra time so I feel like 1 hour is a comfortable
estimate.