top of page

Nomad Error Logs #4

First published on Beehiiv March 11 2024

 

As Spring is getting underway, we welcome in the blooming of flowers, the birth of the adorable little lambs, and the sneezing of a thousand hay fever sufferers (you have my sympathy). It also brings us Issue 4 of the Error Logs. In this issue, I'll be talking about what I’ve been up to recently, sharing some of my inspirations and processes of my artworks, and finally, to round things off I’ll be introducing a nifty little Processing script for glitching.

You may notice that there’s no Artist Spotlight this time around, as the curse of February meant I had less time to get things done. I was also busy both professionally and personally since the last issue, meaning art had to take a backseat. I still wanted to provide some interesting content, so from this month I’ll occasionally be including a new feature called Behind the Glitch, where I write a little about the inspirations and processes behind some of my artworks. It won’t be something I do every month, but I thought it might keep things fresh and it can be useful for and artist to reflect on older works through a fresh set of eyes.

News & Updates

So last issue I wrote a little bit about how I'd been challenging myself to move away from making portraits and focusing on subjects that don't necessarily lend themselves well to my usual glitch techniques. I think I carried on that trend somewhat over the last few weeks. Here’s a selection of my works from February.

Feb works.png

As much as I love glitching portraits, skulls and statues, trying out different subjects has really helped me develop both technically, but also consider my compositions more too.

This newfound desire to challenge myself has led me to start pushing myself in other ways too. 

I've recently been working on a collaboration with another artist. I don't often do collaborations as I'm probably not the easiest person to work with. But what started as a casual "hey do you mind if I play around with that image you made" has turned into something more interesting. I don't have a timeline as to when we intend to publish these works. For now, I’ve been enjoying the process and just seeing where things go naturally. Keep checking out my Instagram over the coming weeks to see how that turns out. 

One positive consequence of this collaboration is that it has made me revisit sonification again (turning images into sound files and glitching them using audio editing software).

Sonification in Audacity was one of the first glitch techniques that I learned. There's something pure about it and it's quite exciting to edit images as sound files. Like you're doing something you shouldn't be doing.

Having said that, it's not a technique that I use very often because I've never really enjoyed the aesthetic of it.

The image below, Buddha, was one of my earliest pieces when I first started playing around with glitch art. The effect on the robes was achieved using sonification in Audacity. You can see how chaotic and ‘unclean’ the results are with it, which has never been my cup of tea.

kamakura buddha finished 2.JPG

Buddha, tokyo_nomad_ 2020

But, I’ve been inspired to come back to Sonification recently. Rather than using Audacity, I’ve been using the Sonification script for Processing from GenerateMe. From what I can tell, it doesn’t actually use Audacity or sound files, but it does mimic the effects of Audacity, and it does a damn god job of it. You have a lot less control over the parameters using this method, but it has the benefit of not needing to constantly change your file types, which can be a colossal pain in the arse when it comes to using Audacity.

Anyway, here are some of the recent experiments I’ve made with Sonification. With the exception of the first one, they’re all raw outputs (and the only editing I did on the first one was just blending the best parts of two similar outputs together).

res_DBA29D68_skull.png

I’ve recently realized that even for Sonification, how you prepare the image before you glitch it can have a pretty big effect on the output (which I spoke a little about in my FUBAR 2023 workshop on GLIC). In much the same way that a photographer needs to consider the framing, lighting, camera settings before they even hit the shutter, considering the size, color, contrast and even file type can have a big effect on your final outputs.

Behind the Glitch

For this feature, I’m going to take a look at some of the inspirations and process for creating some of my older works. For this issue, I’ll be taking a look at a series I made a couple of years ago.


Title: The Crushing Anxiety of Little Miracles

Artist: tokyo_nomad_

Medium: Photo Manipulation 

Size: 1000 x 1000 pixels

Date: Dec 2021 / Jan 2022

res_AE9092AE_image3A419_chroma.jpg

Daedalus, father of Icarus. Master craftsman. Architect of the Minotaur's labyrinth. A figure of knowledge and wisdom. Deadbeat dad. Got his son imprisoned and then came up with the hairbrained escape plan that led to lcarus' death.

Of course, that's not the point of the story of Icarus. It's meant to be a parable about the hubris of youth. Icarus is framed as the arrogant young man ignoring the advice of his wise father. But what if we take a closer look? Perhaps Icarus was wise not to follow his father's advice. This is a man after all, who attempted to murder his nephew in a fit of envy after seeing his potential for greatness (which may explain the Ancient Greeks' penchant for parables warning of the deadly consequences of disobeying one's elders. Threatened much?). Not to mention that Daedulus' dealings with the insane King of Minos got them imprisoned in the first place. It's possible that Icarus saw Daedulus' advice as foolish or self-interested. He was doomed either way. I wonder, after the fall of Icarus, how Daedulus felt. Did he acknowledge that his choices up to that point had led them down this path?

For this project, I created a series of images depicting neglected, sorrowful-looking children. Captions above their heads written in Cyrillic, expressing words of anguish.

The final image depicts the caregiver. As lost and sorrowful as the children.

This particular series was created as a reflection of the insecurities and anxiety that an individual may experience in their role as a parent. The colossal weight of expectations and the nagging worry that we always fall short. The guilt we are left with when we fail to meet the standards we hold ourselves to. When we allow our selfishness or complacently to affect our better judgement. 

I used to feel a lot of anxiety when my daughter was young. I'd often have nightmares in which she would have accidents caused by my negligence. Just that one fleeting second where your attention is taken by something else. Something insignificant. And then the worst happens to the one person who relied on you to keep them safe. Balconies were the worst. You can't stop gravity doing what it does best. As Icarus learned the hard way.

