3 ms·
I was always interested in glitching images - but was frustrated with the checksum/read errors. I took a slightly different approach with JPGCrunk (http://www.m
by mrspeaker 11y ago
I was always interested in glitching images - but was frustrated with the checksum/read errors. I took a slightly different approach with JPGCrunk (http://www.mrspeaker.net/dev/jpgcrunk/ http://www.mrspeaker.net/dev/jpgcrunk/): instead of modifying the image then trying to display it, randomly mess with the internals of the encoder (I used a JavaScript implementation so it was easy to modify https://github.com/mrspeaker/jpgcrunk/blob/master/scripts/enc.js#L548 https://github.com/mrspeaker/jpgcrunk/blob/master/scripts/en...)
This way the "glitching" happens inside the encoder algorithm, and then there's nothing to have to repair!
- nosuchthing 11y agoWhoa, cool. Reminds me a bit of a video codec technique to exaggerate the motion frames and compression ala "datamoshing". Keyframes are removed which leaves only information from the previous frame to be updated by motion frames. Than update/motion frames are reiterated sequentially which creates an effect that just further saturates the previous frame and looks like a fluid melting effect. in use: https://www.youtube.com/watch?v=mvqakws0CeU https://www.youtube.com/watch?v=mvqakws0CeU how to via ffpmeg: https://www.youtube.com/watch?v=tYytVzbPky8 https://www.youtube.com/watch?v=tYytVzbPky8
- Vexs 11y agoGah, that just makes me unconformable on so many levels. It's not helped by the content of the video either...
- provemewrong 11y agoNice, very appropriate design for the web app!