VSE speed effect doesn't work properly #46038

New Issue

mic lack30 · 2015-09-07T12:09:28+02:00

mic lack30 commented

2015-09-07 12:09:28 +02:00

Windows7 x64, 2*GTX680

Broken: 2.75.4 4ae1815

After I have added a speed effect to a movie strip in the VSE, I select the end of the movie strip and move it with G, to make a timelapse or slow motion. This doesn't work. I can still tipe in numbers to multiply the speed by the factor x, but the above mentioned method doesn't work anymore. I tested .mp4 movies with H.264 and .avi with lagarith Lossless Codec.

Can't attach .blend here because it would get to big with a movie in it, but:
Add a movie
Add a speed effect
Select the end of the movie, press G and move it forward of backward
Press play and you should have a slower/faster movie, but this doesn't work

Windows7 x64, 2*GTX680 Broken: 2.75.4 4ae1815 After I have added a speed effect to a movie strip in the VSE, I select the end of the movie strip and move it with G, to make a timelapse or slow motion. This doesn't work. I can still tipe in numbers to multiply the speed by the factor x, but the above mentioned method doesn't work anymore. I tested .mp4 movies with H.264 and .avi with lagarith Lossless Codec. Can't attach .blend here because it would get to big with a movie in it, but: Add a movie Add a speed effect Select the end of the movie, press G and move it forward of backward Press play and you should have a slower/faster movie, but this doesn't work

mic lack30 commented

2015-09-07 12:09:28 +02:00

Changed status to: 'Open'

mic lack30 commented

2015-09-07 12:09:28 +02:00

Added subscriber: @michaellackner

Bastien Montagne commented

2015-09-07 14:16:18 +02:00

Added subscribers: @ideasman42, @mont29

Bastien Montagne commented

2015-09-07 14:16:18 +02:00

Iirc the behavior of speed effect was changed, @ideasman42 think it was you?

Campbell Barton commented

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

The change I made recently only made a very minor change to subframes and doubt it relates to this problem.

@michaellackner, regarding "the above mentioned method doesn't work anymore."

What was the last Blender version that worked?

The change I made recently only made a very minor change to subframes and doubt it relates to this problem. @michaellackner, regarding *"the above mentioned method doesn't work anymore."* - What was the last Blender version that worked?

mic lack30 commented

2015-09-07 19:45:02 +02:00

@ideasman42 I just had a look. 2.75a from here: http://download.blender.org/release/Blender2.75/ worked out quite well. By the way: Thank you for all your work!

Campbell Barton commented

2015-09-07 20:21:04 +02:00

@michaellackner, in your report you say 2.75.4 (a recent test-build) is broken. And official 2.75a release works.

In that case, the up-coming 2.76 release would have the bug.

Can you test a recent build from http://builder.blender.org to see if this is a regression since 2.75a?

@michaellackner, in your report you say `2.75.4` (a recent test-build) is broken. And official `2.75a` release works. In that case, the up-coming `2.76` release would have the bug. Can you test a recent build from http://builder.blender.org to see if this is a regression since 2.75a?

mic lack30 commented

2015-09-08 09:41:06 +02:00

@ideasman42 It was a build from http://builder.blender.org. Even the newest, that means it was probably 12 hours old. :D So yes, the bug must have been "implemented" in that time frame.

Campbell Barton commented

2015-09-08 11:52:00 +02:00

@michaellackner, ok. in future please make this clear in initial report: Worked VERSION, Broken VERSION.
This goes a long way to help narrow down the problem.

@michaellackner, ok. in future please make this clear in initial report: `Worked VERSION, Broken VERSION`. This goes a long way to help narrow down the problem.

mic lack30 commented

2015-09-08 11:54:32 +02:00

@ideasman42 I'm sorry. Will think of it the next time. I thought you know that it is a current build based on the buildnumber I wrote: 4ae1815.

@ideasman42 I'm sorry. Will think of it the next time. I thought you know that it is a current build based on the buildnumber I wrote: 4ae1815.

Campbell Barton commented

2015-09-08 13:34:07 +02:00

Added subscriber: @Psy-Fi