[DASH] Template based url construction with RepresentationID. #848

sr1990 · 2020-09-26T02:03:00Z

Trying to implement template based url construction that uses $RepresentationID$. This will add SegmentTemplate below adaptationSet instead of every Representation.
I have added a new stream descriptor field called rep_id that takes in the representation id.

Example:

../packager \                                                                  
  'in=S-1024x576.mp4,stream=video,init_segment=$RepresentationID$/init.mp4,segment_template=$RepresentationID$/$Number$.m4s,rep_id=RES-1024x576' \
  'in=S-1280x720.mp4,stream=video,init_segment=$RepresentationID$/init.mp4,segment_template=$RepresentationID$/$Number$.m4s,rep_id=RES-1280x720' \
  --mpd_output test_mpd.mpd

and following is the generated mpd:

<?xml version="1.0" encoding="UTF-8"?>                                          
<!--Generated with https://github.com/google/shaka-packager version 5b9fd409a5-debug-->
<MPD xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011 DASH-MPD.xsd" profiles="urn:mpeg:dash:profile:isoff-live:2011" minBufferTime="PT2S" type="dynamic" publishTime="2020-09-26T00:16:44Z" availabilityStartTime="2020-09-26T00:16:43Z" minimumUpdatePeriod="PT5S" timeShiftBufferDepth="PT1800S">
  <Period id="0" start="PT0S">                                                  
    <AdaptationSet id="0" contentType="video" maxWidth="1280" maxHeight="720" maxFrameRate="96/4" segmentAlignment="true" par="16:9">
      <SegmentTemplate timescale="96" initialization="$RepresentationID$/init.mp4" media="$RepresentationID$/$Number$.m4s" startNumber="1">
        <SegmentTimeline>                                                      
          <S t="0" d="576" r="7"/>                                              
          <S t="4608" d="404"/>                                                
        </SegmentTimeline>                                                      
      </SegmentTemplate>                                                        
      <Representation id="RES-1024x576" bandwidth="212490" codecs="avc1.4d401f" mimeType="video/mp4" sar="1:1" width="1024" height="576" frameRate="96/192"/>
      <Representation id="RES-1280x720" bandwidth="2942370" codecs="avc1.4d401f" mimeType="video/mp4" sar="1:1" width="1280" height="720" frameRate="96/4"/>
    </AdaptationSet>                                                            
  </Period>                                                                    
</MPD>

This is similar to MP4Box where ids are specified along with tracks:
Example:

mp4box -dash 12000 -frag 12000 -mem-frags -rap -profile dashavc264:live ^
  -profile-ext "urn:hbbtv:dash:profile:isoff-live:2012" ^
  -mpd-title "" -mpd-info-url "" ^
  -bs-switching no -sample-groups-traf -single-traf -subsegs-per-sidx 1 ^
  -segment-name "$RepresentationID$_$Number$$Init=i$" -segment-timeline ^
  -out "manifest_orig.mpd" ^
  "temp-360p.mp4#trackID=1:id=360p" ^
  "temp-720p.mp4#trackID=1:id=720p" ^
  "temp-1080p.mp4#trackID=1:id=1080p" ^
  "temp-128k.mp4#trackID=1:id=128k"

@kqyang please let me know what you think about this approach.

sr1990 · 2020-10-01T21:08:20Z

Hi @kqyang, any thoughts on this PR?

kqyang · 2020-10-06T06:50:27Z

@sr1990 Thanks for working on it. Yes, that is a great feature. (And sorry for late reply, super busy recently..)

I'll try to look at the PR some time this week.

sr1990 · 2020-10-08T00:21:21Z

@sr1990 Thanks for working on it. Yes, that is a great feature. (And sorry for late reply, super busy recently..)

I'll try to look at the PR some time this week.

Sounds good. Thanks. Once I know that the approach is correct, I can move ahead with adding unit tests and documentation.

sr1990 · 2020-12-04T04:18:27Z

Ping

ProIcons · 2021-06-15T07:01:50Z

bump

sr1990 · 2021-06-28T06:52:34Z

packager/media/base/muxer_options.h

+
+  /// Used as Representation id for template based url construction using
+  /// $RepresentationID$.
+  std::string rep_id;


This should not be added as a muxer option. Will update the PR soon.

joeyparrish · 2022-10-30T20:29:29Z

I'm trying to catch up on the PR backlog as we work to revive the project.

I agree with this feature in principle, but haven't reviewed the code yet. Please merge main into your branch and fix conflicts, and make whatever other changes you're considering (I see a comment you left about moving rep_id out of muxer_options.h). When it's ready for review, let me know, and I'll give it a detailed review. Thanks!

