1. 02 Sep, 2018 1 commit
    • luz.paz's avatar
      misc. global typo fixes · e287a615
      luz.paz authored
      Found with `codespell -q 3 -I ../pitivi--whitelist.txt --skip="*.po,*.svg"`
  2. 29 Aug, 2018 1 commit
  3. 27 Aug, 2018 1 commit
  4. 07 Aug, 2018 1 commit
  5. 23 Jul, 2018 1 commit
  6. 19 Jul, 2018 1 commit
  7. 09 Jul, 2018 1 commit
  8. 08 Jul, 2018 1 commit
  9. 19 Jun, 2018 1 commit
  10. 13 Jun, 2018 1 commit
  11. 18 May, 2018 1 commit
  12. 02 May, 2018 1 commit
  13. 03 Apr, 2018 1 commit
    • yatinmaan's avatar
      ui: Add formatting functions and refactor models · 463a6fea
      yatinmaan authored
      Add formatting functions for framerates, audiorates & audiochannels
      Generate models using formatting functions to ensure a consistent UI.
      Remove display_aspect_ratios and pixel_aspect_ratio models, they were
      not used anywhere.
      Fixes #2160
  14. 17 Mar, 2018 1 commit
    • Suhas's avatar
      timeline: Disable ungroup/group when necessary · 0420e891
      Suhas authored
      ungroup button is now disabled when the current selection
      contains only one GES_TRACK_ELEMENT or when the elements are
      not in a group.
      group button is disabled if the current selection elements
      have the same toplevel parent.
      updateActions is now called in the beginning as well, which
      disables ungroup and group actions.
      Closes #1699
  15. 10 Mar, 2018 1 commit
  16. 07 Mar, 2018 1 commit
  17. 02 Mar, 2018 1 commit
  18. 18 Feb, 2018 1 commit
  19. 09 Feb, 2018 1 commit
    • Alexandru Băluț's avatar
      previewers: Assume the thumbnail generation is accurate enough · a24e1c40
      Alexandru Băluț authored
      It simplifies the logic. There is no good reason for keeping the
      complicated one.
      This change affects the most thumbnail placement at high zoom levels.
      But in this case if the difference between the actual pixbuf position
      and the expected position is so large as to be associated with a
      different thumbnail, we can assume that the format of the file is not
      video-editing friendly, and for these users we prefer to show all
      thumbnails rather than maybe have gaps in the thumbnails.
      Differential Revision: https://phabricator.freedesktop.org/D1940
  20. 06 Feb, 2018 2 commits
  21. 07 Nov, 2017 2 commits
  22. 11 Oct, 2017 1 commit
  23. 04 Oct, 2017 2 commits
  24. 05 Sep, 2017 4 commits
  25. 01 Sep, 2017 1 commit
  26. 19 Aug, 2017 1 commit
    • Thibault Saunier's avatar
      Handle deleted proxy files when loading a project · 4c5e508b
      Thibault Saunier authored
      We handle it as follow:
      Say, the loading project as file A and its proxy A.proxy
       - In Project::missing-uri, return the proxy target URI so the proxy
         is, proxied by it target (A.proxy will be proxied by A)
       - As soon as the A asset is ready, we start creating its proxy
       - Once the A.proxy is created, we reload it, unproxy it (to avoid proxy
         cycles), and start using it as a proxy for A
      Also fix several places where we were considering that an asset
      with a ->proxy_target != None was a proxy in our terms, it is not true
      anymore as during the time where we are recreating 'A.proxy',
      A.props.proxy_target is actually A.proxy, but it is no a proxy for us at
      that point (just a temporary redirection).
      Fixes T7560
      Reviewed-by: 's avatarAlex Băluț <&lt;alexandru.balut@gmail.com&gt;>
      Differential Revision: https://phabricator.freedesktop.org/D1815
  27. 15 Aug, 2017 1 commit
  28. 30 Jul, 2017 2 commits
    • Thibault Saunier's avatar
      validate: Add support for the new scenario API · e838931a
      Thibault Saunier authored
      Keeping backward compat with GstValidate 1.12.
    • Thibault Saunier's avatar
      Make setting encoding profiles more robust · 272f5a60
      Thibault Saunier authored
      When setting an encoding profile from a file we need to make sure
      several restrictions are handled:
       - We need to make sure the resulting restriction caps are
         compatible with the encoder that is going to be used by encodebin
       - We should ensure that the profile restriction caps are fully taken
         into account (if those restriction are not compatible with the encoder
         we can't do much)
       - We need to try as much as possible to use user previously set formats
       - We need to ensure fields that are mandatory for us are set in a way
         that is compatible with the encoder
      This introduces a utility function (for better testability) that allows
      this kind of caps fixation and some unit tests for this function.
      Reviewed-by: 's avatarAlex Băluț <&lt;alexandru.balut@gmail.com&gt;>
      Differential Revision: https://phabricator.freedesktop.org/D1807
  29. 26 Jul, 2017 1 commit
  30. 08 Jul, 2017 4 commits