ColorRamp mute is not working #37334

New Issue

Cenek Strichel · 2013-11-05T21:53:03+01:00

Cenek Strichel commented

2013-11-05 21:53:03 +01:00

%%%--- Operating System, Graphics card ---
W8 64b, GeForce 250 S

- Blender version with error, and version that worked ---

r61076

- Short description of error ---

When you mute ColorRamp node in Compositor, whole render is not visible not only ColorRamp muted.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Node > Toggle node mute or press M with ColorRamp selected.
%%%

%%%--- Operating System, Graphics card --- W8 64b, GeForce 250 S - Blender version with error, and version that worked --- r61076 - Short description of error --- When you mute ColorRamp node in Compositor, whole render is not visible not only ColorRamp muted. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Node > Toggle node mute or press M with ColorRamp selected. %%%

Cenek Strichel commented

2013-11-05 21:53:03 +01:00

Changed status to: 'Open'

blender-admin commented

2013-11-05 21:53:03 +01:00

#37693 was marked as duplicate of this issue

Sergey Sharybin commented

2013-11-06 09:34:17 +01:00

%%%Please always do attach sample .blend file which demonstrates the issue. From my tests muting color ramp works just fine.%%%

Cenek Strichel commented

2013-11-06 10:51:44 +01:00

%%%Strange, for me it is replicatable on really simple scene. Now I tried it on r61157. I attached .blend now. Just press F12, render will black, after unmuting it will ok.%%%

Cenek Strichel commented

2013-11-06 10:54:24 +01:00

%%%I cant attach else .. so I use PasteAll: http://www.pasteall.org/blend/25053%%%

Sergey Sharybin commented

2013-11-07 09:49:32 +01:00

%%%Euh, crazy setup. The thing is, usually when you're muting the node one of it's inputs is getting mapped into output. In this case input is a value and output is a color. This makes piping of input to output being unpossible.

Lukas, can you think of possible tweaks here?%%%

%%%Euh, crazy setup. The thing is, usually when you're muting the node one of it's inputs is getting mapped into output. In this case input is a value and output is a color. This makes piping of input to output being unpossible. Lukas, can you think of possible tweaks here?%%%

Cenek Strichel commented

2013-11-07 12:42:46 +01:00

%%%I dont think that it is crazy :) Sometimes I need remap colors for artistic look. But now I know why mute is not working in this example :) Unless there will some autoconvert function in background for muting.%%%

Jeroen Bakker commented

2013-11-14 18:29:25 +01:00

Added subscriber: @Jeroen-Bakker

Lukas Tönne commented

2013-11-17 13:35:20 +01:00

The muting system uses "internal links" to define how the inputs are mapped to outputs (these are displayed as red links on muted nodes). This mapping currently uses a standard heuristic to find matching input<->output combinations, but it's not so easy to find a "one for all" algorithm. The behavior was changed recently in 834e47d to avoid problems with nonsensical connections, but this now excludes also cases like the color ramp node that would actually make sense ...

We need a coherent set of rules that works in more cases. In principle the method can be defined for each node type individually, but it should be at least possible to categorize nodes somewhat to have it work for certain classes of nodes. Another potential helper feature to make the algorithm more useful could be to tag certain sockets to allow them to connect to outputs with the same tag (like "primary" = main data that gets passed to output if conversion is possible, "secondary" = input parameter that never gets mapped).

The muting system uses "internal links" to define how the inputs are mapped to outputs (these are displayed as red links on muted nodes). This mapping currently uses a standard heuristic to find matching input<->output combinations, but it's not so easy to find a "one for all" algorithm. The behavior was changed recently in 834e47d to avoid problems with nonsensical connections, but this now excludes also cases like the color ramp node that would actually make sense ... We need a coherent set of rules that works in more cases. In principle the method can be defined for each node type individually, but it should be at least possible to categorize nodes somewhat to have it work for certain classes of nodes. Another potential helper feature to make the algorithm more useful could be to tag certain sockets to allow them to connect to outputs with the same tag (like "primary" = main data that gets passed to output if conversion is possible, "secondary" = input parameter that never gets mapped).

Lukas Tönne commented

2013-12-04 09:41:26 +01:00

Added subscriber: @intracube