.GLITCH

Page 1

3


.GLITCH was a project formed in 2014 by photographer and graphic artist Patrick McPeak. Going by the alias _dotty_, he produced, wrote, designed, printed and published this book under this guise. This was his exploration into the world of databending.

Copyright Š 2014 by Rich Kid Records Publishing Co. All rights reserved under International and Pan-American Copyright Conventions. No part of this book may be reproduced in any form or by any electronic or mechanical means, including information storage and retreival systems, without permission in writing from the publisher. Artwork by Patrick McPeak Publication design by Patrick McPeak Edited by Marissa Nicole Pina and Danielle Parsons Text composition by Patrick McPeak and John McCabe Digital transcription by Patrick McPeak Hosted on www.issuu.com Printed in the United States of America by Fireball Printing 3237 Amber St Box 3 Floor 5, Philadelphia, PA 19134




For my mother.



WARNING The presentation of .GLITCH may be unpleasant to look at for long periods of time. For the best experience, the producers recommend short breaks while viewing the art in these pages. The effects applied in this book may be more unpleasant for those who do not have binocular vision. If you would like to contact Rich Kid Records Publishing Company for an ADA compliant copy, we will gladly provide you with one.


10

.GLITCH


TABLE OF CONTENTS Introduction

15

History

19

Databending

31

Pixel-Sorting

45

Color Shifting

63

Television Encryption

77

Appendix

89

Credits

93


12

.GLITCH


13


14


by software engineer John McCabe Most people think that computers are magic. I know they are. I have been studying computer science since 2006. I chose to take “Intro to Programming” instead of an extra free period in high school. I now deal with computer glitches on a daily basis as a professional Software Engineer focusing on Quality Assurance for mobile phone software. My job is to find the glitches and to help fix them for users. One of the first glitches I can remember is a famous glitch found on many versions of Microsoft Windows. As many of you probably remember, Windows would occasionally stop responding to user input. This could occur at the operating system level or just to certain applications. Aside from being very frustrating and counterproductive, the resulting glitch was actually somewhat beautiful. If you dragged your unresponsive program window around the

desktop, it would leave a trail of duplicate windows, as if it were inspired by the solitaire victory animation. This type of glitch, although interesting to look at, did little more than annoy me. For the more entertaining glitches, you have only to look at the world of video games. The most lucrative glitch from my childhood had to be the Missing No. glitch from Pokemon Red and Blue. This glitch required the player to follow an intricate set of steps leading them across the entire game world, but ending with them walking back and forth (swimming actually) on a small patch of land. The player must encounter a rare wild pokemon called Missing No. This pokemon didn’t look anything like any other pokemon, not even the shapeshifting Pokémon, Ditto could look this strange. Missing No. was a black rectangle of scrambled pixels and patterns. If the player defeated

Missing No. the game would award them 99 of whatever item was in the 6th spot of their item list. The most popular item to duplicate was the rare candy, which increases a pokemon’s level by one. Once the player had a near limitless supply of rare candies they could go on beating the game with relative ease. If the player managed to catch Missing No. during the battle stranger things would happen. The game would glitch in small ways at first, from graphics glitches to garbled text. Things could eventually get as bad as losing your saved game or even worse yet, causing the game to become unstable and unplayable. My favorite childhood video game is Halo: Combat Evolved. Halo and its sequels are full of glitches. The physics engine in the first Halo was extremely sensitive to vehicle collisions. Ramming two Warthogs together at full speed would send both players flying across the map. 15


This could be leveraged to escape the intended area of play. Players could get ‘out of the map’. There wasn’t much to do outside the map, after all the game designers intended for you to stay in the area of play. Mainly players attempted this just for street cred. This type of glitching may have contributed to a new emerging art form, Machinima. A company of video game enthusiasts and filmmakers called Rooster Teeth Productions descended upon Halo to create “Red vs. Blue The Blood Gulch Chronichles”. Blood Gulch being a multiplayer map in the game where the show takes place. Linking up to 4 Xbox consoles together and creating a multiplayer game, Rooster Teeth controlled the in-game players like marionettes acting out a script. The show was a parody of first person shooters, military life, and science fiction. Rooster Teeth also utilized a glitch where in which players looking at the ground would have their in-game avatars lower their gun while still looking straight ahead. Combining this glitch with small

16

vertical movements allowed them to make the helmet wearing supersoldiers appear as if they were chatting, making the show seem that much more real. Of course all glitches are not as fortitous to the user as these two examples. A few years ago, I had the opportunity to work on an Xbox 360 title “Kinect Disneyland Adventures”. During the early stages of development, when the art assets were still work in progress, glitches could be found in almost every character interaction. The game was based around walking through a 3D replica of Disneyland and meeting all of the players favorite Disney characters. One of my favorite glitches from this game occured when the player talked with Snow White. Players could hug, high 5 and dance with each of the Disney characters who would perform unique animations for each of these interactions. When the player gave Snow White a high 5, everything was normal. When the player hugged her, the animation was smooth and bug free. When the player tried to dance with

.GLITCH

her, Snow White’s face would begin to animate, and then become impossibly distorted. Her face twisted inward on itself and then out the back of her head to infinity. With the rest of her body animating correctly, I found this glitch to be very humurous. Of course, as a Quality Assurance engineer on the project, it was my responsibility to find these glitches and tell the animators. Luckily for the game studio and the consumers, this glitch was fixed well before the game was released to the public. Computers are designed to do(compute) exactly what you tell them to. Sometimes you can mistakenly tell them to do the wrong thing. In the case of the Snow White glitch, the issue was an invalid coordinate. A portion of Snow White’s face was attempting to translate to a point that did not exist. The computer interpreted this invalid point as infinity, and so off her jaw went. As computers and software become more and more complex, there is more room for error at every level.


17


A A A A A A A A M A M A M A M A M A M A A MO M AMO MO A MO A A MO A MOD A MOD A MOD AMODE MOD A MOD A MODE A MOD MODE A AMODER MODE A MODE A MODE A AMODER MODER A MODER A MODER A MODERN A MODERN A MODERN A MODERN A MODERN AMODERN MODERNH A MODERN A MODERN A A MODERN H A MODERN H A MODERN H AMODERN MODERNHIS H A MODERN H HI A MODERN HI A MODERN HI A AMODERN MODERNHIST HIS A MODERN HIS A HIS AMODERN MODERNHISTO A MODERN HIST A MODERN HIST A HIST AMODERN MODERNHISTO A MODERN HISTO A MODERN HISTO A MODERN HISTO A HISTO AMODERN MODERNHISTOR HISTOR A MODERN HISTOR A A MODERN HISTOR HISTOR A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY A MODERN HISTORY O A MODERN HISTORY O A MODERN HISTORY O A MODERN MODERN HISTORY HISTORY O O A


