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

Adds mfhd starting sequence option to Transmuxer #395

Merged
merged 2 commits into from
Aug 24, 2021

Conversation

collin
Copy link
Contributor

@collin collin commented Aug 24, 2021

This PR replaces #394. It removes build artifacts and address the change in the test suggested by @brandonocasey.

/cc @gkatsev

Adds an option firstSequenceNumber to Transmuxer.

Can be used like this:

new Transmuxer({ firstSequenceNumber: 10 });

This is passed in to VideoSegmentStream and AudioSegmentStream.

When mfhd boxes are constructed, the starting sequence number will be
taken from that option. The default value is zero.

This is useful for generating segmented streams out of order. Out of
oder processing allows for restart, parallelism, or random seeking into
source material.

Adds an option `firstSequenceNumber` to Transmuxer.

Can be used like this:

new Transmuxer({ firstSequenceNumber: 10 });

This is passed in to VideoSegmentStream and AudioSegmentStream.

When mfhd boxes are constructed, the starting sequence number will be
taken from that option. The default value is zero.

This is useful for generating segmented streams out of order. Out of
oder processing allows for restart, parallelism, or random seeking into
source material.
@brandonocasey brandonocasey merged commit 6ff42f4 into videojs:main Aug 24, 2021
@brandonocasey
Copy link
Contributor

This is out in 5.13.0 Thanks @collin

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.

None yet

3 participants