[CinCV TNG] lazy insertion point movement when using keypad
sitelve at gmail.com
Sun Jul 16 15:34:58 CEST 2017
Frederic, did you read this
*?*12 Transport controls
*..When using frame advance functions the behavior may seem odd. If you
frame advance forward and then frame advance backward, the displayed frame
does not change. This is because the playback position is not the frame but
the time between two frames. The rendered frame is the area that the
playback position crosses. When you increment the time between two frames
by one and decrement it by one, you cross the same frame both times and so
the same frame is displayed. *
2017-07-16 15:43 GMT+03:00 Frederic Roenitz <roenitz at aimvis.de>:
> Thank you. :) I think the video didn't show the questions, that I was
> asking myself, clear enough:
> When using keypad1 and keypad4, can I be sure the compositor window
> shows the frame at the insertion point?
> Looking at http://aimvis.de/potentialBug-lazyInsertionPointMovementWhen
> (394K, 37s), unfortunately the answer is *no*!
> Opposed to clicking with the mouse cursor:
> When clicking with the mouse in the timeline in the main window, can I
> be sure the compositor window shows the frame at the insertion point?
> The answer is *yes*! (That's assuring).
> When I want to do something (insert/cut/...) at a specific frame, I
> would like to be sure that what I see in the compositor window shows
> the frame at the current position of the insertion point in the
> What do you think?
> Kind greetings
> Cinelerra mailing list
> Cinelerra at lists.cinelerra-cv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cinelerra