1. 04 Nov, 2010 1 commit
  2. 26 Oct, 2010 1 commit
  3. 12 Oct, 2010 1 commit
  4. 24 Sep, 2010 1 commit
    • Vincent Cappe's avatar
      Fix an issue with the symlinks for pre-0.9.9 tool names · 8ac44ca8
      Vincent Cappe authored
      When files with pre-0.9.9 tool names exist in $(exec_prefix)/bin,
      "make DESTDIR=${staging_dir} install" tries to delete them, which
      may cause a failure for lack of permissions (quite likely to happen
      when building a package as a normal user), and is wrong anyway
      (nothing outside of DESTDIR should ever be changed by "make install").
      
      With this patch, it will now cd to "$(DESTDIR)$(bindir)" and create
      relative symlinks there, if need be. This preverse the old behavior
      when DESTDIR=="", except for the fact the symlinks will be relative
      rather than absolute.
      8ac44ca8
  5. 19 Sep, 2010 2 commits
    • Monty Montgomery's avatar
      oggz-sort: fix handling of stream end · 3fc79474
      Monty Montgomery authored
      oggz-sort would miss an input on an iteration in which a stream ends and is
      removed from the stream table.
      3fc79474
    • Monty Montgomery's avatar
      Fix starting frame numbers for Theora · 631d1121
      Monty Montgomery authored
      The correction for different starting frame numbers on early Theora streams
      was backward, resulting in the timestamp calculation being off by a frame
      on all stream version. This was causing oggz-sort and oggz-merge to mis-mux
      streams (which oggz-validate was catching properly)
      631d1121
  6. 16 Jul, 2010 2 commits
  7. 29 Apr, 2010 1 commit
  8. 24 Apr, 2010 2 commits
  9. 20 Apr, 2010 1 commit
    • conrad's avatar
      Fix regression introduced in 8c2da1 · ccd2a2fe
      conrad authored
      When using a recent liboggz, liboggplay fails to play some files. It
      appears it's only files with Kate streams, however some files with
      Kate streams do play fine, but liboggplay reports unknown
      category/language, so that's probably still failing, but in a way that
      liboggplay can recover from.
      
      A sample file which worked before and does not work now is the good old:
      http://people.xiph.org/~oggk/Stephen_Fry-Happy_Birthday_GNU-hq_600px_780kbit.ogv
      This file is seen as correct by oggz-validate.
      
      Issue:
      
      * when oggz_read() sees the first few packets before it sees a
      granulepos, it buffers them in a dlist
      * then, oggz_read_deliver_packet() is a dlist callback which goes
      through these buffered packets and calls the read callback for each
      * the commit you found by bisection returns an error if the
      read_callback returns non-zero; previously the read_callback return
      values were ignored
      * liboggplay's read_predetected(), the read_callback in use during
      stream detection, returns 1 (OGGZ_STOP_OK) when it has done what it
      needs to do
      
      ... hence, the STOP_OK value gets turned into an error value by the
      bad commit.
      
      Reported-by: ogg.k.ogg.k@googlemail.com
      Signed-off-by: conrad's avatarConrad Parker <conrad@metadecks.org>
      ccd2a2fe
  10. 14 Apr, 2010 1 commit
  11. 10 Apr, 2010 1 commit
  12. 01 Apr, 2010 1 commit
  13. 18 Mar, 2010 3 commits
  14. 06 Mar, 2010 2 commits
  15. 11 Feb, 2010 1 commit
  16. 09 Feb, 2010 2 commits
    • conrad's avatar
      Allow NULL-value comments, and form "KEY=" · aee099bc
      conrad authored
      This commit changes the policy of fs_comment_validate_byname() to
      allow NULL-value comments, and changes fs_comment_new() to handle
      the case where value=NULL, and where the comment has no value but
      has an = sign.
      
      This commit should pass "make check", including the policy change
      introduced in the previous commit.
      aee099bc
    • conrad's avatar
      tests: allow NULL-valued comments · f619cbd2
      conrad authored
      This test changes the policy on what comments are valid, to allow
      plain comments, not of the form KEY=VALUE (the condition reported
      in Mozilla #520500).
      
      As this commit only modifies the test suite, 'make check' is
      expected to fail.
      f619cbd2
  17. 28 Nov, 2009 4 commits
  18. 17 Oct, 2009 1 commit
  19. 07 Oct, 2009 2 commits
  20. 04 Oct, 2009 2 commits
  21. 22 Sep, 2009 1 commit
  22. 14 Sep, 2009 4 commits
  23. 12 Sep, 2009 1 commit
  24. 11 Sep, 2009 1 commit
  25. 10 Sep, 2009 1 commit