Hi Paul
I think you may have misread Simon's question. The scenario he described was one where he was anticipating a lot of swapping out of tracks and to avoid having to recalculate all the subsequent prewaits in a timeline group after doing so. He also wanted the ability to just play from a point in a group with the subsequent cues following on without loading to time
Using Fire first groups with follow ons solves this problem, but because a fire first group has no duration a lot of the timing info is lost. Also the duration of a timeline group containing multiple fire first groups is the time of the last prewait on a nested group within the timeline group group
To a certain extent you can read total times for any point in a group by using the load to time slider, (and some may ask that, if the load to time slider knows where it is within the duration of a fire first group, then why can't the group itself know this and state its duration?)
Nested Playlists in a playlist group behave better for certain uses, but lack the control over overlaps etc.
And of course loops and devamps, take any concept of durations into another dimension.
This screenshot shows the load to time window displaying the true length of the Timeline group (which differs from the duration the Timeline group itself displays)
It also has an example of nested playlist groups which does display the total time correctly. (The top level Playlist can also be loaded to time and the following playlists will trigger as expected, so for many uses this is the best solution.
Mic