A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES AMODERN MODERNHISTORY HISTORYOF OFGLITCHES GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES AMODERN MODERNHISTORY HISTORYOF OFGLITCHES GLITCHES A MODERN HISTORY OF GLITCHES A MODERN HISTORY OF GLITCHES A MODERNHISTORY HISTORYOF OFGLITCHES GLITCHES MODERN HISTORY OF GLITCHES MODERN HISTORY OF GLITCHES MODERN MODERN HISTORY OF GLITCHES MODERN HISTORY OF GLITCHES HISTORY OF GLITCHES MODERN HISTORY OF GLITCHES ODERN HISTORY OF GLITCHES MODERN ODERNHISTORY HISTORYOF OFGLITCHES GLITCHES ODERN HISTORY OF GLITCHES ODERN ODERN HISTORY OF GLITCHES DERN HISTORY OF GLITCHES DERN HISTORY OF GLITCHES DERN HISTORY OF GLITCHES DERN HISTORYOF OFGLITCHES GLITCHES DERN HISTORY OF GLITCHES ERN HISTORY OF GLITCHES DERN HISTORY OF GLITCHES ERN ERN HISTORY ERN HISTORYOF OFGLITCHES GLITCHES ERN HISTORY OF GLITCHES ERN HISTORY OF GLITCHES RN HISTORY RN HISTORY OF GLITCHES RN HISTORY OF GLITCHES RN HISTORY OF GLITCHES RN N HISTORY OF GLITCHES N HISTORY OF GLITCHES N HISTORY OF GLITCHES N HISTORY OF GLITCHES N HISTORY OF GLITCHES NHISTORY HISTORYOF OFGLITCHES GLITCHES N HISTORY OF GLITCHES HISTORY OF GLITCHES HISTORY OF GLITCHES HISTORY OF GLITCHES HISTORY OF GLITCHES HISTORY OFGLITCHES GLITCHES HISTORY OF GLITCHES ISTORY OF GLITCHES ISTORY ISTORY OF GLITCHES STORY OF STORY OF GLITCHES STORY OF GLITCHES STORY OF GLITCHES TORY OFGLITCHES GLITCHES TORY OF GLITCHES TORY OF GLITCHES TORY OF ORY OF GLITCHES ORY OF GLITCHES ORY OF GLITCHES ORY OF GLITCHES ORY OF GLITCHES ORY RYOF OFGLITCHES GLITCHES RY OF GLITCHES RY RY OF GLITCHES RY OF GLITCHES Y OF GLITCHES YOF OFGLITCHES GLITCHES Y OF GLITCHES OF GLITCHES Y OF GLITCHES OF GLITCHES OF GLITCHES OF GLITCHES OF GLITCHES GLITCHES OF

19


Into the void

20

.GLITCH


entemology Glitches are something that are sometimes hard to find historical information of. The definition of a glitch is an unexpected and usually minor problem; especially : a minor problem with a machine or device (such as a computer). As with most small problems, they tend to be erased from history over time in favor for more victorious endeavors. With ENIAC (Electronic Numerical Integrator And Computer) standing as genesis of the computer age, technology advanced as quickly as humans could figure out how to implement it in their endeavors. The computer made everyday tasks automated. This also helped our race reach for the stars with the dawn of our space program, NASA. Although computers launched us into outer space, they did not accomplish it without glitches. The term was brought into the English language around 1960. It is unclear from which language it originally originated from but the two most likely examples are glitsh from Yiddish meaning slippery or giltschen from German meaning to slip or slide. Although there had been communication errors between individuals before, the dawn of the digital age needed a new term to describe uncontrollable errors in computing. This term would become something that more and more humans would become familiar with through the sixties. Not only were glitches temporary, as long as humans are going to interact with anything with a computer in it, glitches are going to be a part of our lives.

HISTORY

21


THE MOST EXPENSIVE HYPHEN IN HISTORY

The first major disaster caused by a computer glitch recorded in human history happened on July 28, 1962 with the launch of Mariner I, a interplanetary space probe. Initially planned to make a fly-by of Venus to measure temperatures and radiation off of our neighboring planet, a fault in the guidance system made controlling the flight path impossible. With a destructive crash in a major North Atlantic shipping lane possible, Mariner I was destroyed by the range safety officer with a remote detonation device onboard the spacecraft 293 seconds after liftoff. A misplaced hyphen in the source code of the launch program became history. Mariner I was the first time significant human progress was halted by a computer’s inability to process human errors. Although Mariner I was our first computerized endeavor into the great beyond, computers in 1962 were not as sophisticated as the computer we have come to know today. Instead of storing computer code in files on hard drives wired directly into the computer’s motherboard, computers in the 1960s read “code” off of paper cards. Small holes were punched out of the numbered cards which was translated into an language that a computer could read. Programmers today have it easy. They make in error in a computer code and many programs are now smart enough to tell them instantly that the code

22

won’t run properly. Programmers in the 1960s did not have the luxury of these sophisticated programs or even a computer screen to look at the code in it’s entirety. The Mariner I “program” was written on these punch cards, an error on one of them would cause the mission to fail completely Launch day was set for July 28th, in Cape Canaveral Florida. The mission was officially launched at 09:21:23 UTC and around three minutes after launch, mission control noticed a problem. An unscheduled yaw-lift maneuver was detected by a range safety officer, the Atlas LV-3 rocket that was propelling the space probe into orbit was off-course. The safety officer made the call to detonate Mariner I four minutes and 53 seconds after lift-off. Mariner I failed to make orbit. Mariner I had pages of punch cards to drive it into outer space. Although most of them were punched perfect, one character caused it’s downfall. What initially happened to the celestial-bound spacecraft was that a failure of an on-board guidance antenna had caused the craft to rely on a back up radar driven system. The radar system should have been able to guide the space craft onward towards Venus but there was a fatal flaw in the system. The fatal error came in the form of a hyphen. In the source code, there were several parameters built into the craft’s guidance

.GLITCH

system. Mainly equations that would help guide the ship into space. One overlooked character in the guidance system was a hyphen instead of an over-bar, confusing the computer with ensuing years instead of ignoring the input, which is what an over-bar is used for. Once the system was unable to tell what the code meant, the rocket made an unexpected move. After it’s detonation, Mariner I became one of the most expensive software glitches in history. It’s been 52 years and the disaster still holds the record. In 1962 it cost NASA and the federal government $18.5 million. In today’s dollars, that is more than $135 million. NASA would finally complete the original mission a month later with the launch of Mariner II. Mariner II was launched August 27th, 1962 and made it’s closest pass by Venus on December 14th, 1962. The mission that was halted by a hyphen was finally a success. Mariner I may have been the dawn of computer problems in our society but it was no where near the end. Computers evolved rapidly but the inherent problem with them is that there are human parts in the computer making machine. No matter how advanced our computer systems may get, we will always encounter glitches. Hopefully, we will never encounter one as expensive as the first one was.


Mariner 1

HISTORY

23


The Y2K Bug

24

.GLITCH


A fear in Uncharted Territory By the end of the year in 1999, computers had become incredibly widespread in the global environment. As many were getting ready to welcome a new year around the world, many were fearing a complete crash of every computer based system in the known world. There were a few concerns that raised the apocalyptic thoughts but many of them had to do with the basic program of computers since the punch card programming days. Although a crisis ended up being just a fleeting concern once the ball dropped, there were many on the edge of their seat as we welcomed in the year 2000. With computing advancing swiftly since the 1950s, computers had gone far beyond simple calculators. They were used to control infrastructure, connect dignitaries through email and even track the stock markets. One of the data points that was crucial in processing all of these records was the date they happened. Originally when computing was done with

punch cards only the last two digits of the year were input. Years like 1984 and 1996 were input as 84 and 96 respectively. With a new millennium only a few months away, programmers began to worry that computers, a child of the second millennium would not be able to process the change in date to 2000 from 1999. With fears of computational confusion would cause the world’s collective clocks to be set back to the year 1900, the problem actually started to get fixed years before the year 2000. Even though the world was a buzz with how Y2K might affect them, the problem had been dealt with long before the ball was even set up in Times Square. Programmers around the world went into action to correct the issue. Just a simple update brought the ability to read four digit dates. After the crisis was averted. In 1997, the British Standards Institute released a new standard of dated events for

HISTORY

all future computers. This list would prevent future confusion. 1. No valid date will cause any interruption in operations. 2. Calculation of durations between, or the sequence of, pairs of dates will be correct whether any dates are in different centuries. 3. In all interfaces and in all storage, the century must be unambiguous, either specified, or calculable by algorithm 4. Year 2000 must be recognized as a leap year The crisis had been averted and the computers made the change over without many problems. There were a few computers that had trouble processing the change but these set backs were minor. January 1st, 2000 was another day for many and silenced many of the doom-sayers.

25


