openshot.bugs team mailing list archive

[Daniel Ellis <mail@xxxxxxxxxxxxxx>]

As this issue is based around indexing frames, it is important for us to
be careful that every frame is included.  To make this easier I have
attatched an image sequence with the first and last frames clearly
marked.

The image sequence is 80 frames long.  The first frame marked with a
large "1" and the final frame marked with "80".

On PAL this sequence should be 3.2 seconds long (80/25).
On NTSC this sequence should be 2.67 seconds long (80/29.97 then rounded to 2 decimal places)

** Attachment added: "FirstLastFrameTestSequence.tar.gz"
   https://bugs.launchpad.net/openshot/+bug/1013035/+attachment/3192346/+files/FirstLastFrameTestSequence.tar.gz

-- 
You received this bug notification because you are a member of OpenShot
Bugs, which is subscribed to OpenShot Video Editor.
https://bugs.launchpad.net/bugs/1013035

Title:
  Fade glitches caused by "out" attribute being greater than clip length

Status in OpenShot Video Editor:
  New

Bug description:
  Continuing from bug #520941.  I have found another scenario which can
  cause glitches with fade when using an imported PNG sequence.  The
  generated XML includes and out attribute which is longer than the
  clip, which causes problems for the rest of the timeline.

  The issue affects 1.4.2 and trunk.

  Attached is a simple patch (agains trunk) which solves the issue.

  The code previously had three branches, but note that the first two
  branches where the same, so I have changed this to a simple if/else
  with just the two relavent branches, as well as fixing the out number
  which was off by 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openshot/+bug/1013035/+subscriptions