When a program is pulled up in Dubber to be segmented, every time a segment is marked and saved, Crispin messages Crisin a Media Update that includes the segment information, duration, SOM, etc. to ProTrack to update their database. So, for example, the first segment that you mark will send a message saying that the total duration of the program is the duration of the first segment. After the second segment is marked, the update will tell ProTrack that the duration of the program is the sum of the duration of both segments. And so on and so on until the last segment is marked.
For most sites, ProTrack is configured to have a duration change threshold. This means that any attempt to update media is compared to the current duration. If the difference between the two is too large a percentage of the current duration, the update will be rejected by ProTrack. This percentage threshold can be adjusted or disabled at your Node. If this setting is still enabled at your node, it can cause ProTrack to reject segments due to the change in duration it initially causes. See the screenshot as an example:
This is the automation event log for one of the shows that had segments sent over from Crispin be rejected by ProTrack. The highlighted line is the first rejection message. Three lines above the highlighted line, you can see that the show came into the system with an initial duration of 01:27:50;00. Two lines above the highlighted line, you can see that the first message is sent, which means the first segment was marked with a duration of 00:18:33;29. This changed the entire duration of the program to 00:18:33;49, and because of the duration threshold setting, it is rejected since the difference is too great. You can see that the second segment is then added and accepted, as it does not trigger the threshold.
Then, in the highlighted line, Crispin attempts to change the duration to 00:41:54;24, which would be almost a 100% increase. The message is rejected. And obviously for every segment added after that, the discrepancy is even larger than the time before, and each is rejected. Crispin is still aware the segments, but ProTrack is just rejecting the media update to their database.
The solution for this actually pretty simple. Before you finish marking the final segment of a show, make note of approximately what the sum of all of the segments’ duration will be and open the show in ProTrack. From the Launch Pad of ProTrack, you can hit the Program Information button, press Q, and put the package number into the package number field. Once you’ve searched and you’re looking at the program offer page, you can press F1 or navigate to Tools->Media Info. On the Media Info page, highlight the attachment, press ‘U’ to update, and then enter the approximate total duration that you made note of earlier. Confirm the update and close out of ProTrack. You should now be able to finish marking the final segment in Dubber, and all of the segments should be reflected. This will work even if any of the segments had been rejected along the way.