cosmin

Overall the adaptation set level segment template seems fine, but non-numeric representation IDs does not seem fine. We could consider allowing the user to use manually specified numeric representation IDs, but it seems like it would be safer to leave representation IDs automatically generated and instead provide a facility to use the generated representation ID in the output filename.

cosmin · 2024-05-01T00:43:15Z

packager/packager.h

@@ -133,6 +133,8 @@ struct StreamDescriptor {
  bool dash_only = false;
  /// Set to true to indicate that the stream is for hls only.
  bool hls_only = false;
+
+  std::string rep_id;


in my experience allowing non-numeric representation IDs is bound to cause problems, last time I tried I believe ExoPlayer failed to parse non-numeric representation IDs for example.

instead of having the user specify the representation ID, what about allowing to specify using the representation ID in the output filename and then substitute in the computed representation ID by packager.

cosmin · 2024-05-01T00:45:22Z

packager/mpd/base/xml/xml_node.h

@@ -66,6 +66,10 @@ class XmlNode {
  /// @param id is the ID for this element.
  void SetId(uint32_t id);

+  /// Sets 'id=rep_id' attribute.
+  /// @param id is the ID for this element.
+  void SetIdString(std::string id);


this is a problem for the same reason I mentioned elsewhere, even internally id is expected to be uint. So the option of passing in an alternate string ID isn't great.

sr1990 · 2024-05-01T09:19:11Z

@cosmin

Overall the adaptation set level segment template seems fine, but non-numeric representation IDs does not seem fine.
As per spec:
Represenation@id,

specifies an identifier for this Representation. The
identifier shall be unique within a Period unless the
Representation is functionally identical to another Rep-
resentation in the same Period.
The identifier shall not contain whitespace characters.
**If used in the template-based URL construction as de-
fined in subclause 5.3.9.4.4, the string shall only contain
characters that are permitted within an HTTP-URL
according to IETF RFC 3986.**

Also exoplayer seems to be parsing Representation id as a string
https://github.com/google/ExoPlayer/blob/faa296ae3c4ac3ceed514b247284f268953afad7/library/dash/src/main/java/com/google/android/exoplayer2/source/dash/manifest/DashManifestParser.java#L688

We could consider allowing the user to use manually specified numeric representation IDs, but it seems like it would be safer to leave representation IDs automatically generated and instead provide a facility to use the generated representation ID in the output filename.
Can you give an example command?

[DASH] Url construction that uses $RepresentationID$.

83cb6a2

sr1990 force-pushed the segmentTemplate_adaptationSet3 branch from e21575b to 83cb6a2 Compare September 26, 2020 03:49

sr1990 changed the title ~~[DASH] Url construction that uses RepresentationID.~~ [DASH] Template based url construction with RepresentationID. Sep 26, 2020

sr1990 commented Jun 28, 2021

View reviewed changes

cosmin requested changes May 1, 2024

View reviewed changes

cosmin marked this pull request as draft May 1, 2024 04:50

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[DASH] Template based url construction with RepresentationID. #848

[DASH] Template based url construction with RepresentationID. #848

sr1990 commented Sep 26, 2020 •

edited

sr1990 commented Oct 1, 2020

kqyang commented Oct 6, 2020

sr1990 commented Oct 8, 2020 •

edited

sr1990 commented Dec 4, 2020

ProIcons commented Jun 15, 2021

sr1990 Jun 28, 2021 •

edited

joeyparrish commented Oct 30, 2022

cosmin left a comment

cosmin May 1, 2024

cosmin May 1, 2024

cosmin May 1, 2024

sr1990 commented May 1, 2024

[DASH] Template based url construction with RepresentationID. #848

Are you sure you want to change the base?

[DASH] Template based url construction with RepresentationID. #848

Conversation

sr1990 commented Sep 26, 2020 • edited

sr1990 commented Oct 1, 2020

kqyang commented Oct 6, 2020

sr1990 commented Oct 8, 2020 • edited

sr1990 commented Dec 4, 2020

ProIcons commented Jun 15, 2021

sr1990 Jun 28, 2021 • edited

Choose a reason for hiding this comment

joeyparrish commented Oct 30, 2022

cosmin left a comment

Choose a reason for hiding this comment

cosmin May 1, 2024

Choose a reason for hiding this comment

cosmin May 1, 2024

Choose a reason for hiding this comment

cosmin May 1, 2024

Choose a reason for hiding this comment

sr1990 commented May 1, 2024

sr1990 commented Sep 26, 2020 •

edited

sr1990 commented Oct 8, 2020 •

edited

sr1990 Jun 28, 2021 •

edited