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

Separate ast and start URL parameters #89

Open
tobbee opened this issue Sep 17, 2023 · 1 comment
Open

Separate ast and start URL parameters #89

tobbee opened this issue Sep 17, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@tobbee
Copy link
Contributor

tobbee commented Sep 17, 2023

Make it possible to set start time separate from availabilityStartTime.

start time is to be interpreted as the timeline offset for media timeline.

In addition, it should be possible to specify that the first period starts at a later time.

For the most general case, we need three URL parameters, all defined in NTP seconds
(relative to epoch start 1970-01-01T00:00:00Z).

  1. start - this is the anchor point for the media timeline relative to epoch start
  2. ast (availabilityStartTime) >= start is the start and reference point for the mediaTimeline in the MPD. It is defined relative to epoch start.
  3. fpstart (firstPeriodStart >= ast is the time that the first period starts. It should be AST when the timeShiftBufferDepth makes the current interval overlap with ast. PresentationTimeOffset values must be set so that the media timeline is correct.

presentationTimeOffset must be set relative to timelineStart (start), so it may be be non-zero even for a period starting at the availabilityStartTime. This mimics the situation where one wants to have the availabilityStartTime point to the start of a program in a live channel, but the media timeline is relative to some other time like the Epoch start.

Constraints:

   start <= ast <= fpstart

If only start is specified (could be via relstart), ast and fpstart will automatically change to the same value.

With more values specified, unspecified values are automatically shifted to fulfil the constraints.
If specified values are not compatible, an error is returned.

@tobbee tobbee converted this from a draft issue Sep 17, 2023
@tobbee tobbee self-assigned this Sep 17, 2023
@tobbee tobbee modified the milestones: v0.8, v0.9 Sep 17, 2023
@tobbee tobbee modified the milestones: v0.9, v1.0 Oct 13, 2023
@tobbee tobbee removed this from the v1.0 milestone Oct 28, 2023
@tobbee tobbee moved this from Todo to Candidates in livesim2 features and enhancements Oct 28, 2023
@tobbee tobbee removed their assignment Oct 28, 2023
@tobbee tobbee added the enhancement New feature or request label Jan 31, 2024
@haudiobe
Copy link

Test Call:

  • good to have done
  • possibly also add large time codes (starting from 1970)

@haudiobe haudiobe moved this from Candidates to Todo in livesim2 features and enhancements Mar 26, 2024
@tobbee tobbee moved this from Todo to Candidates in livesim2 features and enhancements Jun 13, 2024
@tobbee tobbee moved this from Candidates to Todo in livesim2 features and enhancements Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants