Ok, this is a wee little request, but from the Architecture “naming convention” world.
It is very clear AS is going to grow and grow in the coming years, and the use of “+LOOPGUIDE” and other “+” flags (that designate an Ableton track for AS use) is a clean architecture…using the “+ flags” are likely gonna grow graciously, and not need any re-design, as the product grows and grows.
Yet there seems to be an exception to this naming-convention architecture. And bringing this up is rather nerdy (sorry, but “it never hurts to ask”).
Regarding the Ableton track named “Sections” that AS uses for section midi clips. I am sure the majority of the AS community use this track and are happy with the many benefits.
Yet, I seem to really want ANY track that AS uses for key control/functionality, to have a corresponding “+ flag”
Yes, lol, I am actually requesting in this (architecture) Feature Request to create a flag called +SECTIONS
Yes, this change would cause a 1x pain for some (like anyone with MANY MANY “multi-project files”), but perhaps for the majority such a +Sections flag would be easy to adopt (and actually, the track can be called anything, because AS would only care about the + flag).
(A thought…during some number of future releases, it would be helpful if AS, when it sees a MIDI track called “Sections”, without a +SECTIONS flag, would give a helpful nudge to the owner with a reminder…just like it does when no Locators are found).
That’s all. Call me crazy (I would agree). …maybe this +Sections request is just a small necessary “course correction” as AS 2.7.5 becomes 3.0, which someday becomes 7.0…AND BEYOND!
Prost!
(side note: I actually had an Ableton backing track project with an AUDIO (not Midi) track called “Sections”, and this was back when I was just learning (and was overwhelmed with) Ableset, so without much experience, it took me awhile to navigate the issue and create a MIDI track named “Sections”).
