I think that it would be a bit more complicated to implement than to simply increase the number of sequences
in fact, the sequences being mainly “state” informations (track mute/unmute, linked pattern) I think they could raise this number without impacting too much the memory use
moreover, I wonder which Pyramid user actually uses more than 16 different patterns per track…(I’m curious to know)
so if it is a RAM issue maybe it is better to have only 16 different patterns on each track but to raise the number of sequences to 64 (for example)… ?
I guess you have already contacted Squarp directly about that
what is their answer?