Skip to content
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

Resequencer: allow to immediately issue documents #506

Closed
wants to merge 1 commit into from
Closed

Resequencer: allow to immediately issue documents #506

wants to merge 1 commit into from

Conversation

spoeschel
Copy link
Collaborator

So far the resequencer starts to regularly issue documents only after
the first EBU-TT Live document has been received. However for some use
cases this might be inconvenient as an active document must exist at all
times e.g. when creating segments for an MPEG-DASH stream. The reason
for documents being issued only after the first received EBU-TT Live
document is that certain parameters of that document are used for
initialisation.

This commit adds a new configuration parameter that specifies a document
which will be used for initialisation (instead of the first received
EBU-TT Live document). Therefore the resequencer will immediately (be
able to) start issuing documents after its creation.

Closes #505.

@nigelmegitt
Copy link
Collaborator

Hi @spoeschel please could you rebase this on the release/2.1.2 branch? Our release planning pattern here is to open pull requests against a release stage branch, then when we have a good candidate for release, merge that wholesale into master and add a release tag.

@spoeschel spoeschel changed the base branch from master to release/2.1.2 October 9, 2019 11:33
@spoeschel
Copy link
Collaborator Author

Yes, I rebased the MR branch and (force) pushed it again.

@nigelmegitt
Copy link
Collaborator

Thank you! @frans-ebu is on the case to sort out the travis build issue.

@nigelmegitt
Copy link
Collaborator

@spoeschel the travis build issue has now been fixed but I think it may need yet another rebase, apologies.

So far the resequencer starts to regularly issue documents only after
the first EBU-TT Live document has been received. However for some use
cases this might be inconvenient as an active document must exist at all
times e.g. when creating segments for an MPEG-DASH stream. The reason
for documents being issued only after the first received EBU-TT Live
document is that certain parameters of that document are used for
initialisation.

This commit adds a new configuration parameter that specifies a document
which will be used for initialisation (instead of the first received
EBU-TT Live document). Therefore the resequencer will immediately (be
able to) start issuing documents after its creation.

Closes #505.
@spoeschel
Copy link
Collaborator Author

Closing, because of #503 (comment).

@spoeschel spoeschel closed this Oct 10, 2019
@spoeschel spoeschel deleted the issue-505-resequencer-immediately-issue-documents branch October 10, 2019 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants