A video strip is unnecessarily cropped before final mapping to render result #42355

New Issue

Willi · 2014-10-22T23:43:35+02:00

Willi commented

2014-10-22 23:43:35 +02:00

System Information
Win7/64, GTX 750 Ti

Blender Version
2.72

Short description of error
see title

Exact steps for others to reproduce the error

Set the scene's size to 1280x720.
In the VSE, add a video strip with a size greater than 1280x720, and the aspect ratio is not 16:9, for example 1728x1080.
To prevent Blender from chaging the video strip's aspect ratio, enable the video strip's "Image offset" property (in the "strip input" panel)
Add a tranform effect strip to the video strip and scale to 0.5. The problem is: The scaled image is cropped even though the final image after applying all effect strips would fit into the render target.

**System Information** Win7/64, GTX 750 Ti **Blender Version** 2.72 **Short description of error** see title **Exact steps for others to reproduce the error** - Set the scene's size to 1280x720. - In the VSE, add a video strip with a size greater than 1280x720, and the aspect ratio is not 16:9, for example 1728x1080. - To prevent Blender from chaging the video strip's aspect ratio, enable the video strip's "Image offset" property (in the "strip input" panel) - Add a tranform effect strip to the video strip and scale to 0.5. The problem is: The scaled image is cropped even though the final image after applying all effect strips would fit into the render target.

Willi commented

2014-10-22 23:43:35 +02:00

Changed status to: 'Open'

Willi commented

2014-10-22 23:43:35 +02:00

Added subscriber: @willi-2

Antonis Ryakiotakis commented

2014-10-23 12:59:01 +02:00

Changed status from 'Open' to: 'Archived'

Antonis Ryakiotakis closed this issue

2014-10-23 12:59:01 +02:00

Antonis Ryakiotakis self-assigned this 2014-10-23 12:59:01 +02:00

Antonis Ryakiotakis commented

2014-10-23 12:59:01 +02:00

Transform is independent from image offset, you shouldn't expect that the two would interact. Image offset looked a bit suspicious but from discussion at the institute seems like it works as intended as well.

Willi commented

2014-10-23 13:38:27 +02:00

Probably I didn't make myself clear. Sorry for this.

Of course, the Transform strip is independent from image offset. I have to activate "- [x] image offset" (keeping the offset zero) as the first step in the processing queue in order to prevent Blender from changing the original's image aspect ratio.
Second, the Transform strip is to scale the image down in order to fit into the target size. The problem I'm talking about is that the first step unnecessarily crops the image. Therefore, scaling it down gets useless as it has already been cropped.

The point is that Blender crops the image at the first step in the processing queue if it doesn't fit into the render target. Instead, it has to be cropped if it doesn't fit into the render target after the last step in the queue.

This way, information gets lost. Hence I consider it a bug.

Probably I didn't make myself clear. Sorry for this. Of course, the Transform strip is independent from image offset. I have to activate "- [x] image offset" (keeping the offset zero) as the first step in the processing queue in order to prevent Blender from changing the original's image aspect ratio. Second, the Transform strip is to scale the image down in order to fit into the target size. The problem I'm talking about is that the first step unnecessarily crops the image. Therefore, scaling it down gets useless as it has already been cropped. The point is that Blender crops the image at the first step in the processing queue if it doesn't fit into the render target. Instead, it has to be cropped if it doesn't fit into the render target *after the last step* in the queue. This way, information gets lost. Hence I consider it a bug.

Antonis Ryakiotakis commented

2014-10-23 13:50:37 +02:00

Again, from quick discussion here result is:

It's crap but it's intended crap and we may break old files if we change this behaviour. The way we might consider changing this is if it gets wider feedback from VSE users and we agree on breaking this.

Again, from quick discussion here result is: It's crap but it's intended crap and we may break old files if we change this behaviour. The way we might consider changing this is if it gets wider feedback from VSE users and we agree on breaking this.

Willi commented

2014-10-23 14:23:14 +02:00

Ok, I see.
Though, thank you.

Ok, I see. Though, thank you.

Alberto Mardegan commented

2016-08-09 09:09:27 +02:00

Added subscriber: @mardy

Alberto Mardegan commented

2016-08-09 09:20:54 +02:00

I'd like for this bug to be reopened. The current implementation makes it rather troublesome to import high resolution images and have them rendered at a lower scale, like the bug description says. This becomes even harder when importing videos, because doing similar preparation works for videos is far from trivial.
And, most importantly, the current implementation makes it impossible to animate the scale property on such imported images or videos: imagine having a project for a 640x480 video, and importing a 1920x1080 video, which we want to show with an animated scale ranging from 0.4 to 1.0.

I agree that compatibility is an issue here, so the new behaviour would have to be explicitly enabled with a checkbox on the imported image/video strip (or on the transformation strip?).

I might give a try in implementing this. Any hints and suggestions are welcome. :-)

FYI: see also http://blender.stackexchange.com/questions/6712/how-to-shrink-an-image-with-the-video-sequence-editor

