This solved my problem. I had the very same problem per described by previous posters. For a rather easy workaround, I received the following answer from Manfred Hampl (m-hampl) source: https://answers.launchpad.net/openshot/+question/273161
The following should work as a manual workaround: Issue the command gksudo gedit /usr/share/pyshared/openshot/windows/ClipProperties.py (if the command gksudo is not installed, try sudo gedit /usr/share/pyshared/openshot/windows/ClipProperties.py instead; if gedit is not available on your system, then use any other text editor.) This should ask for your password as confirmation for an administrative action and then open the editor with one of the Openshot Python programs loaded. Scroll down near line 91 and change the sequence of two lines from self.txtIn.set_value(round(self.current_clip.start_time, 2)) self.txtOut.set_value(round(self.current_clip.end_time, 2)) into self.txtOut.set_value(round(self.current_clip.end_time, 2)) self.txtIn.set_value(round(self.current_clip.start_time, 2)) Keep the indentations exactly as they are in the file! Search for the occurrence of 0.01 After the second occurrence (probably line 663) delete the block of the three lines if local_out > local_max_length: local_out = local_max_length self.txtOut.set_text(str(local_out)) Attention, you have to make sure that you do not touch the indentation of other lines. Save the file, close the editor, and try using OpenShot again. In case that OpenShot does no more work after these modifications, just reinstall the openshot package and you should be at the same status as before. -- 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 -- Mailing list: https://launchpad.net/~openshot.bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~openshot.bugs More help : https://help.launchpad.net/ListHelp
