{"id":15288,"date":"2020-11-27T23:39:01","date_gmt":"2020-11-27T23:39:01","guid":{"rendered":"http:\/\/astoryisnotatree.net\/?p=15288"},"modified":"2020-12-18T20:12:27","modified_gmt":"2020-12-18T20:12:27","slug":"art-from-code-molnar-and-repetition","status":"publish","type":"post","link":"http:\/\/astoryisnotatree.net\/?p=15288","title":{"rendered":"Art from Code: Molnar and Repetition"},"content":{"rendered":"\n
\"\"
My Molnar-inspired final sketch<\/figcaption><\/figure>\n\n\n\n

My previous article (Art from Code: Time, Space, and Spacetime<\/a>), analyzed the heavily debated question: is computational art really art? If we dig deeper into the debate between computer generated art and conventional art, we\u2019ll find the more nuanced argument concerning the use of repetitions within computational art: how does it aid an artist\u2019s meaning?\u00a0<\/p>\n\n\n\n

Before breaking down this debate, it would be helpful to define repetition for our purposes. Traditionally, repetition is a reoccurrence of an action, event, or thing. Within art, this often evolves into a pattern or patterns. The human eye is inherently drawn to patterns because of their heavy use of repetition. This can be described by the audience as soothing or familiar. The ‘familiar’ piece comes into play as the ”thing” creating the ultimate pattern is displayed over and over: repetition. With more repetition and pattern displayed (usually decided by the size of the artist medium), this can create a familial sense of comfort in the mind — or quite the opposite! <\/p>\n\n\n\n

Repetition lies on a spectrum; from a complete pattern to randomness. If the human eye is so in tune to the comfort of patterns, then a break in this repetition can create extreme tension. Depending on the artist\u2019s desired meaning, this can a powerful tool to convey a particular feeling or emotion to the audience.<\/p>\n\n\n\n

Gradualism \u2014 moderate and measured change \u2014 can act as a middle ground between a perfect pattern and a tense break in the pattern. Vera Molnar, an infamous computational artist, can be known as the god mother of gradualism. She often used this technique to attract a wide variety of audiences with her impeccable art work. <\/p>\n\n\n\n

Gradualism can take place within two different perspectives: within one plane of a gradually changing pattern, or within multiple planes of various patterns that display gradual change on each plane. Molnar\u2019s (D\u00e9s) Ordres<\/em> is an example of gradual change within one plane. It is a pattern no doubt (repetition of each cell), yet each cell is slightly different from its neighbors. I find this much more visually stimulating to the eye than a perfectly plain pattern. Molnar also depicts the latter version of gradualism with grace as well. In the article \u201cMy mother\u2019s letters: simulation by computer,\u201d Molnar practices gradualism by slightly tweaking her code for each individual sketch. In attempt to artistically represent of mother\u2019s uniquely beautiful handwriting in one stroke, she saves each draft of her sketches. This creates a series of sketches that look quite similar, yet with a careful eye, one can find nuanced differences between each frame. Together, the frames work together to produce a gradually changing pattern.  <\/p>\n\n\n\n

Computers and repetition go beautifully hand in hand. Tell the code to do one action once, and then over and over, and it will gladly run in loops. You will also love it; computational loops are fast and relatively easy to make pattern generating a breeze. Rather than creating the individual piece, and then manually doing it again and again, the code can create the pattern for you. Repetition and patterns (and gradualism!) in computational art are virtually limitless when combined with an artist’s creative intuition. <\/p>\n\n\n\n

Of course it wouldn\u2019t be a true opinion essay if I didn\u2019t include my own perspective, thus I give you: my artistic take on Molnar\u2019s gradualism! Starting with one simple, original geometric computational sketch, I made my way to a series of five different sketches while following one rule: change one thing in my code per iteration, and only <\/em>one thing at a time. This could pertain to any aspect of the code, from adding or subtracting color, position, shape, modifications, etc. I was fairly satisfied with my final product below.<\/p>\n\n\n\n