THE FALADOR MASSACRE With the dawn of the Internet bringing human interaction through computers possible it was only a matter of time before video gaming became global. The technology of the fax machine allowed basic online gaming to occur from two different places at once. The first game to use the new technology of the Internet was a game called Maze Wars, developed by Steve Colley in 1974. The game ran on the Imlac PDS-1, which was one of the first computers to offer machine-to-machine connection. Maze Wars developed many concepts which are now fundamentals in online gaming, “first-person shooter” perspective, avatars and the most important peer-to-peer combat. These archetypes would evolve quickly as players became more excited about online gaming. They would evolve from two player games into massively multiplayer platforms supporting millions of gamers all playing at the same time. Online video games in the early 1990s were far-fetched from the hyper-realistic games that plays have come to know and love through today’s world of online gaming. Many of them were text-based and in order to play, players would have to input text commands into a console display to move, open doors, cast spells and use items. The first time any developer came close to the modern experience was in 1991 was Stormfront Studios with 26

their interpretation of the popular board game Dungeons & Dragons. The game was called Neverwinter Nights and it ran through AOL’s servers. AOL being a pay service, the game was incredibly expensive to play, costing users about $6 USD for a day of play. Although this was the first attempt to bring a massive online community to the world, this would not be perfected until Sony developed the open-world gaming community of Everquest in 1999. Once Everquest had reached the masses, there were plenty of other massive multiplayer online roleplaying games (MMORGPs) to follow. One of those to follow was Runescape out of Jagex Game Studios in 2001. Runescape was a similar formula to many MMORPGs but involved a certain amount of item gathering, quest completion and monster hunting. The game was well received and still has a large community of supporting players, moderators and developers to the present day. The game was also the host for one of the most destructive gaming glitches of all time, named for the region of the game that it took place in, the Falador Massacre. Runescape was always about player interaction and featured many sections of in-game maps where players could engaged in combat with one another. These sections of the map were known as player vs player arenas or PvP for short. Players

.GLITCH

could use weapons, spells and items to increase their chances of winning battles but battles would only happen inside designated areas. On June 6th, 2003, the Runescape team introduced an update to the game mechanics with a player skill called construction. Construction was a skill that let player’s characters build their very own house for their character in the game. A player by the name of Cursed You was the first of the community to reach the highest level, 99, in Construction. Cursed You was about to become the “Al Capone” of the Falador Massacre. When players invited other players over to their in-game house, players could exploit a bug in the new updated version of Runescape. When any play initiated combat inside a house, they were instantly “booted” from that part of the map. They would return in the game to the place where they entered the house, usually an area where combat was not allowed by the rules of the game. After players were booted from Cursed You’s house party, they were able to retain the ability to initiate combat anywhere in the map. This allowed players to effectively slaughter players in the region of the game called Falador and steal their items and in-game coins, which were purchased with real-life currency. This glitch was exploited by hundreds of players and the walls of the town of Falador were splashed red with digital blood.


A SLAUGHTERING IN THE ONLINE WORLD OF RUNESCAPE Although the game was quickly fixed and the glitch repaired, the massacre continued on for more than an hour. One of the most ruthless players, Durial321, had already been at an extremely high level before he rampaged through the Runescape world for more than an hour killing off as many lower-level players as he could. He equipped one of the most pointless items in the game, a green party hat, which he looted from a lower-level player to add insult to injury. Overall, the glitch cost Runescape players at least 2 billion in coins, 200 billion in 2013 inflation. There is no official record for all of the losses in game but the fallout was real. Many players did not return to the world after this hour of chaos. The bug was eventually fixed by Jagex Game Studios and many of the offending players were indefinitely banned from ever joining the world they created so much chaos in. Construction still remains a skill in Runescape today but the glitch has been patched. There have been a few more scares of glitches like the Falador Massacre but none have been even close to how destructive the original was. Many players who survived the massacre still play on but attack enemy characters with party hats. Jagex still supports the community but the massacre still lives on in infamy.

HISTORY

27





DATABENDING DATABENDING DATABENDING DATABENDING DATABENDING


32

.GLITCH


DATABENDING DATABENDING DATABENDING Welcome to the world of glitch art. When it comes to the history of the craft, databending stands as genesis. Most budding glitch artists find their way into the genre by accident. An image file opens wrong, crashes upon loading into their photo editing software, a drive gets corrupted or they seek out the art form on purpose. Most artists start here. The process of databending is exactly how it sounds; modifying the raw data that tells the computer the certain file in question is an image file. Once a file is opened wrong, anything can happen to the final output that ends up on the screen. This is the most basic form of glitch art but sometimes it can be the most impressive. Wordpad, Audacity, Microsoft Word. Many computer users are very familiar with these programs. Two for editing word documents and another for editing audio. The genius behind these programs is that they were specifically designed to open files like .doc, .mp3, .txt and make editing them easy for everyone to do. Once the text file is opened, the software places a bunch of code into the source for the file making the text that is displayed neat and organized for the user. What happens if we force one of these programs into opening an image file? The basis behind databending is forcing an image file to open in a program

that was not designed to open image files. With most of my personal pieces, this is done with Audacity. The Audacity designers knew that audio files come in a range of different formats. Some recording equipment spits out its own file types that can’t be read without advanced software. Not only will the program take just audio files, users can upload images files as raw data and perform the same edits that a sound technician would on an audio file.

This process drastically alters the final image file that is spit out of the program in a raw format. Along with all of these modifications comes some gentle coercing to dedicated photo editing software. Once the image file is finally opened in a photo editing software, users may be

DATABENDING DATABENDING

surprised by the results. If they have ever worked with sound before, they may notice some familiar effects. When effects like delay and echo are applied to the raw data in Audacity, the image file will have the repeating effect just like an echo would have on audio. A low pass filter would limit some of the higher light frequencies. Just like sound can be manipulated, photos can be changed just the same way. As with most raw photographs, the raw outputs from Audacity or Wordpad might take some adjustments to finally get them in shape to display. Bumping the exposure and adding a few photo filters on them might make the photo a little easier for viewers to decipher. Since Audacity tends to degrade the quality, users may want to bump up the resolution. There are no rules when databending. That’s the point of it, break the rules set out by the software developers and change what you want. The computer is only there to help you achieve your process of creating art work with it. Databending requires a lot of will power. Things are going to get messy. The rules and this short guide are only mere suggestions. Remember, when the glitching gets tough, the glitchers keep glitching.

33


1 34

.GLITCH


2 DATABENDING DATABENDING

35


3 36

.GLITCH


4 DATABENDING DATABENDING

37


5 38

.GLITCH


6 DATABENDING DATABENDING

39


7 40

.GLITCH


8 DATABENDING DATABENDING

41


9 42

.GLITCH


10 DATABENDING DATABENDING

43


44

.GLITCH


PIXELSORTING


46

.GLITCH


PIXELSORTING PIXELSORTING There is no doubt we live in a computerized world. We wake up thanks to an application built into the super computers we carry around constantly. We check the news on an 11 inch piece of glass with another super computer built into it. Our cars even connect to both of these super computers so we don’t have to spend a second away from our connections, social and professional. Even the modern day camera has become a super computer that just so happen to take radiation and turn it into a digital image of something we focus on. All of this computing is processed into digital bites our computer can display. These digital bites are called pixels. All modern digital photographs are made of pixels. These are the tiny little data points inside the image file that display a certain color that is recorded by the camera’s photo sensor when focused light is cast onto it by the opening shutter. The amount of pixels varies between camera models. These are usually rated in megapixels. Most consumer digital cameras output raw image files with more than 12 million pixels in them. With the tool of pixelsorting, artists can manipulate where the image files places these million pixels in the image file. Overall, pixelsorting is a pretty

complicated process but it can all be done with some basic computer programming skills. The modern computer can interpret

many different languages. Just like humans communicate using English, Portuguese or Russian, computers also complete tasks with different languages. Some of these include C++, Java, Ruby and Python. Each language has its benefits but most of

them are capable of doing the same thing. They just need to be told what to do. Pixelsorting is a program written in a computer language to sort the pixels of an image file into respective position typically based on three different values. The program, which I wrote in Java, sorts the pixels in an image based on their white values, black values or brightness values. When the program finds a pixel with a white value (for example), it will take the surrounding pixels with similar white values and organize them on the intensity of that value with completely white pixels going all the way to the right of the image file. This can create some spectacular results. Just armed with a basic knowledge of programming or access to a pixelsorting program on websites like GitHub, artists can start sorting the pixels that their camera creates for them. The images that some of these programs can spit out almost look like God’s computer has taken a day off, rendering once soft and smooth landscapes completely jagged and smeared. It can turn a friendly face into something incredibly demonic looking. It is all a matter of persistence. Whatever comes out on the other side of the program is always going to be something that you’ll never be able to predict.

47


11 48

.GLITCH


12 PIXELSORTING

49


13

50

.GLITCH


14

PIXELSORTING

51


15 52

.GLITCH


16 PIXELSORTING

53


17 54

.GLITCH


18 PIXELSORTING

55


19 56

.GLITCH


20 PIXELSORTING

57


21 58

.GLITCH


22 PIXELSORTING

59


23 60

.GLITCH


24 PIXELSORTING

61



COLORSHIFTING COLORSHIFTING


64

.GLITCH


COLORSHIFTING Photography is the transmission of light onto photosensitive materials. The most basic forms of photography can be accomplished with nothing more than

an oatmeal can, a pinhole and a piece of light sensitive paper. As technology developed, photographers were able to capture images in color. As technology went even further, photographers were able to produce digital files that were in full color. The way this technology works is exactly how colorshifting is exploited. Modern digital cameras record three frequencies of light. Each photo diode in a digital photo sensor can read the intensity of three colors. These colors are the primary colors red, green and blue. The different intensities of these colors are recorded by the photo diode

and combined into a composite image. Colorshifting takes these values and places them on different layers and in different places on an image. Once the layers are separated, users have the freedom to move them around. They can split the red layer from the blue and green layers to create what looks like a three dimensional image if viewed with red and cyan tinted glasses. If all three layers are shifted independently, it can create a surreal three-dimensional effect. This shifting of layers can be accomplished in many different ways. In the year 1990, Adobe launched a program that would revolutionize the world of digital image file editing, Photoshop. Since Photoshop has grown into one of the most powerful image processing software, shifting color layers can easily be accomplished with it. Users can also choose which color layers they want to shift by either keeping the colors in additive mode (RGB) or subtractive (CYMK). A combination of both creates an even more glitch-like look. As long as Photoshop keeps improving their photo editing software, users are going to have more and more control over what their final product is

COLORSHIFTING COLORSHIFTING

going to look like. Images keep getting sharper, artists have more control over color-casts and exposure; even objects can be completely removed from a photograph without any trace. The more features that Adobe places into their

program, the more that users are going to change their raw photographs.

65


25 66

.GLITCH


26 COLORSHIFTING COLORSHIFTING

67


27 68

.GLITCH


28 COLORSHIFTING COLORSHIFTING

69


29 70

.GLITCH


30 COLORSHIFTING COLORSHIFTING

71


31 72

.GLITCH


32 COLORSHIFTING COLORSHIFTING

73


33 74

.GLITCH


34 COLORSHIFTING COLORSHIFTING

75





TELEVISION ENCRYPTION Television encryption was invented to solve a problem. With the dawn of premium subscription based television channels, many customers did not pay for channels such as HBO and Cinemax. These customers were still able to access the premium content presented on this channels. Since premium channels did not want to simply give out the content for free so they added in interfering video signals and audio channels. This resulted in a “scrambled” broadcast until the cable provider approved the signal. One of the first weapons that cable providers had against television piracy was a scrambling device called the VideoCipher I. The VideoCipher I encrypted video signals being sent over the air. Once this device was implemented, standard cable subscribers could only access the channels they paid for. To decrypt the signal, cable providers would simply have to deactivate the VideoCipher for the customer’s account. Along with the progression of broadcast technology came the progression of encryption. General Instruments, the makers of the VideoCipher upgraded the VideoCipher IB to the VideoCipher II-RS+, currently the most secure way to encrypt an analogue broadcast signal.

After the mid-90’s, many cable providers moved to more digital methods to provide cable to subscribers. This brought the dawn of the in-home set-top box. Providers like Comcast, were able to limit the channels that subscribers accessed by limiting them remotely from the set top box. Along with this technology came the death of standard video encryption. Anyone who grew up the late 80’s and early 90’s, before television signals updated to digital, tuning to the premium channels was an interesting experience. A jumbled mess of colors and images would come through along with a somewhat clear audio broadcast. This inspired many teenagers at the time to stay up late and see what HBO would be playing after dark. This phenomenon carries a lot of nostalgia for those who grew up in those time periods. With the rise of new technology, VideoCipher devices have been increasingly easier to come by. Many dead-stock units can be bought at online retailers for around $100. The Internet makes sharing this technology even easier. Some computer programmers have created emulators that will scramble a video file which can then be converted into .gif format or simply used as still images. This is what I have done for my

TELEVISION ENCRYPTION

project. Using a modification to the app Snapchat in the current model Apple iPhone, I managed to use the trendy app to my advantage. I used user-submitted photos as raw material to run through the VideoCipher emulation program. The resulting images are as authentic to video

encryption that I could possibly achieve. Television Encryption may have died with the coming of the digital age but many young adults still have clear memories of what the technology did.

79


35 80

.GLITCH


36 TELEVISION ENCRYPTION

81


37 82

.GLITCH


38 TELEVISION ENCRYPTION

83


39 84

.GLITCH


40 TELEVISION ENCRYPTION

85


41 86

.GLITCH


42 TELEVISION ENCRYPTION

87



APPENDIX


