1. 01 Mar, 2019 1 commit
  2. 02 Feb, 2019 1 commit
  3. 26 Dec, 2018 1 commit
  4. 28 Nov, 2018 2 commits
  5. 15 Nov, 2018 1 commit
  6. 07 Nov, 2018 1 commit
  7. 27 Oct, 2018 1 commit
  8. 24 Oct, 2018 1 commit
  9. 03 Oct, 2018 2 commits
    • Thibault Saunier's avatar
      matroskdemux: do not use MapInfo.data after unmapping · defae350
      Thibault Saunier authored
      And minor gst-indenting
      defae350
    • Yacine Bandou's avatar
      matroska: Add the WebM encrypted content support in matroskademux · 04328269
      Yacine Bandou authored
      This commit:
      
      1. Reads the WebM and Matroska ContentEncryption subelements.
      
      2. Creates a GST_PROTECTION event for each ContentEncryption, which
         will be sent before pushing the first source buffer.
         The DRM system id field in this event is set to GST_PROTECTION_UNSPECIFIED_SYSTEM_ID,
         because it isn't specified neither by Matroska nor by the WebM spec.
      
      3. Reads the protection information of encrypted Block/SimpleBlock and
         extracts the IV and the partitioning format (subsamples).
      
      4. Creates the metadata protection for each encrypted Block/SimpleBlock,
         with those informations: KeyID (extracted from ContentEncryption element),
         IV and partitioning format.
      
      5. Adds a new caps for WebM encrypted content named "application/x-webm-enc",
         with the following new fields:
      
         "encryption-algorithm": The encryption algorithm used.
                                 values: "None", "DES", "3DES", "Twofish", "Blowfish", "AES".
      
         "encoding-scope": The field that describes which Elements have been modified.
                           Values: "frame", "codec-data", "next-content".
      
         "cipher-mode": The cipher mode used in the encryption.
                        Values: "None", "CTR".
      
      https://bugzilla.gnome.org/show_bug.cgi?id=765275
      04328269
  10. 21 Sep, 2018 4 commits
  11. 06 Sep, 2018 1 commit
  12. 27 Aug, 2018 7 commits
  13. 23 Aug, 2018 1 commit
  14. 27 Jul, 2018 1 commit
  15. 26 Jul, 2018 3 commits
  16. 29 Jun, 2018 1 commit
  17. 23 May, 2018 1 commit
  18. 15 May, 2018 1 commit
  19. 25 Apr, 2018 1 commit
  20. 13 Apr, 2018 1 commit
  21. 28 Feb, 2018 3 commits
  22. 15 Dec, 2017 3 commits
    • Sean DuBois's avatar
    • François Laignel's avatar
    • François Laignel's avatar
      matroska: re-activate and update TOC support · a6702a76
      François Laignel authored
      TOC support in mastroskamux has been deactivated for a couple of years. This commit updates it to recent GstToc evolutions and introduces toc unit tests for both matroska-mux and matroska-demux.
      
      There are two UIDs for Chapters in Matroska's specifications:
      - The ChapterUID is a mandatory unsigned integer which internally refers to a given chapter. Except for title & language which use dedicated fields, this UID can also be used to add tags to the Chapter. The tags come in a separate section of the container.
      - The ChapterStringUID is an optional UTF-8 string which also uniquely refers to a chapter but from an external perspective. It can act as a "WebVTT cue identifier" which "can be used to reference a specific cue, for example from script or CSS".
      
      During muxing, the ChapterUID is generated and checked for unicity, while the ChapterStringUID receives the user defined UID. In order to be able to refer to chapters from the tags section, we maintain an internal Toc tree with the generated ChapterUID.
      
      When demuxing, the ChapterStringUIDs (if available) are assigned to the GstTocEntries UIDs and an internal toc mimicking the toc is used to keep track of the ChapterUIDs and match the tags with the appropriate GstTocEntries.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=790686
      a6702a76
  23. 13 Nov, 2017 1 commit