1. 14 Jul, 2020 1 commit
  2. 10 Jul, 2020 2 commits
  3. 08 Jul, 2020 2 commits
  4. 03 Jul, 2020 1 commit
  5. 02 Jul, 2020 1 commit
  6. 23 Jun, 2020 5 commits
  7. 22 Jun, 2020 1 commit
  8. 19 Jun, 2020 3 commits
  9. 17 Jun, 2020 2 commits
  10. 16 Jun, 2020 4 commits
  11. 09 Jun, 2020 2 commits
  12. 08 Jun, 2020 1 commit
  13. 04 Jun, 2020 3 commits
  14. 03 Jun, 2020 1 commit
  15. 27 May, 2020 2 commits
  16. 26 May, 2020 2 commits
  17. 25 May, 2020 7 commits
    • Thibault Saunier's avatar
      formatter: Fix saving/loading project with clip speed rate control · db5c62ad
      Thibault Saunier authored
      We need to ensure that clips duration is set after time effects are
      added and we now need to serialize effects inpoints and max duration.
      
      Part-of: <!177>
      db5c62ad
    • Henry Wilkes's avatar
      docs: add some notes on Time in GES · e142f491
      Henry Wilkes authored
      These notes cover time coordinates in GES, time effects, time
      translations.
      
      It also goes into why keyframes will not work with non-linear time
      effects.
      
      Part-of: <!177>
      e142f491
    • Henry Wilkes's avatar
      uri-clip: don't assume duration needs to stay the same · a6d0418f
      Henry Wilkes authored
      ges_uri_clip_asset_get_duration does not tell us what the duration in
      the timeline needs to be. Especially when we have time effects, or
      effects with finite max-durations. So we should no longer expect the
      duration to stay the same when replacing assets. Instead, we just check
      that the new max-duration would be compatible with the current in-point
      (which was not checked before), and the clip would not be totally
      overlapped if its duration-limit changes.
      
      This is based on the assumption that each source is replaced one-to-one
      in its track. If a source is replaced with nothing in the same track,
      this check may be a little too strong (but still mostly weaker than
      before). However, problems could occur if track selection does
      something unexpected, such as placing the new source in a track not
      previously occupied.
      
      Part-of: <!177>
      a6d0418f
    • Henry Wilkes's avatar
      clip: provide an example of using time effects · f269a7f2
      Henry Wilkes authored
      Part-of: <!177>
      f269a7f2
    • Henry Wilkes's avatar
      track-element: use out-point for updating control bindings · 9e18e039
      Henry Wilkes authored
      The out-point, which is an internal time, is used instead of the
      duration for determining the control binding value at the end of the
      element.
      
      Also, allow the user to switch off the auto-clamping of control sources
      if they are not desired. And allow them to clamp specific control sources
      individually.
      
      Also, fix a lot of memory leaks related to control sources. In
      particular, releasing the extra ref gained by source in
      g_object_get (binding, "control-source", &source, NULL);
      
      Part-of: <!177>
      9e18e039
    • Henry Wilkes's avatar
      clip: test for layer in group · 73852466
      Henry Wilkes authored
      Make sure the layer exists before we try to remove the grouped clips
      from it.
      
      Part-of: <!177>
      73852466
    • Henry Wilkes's avatar
      timeline-tree: make sure the layer priority refers to an existing layer · 34719efa
      Henry Wilkes authored
      If a layer priority sits between the priorities of two layers in the
      timeline, i.e. it references a gap in the timeline's layers, then
      ges_timeline_append_layer will never fill this gap and create the
      desired layer, so the edit in timeline-tree would loop forever. So a
      check was added to avoid this.
      
      This would be a usage error, but a user can reasonably end up with a gap
      in their layers if they remove a layer from the timeline.
      
      Part-of: <!177>
      34719efa