I'd like for this bug to be reopened. The current implementation makes it rather troublesome to import high resolution images and have them rendered at a lower scale, like the bug description says. This becomes even harder when importing videos, because doing similar preparation works for videos is far from trivial. And, most importantly, the current implementation makes it impossible to animate the scale property on such imported images or videos: imagine having a project for a 640x480 video, and importing a 1920x1080 video, which we want to show with an animated scale ranging from 0.4 to 1.0. I agree that compatibility is an issue here, so the new behaviour would have to be explicitly enabled with a checkbox on the imported image/video strip (or on the transformation strip?). I might give a try in implementing this. Any hints and suggestions are welcome. :-) FYI: see also http://blender.stackexchange.com/questions/6712/how-to-shrink-an-image-with-the-video-sequence-editor

Dyzinel commented

2016-09-22 01:12:36 +02:00

Added subscriber: @Dyzinel

Dyzinel commented

2016-09-22 01:12:36 +02:00

Duuuuuude.... I'm SO ANRGY for trying to scale my video for AN ENTIRE MONTH and be unable to do it properly just to know it was IMPOSIBLE TO ACTUALLY FUC**** DO IT! Right now I just feel like removing all my hair with my hands or jump in a volcano... Well, not really. But duuuuuuuudes, that bug was reported back in 2014 and yall still didn't do a thing about it?! Like, rREALLY? I'm trying to do a simple edit of my smartphone's video while I'm almost exploding (even so it lags by a lot even if it is actually just 2 minutes while my PC videos that are over an hour doesn't lag at all). Like, I'm feeling so much headache just by trying to make this damn video... I know I should be grateful for Blender being a free software but, really... It's literally impossible to make a good edition of a large resolution video into a new smaller video with different aspect ratio without ruining it completely... Well, tired of typing, please do something about it, thanks.

Alberto Mardegan commented

2016-09-22 10:01:21 +02:00

In #42355#393050, @Dyzinel wrote:
Duuuuuude.... I'm SO ANRGY for trying to scale my video for AN ENTIRE MONTH and be unable to do it properly just to know it was IMPOSIBLE TO ACTUALLY FUC**** DO IT!

It's impossible to do that in the sequencer, but you can still do it using the node compositor. It's a more lengthy process, but it works. Here's a video (in Spanish, I didn't find an English version, but you should get it anyway) which shows how it's done:

https://www.youtube.com/watch?v=7vJKwqbSi6U

Just use the sequencer as you normally do, and create a separate scene for each image you want to put into the video, then add the scenes as strips into the sequencer.

> In #42355#393050, @Dyzinel wrote: > Duuuuuude.... I'm SO ANRGY for trying to scale my video for AN ENTIRE MONTH and be unable to do it properly just to know it was IMPOSIBLE TO ACTUALLY FUC**** DO IT! It's impossible to do that in the sequencer, but you can still do it using the node compositor. It's a more lengthy process, but it works. Here's a video (in Spanish, I didn't find an English version, but you should get it anyway) which shows how it's done: https://www.youtube.com/watch?v=7vJKwqbSi6U Just use the sequencer as you normally do, and create a separate scene for each image you want to put into the video, then add the scenes as strips into the sequencer.

Ben commented

2016-10-03 19:55:31 +02:00

Added subscriber: @holyone2

Ben commented

2016-10-03 19:55:31 +02:00

+1 to this. Surely this is a very big bug given that it must be a common use-case that people want to import high-resolution images and downscale the output to a low resolution, without loosing part of their image!

David commented

2017-02-08 19:38:12 +01:00

Added subscriber: @CrowdLeader

David commented

2017-02-08 19:38:12 +01:00

just want to add to the continued frustration of trying to scale down images without window-boxing them :-(

David commented

2017-02-08 19:58:57 +01:00

one kind of solution... if you 'check' "image offset" on the image strip and then change the render resolution it does not transform the image.
set the render resolution to the original image size, uncheck image offset, change render resolution back to desired size and then at a transform strip to deal with any ratio change issues.

one kind of solution... if you 'check' "image offset" on the image strip and then change the render resolution it does not transform the image. set the render resolution to the original image size, uncheck image offset, change render resolution back to desired size and then at a transform strip to deal with any ratio change issues.

Olly Funkster commented

2017-02-09 18:04:26 +01:00

Added subscriber: @Funkster-3

Olly Funkster commented

2017-02-09 18:04:26 +01:00

Because I felt like it, I have made D2506 which introduces Ken Burns Mode to Transform strips. If you find it helps then use it, if you don't then don't! :o)

Because I felt like it, I have made [D2506](https://archive.blender.org/developer/D2506) which introduces Ken Burns Mode to Transform strips. If you find it helps then use it, if you don't then don't! :o)

Kakurady Drakenar commented

2017-03-04 13:58:47 +01:00

Added subscriber: @kakurady

Landon commented

2021-08-04 11:10:14 +02:00

Added subscriber: @Ref

Landon commented

2021-08-04 11:10:14 +02:00

In #42355#265551, @Psy-Fi wrote:
Again, from quick discussion here result is:

It's crap but it's intended crap and we may break old files if we change this behaviour. The way we might consider changing this is if it gets wider feedback from VSE users and we agree on breaking this.

Blender can't scale video down because of... anxiety?

> In #42355#265551, @Psy-Fi wrote: > Again, from quick discussion here result is: > > It's crap but it's intended crap and we may break old files if we change this behaviour. The way we might consider changing this is if it gets wider feedback from VSE users and we agree on breaking this. Blender can't scale video down because of... anxiety?

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

A video strip is unnecessarily cropped before final mapping to render result #42355