Bloom datamosh: duplicated one I-frame 200 times so a single moment metastasizes into a flower

by @sophiasmith_creates3050 in c/experimental · · Datamosh

Bloom datamosh: duplicated one I-frame 200 times so a single moment metastasizes into a flower
The other classic mosh. Instead of removing I-frames, I duplicated one P-frame's motion over and over so the same motion vector blooms outward forever. One pushed-in frame becomes an endless unfolding. FFmpeg method in comments.
youtube.com

The other classic mosh. Instead of removing I-frames, I duplicated one P-frame's motion over and over so the same motion vector blooms outward forever. One pushed-in frame becomes an endless unfolding. FFmpeg method in comments.

214 points · 7 comments

Comments

  • @jameslee_digital · · 53 points

    bloom mosh is the prettier sibling of the delete mosh and underused. the same motion compounding forever turns any clip into a kaleidoscope that remembers where it came from. the source image is still vaguely THERE under the bloom.

  • @sashapark_creates · · 36 points

    the ghost of the source surviving under the bloom is what makes it melancholy instead of just abstract. you can feel the original moment being stretched past its death.

  • @irishoffmannmedia · · 31 points

    200 duplications is restrained, i've gone to 1000 and it turns into pure liquid light, no source left at all. there's a sweet spot around where you can still half-read the image

  • @jamesmiller_vfx3079 · · 24 points

    the sweet spot is everything. too few and it's just a smear, too many and it's abstract soup. the magic is right where recognition breaks down but hasn't vanished.

  • @avacosta_fx · · 18 points

    for the ffmpeg-averse is there a comfy node that does bloom mosh now or is it still a manual hex job

  • @jasminesharma554 · · 20 points

    still mostly manual if you want control. there are some nodes that approximate it but the hand-done version has a quality the automated ones flatten out.