Skip to content

How to manage AMYboards chained to each other (or to a Tulip) #1049

Description

@bwhitman

Discussed in #1048

Originally posted by dpwe June 25, 2026
The Grove I2C connector allows one AMYboard to be an I2C secondary to another AMYboard (or to a Tulip CC). This provides additional synthesis horsepower for richer, more complex synthesis. But what should the control look like?

You could imagine having the user see a single synth, but have polyphony spread across multiple instruments. However, this could be a bit weird with any given note appearing on an unpredictable device in the chain.

I prefer the idea of having a given synth reside on a particular device, then having software on the "main" device know how to dispatch to the correct device.

I guess you could do that now with (almost) no software, by chaining devices' audio and midi (as well as I2C), running midi-thru and mix-audio-in software on each device, then having different MIDI devices configured on each AMYboard so they each respond only to the MIDI messages they recognize.

Any other ideas about how you'd want this to work, or how it should be managed internally?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    AMYboard

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions