Jim Nista On Code Painting

The 16:9 PODCAST IS SPONSORED BY SCREENFEED – DIGITAL SIGNAGE CONTENT When a big LED video wall gets populated with fresh creative, the creatives and the people operating a display are likely going to have a conversation about the size of the finished file and how to move it – because there’s a good chance the rendered file is huge, and not something that can attach in an email. So I was intrigued as hell when a creative guy told me the video wall creative he’d produced for a project could fit on an old-school floppy disk … because it was really just some lines of code. A lot of people in the digital signage ecosystem will know Jim Nista. He started and ran the LA creative technology shop Insteo, before it was acquired by Almo. Nista worked for his new masters for a while, but eventually went off on his own, and is now spinning up a new boutique agency that’s doing creative for visual projects. One of the things he’s been actively working on is what he calls Code Painting – a big visual that gradually builds in front of viewers and then self-destructs, replaced by a new visual that again starts to build. You set the file and visual instructions, and then forget it, as it will just run and run but always be a bit - or a lot – different. It’s all done in programming instructions, and in the case of his current efforts, is focused on the familiar visuals of flowers. Nista’s work was one of three used for the Sixteen:Nine Mixer at InfoComm last month. Having had a couple of explainers of what was going on, and the approach, I figured a podcast was the best way to help the industry understand what he’s figured out, and what he’s delivering to clients. Subscribe from wherever you pick up new podcasts. TRANSCRIPT Hey Jim, can you explain what code painting is?  Jim Nista: Yeah, it's a fun new concept for me. I know that other people are doing some of the same types of things, but really, I have been trying to make a painting through either JavaScript or other coding techniques. I started with a more simple approach, and the goal truly was to create something that you're watching a painting come to life, and my own brief to myself was this needs to look good at every stage of the process. Sometimes a time-lapse at the beginning is. what are we looking at here? And so it's been a fun process for me to figure out a way to make something, not just paint itself through code, but to be interesting to look at through the entire process, however long it takes, but 30 seconds to a minute is what I'm usually trying to come towards.  But it is truly just code. There are no images, videos, AI, machine learning, or anything else. It's just a scripted process of creating a unique painting while you watch.  We were sitting in Orlando, chatting about this and you were describing it to me, and I was thinking, boy, this is a little bit over my head, but it sounded like it starts with almost like an armature. You start with some curves, and it just builds from there? Jim Nista: Yeah. It starts from a very primitive drawing. It is almost like a child's drawing because some of the early pieces, and certainly some of the pieces that I showed down in Orlando, are flowers because those are shapes that are very recognizable to our eyes. We can spot a flower-type shape almost as well as we can determine a human face style shape. I don't know why, and I don't know the evolutionary reasons behind it, but I realized that this is a pattern that we can determine very easily so behind the scenes, one of the very first things that this code does is to generate out some curves and if you think about the shape of a curve, if you flip that shape, it makes a petal or a leaf shape. So if you make a simple curve and then flip it, you end up with a leaf shape or a petal shape, and if you take that and rotate it around in a certain way and put a dot in the center, our eyes say “flower,” and we're really good at it, right?  It probably has something to do with o