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

SegmentTemplate format specifier #177

Closed
TheModMaker opened this issue Mar 20, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@TheModMaker
Copy link

commented Mar 20, 2018

There has been some confusion within Shaka Player and some of our partners about how to handle SegmentTemplate substitution parameters. DASH section 5.3.9.4.4 states the following:

Each identifier may be suffixed, within the enclosing ‘$’ characters, with an additional format tag aligned with the printf format tag as defined in IEEE 1003.1-2008 [10] following this prototype:

%0[width]d

Since it mentions IEEE 1003.1, it suggests that it could be any general format specifier; but to me, the following this prototype after means that it must be the following format. dash.js supports the more general form, supporting d, x, i, etc.; but Shaka Player only supports d since the text suggests that only that is valid. So my question would be: is $Number%05x$.mp4 a valid format?

The IOP guidelines offer no advice (that I can see); it would be helpful to include a clarification on this point.

@sandersaares

This comment has been minimized.

Copy link
Member

commented Mar 22, 2018

There was a discussion internally in DASH-IF about this in March 2017. While it did not result in any addition to DASH or IOP, I paste here the explanation expressed in that discussion:

The intention was to restrict to %0[width]d.
The reason was that the simple %0[width]d can be implemented w/o a library. If you need a full library for creating this, it may result in interoperability issues.

Perhaps we can make it more explicit in IOP vNext.

@sandersaares

This comment has been minimized.

Copy link
Member

commented Mar 28, 2018

It was decided yesterday that the above clarification will go into IOP 4.2.

@joeyparrish

This comment has been minimized.

Copy link

commented Mar 28, 2018

Thanks!

@haudiobe

This comment has been minimized.

Copy link

commented Mar 30, 2018

addressed in v4.14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.