December 25, 2012
360 of 366
Processing + JPGs
After meeting Ted Davis (FFD8) and attending his panel with Paul Hertz at Gli.tc/h in Chicago earlier this month, I decided that I should get over my personal aversion to programming.
Using Processing, I’ve written a primitive (and probably poorly structured) program that will enable me to go through a file byte by byte and sequentially change the value of a particular byte.
The GIF above started as a JPG.  By stepping byte number 0xC4 (or the 196th byte in the file) through values 128 through 220, the alignment of the image raster was thrown askew.
Writing a program to proceduralize the restructuring of data doesn’t seem antithetical to the glitch ethos.  Though, somehow there’s a line that is crossed once that code becomes packaged and sold, used only for a particular effect, rather than extended further.  At that point, the process seems little different from the ritualized produce/consume (prosume) paradigm established by large “productivity” software firms.  For me, anyways, glitch has been about skirting the usual channels of productivity.  Creating your own tools is part of that.
Processing code

360 of 366

Processing + JPGs

After meeting Ted Davis (FFD8) and attending his panel with Paul Hertz at Gli.tc/h in Chicago earlier this month, I decided that I should get over my personal aversion to programming.

Using Processing, I’ve written a primitive (and probably poorly structured) program that will enable me to go through a file byte by byte and sequentially change the value of a particular byte.

The GIF above started as a JPG. By stepping byte number 0xC4 (or the 196th byte in the file) through values 128 through 220, the alignment of the image raster was thrown askew.

Writing a program to proceduralize the restructuring of data doesn’t seem antithetical to the glitch ethos. Though, somehow there’s a line that is crossed once that code becomes packaged and sold, used only for a particular effect, rather than extended further. At that point, the process seems little different from the ritualized produce/consume (prosume) paradigm established by large “productivity” software firms. For me, anyways, glitch has been about skirting the usual channels of productivity. Creating your own tools is part of that.

Processing code

  1. 3zvm reblogged this from yearoftheglitch
  2. hazeandnostalgia reblogged this from yearoftheglitch and added:
    This was posted on my birthday. I’ll consider that a gift. Thanks!
  3. tocahontass reblogged this from swedishgreyhound
  4. swedishgreyhound reblogged this from yearoftheglitch
  5. goodtimesbadfriends reblogged this from tsarcasm
  6. magicalhawkgirl reblogged this from tsarcasm
  7. stop-laughing reblogged this from tsarcasm
  8. spreadyourwingson1-2-3 reblogged this from tsarcasm
  9. tsarcasm reblogged this from yearoftheglitch
  10. hirosheena reblogged this from yearoftheglitch
  11. spreadingthebeautiful reblogged this from yearoftheglitch
  12. mainshore reblogged this from glitchgifs
  13. keifer1231 reblogged this from yearoftheglitch
  14. juandmarin reblogged this from yearoftheglitch
  15. o7o52674863 reblogged this from glitchgifs
  16. ravelite reblogged this from yearoftheglitch
  17. love-dreams- reblogged this from yearoftheglitch
  18. honeylocks-fuzzysocks reblogged this from yearoftheglitch
  19. patriotrolanzo reblogged this from glitchgifs