As she gets older, the anxiety remains but the triggers have changed. Have I made decisions that will play out in her best interest? Have I always set a good example? Have I said something carelessly that has upset her? Have I brushed off her worries about something when I should have listened? 

It made me realise that perhaps parents don't know what they're doing any more than the child does.

What's more, it's not always easy for the parent and child to understand one another. We've grown up in different worlds. Two generations apart. And in my case, two countries 10,000 miles apart with vastly different cultures. My understanding of her struggles or viewpoints distorted by a filter of my own experiences.

To create these works, each piece was run through several different processes to achieve this brown, grimy look. I also distorted the faces using pixelsorting and pixelstretching in order to reflect the perceived physical deterioration of the children, but also the emotional decay of the parent brought about by their self-doubt.

I decided to have the text in a foreign language to help convey this idea of two people talking but not understanding one another.

I wanted to use a language that had a script significantly different from my own language of English. 

Greek was a bit too obvious and cliche, despite the Icarus connection, and would have felt too much like a play on the phrase "it's all Greek to me" - I wanted to steer clear of that kind Sunday newspaper comic strip satire vibe. Japanese was a little too on-the-nose considering my own situation. Plus, Japanese has a different set of connotations, being much more commonly used in science fiction or cyberpunk genres - it wasn’t really well suited for the story I wanted to tell.  I went with Russian because, in a literary sense, it is a language imbued with a rich history of guilt, shame and suffering, from Dostoevsky to Tolstoy to Chekhov, it was an obvious choice to convey those feelings.

The three images of children contain the text;

Мне грустно - I'm sad

Простите меня - Forgive me

я прощаю тебя - I forgive you

These words reveal the innocence and naivety of the children, in that they still continue to blindly trust in the capabilities of the parent.

For the image of the parent, a self-portrait, the caption reads "Bastard". We're left to wonder if these are these the eventual words of the children as they get older, or if this is a self-appointed label as the parent imagines the same mistakes Daedalus made.

Tool Time: Glitch FX

In this month's newsletter, I'd like to write about a nice little Processing script.

If you're not familiar with Processing, it's a programming language designed specifically for the visual arts (although it's not the only programming language good for visual arts, p5.js being another one).

 

It's used by a lot of generative artists, so a lot of those cool looking math-based artworks might have been made in Processing. To give you an example of what I mean, here’s an artwork that I made using GenerateMe’s vector field code as a base.

diagonal10 300dpi upscaled.jpg

Threads, tokyo_nomad_ 2021

Now, you don't need to be a master of coding to use Processing. There's a wealth of scripts that have already been made and shared for you to use.  It’s the artists’ equivalent of the hacking world's script kiddies. And there's no shame in that because I'm here to make art not computer programs.

Not everything in Processing involves generating things from scratch. If you're a glitch artist that hasn't explored Processing, I highly recommend doing so because there are a lot of good scripts and micro programs out there specifically for glitching, and I'd say the vast majority of my glitch work is done within Processing.

So, the script I'll be introducing today is called GlitchFX and was created by cyberart_by_justin (an artist that I'd love to do an artist spotlight on in the future)

I'll include some brief instructions on setup at the bottom of this section, so if you're only interested in seeing what it does and not interested in trying yourself, I'm not boring you with the technical stuff.

So GlitchFX basically applies a random set of glitch parameters to any image that you input. From the README that comes in the ZIP folder, the script applies the following effects:

  • Scanlines

  • Warp

  • Pixel Burn

  • Noisy

  • Scanner

  • Jpg Degrade

  • Invert Saturation

Here’s a couple of examples of my artworks that have used Glitch FX (note: there were other effects applied to these works).

glitch fx examples.png

1. First Issue, tokyo_nomad_ 2023 2. Out of Sequence, tokyo_nomad_ 2023

Here are some raw outputs to give you a better idea of what it can do.

O.png

So far so good, but I think this script comes into its own when you combine it with other things like in my works I posted above. I ran the skull through a few other programs/scripts so you could compare the base effects with what can be done when you mix and match different things.

So, if you’d like to try it out for yourself, first you’re going to need to download Processing. We’re currently onto Processing version4, but this script works in Processing 3. You can downlaod that from here. Just click on Version 3.5.4 and choose the OS version you need.

Once you’ve done that, you can download the Glittch FX script from the following Github link.

If you’re not familiar with Github, just hit the green button that says Code and download the Zip.

Once you’ve downloaded and unzipped it, just open the file Glitch_FX.pde and it should open it automatically in Processing 3. Then hit the play button in Processing and it’ll prompt you to choose an image. Once it’s loaded in, just hit ‘G’ to generate and either ‘J’ to save as a JPEG, or ‘P’ as a PNG.

The script reduces the size of the image by x4, so you either need to make sure that your original image is big enough or you need to change the script so that it's dividing the input image by 1 instead of 4. I'm sure that probably has some kind of effect on the final output as I don't imagine he just put that in there for shits and giggles, but in this case I subscribe to the policy of "what you don't know won't hurt you" as the outputs have always looked fine to me.

So that’s it for this month’s Error Logs.

I'm not going to lie, trying to write consistently and meet deadlines has been kind of tough. I guess at first, I thought it would just be writing out my (largely) unedited thoughts, but the research and formatting takes longer than expected. It’s been a great learning experience for me, and I still think this is a worthwhile endeavor, but it has been reducing my artistic output a little.

With that in mind, I've decided to make some changes to my posting schedule. Currently I've been trying to do one blog post and one newsletter a month, but I’ve decided to make the blog posts irregular and keep the Error Logs as my consistent monthly post. I think that's going to be the best way of keeping the content at a high level.

So I’ll be posting again in March. If you enjoyed this, please feel free to subscribe or share it with friends or on your social media!

bottom of page