ͦ͐̓ͯ ̉ ̾ ͠ ͥ̓̚ ̾̓ͤ ͤͪ̋ ͡ ͥ ͝ ͐̂ ̀ ͨ ̾̏͠ ͭ͒ ̽͊̋ͯ ̈ͦ̓ ͮ ́ ͝ ̾̄ ́ ́ ͆̋ ̐̾ ͛̽ ͨ ̔ͧͣͤ ̉ ̓̑ ̍̽ ͛͂ ͐ͨ͑̿ͬ ͞ ͐̊ ͡͞ ̊͑̍̓̑ ͩ ͪ̾̈͊̅ t͟ ͢ ̖ h̞͎͌ͩ​͎ ȋ̛̫͈͛ s͓͎̞̾ ̣ ̀ í͇̯͍̈ͤ̋ s̨̙̻͈̍ͥ a̮​̮̼ͤ ̀ ̀ ṗ̻͔̿ͨ ͘͡ě̾ ̎ͭ̚ ̞͙̦ ́ ̀ ̵r̸͉͈͍͐͗ s̙̠̥̈ͦ ́ o̯̥̻ n̵̜̺̯ ̸a͇͖̮̐ͫ l̨͚͔̱̾ ́ě̙̪̤ s҉̵̧ ͇̬̥͛̔ͧͣ s҉ ͮ̿ a͘͏̲̤̝ ̘̥͔ ỷ̷͜ ̙̺ ̡b͈̹̰͐ ỹ̸̺͓ͯ t̢͉̲̟̓̊̎͂̍ ĥ̛̹̈ͩ ͢ ́ ę̃ ̞̥ͮ͆ ͐t̖̓ͯ h̉ ͕̞ͦ̾͌ ͠i̛̫̝͚ͥ̓̑̚ s͓̓ͤ í͇͙ͤ​͙̻ͪ s̨͡ ͓̪̻ͥ̍ a͝ ̥͇̮̺͐̂ ṗ̿ ͘͡ě̏͠ ͒ ̖͎̞̯ ̀ ̵r̸͉͔ ̽͊̋ͯ͐ s̠̓ ͮ o͝ ̬̯̾̄ ́ ́ n̵͔̯͆̋ ̸a͓̩͇̤̐̾ l̨̻͚̹̯͛̽ ě̙̘ͨ s҉̵̧ ̲̗̖͇ͣͤ͛ ̉ s҉ ̓̑ ̟̼a͘͏̲͍ ͇͈̘̤̍̽ ỷ̷̥͇̦͛͂ ̡b͈̤̰̻ͨ͑̿ͬ ỹ̸͞ ̲͐̊ ͡͞t̢͉͑̓̑̎ ĥ̛̹ę̃ ̞̘͉̾ͪ̈͊ͮ͆̅ ͟ ͢ ͐ ̉ ͎ͩ​͎͕ͦ ͈̝͛ͥ ͎̞̾̓ ̣ ̀ ̯̭͍͙̈ͤ̋ ̬̙͓͈ͥ ̣ ̮̼̥̻ͤ ͅ ̀ ̀ ̻͔ͨ ̾̏ ̎ͭ̚ ͙̦̖ ́ͅ ͈͍͔ ̽͗ ̙̥̈ͦ ́ ̥̻̬ ́ ̜̺͔ ͖̮͓̹̐ͫ̐ ͔̱̻̾͛ ́ ̪̤̘ͨ ̭̬̩̥̲̔ͧͣ ͮ̿̓ ̙̤̝̟ ̥͔͇ ͜ ̙​̙̝̺͎̥͛ ̹̰̤͐ ̺͓̲ͯ͐ ̲̟̓̊͂̍̓ ̈ͩ ͢ ́ ̞̥̞̤͕̬ͪ̾ ̓t͟ ͢ ̖ͯ h̞͎̾͌ ͠i̛̫͈͚̓̑̚ s͓͎ͤ í͇̯͙̻̭ͪ̈ s̨͡ ̪̬̻͈ͥ̍ a͝ ͇̮͐​̮̺̻̂ ṗ̻̿ ͘͡ě͠ ͒ ͎̞̯͙ ͅ ̀ ̵r̸͉͈͊̋ͯ͐ s̠̥̓ ͮ o͝ ̯̥̾̄ ́ n̵̜̯͆̋ ̸a̩͇̤͖̹̐ͫ̾ l̨͚͔̹̯̽ ́ě̙̪ s҉̵̧ ̗̖͇̬̭ͣͤ͛ ̉ s҉ ̑̿ͮ ̙̼a͘͏̲̤͍ ͈̘̤̥̍̽ ỷ̷͜ ̙͇̦̝͂ ̡b͈̰̻̹ͨ̿͑ͬ ỹ̸͞ ̺̊ͯ ͡͞t̢͉̲͑̑̓̎ ĥ̛̹͢ ę̃ ̞̘͉̤̈͊ͮ͆̅ ͩ͐ ̉ ͎͕ ̝͚͛ͥ ̞̾̓ͤ ̣ ̀ ͍͙ͤ̋ ̙͓ͥ​ͥ ̣ ͝ ̼̥͇ͤ̂ ͅ ̀ ̀ ͔ͨ ̾̏ ̎ͭ̚ ̦̖ ́ ͍͔ ̽͗ ̙̈ͦ ́ ͝ ̻̬ ́ ̺͔ ̮͓̐ ̱̻̹̾͛ ̤̘ͨ ̥̩̲̗̔ͧͣ ̓ ̝̟̼ ͔͇̍ ̙̺͎̥͛ ̰̤͐ ͓̲͐ ̟̓̊͂̍̓ ̈ͩ ́ ̥̞͕̬̘ͪ ̓t͟ ͢ ̖ͯ h̞͎ͦ̾͌ ͠i̛̫͈̓̑̚ s͓͎ í͇̯͙̻̭ͪ s̨͡ ̪̬̻͈ a̮͐​̮̺̻ ṗ̻̿ ͘͡ě͠ ͒ ͎̯̞͙ ͅ ̀ ̵r̸͉͈͊̋ͯ s̠̥̓ ͮ o̯̥̾̄ ́ n̵̜̯͆̋ ̸a̩̤͇͖̹̾ l̨͚͔̯̽ ě̙̪ s҉̵̧ ̖͇̭̬ͣ͛ͤ ̉ s҉ ̑̿ ̙a͘͏̲̤͍ ͈̤̘̥̽ ỷ̷͜ ̙͇̦̝͂ ̡b͈̰̻̹̿͑ͨͬ ỹ̸͞ ̺̊ ͡͞t̢͉̲͑̑̓ ĥ̛̹͢ ę̃ ̞͉̤̾̈͊̅ ͎͐ ̉ ͦ ͕ͩ ̝͚͛ͥ ̞̾̓ ̣ ̀ ͤ ͍͙ͤ​͙̈̋ ̙͓̪̍ͥ ̣ ̼̥͇ͤ ͅ ̀ ̀ ͔ͨ ̎ͭ̾̏̚ ̦̖͎ ́ ͍͔ ͯ ̽͐͗ ̙̈ͦ ́ ̻̬ ́ ̺͔ ̮͓̩̐ͫ ̱̻̹̾͛ ́ ̤̘ͨ ͣ​ͣ ̩̥̲̗̔ͧ ͮ̓ ̝̟̼ ͔͇͈ ̙͎̺̥͇ ͨ ̰̤̰͐ ͓̲ͯ͐ ̓̊͑ ̟̎͂̍̓ ̈ͩ ́ ̾ ̥̞͕̬̘ͮ͆ͪ ̓t͟ ͯ͢ ̖ h͌ͩ ̞͎̾ ͠ȋ̛̚ ̫͈̓ s͓͎ͤ íͪ̈ ͇̯̻̭ s̨͡ ̍ͥ ̬̻͈ͥ ̣ a͝ ̮͐​̮̺̻̂ ̀ͅ ṗ̻̿ ͘͡ě͒͠ ̚ ̯̞͙ ͅ ̀ ̵r̸͉͈͐͗ ͊̋ s̠̥ͮ̓ o͝ ̯̥̾̄ ́ n̵̜̯͆̋ ̸a̐ͫ ̤͇͖̹̐̾ l̨̾ ͚͔̯̽ ́ ě̙̪ s҉̵̧ ͤ ̖̭͇̩̬͛ͣ ̉ s҉ ͮ ̑̿ ̙a͘͏̲̤͍ ̤̘̥̍̽ ỷ̷͜ ̙̦̝͎͛͂ ̡bͬ ͈̻̹͑̿ ỹ̸ͯ͞ ̺̊ ͡͞t̢̓̎͂ ͉̲̓̑ ĥ̛̈ ̹ ́͢ ̃ ę̈ͮ͆̅ ̞͉̤͕͊ ͎͐̓ ̉ ̾ ͕ͦ ͠ ͛ͥ ̝͚ ̾̓ͤ ̞ ̣̀ ͤ̋ ͍͙​͙ͤͪ ͡ ͥ ̙͓̪ ͝ ͤ̂ ̼̥͇ ̀ ͨ ͔ ̾̏͠ ̎ͭ ̦̖͎́ ͍͔ ̽͊ ͯ ̈ͦ ̙ ͮ ́ ͝ ̄ ̻̬ ́ ́ ̺͔͆ ̐ ̮͓̩ ͛̽ ̱̻̹ ͨ ̤̘ ̔ͧ ̥̲̗ͣ ̉ ̓̑ ̝̟̼ ̍ ͔͇͈ ̙̺̥͇͛͂ ͐͑̿ ̰̤̰ͨ ͞ ͐̊ ͓̲ ͡͞ ̍̓̑ ̟̊͑̓ ͩ ͪ ̥̞̬̘̾̈ t͢ ̖ ͯ h̞͎​͎ ͌ͩ i̛̫͈̓ ̑͛̚ s͓͎̞ ̣̾ ̀í͇̯͍ ̻̭̈ s̨̙̻͈ ̬̍ͥ ̣ a̮͐​̮̼ ̺̻ͤ ͅ ̀ ̀ṗ̻͔̿ ͨ ͘͡ě̾ ̞͙̦͒ ̯ ́̀ͅ ̵r̸͉͈͍̋ ͐͗ s̙̠̥̓ ̈ ́o̯̥̻̾ n̵̜̺̯̋ ̸a͇͖̮̾ ̤̹̐ͫ l̨͚͔̱ ̯̾ ě́ ̙̪̤ s҉̵̧ ͇̬̥͛ ̖̭̩ͤ̔ͧ s҉ ̿ ͮ a͘͏̲̤̝ ̙͍ ̘̥͔̽ ̤ ỷ̷͜ ̙̺ ̦̝͎ ̡b͈̹̰ ̻ͬ͐ ỹ̸̺͓ͯ t̢͉̲̟̎͂̍ ĥ̛̹̈ͩ͢ ́ ę̃ ̞̥͊ ͉̤͕ͮ͆̅ ͐t̖̓ h̉ ͕ ̞̾ ͠i̛̝͚ ̫ͥ̓ s͓̓ͤ í͙​͙̻ ͇ͤ̋ s̨͡ ͓̪̬ ̻ͥ ḁ͇̺͝ ̮͐̂ ṗ̿ ͘͡ě̏͠ ̖͎̯ ̞ ̀ ̵r̸͔ ͉ ̽͊̋ s̠ͦ̓ o̬͝ ̯̾̄ ́ ́ n̵͔ ̯͆̋ ̸a͓̩̤ ͇̐̾ l̨̻̹̯ ͚͛̽ ě̘̙ͨ s҉̵̧ ̲̗̖ ͇͛ s҉ ̓̑ ̟̼͍ a͘͏̲ ͇͈̤ ̘̍̽ ỷ̷̥͇̦ ̙͛͂ ̡b̤̰̻ ͈͑̿ ỹ̸̲͞ ͐̊ ͡͞t̢͉̓̑ ĥ̛̹ę̞̘͉ ̬ͪ͊ ͟ ͢ ͎ ͈ ͎ ̭ ̯ ͈ ̻ ̮ ̻ ͙ͅ ͈ ̥ ̥ ̜ ̹ ͖ ͔ ̪ ̭ ̬ ̿ ̙ ̤ ̥ ͜ ̝ ̙ ̹ ̺ ̲ ͢ ̤ ̞ I have always found glitches everyday. It’s not necessarily what I do for a living but with the way I look at the world a lot of things I encounter on a daily basis could be described as glitches. I’m not necessarily sure that we as humans have figure out how our reality actually operates but I’ve always believed that existing in a computer program wouldn’t be all too far-fetched. It would definitely be the most complicated computer program ever discovered but as we all know, life is quite complicated. Dealing with glitches only really makes our lives more confusing and difficult to work around but I’ve been dealing with glitches all my life. This year I turn 24 years old. I was born in 1990 in Springfield, Massachusetts. I was born in the era right before computers became a major part of our daily routines. Most of us didn’t have cell phones yet and my dad was beyond excited about his new pager could display two lines of text and a phone number to call back. I think it was 1995 when we finally bought our first IBM computer. It wasn’t until around 1998 until I first dialed up the Internet.

