Skip to content

Better routing of instruments and sounds #58

@lilyvanoekel

Description

@lilyvanoekel

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:

  • Changes the architecture quite significantly and might touch nearly all cmajor code.
  • Cmajor didn't have a great way of supporting this task last time I looked into something like this.
  • This task is a bit vague in terms of goals.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions