shader_buffers 1.0.1

Using shaders to feed a shader. Make shaders simplier to use.

shader_buffers aims to simplify the use of shaders with a focus on the ShaderToy.com website.

• Features
• ShaderBuffers widget Usage
  • User interaction
  • Add simple check value operations
• Additional information
  • Writing a fragment shader

Features

• ✅ Use shader output to feed other shader textures.
• ✅ Feed shaders with asset images or any widgets as sampler2D uniforms.
• ✅ Capture user interaction.
• ✅ Easily add custom uniforms.
• ✅ Animate custom uniforms.
• ✅ Play / Pause / Rewind shader.
• ✅ Conditional operations to check mouse/tap position, time, frame number, and custom uniforms.

Please, take a look at the shader_presets package which implements some ready-to-use shaders, like transitions and effects (from gl-transitions and ShaderToy).

Tested on Android Linux and web, on other desktops, it should work. Cannot test on Mac and iOS. Shader examples are from ShaderToy.com and have been slightly modified. Credits links are in the main shaders sources.

Note

Using a shader output to feed itself, produces a memory leak: memory leak issue. Please thumb it up! A temporary fix is used.

ShaderBuffers widget Usage

The main widget to use is ShaderBuffers, which takes its size and mainImage as input. Optionally, you can add the buffers.

mainImage and buffers are of type LayerBuffer, which defines the fragment shader asset source and the texture channels.

mainImage shader must be provided. The more buffers, the more performances will be affected. Think of mainImage as the Image layer fragment in ShaderToy.com and buffers as Buffer[A-D].

Each frame buffers are computed from the 1st to the last, then mainImage.

This widget provides the following uniforms to the fragment shader:

• sampler2D iChannel[0-N] as many as defined in LayerBuffer.channels
• vec2 iResolution the widget width and height
• float iTime the current time in seconds from the start of rendering
• float iFrame the current rendering frame number
• vec4 iMouse for user interaction with pointer (see IMouse)

To start, you can define the layers:

/// The main layer uses `shader_main.frag` as a fragment shader source and some float uniforms
final mainImage = LayerBuffer(
  shaderAssetsName: 'assets/shaders/shader_main.glsl',
  uniforms: Uniforms([
      Uniform(
        name: 'blur',
        range: const RangeValues(0, 1),
        defaultValue: 0.9,
        value: 0.9,
      ),
      Uniform(
        name: 'velocity',
        range: const RangeValues(0, 1),
        defaultValue: 0.2,
        value: 0.2,
      ),
    ]),
);

Now you can use ShaderBuffer:

ShaderController controller = ShaderController();
ShaderBuffer(
  controller: controller,
  mainImage: mainImage,
)

mainImage and buffers are of type IChannel. The latter represents the uniform sampler2D texture to be passed to the fragment shader.

User interaction

ShaderBuffer listen to the pointer with onPointerDown, onPointerMove, onPointerUp which give back the controller and the position in pixels. Most of the time is more useful to have back the normalized position (in the 0~1 range) instead of pixels. This can be achieved with onPointerDownNormalized, onPointerMoveNormalized, onPointerUpNormalized callbacks. With the controller, the one passed to ShaderBuffer, or the one returned by the onPointer* callbacks, is possible to do these:

• play
• pause
• rewind
• getState
• getImouse
• getImouseNormalized

Add simple check value operations

It's possible to check for some conditions.

• a condition is bonded to a given LayerBuffer.
• the param could be:iMouseX, iMouseY, iMouseXNormalized, iMouseYNormalized, iTime, iFrame
• checkType could be: minor, major, equal
• checkValue is the value to check
• operation is the callback that returns true of false based on the resulting check

controller
  ..addConditionalOperation(
    (
      layerBuffer: mainImage,
      param: Param.iMouseXNormalized,
      checkType: CheckOperator.minor,
      checkValue: 0.5,
      operation: (result) {
        /// [result] == true means (iMouseXNormalized < 0.5 )
      },
    ),
  )

To get something similar to this chart

final mainLayer = LayerBuffer(
    shaderAssetsName: 'assets/shaders/shader_main.frag',
);
final bufferA = LayerBuffer(
    shaderAssetsName: 'assets/shaders/shader_bufferA.frag',
);
final bufferB = LayerBuffer(
    shaderAssetsName: 'assets/shaders/shader_bufferB.frag',
);
final bufferC = LayerBuffer(
    shaderAssetsName: 'assets/shaders/shader_bufferC.frag',
);
mainLayer.setChannels([IChannel(buffer: bufferC)])
bufferB.setChannels([IChannel(buffer: bufferA)]);
bufferC.setChannels([
  IChannel(buffer: bufferA),
  IChannel(buffer: bufferB),
  IChannel(assetsImage: 'assets/bricks.jpg'),
]);

Additional information

The main drawback when willing to port ShaderToy shader buffers is that they use 4 floats per RGBA channel, while with Flutter shader we are stuck using 4 int8 RGBA. Also, the coordinate system is slightly different: the origin in ShaderToy is bottom-left while in Flutter, is top-left. This latter issue can be easily bypassed where in the main image layer you see this: vec2 uv = fragCoord.xy / iResolution.xy; after this line, you can add this to swap Y coordinates: uv = vec2(uv.x, 1. - uv.y);

Writing a fragment shader

It's mandatory to provide the shader the following uniforms since shader_buffer always sends them:

uniform vec2 iResolution;
uniform float iTime;
uniform float iFrame;
uniform vec4 iMouse;

For simplicity, there is assets/shader/common/common_header.frag to include at the very beginning of the shader: #include <common/common_header.frag>

it provides also: out vec4 fragColor;

If are experimenting with ShaderToy shaders, start your code copied from it and at the bottom of the file include main_shadertoy.frag: #include <common/main_shadertoy.frag>