90

.GLITCH

The 90’s were severely strange times for the early Internet. I like to think of them as growing pains but basic HTML was hot and having a “girlfriend” from a chat room was talk of 5th grade class. It was later on that year that I would encounter my first glitch I could remember. For my 6th birthday, my dad took my brother and I to Best Buy to pick up my 6th birthday present. This was the big one; the Nintendo 64, the greatest gaming system known to man at the time. Not only did we pick up the gaming system but we managed to get two games that I still regard as some of my favorites. Super Mario 64 and Star Wars: Shadows of the Empire. Already being a big Star Wars fan, I instantly gravitated towards the space-themed shoot-em-up. Those first few weeks that I played that game, I consumed everything I could find about it on the very primitive Internet. I used all of the cheat codes, managed to find every hidden secret and then I managed to find what would be the first glitch I would ever find. The fact that you could pilot an AT-ST and you could glitch yourself beyond the virtual battlefield of Hoth.


̑ͬ ̓ͨ ̀ ̐ͧ ͞ ͬ͐ ͧ̚ ͬ̌͗ͮ ̀ ͐̓ ̉ ͦ̾ ͠ ͥ ̾̓ͤ ͤͪ̋ ͡ ͥ ͝ ̂ ̀ ͨ ̾̏͠ ͭ ̽͊ͯ ̈ͦ ͮ ́ ͝ ̄ ́ ́ ͆ ̐ ͛̽ ͨ ̔ͧͣ ̉ ̓̑ ęa̧̪̠̬̒͌̑ͬ ụ̭̬ṫ̢̧̖̘̗ ḩ͜ ̪̝ͮͧ o͜ ̞̪̬ r̢̲̗͇ ͯ̌̋ͮ ͏ t͟ ͢ ̖ͯ h̞͎͌ͩ​͎ͦ i̛̫͈̓̑͛̚ s͓͎̞̾ ̣ ̀ í͇̯͍̈ͤ̋ s̨̙̻͈̍ͥ a̮͐​̮̼ͤ ̀ ̀ ṗ̻͔̿ͨ ͘͡ě̾ ͒̎ͭ̚ ̞͙̦ ́ ̀ ̵r̸͉͈͍̋͐͗ s̙̠̥̈̓ͦ ́ o̯̥̻̾ n̵̜̺̯̋ ̸a͇͖̮̐ͫ̾ l̨͚͔̱̾ ́ě̙̪̤ s҉̵̧ ͇̬̥ͤ͛̔ͧͣ s҉ ͮ̿ a͘͏̲̤̝ ͥ ̽ ̐ ͬ ̟ ̝ ͛ ́ ̉ ͤ ͨ ͔ ͐ ͯ ͣ ̓ ̀ ̥ ͧ ̻ ̏ ̀ ̓ ̓ ̥ ͙ ͗ ͕ ͔ ͈ ̪ ̖ ̲ ͓ ͚ ̘ ͓ ̬ ͔ ͙ ̐ ̚ ̉ ͤ ͥ ͝ ͝ ͨ ͬ ̂ ͧ ͊ ̄ ͠ ͠ ͪ ͡ ̼ ͚ ́ ̾ ̽ ͞ ͓ ̗ ̑ ̫ ͮ ̓ ͆ ̹ ͇ ͐ ͙ ͎ ̩ ̩ ̜ ̪ ̻ ͤ ̋ ̚ ͒ ͮ ͯ ̓ ͣ ̒ ̋ ̋ ͐ ̾ ̾ ęa̧̪̠̬͌̑ͬ ụ̙̱̭̬ ṫ̢̧̖̘̗̺̪ ḩ͜ ̪̝ͧ o͜ ̞̼̪͔̬̗ r̢̙̲̪̗͇ ͯ̌ ͏ t͟ ͢ ̖ h̞͎͎͌ͩͦ i̛̫͈̓̑͛ s͓͎̞̾ ̣ ̀ í͇̯̻̭͍ͤ̈̋ s̨̬̙̻͈̍ͥ ̣ a̮​̮̼̺̻ͤ ͅ ̀ ̀ ṗ̻͔̿ͨ ͘͡ě̾ ̎ͭ̚ ̞̯͙̦ ́ͅ ̀ ̵r̸͉͈͍͐͗ͯ s̙̠̥̈ͦ ́ o̯̥̻ n̵̜̺̯ ̸a͇̤͖̮̹̐ͫ l̨͚͔̱̯̾ ́ě̙̪̤ s҉̵̧ ̖͇̭̬̩̥͛̔ͣͧ s҉ ͮ̿ ̙a͘͏̲̤̝͍ ͥ ̽ ̐ ̪ ͬ ̟ ̝ ͛ ́ ̉ ͤ ̉ ͮ ͨ ͔ ͐ ̓ ̥ ͧ ̻ ̏ ̀ ͪ ̓ ̓ ̥ ͙ ͗ ͕ ͔ ͈ ̪ ̖ ̲ ͓ ͚ ̘ ͓ ̬ ͔ ͮ ͙ ̐ ̬ ̀ ̚ ͤ ͥ ͝ ͝ ͨ ͬ ̂ ͧ ͊ ̄ ͠ ͠ ͡ ̼ ͤ ͚ ́ ̾ ̽ ̚ ͒ ͞ ͯ ͓ ̗ ̑ ̫ ̓ ͆ ̹ ͇ ͙ ͎ ̩ ̩ ̜ ͌ ̪ ̑ ̻ ͐ ̍ ̓ ͣ ̒ ̋ ̋ ͐ ̾ ̾ ͐ ̓ ̙ ęa̧̪̠̬͌ ụ̱̭̬ ṫ̢̧̖̘̗̺̪ ḩ͜ ̪̝ͮͧ o͜ ̞̼̪͔̬̗ r̢̙̲̪̗͇ ͯ̋ ͏ t͟ ͢ ̖͐ h̉ ̞͎͎ͩͦ i̛̫͈͛ͥ s͓͎̞̾̓ ̣ ̀ í͇̯̻̭͍ͤ̈ͤ̋ s̨̬̙̻͈ͥ ̣ a̮​̮̼̺̻ͤ ͅ ̀ ̀ ṗ̻͔̿ͨ ͘͡ě̾̏ ̎ͭ̚ ̞̯͙̦ ́ͅ ̀ ̵r̸͉͈͍̽͗ͯ s̙̠̥̈ͦ ́ o̯̥̻ ́ n̵̜̺̯ ̸a͇̤͖̮̹̐ͫ l̨͚͔̱̯̾͛ ́ě̙̪̤ͨ s҉̵̧ ̖͇̬̭̥̩͛̔ͧͣ s҉ ͮ̿̓ ̙a͘͏̲̤̝͍ ̜̪̑ͬ ̙̥̫̓ͨ ̀ ͚̩̪̐ͧ ͞ ͈ͬ ͙̬̻ͧ̚ ͔͓ ͬ̌͗ͮ ̀ t̖̓ͯ h͕̞̾͌ ͠i̛̫̝͚̓̑̚ s͓ͤ í͇͙​͙ͪ s̨͡ ͓̪̻ͥ̍ a͝ ̥͇̮͐̂ ṗ̿ ͘͡ě͠ ͒̚ ̖͎̞ ̀ ̵r̸͉͔ ͊̋͐ s̠̓ ͮ o͝ ̬̯̾̄ ́ n̵͔̯͆̋ ̸a̐​͓̩͇̐̾ l̨̻͚̹̽ ě̙̘ s҉̵̧ ̲̗͇̖ͤ͛ͣ ̉ s҉ ̑ͮ ̟̼a͘͏̲͍ ęa̧̪̠̬̒͌ ụ̱̭̬ t̢̧̖̘̗̺̪​̪ ḩ͜ ̪̝͐ͮͧ o͜ ̞̼͔̪̗̬ r̢̙̪̲̗͇ ͯ̋ ͏ ͟ ͢ ͐ ̉ ͎͎͕ͩͦ ͈̝͛ͥ ͎̞̾̓ͤ ̣ ̀ ̯̻͍̭͙ͤ̈ͤ̋ ̬̙͓ͥ​͈ͥ ̣ ͝ ̮̼̥̺̻ͤ̂ ͅ ̀ ̀ ̻͔ͨ ̾̏ ̎ͭ ͙̯̦̖ ́ͅ ͈͍͔ ̽͊͗ͯ ̙̥̈ͦ ́ ͝ ̥̻̬̄ ́ ̜̺͔ ̤͖̮͓̹ͫ̐ ͔̱̻̯̾͛ ́ ̪̤̘ͨ ̬̭̥̩̲̔ͧͣ ̉ ̿̓ ̙̤̝̟ ̜̪̑ͬ ̙̥̫̓ͨ ̀ ͚̩̺̐̇ͧ ͐͞ ͈ͬ ͙̻̼ͧ̚ ͔͓̪ ͮͬ̌͗ ̀ t͟ ͢ ̖̓ͯ h̞͎̾͌ͩ ͠i̛̫͈͚̓̑͛̚ s͓͎̾ ̣ ̀ í͇̯͙̻̭ͪ̈ͤ s̨͡ ̪̬̻͈̍ͥ a͇̮͐​̮̺̻ͤ ̀ ṗ̻̿ ͘͡ě͠ ͒̎̚ ͎̞̯͙ ́ͅ ̀ ̵r̸͉͈̋͐͗ s̙̠̥̓ ͮ o̯̥̾ ́ n̵̜̯͆̋ ̸a̩͇̤͖̹̐ͫ̾ l̨͚͔̹̯̽̾ ́ě̙̪ s҉̵̧ ̗͇̖̬̭ͤ͛̔ͣ s҉ ̑ͮ̿ ̙̼a͘͏̲̤̝͍ ęa̧͌̑ͬ ̪̠̬̒ ụ̱̭̬ ṫ̢̧ ̖̘̗̪​̪ ḩͮͧ͜ ̪̝ o͜ ̞͔̪̗̬ r̢̙̲̗͇ ͯ̌̋ ͏ ͐̓ͯ ̉ ͎͕ͦ̾ ͠ ̝͚ͥ̓̚ ̞̓ͤ ͍͙ͤ​͙ͪ̋ ͡ ̙͓̪ͥ ̣ ͝ ̼̥͇͐̂ ͅ ̀ ͔ͨ ̾̏͠ ͭ͒̚ ̦̖͎ ͍͔ ̽͊̋ͯ ̈ͦ̓ ͮ ́ ͝ ̻̬̾̄ ́ ́ ̺͔͆̋ ̮͓̩̐̾ ̱̻̹͛̽ ̤̘ͨ ̩̥̲̗̖ͧͣͤ͛ͣ ̉ ̓̑ ̟̼͍ ͮ s í i̛ t h s̨ a ṗ ě ͡ ͘ ̵ r̸ s o a n̵ ̸ s ҉ s ̲ ͏ ͘ a l̨ ě ̧ ̵ ҉ ͇ ̀ ̞ ̫ ̯ ͉ ̯ ͚ ̖ ̮ ̞ ̠ ̯ ͇ ͇ ̙ ̻ ͌ ̿ ̑ ̺ ̯ ̐ ̻ ̤ ͬ ͐ ͓ ̎ ̍ ͔ ̬ ͤ ̥ ͧ ̀ ̐ ̀ ̓ ̙ ͈ ̪ ̿ ͮ ͚ ̤ ͗ ͙ ̥ ̈ ͈ ͫ ́ ̭ ͭ ͟ ͢ ̯ ͎ ͈ ̚ ̻ ͔ ̮ ͙ ̥ ̬ ͖ ͨ ͬ ͧ ̀ ͈ ̜ ̹ ͅ ̪ ̭ ̻ ͩ ̾ ͎ ͥ ͗ ͦ ͓ ͞ ͤ ̫ ̀ ͛ ́ ̝ ̩ ̜ ̔ ͯ ͣ ͐ ̙ ̣ ̻ ̩ ̾ ̾ ͍ ͎ ͍ ̀ ͔ ̱ ̼ ̦ ̥ ̮ ̋ ̈ ̙ ̻ ̒ ͨ ͮ ̺ ̤ ̣ ͅ ̙ ͧ ́ ̞ ͦ ̉ ̋ ͥ ̪ ęa̧̪̠̬͌̑ ụ̭̬̱ t̢̧̖̘̗ ̺̪̇ ḩ͜ ̪̝ ͧ o͜ ̞̪̬ ̼͔̗ r̢̲̗͇ ̙ ͯ̌ ͏ ͐̓ͯ ̉ ͕̾͌ ͠ ̝͚̑̓̚ ̓ͤ ͙ͤ​͙ͪ̈ ͡ ͓̪ͥ̍ ͝ ̥͇͐̂ ̀ ̏͠ ͒ ̖͎ ͔ ̽͊̋͐ ̓ ͮ ͝ ̬̾̄ ́ ́ ͔͆̋ ̐​͓̩̐ͫ̾ ̻̹͛̽ ́ ̘ͨ ̲̗̖ͤ͛ ̓̑ͮ ̟̼͍ ̜ͬ ̒ ̙̥̫ ̓ͨ ̀ ͚̩ ̪̐ͧ ͈͞ ͬ ͙̻ ̬ͧ̚ ͔͓ ͬ͗ t͟ ͢ ̖͐ h̉ ̞͎ͩ​͎ i̛̫͈͛ͥ s͓͎̞̾̓ ̣ ̀ í͇̯̻̭͍ͤ̋ s̨̬̙̻͈ͥ ̣ a̮​̮̼̺̻ͤ ͅ ̀ ṗ̻͔̿ͨ ͘͡ě̾̏ ̞̯͙̦ ́ͅ ̀ ̵r̸͉͈͍̽͗ s̙̠̥̈ͦ ́ o̯̥̻ ́ n̵̜̺̯ ̸a͇̤͖̮̹̐ l̨͚͔̱̯̾͛ ě̙̪̤ͨ s҉̵̧ ͇̭̬̩̥̔ͧ s҉ ̿̓ ̙a͘͏̲̤̝ ̪ ęa̧̪̠ụ̱ ̭ t̢̧̺̪ ̖̘ ḩ͜ ̪ o̼͔͜ ̞̪ r̢̙̪ ̲̗ ͏ t̖̓ h͕̞̾ ͠i̛̫̝͚̓ s͓ͤ í͇͙​͙ s̨͡ ͓̻ͥ a͝ ̥̮͇͐̂ ṗ̿ ͘͡ě͠ ̖̞ ̀ ̵r̸͉͔ ͊̋ s̠̓ o͝ ̬̯̾̄ ́ n̵͔̯͆̋ ̸a͓͇̾ l̨̻͚̹̽ ě̙̘ s҉̵̧ ̲̗͇͛ s҉ ̑ ̟͘͏̲a̼ I spent almost a whole day trying to figure out how to completely accomplish the glitch. You had to enter in a special name for your character to send the game into debug mode and then input a very specific combination of buttons to pilot the Imperial Walker. Once inside it, there were very little limits to where you could not go with it. Once you got beyond the mountains, there was an infinite landscape of clouds. After that, things really got glitchy. Textures would bend, repeat and eventually warp their once familiar colors. You could keep going until the physical game would completely crash and you would have to reset your game cartridge. I can still remember the look on my neighbor’s face that moment I stepped beyond the mountains. As I’ve gotten older and technology has taken over, I encounter more and more glitches that I don’t even have to force like in Shadows of the Empire. Even just simple things like when I’m switching computer displays, the video drivers in my Macbook Pro get a little confused and create their own little

