Translate and Transform nodes unexpected behaviour #41104

New Issue

Mikhail Rachinskiy · 2014-07-16T17:24:39+02:00

2014-07-16 17:24:39 +02:00

System Information
Windows 8.1 x64
Renderer: GeForce GTX 860M/PCIe/SSE2
Vendor: NVIDIA Corporation
Version: 4.4.0

Blender Version
Broken: 2.71.2 de379c0

Short description of error
It seems like Translate and Transform nodes working withing the initial boundaries of transformed image/movie. Issue appears when I want to composit two images, each with different aspect ratio.

Exact steps for others to reproduce the error

Open blend file{F98156}
Press F12 to start render

See the results in various Preview nodes

**System Information** Windows 8.1 x64 Renderer: GeForce GTX 860M/PCIe/SSE2 Vendor: NVIDIA Corporation Version: 4.4.0 **Blender Version** Broken: 2.71.2 de379c0 **Short description of error** It seems like Translate and Transform nodes working withing the initial boundaries of transformed image/movie. Issue appears when I want to composit two images, each with different aspect ratio. **Exact steps for others to reproduce the error** - Open blend file{[F98156](https://archive.blender.org/developer/F98156/transform_node.blend)} - Press F12 to start render # See the results in various Preview nodes

Mikhail Rachinskiy commented

2014-07-16 17:24:39 +02:00

Changed status to: 'Open'

Mikhail Rachinskiy commented

2014-07-16 17:24:39 +02:00

Added subscriber: @MikhailRachinskiy

Bastien Montagne commented

2014-07-16 17:32:31 +02:00

Added subscriber: @mont29

Lukas Tönne commented

2014-07-16 18:47:24 +02:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-07-16 18:47:24 +02:00

I'm afraid this might be a limitation of the current compositor that can only be resolved by some recoding. It's related to how nodes pick their resolutions:

When connected to a render, preview or other output node with a higher resolution, this will be used for evaluating the node
When the Blur node is connected it creates a buffer first, which uses the "original" resolution of the input nodes, i.e. all parts outside this buffer get clamped (muting the blur will keep them visible).

It could perhaps be a simple fix of the Blur node, but have to investigate.

I'm afraid this might be a limitation of the current compositor that can only be resolved by some recoding. It's related to how nodes pick their resolutions: * When connected to a render, preview or other output node with a higher resolution, this will be used for evaluating the node * When the Blur node is connected it creates a buffer first, which uses the "original" resolution of the input nodes, i.e. all parts outside this buffer get clamped (muting the blur will keep them visible). It could perhaps be a simple fix of the Blur node, but have to investigate.

Mikhail Rachinskiy commented

2014-07-17 01:06:56 +02:00

Makes sense, maybe better leave i as is, anyway it is easier to put Blur node before Scale and Translate to make it work correctly.

You can not answer that, but I have a small question: I wonder why Transform node is even there? It is less convenient and less functional than Scale, Translate and Rotate nodes.

Makes sense, maybe better leave i as is, anyway it is easier to put Blur node before Scale and Translate to make it work correctly. You can not answer that, but I have a small question: I wonder why Transform node is even there? It is less convenient and less functional than Scale, Translate and Rotate nodes.

Lukas Tönne was assigned by Sergey Sharybin

2014-07-17 08:15:46 +02:00

Sergey Sharybin commented

2014-07-17 08:15:46 +02:00

Added subscriber: @Sergey

Lukas Tönne was unassigned by Sergey Sharybin

2014-09-17 15:05:45 +02:00

Sergey Sharybin self-assigned this 2014-09-17 15:05:45 +02:00

Sergey Sharybin commented

2014-09-19 11:32:11 +02:00

Added subscriber: @Jeroen-Bakker

Sergey Sharybin commented

2014-09-19 11:32:11 +02:00

@Jeroen-Bakker, i'm not actually sure. Shall i try fixing it or you'd think of better wait for the canvas-awareness?

Sergey Sharybin commented

2014-10-07 11:21:27 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-10-07 11:21:27 +02:00

Sergey Sharybin commented

2014-10-07 11:21:27 +02:00

Well, personally i would just call i known behavior and solve ll issues together as a part of canvas awareness project. This would hopefully happen for Gooseberry project.

Thanks for the report anyway.

Well, personally i would just call i known behavior and solve ll issues together as a part of canvas awareness project. This would hopefully happen for Gooseberry project. Thanks for the report anyway.

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

Translate and Transform nodes unexpected behaviour #41104

See the results in various Preview nodes