A video can be entirely i-frames but the file size is much larger than setting an i-frame every 10 or 20 frames and making the rest p-frames. I-frames (aka key frames) give a full frame’s worth of information while p-frames are used to calculate the difference from frame to frame and avoid storing lots of redundant frame information. There are 2 types of frames that we’re dealing with: i-frames and p-frames. What’s happening in the Python datamosh tool is that first the video file is converted to AVI format which is glitch friendly as it sort-of doesn’t care if you delete frames from the middle willy-nilly (mp4 gets real mad if you delete stuff in a video file). We datamosh because we can, and because it looks really cool. In plain English, datamoshing is an umbrella term for an array of cool effects you get by glitching, altering, or otherwise breaking the fundamental structure of video files’ data. There’s no decent datamoshing addon written yet, and I think this could be interesting for a lot of people in the oF community.

The Python tool already needs some maintenance (found some broken stuff), and I thought it would be a nice exercise (C++, Python) to refactor the “ you-can-datamosh-on-linux ” as an openFrameworks addon. The Python script also has the algorithm to edit i-frames and p-frames.

Ffmpeg is used for the video format conversion. It is basically a Python script that wraps around the famous ffmpeg, a vast software tool suite of libraries and programs for handling video, audio, and other multimedia files and streams. I could only find one single datamoshing tool that is able to run on Linux: I was reading about datamoshing and fell in love with it.

Datamoshing video processing