Mosaic — 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 camera pulls back over a wall of rotated tiles from both shots, pans, and settles on the next

Prompt that renders it frame-exact

Add the "Mosaic" transition from GL Transitions (by Xaychru, MIT; https://gl-transitions.com/editor/Mosaic, GLSL source https://github.com/gl-transitions/gl-transitions/blob/master/transitions/Mosaic.glsl) between two scenes of a recap or a portfolio reel: 1.4 s, ease-in-out. Mirrored and upside-down copies of both shots fill the wall. Remotion: npm install gl-transitions @gl-transitions/remotion @remotion/transitions, then a <TransitionSeries.Transition> with presentation={glTransition({ name: "Mosaic", params: { endx: 2, endy: -1 } })} and timing={linearTiming({ durationInFrames: 42, easing: Easing.inOut(Easing.cubic) })} (42 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) / 1.4, 0, 1) through the easing; never from requestAnimationFrame or a timer, so every frame renders the same. ffmpeg's xfade can't run GLSL. endx (2) and endy (-1) are integers that set which tile the pan ends on.

Used in

More transitions