PeterMoretti wrote:The current way the list works is almost unusable for the project I'm working on.
I think the answer here is that you have to change your working philosophy in order to adapt to the software, rather than trying to force the software to work according to your philosophy.
My method is to break a project down to multiple session files, each with a limited number of timelines. Even with very, very complicated jobs, I can't recall ever going over (say) 40 timelines. And even then, I would bet not even 10 of them wind up in the final.
As sessions get approved and finalized, I generally will create a new project called FINAL (or something like it), and even break that apart to FINAL TEXTLESS or FINAL HD or FINAL 4K. This works for me, but I concede there's lots of ways to tackle it. None of them would require having dozens of timelines in a single project.
The three reasons I try to avoid lots and lots of timelines in one project:
1) it's clumsy to find where they are and which is the one I really need (particularly when many changes are happening)
2) the computer slows down quite a bit when you load in lots of media and lots of timelines, particularly with complex node structures (at least on my hardware)
3) logistically, I can jump around a lot faster to one session with 6 or 7 current timelines than to have to juggle 20 or 25 timelines. To me, it's all about speed and avoiding confusion.
Having said all that: I totally agree that I would prefer for the timelines to auto-sort in Alphabetical order and not in Creation order. At worst, make it a pref or make the timelines sortable in the Timeline window.