Custom Shaders is a LUA script for Open Broadcaster Software (OBS) that can be used to apply OBS effects to any image source. An OBS effect (or shader) is defined in a file with a nearly identical syntax to Direct3D 11 HLSL effect files.

This script was inspired by the filter-custom included in DarkLink's Script Pack and builds upon the features provided by the obs-shaderfilter and the OBS ShaderFilter Plus plugins.

As a Linux user I couldn't use obs-shaderfilter because it is only supported for Windows and a tentative compilation lead to nowhere. OBS ShaderFilter Plus works very well under Linux and, in some ways, is an improved version of obs-shaderfilter but it seems its development is uncertain and I don't know Rust.

And so, I turned to the scripting languages that OBS supports and Lua(JIT) became the natural candidate over Python.

1. No compilation and no installation of pre-compiled components are required
2. Cross-platform by nature (although it has only be tested under Linux. I'll be glad to receive feedback from users of other OSes)
3. Enlarged support of variable types
4. Allows the use of vertex or pixel shaders (see below for the conventions adopted)
5. Full support of image files (textures)

Custom Shaders is a single file script that can be placed anywhere in your filesystem. Add it to OBS on the Tools > Scripts menu and it will be ready to use.

1. Add a filter to a source by right-clicking a source, going to Filters, and adding Custom Shader. The following default effect will be immediately applied to let you know that the script is working. This effect will also be used as a fallback if any recoverable error happens when an effect file is loaded.

   

2. Select an effect file by clicking the Browse button and picking the file containing the effect source code.

3. If everything goes well, you can customize the behavior of the shader via the shader-specific user interface (UI).

Example shaders can be found in the examples directory of this repository.

Shaders are programs executed on the GPU that apply special visual effects to the rendered graphics. They can be written in GLSL (OpenGL) or HLSL (DirectX), among other languages. OBS uses its own limited version of HLSL

The shaders that can be used with this plugin are of two types:

• pixel shaders that modify attributes of each pixel in every frame.

  The script will look in the effect file you provide for a line like the following:

  float4 mainImage(VertData v_in) : TARGET
  

  with or without an opening bracket at the end. Spaces are irrelevant and the input variable, v_in, can be named anything else. If it succeedes, it will be assumed that a pixel shader is provided in the file. Otherwise, the following dummy pixel shader will be used:

  float4 mainImage(VertData v_in) : TARGET
  {
     return image.Sample(textureSampler, v_in.uv);
  }
  

• vertex shaders that can manipulate properties such as position, color and texture coordinates of points in 2D or 3D space.

  The same as before applies with the following dummy vertex shader:

  VertData mainTransform(VertData v_in)
  {
     VertData vert_out;
     vert_out.pos = mul(float4(v_in.pos.xyz, 1.0), ViewProj);
     vert_out.uv  = v_in.uv;
     return vert_out;
  }
  

Type	Controlled in the UI	Default value
int	Yes
int2	No
int3	No
int4	No
float	Yes
vec2 / float2	No
vec3 / float3	No
vec4 / float4	Yes (treated as a color)	#00000000
bool	Yes	false
texture2d	Yes (as a path to an image file)

To every shader loaded by this script the following uniform variables are added:

For each declared texture2d variable it will also be included a float2 uniform containing the width and height of the image. For a variable named myImage the corresponding size uniform will be called myImage_size.

As presented in the fist table above, five types of variables can be controlled in the filter UI. The names of those types of variables are capitalised and underscores are replace with spaces in the UI.

You can further customize the UI elements by including special directives (pragmas) in the effect code. So, for an uniform variable named speed, you can write a pragma with up to four parameters:

#pragma speed 0.0, 10.0, 1.0, 0

meaning, in this example, that the variable has a minimum value of 0.0, a maximum value of 10.0, can be changed in steps of 1.0 and it should not be controlled by a slider. Any missing parameter will be replaced by a default value.

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to http://unlicense.org/