-
Notifications
You must be signed in to change notification settings - Fork 11
Better routing of instruments and sounds #58
Copy link
Copy link
Open
Labels
area:dspTouches on DSP/Cmajor onlyTouches on DSP/Cmajor onlycmajor:highA lot of Cmajor knowledge is neededA lot of Cmajor knowledge is neededcomplexity:5High complexityHigh complexitypriority:lowNice to haveNice to havestatus:readyCan be picked upCan be picked uptype:featureNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
area:dspTouches on DSP/Cmajor onlyTouches on DSP/Cmajor onlycmajor:highA lot of Cmajor knowledge is neededA lot of Cmajor knowledge is neededcomplexity:5High complexityHigh complexitypriority:lowNice to haveNice to havestatus:readyCan be picked upCan be picked uptype:featureNew feature or requestNew feature or request
Feature Description
Currently each instrument's code decides for itself if it should play. This works, but it might not be the most efficient approach. A router or controller type of component might be needed.
This is a complex task because it:
This task might also be a good opportunity to see how the grouping of instruments currently works, and if that could be improved as well. Maybe a more "shared architecture" of components can be achieved, although we do need to be sure we keep supporting multiple drum sounds playing at the same time.
Only pick this up if you know what you're getting into 😄
Motivation / Use Case
Better architecture might be needed to scale to support more sounds.
Alternatives Considered
No response
Additional Context
No response