eg, a scheduled 3m05s commercial break [stop set], plays all events (cut start to transition start) within it at the speed required to make the break exactly 3m5.00s long. Overrides 'forced length' of individual carts. Respects rdadmin global time scaling limits (eg max +/-3%). This is like Nexgen/WO etc.
Prime advantages over using 'Forced length' (Individual TS mode) are;
Far easier management (no need to manually turn on 'enforce Length' and set duration in each individual cart within the break)
all events play at same speed, so if one short cart (say a 5 second ID at end of break) is 1s shorter/longer than it should be, than across a long ad break, time scaling can compensate for that.
it's easy on a log to 'see' if a break is full/empty. Suggest slightly visually indenting nested commercial breals Av/NexGen style.
It works around latency issues better. i.e. if there are 8 items in break, and each have a system segue latency gap of ~30ms, then cumulatively this causes a break (using 'Individual TS') to return ~0.25s late. The same break taken in 'Block TS' compensates for much of the latency on the fly, and the return (late) error is much smaller.
eg, a scheduled 3m05s commercial break [stop set], plays all events (cut start to transition start) within it at the speed required to make the break exactly 3m5.00s long. Overrides 'forced length' of individual carts. Respects rdadmin global time scaling limits (eg max +/-3%). This is like Nexgen/WO etc.
Prime advantages over using 'Forced length' (Individual TS mode) are;