DASH: Format strings not supported in SegmentTemplate

[GoogleCodeExporter]

> What steps will reproduce the problem?
1. Load an MPD which uses $Number%08x$ in the SegmentTemplate.
2. Cast requests segments with the string "$Number%08x$" in them.

> What is the expected output? What do you see instead?

Chromecast should request ".../00000001.m4s" rather than 
".../$Number%08x$.m4s". After 00000009.m4s it should request 0000000a.m4s.

> What version of the product are you using? On what operating system?
Chromcecast firmware version 31432.

Please provide any additional information below.

ISO/IEC 23009-1:2012(E) 5.3.9.4.4:
"Each identfier 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"

Beware that the examples in the DASH spec don't include the trailing format 
specifier, ie. they use "$Number%05$ which is inconsistent with the 
specification. However the dashif.org reference player v1.3.0 supports the 
format specifiers d, i, u, x, X and o: 
https://github.com/Dash-Industry-Forum/dash.js/blob/development/src/dash/DashHan
dler.js#l80

Original issue reported on code.google.com by ted.perc...@gmail.com on 1 Jun 2015 at 5:00

Attachments:

• live.mpd

[GoogleCodeExporter]

Original comment by jonathan...@google.com on 1 Jun 2015 at 7:31

• Changed state: Accepted

[GoogleCodeExporter]

This has been addressed in the latest Chromecast version (38401). You can check 
the release notes for information on other fixes.

Original comment by jonathan...@google.com on 10 Aug 2015 at 11:08

• Changed state: Fixed