Nodes: Add SepiaNode

[cmhhelgeson]

Related issue:

Description

Port of GLSL Sepia Shader to node system.

postProcessing = new THREE.PostProcessing( renderer );
const scenePass = pixelationPass( scene, camera, effectController.pixelSize, 
effectController.normalEdgeStrength, effectController.depthEdgeStrength );
// scenePass.getTextureNode() returns pixelation.textureNode, renderOutput returns full effect
const sepiaPass = sepia( { color: scenePass.renderOutput() } );
postProcessing.outputNode = mix( scenePass, sepiaPass, effectController.mixValue );

Live Example

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

Filesize dev	Filesize PR	Diff
684 kB (169.4 kB)	684 kB (169.4 kB)	+0 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

Filesize dev	Filesize PR	Diff
460.9 kB (111.2 kB)	460.9 kB (111.2 kB)	+0 B

[sunag]

I think serpia could be introduced without needing a texture as a parameter, maybe just a tslFn could solve the issue.

[sunag]

Could amount be replaced by a mix externally? Maybe we don't need it as a parameter.

[cmhhelgeson]

Could amount be replaced by a mix externally? Maybe we don't need it as a parameter.

I think that makes sense if we're just strictly replicating the sepia effect, but for portability between the old and new shaders I think it makes sense to keep in cases where people are deliberately pushing the value to achieve specific effects.

I think serpia could be introduced without needing a texture as a parameter, maybe just a tslFn could solve the issue.

Were you think something more like the colorAdjustmentNode where the tslFn is only taking in a color? Or just export a tslFn directly from the file?

[sunag]

I think that makes sense if we're just strictly replicating the sepia effect, but for portability between the old and new shaders I think it makes sense to keep in cases where people are deliberately pushing the value to achieve specific effects.

Developers didn't have support for this level of abstraction before, so we had intensity and amount everywhere, but that's no longer necessary, adding them nowadays would just be adding extra code and operations.

Even if this were preserved and for the sake of practicality, the feeling when looking at the code is that it should be done with mix, multiplying all the values ​​of the serpia vector seems more costly for gpu..

Were you think something more like the colorAdjustmentNode where the tslFn is only taking in a color? Or just export a tslFn directly from the file?

I think no class is needed for this, just export tslFn, like:

export const serpia = /*@__PURE__*/ tslFn( ( [ color ] ) => {

} );

[cmhhelgeson]

Developers didn't have support for this level of abstraction before, so we had intensity and amount everywhere, but that's no longer necessary, adding them nowadays would just be adding extra code and operations.

That makes sense, thank you for that explanation, and I'll adjust the code accordingly.