ISF Shaders
The ISF Shader process runs Interactive Shader Format fragment shaders on the GPU. Use it for video filters, generators, feedback effects, post-processing, texture conversion, and Shadertoy-style visuals.
ISF shaders can be drag-and-dropped from the process library, user library, or file explorer. score reads the JSON header, creates controls and texture ports automatically, and recompiles the shader while the score is running.
When to use ISF
Use ISF when the shader renders a fullscreen image pass. Use a different process when the work is not a fullscreen fragment pass:
| Goal | Better process |
|---|---|
| Run arbitrary compute, write storage images, generate geometry | Compute Shaders |
| Draw custom 3D geometry with a vertex shader | Render Pipeline |
| Display existing geometry quickly | Model Display |
| Write Vertex Shader Art-style point / line visuals | Vertex Shader Art |
Files and live editing
An ISF shader is usually a .fs or .frag file with a JSON header followed by GLSL. A custom vertex shader can be paired with the fragment shader; the editor can live-code both stages.
Press Ctrl+Enter(Win / Linux) or⌘+Enter(Mac) in the shader editor to recompile during playback. For production authoring, the official ISF editor remains useful, but score supports the runtime-specific features documented here.
Shader sources can use #include; include paths are resolved before parsing.
Language reference
The ISF language reference documents the JSON header, controls, textures, audio, built-ins, outputs, multipass rendering, sizing and alpha. It distinguishes standard ISF from score extensions. Start with its brightness filter, or follow Shader cookbook for feedback and MRT recipes.
Go directly to a relocated section:
- JSON header
- Common fields
- Scalar input types
- Texture inputs
- 2D image
- 3D image / volume
- Cubemap
- Sampleable depth
- Sampler state
- Audio textures
- Texture macros
- Built-in uniforms
- Outputs
- Multiple render targets
- Output fields
- Multipass rendering
- Size expressions
- Alpha and compositing
- Examples
- Simple color filter
- Generator
- Feedback trail
- MRT output
Connecting and previewing
Connect a video or image producer to the generated image inlet, adjust the controls, and connect the shader output to a video output or another effect. Generators need no image inlet. The texture inlet inspector provides an explicit size checkbox with width and height controls; uncheck it for Auto sizing. The Show shader previews toolbar action controls library and inspector previews. See Graphics pipeline for sizing and backend limits.
Related Processes
- Compute Shaders: Compute shaders for images, buffers, volumes, and geometry.
- Render Pipeline: Raw vertex / fragment pipeline for custom 3D rendering.
- Vertex Shader Art: Vertex Shader Art-compatible generative shaders.
- Model Display: Built-in renderer for geometry.
- Lightness Computer: Convert textures to pixel arrays for LED workflows.