I think that 15 characters is mostly enough. The list display could clearly handle longer names, automation display would require scrolling as you’ve suggested.
Assign labels are bigger issue in my point of view, as mentioned in the ASSIGN - The most misunderstood Hapax feature :
Nice to have feature would be dual labels in CC definitions, where current primary label would be used in lists (15 characters long) and secondary optional 7-characters long label would be used on the ASSIGN pots. Using single label for both purposes generally makes one of the two views compromised.
Clearly both our suggestions are sub-optimal in terms of memory management.
I can’t guess what the cost of these changes would be, but it would certainly feel nice not to have to compromise on labeling in instrument definitions ![]()