Skip to content

Add support for MKI devices #4

@dagargo

Description

@dagargo

I think Analog Heat MKI could work with the same configuration as the MKII because the number of tracks and the bit depth are the same (4x4 and 24 bits). We just need to replicate the configuration.

But for Analog Rytm MKI, Analog Four MKI and Analog Keys the amount of tracks is user configurable and so is the bit depth. So, without reverse engineering how those are configured, we can only give it a try for now.

Assuming the blocks have the same structure for 24 bits values, we need to know if the track and bit depth configuration is stored in the machines. If this is the case, we could set the tracks configuration to be 4 device outputs (better if we use here the 4 output tracks) and 2 device inputs (better if we use here the main output) using Overbridge and then use it on Overwitch.

If the Overbridge block structure is the same as in the Digitakt and we're using 24 bit values, we can define the Analog Keys MKI as follows.

static const struct overbridge_device_desc AKMK1_DESC = {
  .pid = AFMK1_PID,
  .name = "Analog Four MKI",
  .inputs = 2,
  .outputs = 4,
  .input_track_names = {"Main L", "Main R"}
  .output_track_names = {"Track 1", "Track 2", "Track 3", "Track 4"},
};

And add it to the OB_DEVICE_DESCS array.

If all the above constraints are fulfilled, it could work.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions