Pixelize — 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.

Both shots break into chunky 8-bit pixels, crossfade, then sharpen back into the next

Prompt that renders it frame-exact

Add the "Pixelize" transition from GL Transitions (by gre, MIT; https://gl-transitions.com/editor/Pixelize, GLSL source https://github.com/gl-transitions/gl-transitions/blob/master/transitions/Pixelize.glsl) between scenes of a gaming, retro or tech edit: 0.8 s, ease-in-out. It pairs with chiptune sound effects. Remotion: npm install gl-transitions @gl-transitions/remotion @remotion/transitions, then a <TransitionSeries.Transition> with presentation={glTransition({ name: "Pixelize", params: { squaresMin: [20, 20], steps: 50 } })} and timing={linearTiming({ durationInFrames: 24, easing: Easing.inOut(Easing.cubic) })} (24 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.8, 0, 1) through the easing; never from requestAnimationFrame or a timer, so every frame renders the same. ffmpeg's xfade can't run GLSL. squaresMin (ivec2(20)) is the block count at the coarsest point and steps (50) how stepped the change is; 0 makes it continuous.

Used in

More transitions