VSE strip and snapping offset #46035

New Issue

JA 12 · 2015-09-07T00:34:24+02:00

JA 12 commented

2015-09-07 00:34:24 +02:00

System Information
Ubuntu 14.04 64bit, Gnome 3 Classic, nvidia graphics.

Blender Version
Broken: 2.75.4 ef629e0

Getting weird offsets when adding a movie strip, image strip, using a hotkey to move to the end frame and snapping image strip handle to the time cursor.

End frame is set to frame 4989 as on the timeline. The time cursor is moved on the last frame with shift+right arrow and image strip handle is snapped to that.

This results to image not showing (shows on the frame before), video not showing, and none of the information match up: image strip information says its length is 4988 when it's clearly 4989, it also says the playhead is at 4988 and still frame at 4987 whatever that is.

Sequencer seems to end at frame 4990 where the video frame ends, but it doesn't show up on the last frame (that snaps to 4989) but on the frame before that (4988).

Exact steps for others to reproduce the error
Add a video strip, adjust frame range to match. Add an image strip, shift+right arrow to go to end frame, select right handle and shift+S to snap.

Would have provided a test file with an image (since video files can't be packed) but looks like I can't find a way to pack the image on the strip either. Can't find a pack button on the strip properties, menus, added the image in the UV/Image editor which could be packed but that can't be dragged as a image strip or added through add menu. So no file.

**System Information** Ubuntu 14.04 64bit, Gnome 3 Classic, nvidia graphics. **Blender Version** Broken: 2.75.4 ef629e0 Getting weird offsets when adding a movie strip, image strip, using a hotkey to move to the end frame and snapping image strip handle to the time cursor. ![screen2.png](https://archive.blender.org/developer/F230948/screen2.png) End frame is set to frame 4989 as on the timeline. The time cursor is moved on the last frame with shift+right arrow and image strip handle is snapped to that. This results to image not showing (shows on the frame before), video not showing, and none of the information match up: image strip information says its length is 4988 when it's clearly 4989, it also says the playhead is at 4988 and still frame at 4987 whatever that is. Sequencer seems to end at frame 4990 where the video frame ends, but it doesn't show up on the last frame (that snaps to 4989) but on the frame before that (4988). **Exact steps for others to reproduce the error** Add a video strip, adjust frame range to match. Add an image strip, shift+right arrow to go to end frame, select right handle and shift+S to snap. Would have provided a test file with an image (since video files can't be packed) but looks like I can't find a way to pack the image on the strip either. Can't find a pack button on the strip properties, menus, added the image in the UV/Image editor which could be packed but that can't be dragged as a image strip or added through add menu. So no file.

JA 12 commented

2015-09-07 00:34:25 +02:00

Changed status to: 'Open'

JA 12 commented

2015-09-07 00:34:25 +02:00

Added subscriber: @ja12

Campbell Barton commented

2015-09-07 08:42:33 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-09-07 08:42:33 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2015-09-07 08:42:33 +02:00

Campbell Barton self-assigned this 2015-09-07 08:42:33 +02:00

Campbell Barton commented

2015-09-07 08:42:33 +02:00

Snapping to the last frame not showing the image is working as intended, This last frame is where a new strip would be added without overlapping.

As for the offset with the audio, this is caused by a mismatch with the frame-rate.

Try set the frame-rate to 23.98 or 29.97, then re-import the video.

Closing, since this is a common misunderstanding.
See: http://blender.stackexchange.com/questions/6268

We can re-open if you are sure everything is set correctly, but the file still doesn't load right.
In this case we would need an example file so we can redo the error.

Snapping to the last frame not showing the image is working as intended, This last frame is where a new strip would be added without overlapping. As for the offset with the audio, this is caused by a mismatch with the frame-rate. Try set the frame-rate to 23.98 or 29.97, then re-import the video. Closing, since this is a common misunderstanding. See: http://blender.stackexchange.com/questions/6268 --- We can re-open if you are sure everything is set correctly, but the file still doesn't load right. In this case we would need an example file so we can redo the error.

JA 12 commented

2015-09-07 14:28:44 +02:00

In #46035#332940, @ideasman42 wrote:
Closing, since this is a common misunderstanding.
See: http://blender.stackexchange.com/questions/6268

There is no audio. In a sentence, the confusion comes from UI saying one thing and then doing something else. The strips are of different length and the last frame (the end frame) is transparent.
vse_offset.zip

I add a video strip (fps 15) and the strip says it's 380 frames. I set end frames as 380 by typing in the value. Going to the other end of the strip: the strip reaches frame 381, the time cursor snaps at the end frame (380) and edit strip info says playhead 379.

Adding an image while the time cursor is at frame 1. Selecting the right handle, moving the time cursor to the end frame, and then snapping the handle to it. Video strip and image strip are offset by 1 frame. The time cursor is at frame 380, the image strip says it's 379 frames.

The last frame for the image is transparent, so is the second from last frame of the video strip. If I wanted to end the video on the last visible frame I would visually have to set the end frame to -2 frames from the video strip. Or maybe adding another file just right after the video file, the image would show up transparent, then the video would be transparent and then it would continue with the new file.

The report is/was about the strip offsets in case they're not right.

> In #46035#332940, @ideasman42 wrote: > Closing, since this is a common misunderstanding. > See: http://blender.stackexchange.com/questions/6268 There is no audio. In a sentence, the confusion comes from UI saying one thing and then doing something else. The strips are of different length and the last frame (the end frame) is transparent. [vse_offset.zip](https://archive.blender.org/developer/F231169/vse_offset.zip) ![vse_offset1.png](https://archive.blender.org/developer/F231160/vse_offset1.png) I add a video strip (fps 15) and the strip says it's 380 frames. I set end frames as 380 by typing in the value. Going to the other end of the strip: the strip reaches frame 381, the time cursor snaps at the end frame (380) and edit strip info says playhead 379. ![vse_offset2.png](https://archive.blender.org/developer/F231162/vse_offset2.png) Adding an image while the time cursor is at frame 1. Selecting the right handle, moving the time cursor to the end frame, and then snapping the handle to it. Video strip and image strip are offset by 1 frame. The time cursor is at frame 380, the image strip says it's 379 frames. The last frame for the image is transparent, so is the second from last frame of the video strip. If I wanted to end the video on the last visible frame I would visually have to set the end frame to -2 frames from the video strip. Or maybe adding another file just right after the video file, the image would show up transparent, then the video would be transparent and then it would continue with the new file. The report is/was about the strip offsets in case they're not right.

Campbell Barton commented

2015-09-08 07:52:45 +02:00

Changed status from 'Archived' to: 'Open'

Campbell Barton reopened this issue

2015-09-08 07:52:45 +02:00

Campbell Barton commented

2015-09-08 07:52:45 +02:00

My bad, re-opening.

but still not sure this is a bug. though it is indeed confusing.

In the test file, the last frame the cursor image (top strip) is visible is 279, so if you wanted to end the animation there. You would need to set the last frame of the animation to 279.

My bad, re-opening. but still not sure this is a bug. though it is indeed confusing. In the test file, the last frame the cursor image (top strip) is visible is 279, so if you wanted to end the animation there. You would need to set the last frame of the animation to 279.

Campbell Barton commented

2015-09-08 19:37:07 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2015-09-08 19:37:07 +02:00

Campbell Barton commented

2015-09-08 19:37:07 +02:00

Ok, I follow you now.

The last frame displayed, and the last frame used for snapping is off by one, but its intentional.

Shift right moves the playhead to the last visible frame.
Snapping the strip will move it to the point up-until, but not occupying the current play-heads frame.

... This makes sense if you consider you could have a play-head on the start of a strip, and you may want to snap the end of an earlier strip to it, however in this one case its not working so usefully.

For editing (in this case), it would make sense for Shift-right to go to the lastframe+1, but not for playback.

Hint - Use page-up/down instead of first-last frame shortcut keys, this uses frames useful for snapping.

Even so, this isn't a bug. its just a mix of options not working so usefully together.

Ok, I follow you now. The last frame displayed, and the last frame used for snapping is off by one, but its intentional. - Shift right moves the playhead to the last visible frame. - Snapping the strip will move it to the point up-until, but not occupying the current play-heads frame. ... This makes sense if you consider you could have a play-head on the start of a strip, and you may want to snap the end of an earlier strip to it, however in this one case its not working so usefully. For editing (in this case), it would make sense for Shift-right to go to the lastframe+1, but not for playback. Hint - Use page-up/down instead of first-last frame shortcut keys, this uses frames useful for snapping. Even so, this isn't a bug. its just a mix of options not working so usefully together.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE strip and snapping offset #46035