Node reference

How to use CC Blobbylize node in Oraphim

Use the CC Blobbylize node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.blobbylize.

Updated August 28, 2026

How to use CC Blobbylize node in Oraphim

Type ID: fusion.blobbylize
Category: Distort

What this node does

The CC Blobbylize node is registered in Oraphim's Distort category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 3 sockets and 21 properties for this node. Its main registered inputs are Input, Blob Layer; its main outputs are Output. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Input in_color Image
Blob Layer in_blob_layer Image

Outputs

Socket Key Type
Output out_color Image

Controls

Control Key Type Group Registry default
Effect Type effectType String Internal fx_cc_blobbylize
Property blobProperty String Blobbiness Luminance
Softness softness Float Blobbiness 12.0
Cut Away cutAway Float Blobbiness 20.0
Light Intensity lightIntensity Float Light 100.0
Light Red lightR Float Light 1.0
Light Green lightG Float Light 1.0
Light Blue lightB Float Light 1.0
Light Type lightType String Light Distant
Light Height lightHeight Float Light 60.0
Light Position X lightPositionX Float Light 0.25
Light Position Y lightPositionY Float Light 0.25
Light Direction lightDirection Float Light 45.0
Ambient ambient Float Shading 20.0
Diffuse diffuse Float Shading 80.0
Specular specular Float Shading 65.0
Roughness roughness Float Shading 30.0
Metal metal Float Shading 0.0
Edge Mode edgeMode String Edges Clamp
Quality quality String Quality High
Preserve Alpha preserveAlpha Bool Alpha 1.0

How to use it

  1. Add CC Blobbylize from node search. Use fusion.blobbylize when you need the exact registry entry.
  2. Connect a compatible Image source to Input. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Property, Softness, Cut Away first so you can see the node's effect in isolation.
  4. Route Output (Image) into a compatible downstream node, viewer, or output path.
  5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with CC Blobbylize. Feed a compatible source into Input. Change Property away from its registry default and compare the result. Connect Output to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

  • If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
  • If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
  • If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
  • If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Return to the complete Oraphim node reference.