The first valid Part in a displayDurationGroup has its expectedDuration extended by 3 seconds under rare conditions about sofie-core HOT 2 CLOSED

That is a reasonable explanation to me! Thanks 🙂

from sofie-core.

Actually, I think this works correctly. Here's why I think so:

1. The Part 1 is invalid, but it's expectedDuration is 3 seconds.
2. An invalid Part is a Sofie invention. The NRCS has no idea, that this is invalid, so it's counting the show as if that 3 seconds are supposed to happen.
3. If both of these parts belong to the same displayDurationGroup, then they share the pool of their expectedDurations.
4. Since Part 1 is invalid, it has no chance of playing. That means all of it's expectedDuration (3 seconds) should "oveflow" to the next available Part, which in this case in Part 2.
5. By overflowing the time, Sofie maintains, to the best of it's ability, the intention of the description of the Rundown from NRCS: there are 3 seconds planned in Part 1, but they cannot play, and Part 1 and Part 2 share timing.
6. If the duration of Part 1 should be discarded, because it's invalid, Blueprints should set it's expectedDuration to 0 (they are not expecting it to play).
7. If the duration of Part 1 should not be discarded, but (1) and (2) should not share timing, they should use unique displayDurationGroupIds.

from sofie-core.