I guess you probably mean increase as reducing TxP may actually imply deleting already recorded tracks/parts and introduces the need of multiple checks to be performed as well as potential user confirmation before deletion, then you may want as well the possibility to undo etc…
And even if you just allow to increase TxP, and actually do it “by mistake”, you may want to come back to the original state, thus implying the need for deletion or undo… Honestly it sounds far too complex to me and as such I doubt modifying an existing song TxP is likely to happen… at least in the flow you describe (we could imagine as part of song management that we could duplicate a song and change its target TxP at that time without then the need to provide undo mechanism)…
But it remains a very good idea and a way to define the famous already discussed “matrix” feature for empty songs… and that would already be great.
If you talk about T <= 6 and P <= 6, I fully agree, I see no reason why we couldn’t have this. But if you imagine expanding further than 6x6, then other considerations come to my mind:
- Impact in the UI. more than 6 tracks or parts would imply a kind of scrolling in the UI, and this is not probably what we want.
- Specs of the hardware. I have no idea what the specs of the Aeros are in terms of bus, RAM or CPU… and we may reach some limitations. @DavidPackouz: Do you think it would be possible that you disclose some of those characteristics of the hardware specs somehow (maybe it’s even already published somewhere, but I didn’t find this information, I mean beyond just the storage specs) ? Just at least to have an idea of what is realistic to expect from the platform ?
Honestly I never felt yet the need to go further than 6x6, but maybe someone else did. I would then be very curious… Is it still the a looper or is it a full-blown DAW that you need in this case ?