OK, I’ve been making a concerted effort to use cycle markers and I think that while the metaphor works, Cubasers don’t -use- Cubase like that (or rather… would prefer it to work in reverse.)
For example, clearly the Locators were meant to be a tool for cycle markers. But that’s not how most users see it… which is why all the posts about ‘How Do I Lock The Locators’. We don’t want to lock a cycle marker. The Locator is the thing that should be locked.
Unless I’m missing something, cycle markers can’t be -individually- locked.
And, back to my original b-i-atch… cycle markers are not hierarchical… you can’t have a child inside a parent. And THAT’S what I want.
Actually, if anyone @ SB has a copy of Photoshop, just copy their Layers window (and while yer at it, copy their whole dockable framework!). A Layer in Photoshop can be a child and parent of another layer. You can group layers, lock them, move them, duplicate them, at will.
Ultimately THAT’S what I want. I want markers to be like a Layer… a ‘container’ for a -horizontal- section of a project, that I can manipulate like one can -vertically- with a Cubase Folder or Track/Lanes. For example, if I could select a ‘Layer’ and then change the tempo for that section, or duplicate it, or move it inside another layer as part of a larger section. SB came up with ‘Arrangements’ but it’s too clunky. So are Cycle Markers.
You can -do- anything in Cubase, but the current arrangement of cycle markers and ranges and whatnot is just not that intuitive and slow to work with on big projects.