-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EBUTTDEncoder] Allow first output file number to be specified #481
Comments
nigelmegitt
added a commit
that referenced
this issue
May 9, 2018
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: