You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FilesystemProducerImpl always begins output file numbers at 1 when it is first run, for EBU-TT-D documents. Allow it to be specified as a config parameter.
Rationale:
When creating EBU-TT-D documents to be wrapped in MP4 and served with a DASH manifest, the process may need to be begun some time after the MPD's availabilityStartTime. When this happens, in a live mode, the segment number needs to be the (currentTime - availabilityStartTime)/segmentDuration - that could be calculated in the encoder, or alternatively it could be preset in a config file that is modified to set the right value.
The text was updated successfully, but these errors were encountered:
Part of the fix for #481 - allow the filesystem output carriage begin count to be overridden in the ebuttd-encoder using a first document datetime and a document duration. The zeroth document is calculated as the difference between the current datetime and the specified datetime divided by the document duration.
The
FilesystemProducerImpl
always begins output file numbers at1
when it is first run, for EBU-TT-D documents. Allow it to be specified as a config parameter.Rationale:
When creating EBU-TT-D documents to be wrapped in MP4 and served with a DASH manifest, the process may need to be begun some time after the MPD's
availabilityStartTime
. When this happens, in a live mode, the segment number needs to be the(currentTime - availabilityStartTime)/segmentDuration
- that could be calculated in the encoder, or alternatively it could be preset in a config file that is modified to set the right value.The text was updated successfully, but these errors were encountered: