[Bug 732237] New: dashdemux: expose language tags

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=732237
  GStreamer | gst-plugins-bad | git

           Summary: dashdemux: expose language tags
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: matthieu.bouron at collabora.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Currently dashdemux parse various language properties contained in the
AdaptationSet and ContentComponent nodes but does not send any language tags to
downstream.

There are a few cases we need to deal with.

1) The lang property is set on the AdaptationSet node. Information can be
forwarded downstream using a single tag (GST_TAG_LANGUAGE_CODE)

2) The lang property is not set on the AdaptationSet node but ContentComponents
are present and have the lang property. In this case, we will need to find a
way to forward downstream multiple lang tags corresponding to the streams
contained in the fragments of this AdaptationSet.
Is it reasonable to use the GST_TAG_LANGUAGE_CODE tag with multiple value here
? Each index value corresponding to the real stream index ?
Or something like "stream-%d-language-code" makes more sense ?
Also we can only trust the order of appearance of the ContentComponent nodes to
associate it a stream index.

On the qtdemux/[...] side, the tag event should be handled and the upstream
tags stored globally.
For each output stream it should look at the proper language tag / value index,
get the value, and push the tag to the stream tags.
The rest of the upstream tags will be pushed with the other global tags.

What do you think ?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.