Compositing: Artefacts on tile borders when using filters #52534

Closed
opened 2017-08-25 12:06:38 +02:00 by Steffen Dünner · 8 comments

System Information
Win10 x64, nVidia GTX 1080Ti

Blender Version
Broken: 2.78c, 2.79RC2, Buildbot builds, own builds
Worked: none so far

Short description of error
Yesterday I had to upres some rendered pictures to match 4k footage. I used the Scale node set to "Render Size".
Incoming footage and render size was at 4096x2304, rendered pictures were half res ( 2048x1152).
I noticed that the upscaling looked terrible, like a simple nearest filter. (It would be nice to offer a selection of filters for scaling BTW, just like in the transform node).
The rendered stuff I had to upscale was just some blurry glows and light strokes, nothing too detailed or fancy. So I added a simple filter node set to "Soften" before the scale. It did the job, everything was smooth and it kind of matched the camera footage which looked a bit blurry as well.
But then I noticed ugly vertical and horizontal lines. The distribution varied with the tile size I set for the comp. The default of 256x256 gave me fewer of these lines than e.g. 64x64. They only appeared when using the filter before the scale node. They also show up when you put a blur node before the scale, even with a blur size of 0. I didn't try any other nodes because of lack of time, but I suspect there are others showing this behaviour as well. I don't know if it's the filter node's fault or the scale.
The "lines" show up both the the RGB and in the alpha channels. As a quick "fix" I used an Inpaint node to fill the gaps but this isn't a real solution.
This kind of bug also exists in older versions of Blender so it's not a regression.

Here's an example of this pattern. It's just an image with a constant colour scaled up 2 times.

Filter_Tile_Borders.png

Exact steps for others to reproduce the error

  • Open the attached blend file
  • Go to Compositing Layout and CTRL+SHIFT click the scale node to refresh the Viewer
  • See the ugly black lines
  • Switch the viewer to show the Alpha channel -> Ugly lines as well
  • Detach the Filter node and attach the Blur node instead: Same result
  • Change the tile size for the comp -> watch the grid like pattern become larger of smaller
  • Mute the Filter or the Blur node: Clean result

Scale_Filter_v01.blend

EDIT: After sending this ticket I noticed that the attached PNG uses the transparency of the alpha channel in the browser. You have to look closely but the lines are visible.

**System Information** Win10 x64, nVidia GTX 1080Ti **Blender Version** Broken: 2.78c, 2.79RC2, Buildbot builds, own builds Worked: none so far **Short description of error** Yesterday I had to upres some rendered pictures to match 4k footage. I used the Scale node set to "Render Size". Incoming footage and render size was at 4096x2304, rendered pictures were half res ( 2048x1152). I noticed that the upscaling looked terrible, like a simple nearest filter. (It would be nice to offer a selection of filters for scaling BTW, just like in the transform node). The rendered stuff I had to upscale was just some blurry glows and light strokes, nothing too detailed or fancy. So I added a simple filter node set to "Soften" before the scale. It did the job, everything was smooth and it kind of matched the camera footage which looked a bit blurry as well. But then I noticed ugly vertical and horizontal lines. The distribution varied with the tile size I set for the comp. The default of 256x256 gave me fewer of these lines than e.g. 64x64. They only appeared when using the filter before the scale node. They also show up when you put a blur node before the scale, even with a blur size of 0. I didn't try any other nodes because of lack of time, but I suspect there are others showing this behaviour as well. I don't know if it's the filter node's fault or the scale. The "lines" show up both the the RGB and in the alpha channels. As a quick "fix" I used an Inpaint node to fill the gaps but this isn't a real solution. This kind of bug also exists in older versions of Blender so it's not a regression. Here's an example of this pattern. It's just an image with a constant colour scaled up 2 times. ![Filter_Tile_Borders.png](https://archive.blender.org/developer/F725116/Filter_Tile_Borders.png) **Exact steps for others to reproduce the error** - Open the attached blend file - Go to Compositing Layout and CTRL+SHIFT click the scale node to refresh the Viewer - See the ugly black lines - Switch the viewer to show the Alpha channel -> Ugly lines as well - Detach the Filter node and attach the Blur node instead: Same result - Change the tile size for the comp -> watch the grid like pattern become larger of smaller - Mute the Filter or the Blur node: Clean result [Scale_Filter_v01.blend](https://archive.blender.org/developer/F725126/Scale_Filter_v01.blend) EDIT: After sending this ticket I noticed that the attached PNG uses the transparency of the alpha channel in the browser. You have to look closely but the lines are visible.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @SteffenD

Added subscriber: @SteffenD

Added subscribers: @Sergey, @dfelinto

Added subscribers: @Sergey, @dfelinto
Jeroen Bakker was assigned by Dalai Felinto 2017-08-29 11:40:09 +02:00

Confirmed here. That said, If you use the scale node BEFORE the other nodes things work fine.

Confirmed here. That said, If you use the scale node BEFORE the other nodes things work fine.

Thanks for confirming this. Yes, it "works" when scaling first, but in my case all the filters were set to a specific look and I was about to start the playout for the final delivery of several shots in 4k when all of a sudden I noticed this bug.
In the end I started resizing all of the render pictures with Fusion.

Thanks for confirming this. Yes, it "works" when scaling first, but in my case all the filters were set to a specific look and I was about to start the playout for the final delivery of several shots in 4k when all of a sudden I noticed this bug. In the end I started resizing all of the render pictures with Fusion.
Member

Added subscriber: @monique

Added subscriber: @monique
Member

These lines appear when determining the area of interest. Not sure why we never seen this one failing. But I added 1 pixel slack to the maxx and maxy side. Also tested with other resolutions and other tile orders.

These lines appear when determining the area of interest. Not sure why we never seen this one failing. But I added 1 pixel slack to the maxx and maxy side. Also tested with other resolutions and other tile orders.
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#52534
No description provided.