Compositor works poorly with Full Sample Antialiasing #39143

New Issue

Zauber Paracelsus · 2014-03-12T21:30:49+01:00

Zauber Paracelsus commented

2014-03-12 21:30:49 +01:00

System Information
64bit Linux Mint 16
Linux Kernel 3.11.0
nVidia GTX 650 Ti, driver 319.32

Blender Version
Broken: Broken: 2.69, 2.70 Release Candidate 1

Short description of error
When the "Full Sample" option for antialiasing is used, the compositor operates on each sample image individually, leading to a much longer time for compositing. In addition, if you edit the compositor nodes or toggle any compositor settings, then when re-applying the compositor nodes, it only applies to the first sample, requiring you to do a full re-render.

Suggested fix: Do not apply the compositor to individual antialiasing samples: only apply it to the final result of the render.

Exact steps for others to reproduce the error
Open any scene using the compositor along with the glare node. Then render both with and without Full Sample on Antialiasing.

**System Information** 64bit Linux Mint 16 Linux Kernel 3.11.0 nVidia GTX 650 Ti, driver 319.32 **Blender Version** Broken: Broken: 2.69, 2.70 Release Candidate 1 **Short description of error** When the "Full Sample" option for antialiasing is used, the compositor operates on each sample image individually, leading to a much longer time for compositing. In addition, if you edit the compositor nodes or toggle any compositor settings, then when re-applying the compositor nodes, it only applies to the first sample, requiring you to do a full re-render. Suggested fix: Do not apply the compositor to individual antialiasing samples: only apply it to the final result of the render. **Exact steps for others to reproduce the error** Open any scene using the compositor along with the glare node. Then render both with and without Full Sample on Antialiasing.

Zauber Paracelsus commented

2014-03-12 21:30:49 +01:00

Changed status to: 'Open'

Zauber Paracelsus commented

2014-03-12 21:30:49 +01:00

Added subscriber: @ZauberParacelsus

Zauber Paracelsus commented

2014-03-12 21:39:01 +01:00

As an additional note, this can also cause the composited image to appear incorrectly. For example, the use of a glare node might appear brighter than it should be. I've uploaded some examples below:

Without Full Sample:
With Full Sample:

As an additional note, this can also cause the composited image to appear incorrectly. For example, the use of a glare node might appear brighter than it should be. I've uploaded some examples below: **Without Full Sample:** ![FullSampleTest_Off.png](https://archive.blender.org/developer/F80872/FullSampleTest_Off.png) **With Full Sample:** ![FullSampleTest_On.png](https://archive.blender.org/developer/F80874/FullSampleTest_On.png)

Adam Friesen commented

2014-03-12 21:58:55 +01:00

Added subscriber: @Ace_Dragon

Adam Friesen commented

2014-03-12 21:58:55 +01:00

This is more or less due to how FSA works at the moment.

For FSA to even work like it does now, it needs to take multiple samples of the entire composited image (which the only way to get those samples is to re-composite multiple times).

As for the FSA disappearing when a setting is changed, this has been a limitation of the system since its initial implementation (more in the line of missing functionality rather than a bug). In general, I believe that people would usually get the compositing right first and then render using FSA, but reworking the implementation so that it does the anti-aliasing process over again on a setting change (or implementing a new system which doesn't require 4-8-16 re-composites) is not really seen to be in bug territory.

This is more or less due to how FSA works at the moment. For FSA to even work like it does now, it needs to take multiple samples of the entire composited image (which the only way to get those samples is to re-composite multiple times). As for the FSA disappearing when a setting is changed, this has been a limitation of the system since its initial implementation (more in the line of missing functionality rather than a bug). In general, I believe that people would usually get the compositing right first and then render using FSA, but reworking the implementation so that it does the anti-aliasing process over again on a setting change (or implementing a new system which doesn't require 4-8-16 re-composites) is not really seen to be in bug territory.

Zauber Paracelsus commented

2014-03-12 22:01:00 +01:00

Well, for right now I'm using FSA to work around an issue I have, where surfaces with high emission will have heavier aliasing than other surfaces. Are there any other workarounds I could try?

Sergey Sharybin commented

2014-03-13 08:38:11 +01:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-03-13 08:38:11 +01:00

Sergey Sharybin self-assigned this 2014-03-13 08:38:11 +01:00

Sergey Sharybin commented

2014-03-13 08:38:11 +01:00

Thanks for the report, but it's obviously not a bug but a specific of how compositor is designed at this moment. Improvements are possible but they're considered a TODO. Made sure this report is listed in our wiki: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Compositing

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

Compositor works poorly with Full Sample Antialiasing #39143