artistic crash. They’ve even helped make my life a lot more pleasant with concepts like “jailbreaking” my iPhone. Glitches are something I’ve come to love, which is half the reason I decided to embark on this project to discover everything I could about not only computers but art. I think I’ve always gravitated towards things that are not inherently trendy. I still believe the best mobile phone operating platform is the Blackberry OS. I can’t stand when people try to tell me that the sound quality of vinyl is the best sound quality you can achieve. I even love the wonderfully disgusting Philadelphia tradition of “scrapple.” In turn, I’ve always had that feeling that coincidences don’t exist in the form of chance. There must be some kind of background programming to this concept humans have defined as reality that sometimes repeats itself. The operating system we’ve defined as “Reality 1.0” must have it’s fair share of glitches. It’s almost like typing something into the search bar of life and having this system recall several of the same file. As much sense as it doesn’t make, for some reason, I’ve always found a little calm in

APPENDIX

chaos. It puts a lot less pressure on us to be perfect files or applications. Living life within a giant perpetual computer that operates itself.

There are so many things that life hasn’t necessarily explained to us humans yet. Computers are much easier to work with. If something is going a little haywire, there is definitely several hundred people who have had the same problem just a few keystrokes away. Life doesn’t come with a troubleshooting manual. You just have to figure it out as your go along; similar in a sense to glitches. Glitches are uncharted territory as is life.

