← Back to team overview

openshot.code team mailing list archive

[Branch ~openshot.code/openshot/main] Rev 535: I found a very serious bug, which I would like to say is a regression, but I can't figure out whe...

 

------------------------------------------------------------
revno: 535
committer: Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx>
branch nick: openshot
timestamp: Wed 2011-08-31 23:24:58 -0500
message:
  I found a very serious bug, which I would like to say is a regression, but I can't figure out when it broke...  However, this was preventing the "Clip Properties" video preview from applying effects correctly.  The effects were being placed on the timeline at the clips actual "position", and not starting at frame 0, which is what the preview needs.  So, in other words, If an effect was starting on frame 100, the clip preview would not show any effects until frame 100.  Fixed!
modified:
  openshot/classes/clip.py


--
lp:openshot
https://code.launchpad.net/~openshot.code/openshot/main

Your team OpenShot Code is subscribed to branch lp:openshot.
To unsubscribe from this branch go to https://code.launchpad.net/~openshot.code/openshot/main/+edit-subscription
=== modified file 'openshot/classes/clip.py'
--- openshot/classes/clip.py	2011-08-16 19:51:22 +0000
+++ openshot/classes/clip.py	2011-09-01 04:24:58 +0000
@@ -394,7 +394,7 @@
 				blank_node.setAttribute("length", str(blank))
 				xmlParentNode.appendChild(blank_node)
 				
-		elif preview_mode == "trimming":
+		elif preview_mode in ["trimming", "clip-properties-preview"]:
 			# preview mode is True, always start at frame zero, and include the 
 			# entire clip in the preview XML (ignore the IN and OUT)
 			current_frame = 0