openshot.bugs team mailing list archive

[MorrisseyJ <1198555@xxxxxxxxxxxxxxxxxx>]

I agree that this is a major bug. Notably it also seems that it is
triggered by clicking the lengh tab in the clip properties dialogue. In
addtion to the problems pointed out by vinislentoje, if you are changing
the length of the clips (which you now apparently have to do if you
change the speeds) the info contained in 'position in timelinel' also
goes wrong. At that point you have no information about the lengh of
your clip.

To create the problem.

1. Add a clip.
2. Split that clip in half
3. Right click on the second clip (generated by splitting the first clip in two) and open 'clip properties'
4. Under the 'general tab' you should see the 'position in timeline' statistic
5. Click play on the preview, and clip will play as expected.
6. Click 'length tab' - here you will see the problem, described by bitbjorn above, that the In time is 0.00 or -0.01 (this is clearly wrong)
7. Now click play in the preview and the clip will run from the start of both clips (from 0.00).

- So it seems to be the length tab which is messing things up

Things get even more confusing if you start changing the lenght of your
clips which you now have to do in order to change thier speed (post #2:
http://openshotusers.com/forum/viewtopic.php?f=11&t=2000), with differnt
clips running at multiple differents speeds. In this case the
information given in the lengh tabs and position in clip tabs both go
wrong.

-- 
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/1198555

Title:
  In time in clip properties is not set correct

Status in OpenShot Video Editor:
  New

Bug description:
  Openshot 1.4.3 on Linux Sabayon.

  Under the "length"-tab in clip properties there is a textbox with start time for the clip, this time is always 0 (or actually -0.01).
  The reason for this is that when clip properties dialog is loaded the txtIn-textbox is set before txtOut-textbox which lead to that local_out is 0.0 in on_txtIn_value_changed(). The logic:
  		if local_in >= local_out:
  			local_in = local_out - 0.01
  			self.txtIn.set_text(str(local_in))
  will then set textbox text to -0.01.

  One solution to this is to switch the order for setting txtOut and
  txtIn, that is set txtOut before txtIn (in
  frmClipProperties::__init__()).

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