Convergence of Trigger16 and Multi-IO track types

[sarukas]

It seems to me that the two track types in terms of software UI are essentially converging to similar functionality.

Why not merge both types into one type:  multi-io. Multi-io is winning out. This could be useful cleanup at least on the UI level, so that they are one and the same and share all  key feature (like drummatrix for trigger16). Multi IO today has a bit more capability alteady and I find myself just using MultiIO to drive the Trigger16 outputs. 

Would simplify things in the long term, at least it looks that way from where I stand. 

[Airell]

Hmmm... I'm using both, with the TR16 drum matrix I get dedicated outs to trigger stuff on my modular (non-Midi) and have Mappings for clock divisions out. From the Multi Track drum matrix I trigger Midi things (bitbox micro / external drum machine).
Each expander unlocks it's own screen, and if you use the MultiIO Screen for TR16, you don't have to 'enable' the TR16 on a track, right?