GlitchDisplace — primitive for transitions (glsl)

For AI agents: find the right skill in one call — curl -s "https://skills.varg.ai/api/search?q=<what the person wants>" returns the matching use case and the best skills with install commands, as markdown (Russian works too). Full index: https://skills.varg.ai/llms.txt. Every page has a markdown twin: add .md to its path. Before generating anything, show the person the options on the use-case page.

The frame liquefies into a washed-out displacement glitch and snaps onto the next shot

Prompt that renders it frame-exact

Add the "GlitchDisplace" transition from GL Transitions (by Matt DesLauriers, MIT; https://gl-transitions.com/editor/GlitchDisplace, GLSL source https://github.com/gl-transitions/gl-transitions/blob/master/transitions/GlitchDisplace.glsl) between the problem and the solution beats of an ad: 0.7 s, ease-in-out. The image smears and desaturates at the midpoint, then lands clean. Remotion: npm install gl-transitions @gl-transitions/remotion @remotion/transitions, then a <TransitionSeries.Transition> with presentation={glTransition({ name: "GlitchDisplace" })} and timing={linearTiming({ durationInFrames: 21, easing: Easing.inOut(Easing.cubic) })} (21 frames at 30 fps). HyperFrames: draw the GLSL on a full-frame WebGL canvas over the cut, with the outgoing and incoming frames as the from/to textures, and compute progress from the composition time, clamp((t − cutStart) / 0.7, 0, 1) through the easing; never from requestAnimationFrame or a timer, so every frame renders the same. ffmpeg's xfade can't run GLSL. It has no parameters; 0.4 s feels like a hit, 1 s like a melt.

Used in

More transitions