-
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
Should all inlets be hot? #7
Comments
While extra patching is bit annoying in simple situations like this help patch, I think being able to synchronize inlets is useful for optimization purpose. Below is a quick perf test patch that shows some significant differences (case 1°: as is, case 2°: azi & elev synchronized, case 3°: all inlets hot) Maybe @matcham or @bltzr have strong opinion on this ? Do you guys think vbap's inlets should be hot ? Maybe an option would be nice, but depending on how much work it is, I wonder whether it is worthing it (my impression is that it is not). If we were to put some time on vbap external, I tend to think we'd better revamp it from the ground up to modernize its interface (ie. specifying position as aed arrays) rather than adding options here and there. (just thinking out loud, here) Test patch below:
|
It seems like there is a lot of extra patching needed to generate output from vbap with trigger objects (see attached screenshot). Would it be better to just make all inlets hot so that they generate output? Is there ever a situation when you would not want output?
Since this is a function change, we want to be careful. Making it an option is more difficult than just changing them to be hot.
And depending on the difficulty, I may need to tackle it later.
The text was updated successfully, but these errors were encountered: