The new capability of loading user-provided GLSL shaders into Processing’s P2D and P3D renderers opens up the possibility of customizing all the rendering operations in Processing, as well as of creating interactive graphics that would be very hard or impossible to generate otherwise. For OpenGL web applications, WebGL supports (only) programmable pipelines through GLSL shaders, and this has motivated the creation of online repositories of shader effects that can be run directly from inside the web browsers, as long as they support WebGL. Sites like the GLSL sandbox or Shader Toy hold large collections of shader effects that can be edited and controlled interactively through the browser. This new post will explain how to integrate GLSL shaders from the GLSL sandbox and Shader Toy websites into a Processing sketch.
Update: With the release of Processing 2.0 final, some of the contents in this post are outdated, please check this tutorial for a detailed description of the finalized shader API.

This new release of GLGraphics comes hand in hand with GSVideo 0.9, also available today. These new versions of the two libraries introduce a combined mode of operation that greatly improves video playback performance, which I will describe in the next post. Now I will focus on the new features of GLGraphics concerning exclusively with rendering and shading.

This is the second part of the Andiamo reference manual. It describes the installation process, overview of the interface  and configuration files.

I couple of weeks ago I started coding up in Processing a tool for live visual performance using real-time video effects, drawing, animation and computer vision techniques. The name of this tool is ANDIAMO, which is an Spanish acronym for ANimador DIgital Analógico MOdular (Digital-Analog Modular Animator).

This release of GLGraphics introduces a new and improved way of handling the parameters of the texture filters. Before 0.8.9, the parameters had to be passed to the filter with a GLTextureFilterParameters object. This object allowed only a predetermined number of parameters to be set in the shader. Furthermore, the name of these parameters was hard-coded, for example a float parameter in the shader had to be called par_flt1, for instance, in order to be recognized by the filter.