Project 1: Dystopia For Project 1, a collection of 16 stills, 5 GIFs, and a datamosh video were created on the theme of loss. I selected photos from my travel experiences based on objects I thought would be inaccessible or unavailable centuries from now, and I tried to make them look like corrupted data. As a base for my glitches, I mostly used Notepad++ combined with a hex editor because it gave me the best color-changing glitches, but I also used Processing for a couple of pixel sorted stills.
StillsThe first set of stills are the glitch images while the second set of stills are the original, untouched images. Glitch images: Original Images: GIFsThe GIFs were surprisingly difficult to make and required much more time than expected, basically consuming most of my effort for this project. I used slightly different glitch effects to mask what I thought would no longer exist, so I was able to play with a few different visuals. I stuck with black and white edits of various wave effects and put them together using Photoshop's timeline. The most time consuming GIFs were the flower and fence because I had to edit out the entire subject. The GIFs came out well, but I struggled to get through them because of how time consuming they were. For future reference, the easiest images to work with would be the ones that don't need to have certain subjects edited out, such as the image with tea cups. DataMoshThe datamosh video was very fun to make, and it actually turned out better than expected. At first I was worried that the small movements I chose to scrub wouldn't melt well, but they worked suprisingly well. I had to edit the video clip multiple times in Avidemux, but it was fun to look at the results of my work each time I exported an edit. The hardest part was syncing up the datmosh video to the original sound, and I needed to shorten certain scenes so video and voice fit well together. Overall, this glitch outcome is one of my favorite pieces for this project, and I think the datamosh corruption on a clip of axolotls, an endangered species, works well as commentary. The datamosh video used for this project. Twitter bots Two twitter accounts were set up to simulate a call-and-response from one account to the other. The basic premise was that C3_56T, an archive robot in the future, accessed and posted about an adventerous girl's travel account from a thousand years ago. Due to corrupted data, the bot displays its confusion and posts to see if anybody can provide assistance in identifying the glitched images. The first account, Eminy Emily, was made private to feel mysterious and make people unable to see the "past". The second account, C3_56T is public and acts as a window to the past by retrieving "lost data" from the first account. The personality of Eminy Emily was made to be bubbly and charming, and every post has some sort of emoticon attached to it. On the other hand, C3_56T is more stoic and analytic. This difference in personalities further contrasts the difference between past and future, from something more familiar and warm to something more distant and cold. Initially, I planned to post all assets from this project to Eminy Emily's account, but then I realized I didn't need to for the GIFs and datamosh video since they would have to be directly posted to C3_56T's account. Then, I took screenshots of some Eminy Emily posts and posted them to C3_56T's account with confused commentary. As the second part of the Twitter project, I set up Twitter bots to post on both accounts. The automatic messages were made to feel as diverse as possible, so each code had several phrases with multiple parts that provided a variety of mix-and-match options. I tested each phrase's code until the bot for each account seemed varied enough. The set up of the bot is much easier to see and understand in the codes below. I left the posting queue to manual so that I had control over how many times the bot would post. Eminy Emily's bot code focuses solely on text because few people would be able to see it. On the other hand, C3_56T's bot code includes line breaks, images, and reposts of previous tweets, which makes the code a little more complex. For me, the coding was quite fun, although it involved a lot of logical thinking. I enjoyed the process and am curious just how far I can make each automatated tweet feel indivdual. Twitter bot code for Eminy Emily: { "origin": ["#opening# this #color animal#! The colors #color descriptor#.", "#today location# #scenery# is #location descriptor# #happy emoticon#"], "opening":["Take a look at", "I bet you haven't seen anything like", "Check out"], "color animal":["tiger", "frog", "turtle", "snake", "whale", "funky bird", "chameleon", "scaly friend", "parrot", "tropical fish", "butterfly", "chameleon"], "color descriptor":["look so pretty", "are so vibrant", "are really neat", "stand out so much", "are so eyecatching", "are amazingly captivating"], "location":["the Amazon Rain Forest", "the beach", "the mountains", "the Amazon River"], "scenery": ["scenery", "landscape", "view"], "location descriptor": ["breathtaking", "so refreshing", "amazing!", "worth the trek", "so beautiful ~", "to die for!"], "happy emoticon": ["^^", "(^▽^)", "( ˘ ³˘)♥", "o(〃^▽^〃)o"], "today location": ["Today I went to #location#, and #exclamation#, the", "I took a picture of #location# today! The", "Today I went to #location# (^▽^)! The", "Today's picture is from #location#! The", "Check out this picture of #location# I took #happy emoticon# The", "Take a look at this picture of #location#! The"], "exclamation": ["oh boy", "wow", "whew"], "the": ["the"] } Twitter bot code for C3_56T: { "origin": ["Opening #num#", "Reopening #case#"], "loading": ["■■■□□□□□□□ NOW LOADING", "■■■■■□□□□□ NOW LOADING", "■■□□□□□□□ NOW LOADING", "■□□□□□□□□□ NOW LOADING", "■■■■□□□□□□ NOW LOADING", "■■■■■■■■□□ NOW LOADING", "■■■■■■□□□□ NOW LOADING", "■■■■■■■■■□ NOW LOADING", "■■■■■■■□□□ NOW LOADING"], "num": ["Case-1320: @EmilyEminy\n Beginning retrieval process, Log 3025-04.16 \n #loading# \n #imgresponse# \n {img https://placeimg.com/640/480/animals/image.jpg}"], "imgresponse":["Subject unidentifiable.", "Unable to decipher file.", "Too many unknowns.", "File of questionable origins.", "Curious ...", "Unable to identify subject.", "Attempting to decipher ...", "Requires further assistance.", "Requires further assistance.", "Data insufficient ...", "Need assistance to identify subject.", "Unable to find a match with archives.", "Locating subject ...", "Locating subject ...", "...", "No matching data found.", "File exceeds corruption limit.", "File exceeds corruption limit.", "File beyond repair.", "Hmm ...", "Hmm ...", "Attempting to reference archives.", "Unable to process file.", "Insufficient data."], "case": ["Case-1320. \n Beginning retrieval process. \n #loading# \n #linkresponse# \n #twtlink#"], "linkresponse": ["Too many unknowns.", "Attempting to decipher ...", "Requires further assistance.", "Need assistance to identify subject.", "Need assistance to identify subject.", "Unable to identify subject.", "Requires additional insight."], "twtlink": [""] }
0 Comments
|
Archives
May 2022
Categories
All
|