Replies: 2 comments
-
Yep, that's correct. They stay enabled. A bypass option could work, but may not be consistent across all plugins. i.e. they can just ignore bypass. Some plugins have major problems when the audio callback stops, so just stopping processing could get weird. Bypass I think would be easy enough to sneak in. Eventually I'd like to have plugin loading/unloading happen async in the background and also add a "unload when not active" option. Crossfading graph change - that's exactly what it's doing now, just not user-definable. I do plan on a user option in the future though. |
Beta Was this translation helpful? Give feedback.
-
Great, thanks for considering it! Long crossfades would work nice when there are delay and reverb tails. |
Beta Was this translation helpful? Give feedback.
-
In my brief testing, I noticed how well graphs are changed from one to another in Single mode (I'm changing via Program Change). Nice! Then I saw that for each new graph added with its own plugin(s), the cpu use increased. I suppose keeping them enabled allows for the smooth switching, but perhaps an option to bypass the other graphs would be quite helpful to keep cpu use down?
Or is there another approach I didn't find that would have this result? I suppose that would be more like changing Sessions via Program Change?
Also ideally, especially in the case where the graphs are not bypassed, I thought an option to automatically crossfade (as a user definable time length) between one to the other would be very nice, so as to avoid clicks/abrupt changes.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Beta Was this translation helpful? Give feedback.
All reactions