91


CREDITS



1 3 5 7 9 11

The Philadelphia Experiment Logan Neighborhood Philadelphia, PA Texting & Driving County Line Road Horsham, PA The Midway Steak House The Boardwalk Seaside Heights, NJ (Meredith Rogers) North Phiadelphia Philadelphia, PA Leaving (New York City) Vince Lombardi Service Area Ridgeway, NJ Speed, Daemons, Sword, Test Bella Vista Neighborhood Philadelphia, PA

94

.GLITCH

2 4 6 8 10 12

Courtney Rowland Temple University Philadelphia, PA Texting & Driving (Cut/Copy) County Line Road Horsham, PA Missing Reward Missing Morris & Moyamensing Streets Philadelphia, PA System Shock 3.0 The Boardwalk Point Pleasant, NJ Fuuuunnnnn House The Boardwalk Point Pleasant, NJ City Hall, Philadelphia Center City Philadelphia, PA


13 15 17 19 21 23

Overshadowing Nature 15th & Ruscomb Streets Philadelphia, PA “My Family under and God Homies” Inside Navigational Beacon Altantic Heighlands, NJ The Problem with Blight 15th and Lindley Streets Philadelphia, PA Jailbrrrrrreak The Internet Upper Gwynedd, PA BbyFace Lower Gwynedd Trails Lower Gwynedd, PA blondie_1 Bathroom Rosemont, CA

14 16 18 20 22 24

The Day the Sun Didn’t Rise Montauk Point Beach Montauk, NY R ACY Broad & Oxford Streets Philadelphia PA Slight Turbulence 37,000 feet Billings, MT Rustang The Wonder Bar Asbury Park, NJ EXiT Annenberg Hall Philadelphia, PA PiXELCoURT John & Leslie’s Malvern, PA

CREDITS

95


25 27 29 31 33 35

Courtney Rowland Temple University Philadelphia, PA Technicolor Tiger Park Avenue & Cumberland Street Philadelphia, PA FUCK UR COUCH Pennsport Neighborhood Philadelphia, PA WALNUT/LOST City Hall Entrance to Walnut/Locust Philadelphia, PA Danielle Parsons Temple University Philadelphia, PA three_glitchM

96

26 28 30 32 34 36

Courtney Rowland Temple University Philadelphia, PA WIDELOAD Cumberland Street Philadelphia, PA Turn to Clear Vision Montauk Point Beach Montauk, NY Senioritis (Charlotte Jacobson) Temple University Philadelphia, PA BANKRVPT Revel Casino & Resort Atlantic City, NJ four_glitchK

.GLITCH


37 39 41

eight_glitchK six_glitchM ten_glitchD

38 40 42

five_glitchM seven_glitchM eleven_glitchD

CREDITS

97


&

thank yous. fuck yous.

thank yous

To my parents and my brother, for being such incredibly sources of support and being patient as I finished up my last year of college.

fuck yous

To John McCabe, for being the best buddy any bro could ask for. Beers are on me after this one. To Charlotte Jacobson, from all of our yesterdays to our tomorrows, you sure can dance the dance. To my friends, there are so many nights I can’t remember but so many more I’ll never forget. To everyone featured in this book, this would have never happened without you.. To Dr. Edward Trayes, for teaching me I knew nothing about photography and teaching me everything I know about photojournalism. To the teachers and adjuncts, for pushing me and inspiring me to do good fucking journalism.

To the programmers and designers, for making such incredible pieces of technology. To the dreamers, keep on dreaming.

98

.GLITCH

Everyone who has told me that journalism is a dying profession. How the fuck do you learn about your surroundings? Good journalism will never die.

Journalists who write ledes that involve them sitting in a coffee shop. We know where you wrote the fucking lede. To people who go out of their way to make others feel insignificant. We all know who really feels insignificant. It’s you, dipshit. People who aggressively hashtag things on social media. There’s more to life than likes and retweets. Anyone stupid enough to print hashtags, fuck them as well. People who refuse to update their software due to the fact they “don’t have time.” If you don’t have 15 minutes to update a program, you’re not going to fucking have time for a system crash or having your identity stolen. People work hard on this shit. Trends and hype. Don’t fall for it.


CREDITS

99



Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.