I really enjoyed reading about Kurokawa’s approach to his creative works. What he said about nature especially stood out to me. He explained that nature is disorder, and he likes to use it to create order and show another side of it. In simple terms, he likes to “de-nature” a subject to reveal the patterns and structures within it. This is a great way to think about generative art. From my own experience, I often start with noise or randomness and then use functions to shape it into something appealing or familiar. Reading this makes me realize that live coding shouldn’t just be about showing off a cool new visual, a sound, or a fast algorithm. It should be about evolution. If I want my compositions to stand out, they should feel like they are growing in front of the audience. Anything that feels natural stands out to us because we recognize those same patterns within ourselves. I also believe in maintaining a “sweet spot” of balance between abrupt changes and consistent patterns.

Kurokawa’s lack of bias and his openness to exploring new tools, whether they are legacy software or brand-new technology, is the exact spirit that allows for true artistic exploration. He avoids sticking to just one tool or software, which usually limits what we can create. By setting aside these biases, Kurokawa leads the way in bringing complex ideas to reality in their best possible form.

Humans have a natural instinct for macro and micro scales. See Rumi: “That I might behold an ocean in a drop of the water, a sun enclosed in a mote.” Kurokawa throws up the same prayer with his work. I started thinking about how the tools we use shape our conceptualizations of the nature of reality, how we cannot extricate the soul from the body (loosely related to synesthesia). Our visceral understanding of the configurations of nature became more quantitative – “Powers of Ten.” The presence of modern technology and scientific thought is strong. Rather than see man in God’s image, Eames noticed the planet as seen from a US-Russia-Space Race spaceship in a microscopic 1920s lab-possible cell. Despite the contextual distance, the spiritual epiphany is the same, and this is interesting to me.

Kurokawa’s disregard for the tools he uses was also interesting. Like in Powers of Ten, how we understand and what we create is shaped by the tools we use. I wanted to know more about what Kurokawa thinks about this relationship, the inherently mutually-constraining dynamic between his tools and what he creates. I get not being into tech-nostalgia (nostalgia has always seemed too navel-gazey for me). I don’t like my books because of the way they smell. I’ll read a pdf too. Just wanted to know more about this.

Even if he doesn’t care about the technology itself, and more about what kind of soul these devices can process and display, boy does he keep up just as fast as technology moves, huh? I was really interested in his setup. The iMac, the speakers, the mixing board, whatever the hell a “subwoofer” is, and the “X” where he can stand and scrutinize the total composition the way an audience in a theater will. I liked the idea of needing to move up close and back up, again and again. I really liked this “X.”

I also liked using “NASA topographic data to generate a video rendering of the Earth’s surface.” Just shows how many resources are at your disposal, if you can think of them. I also like how the reading mentions the sublime. I always thought of nature as an intelligent, subversive force. I also noted how Kurokawa uses a sketchbook to communicate ideas. It’s not all done on computers, but a lot of performance conceptualizations begin by being drawn by hand.

I also liked reading about the actual logistics that live performances take, like figuring out how to record a waterfall, or get your hands on dried insects, or balance 200 meters of cable in a historically old and valuable roof. Producing the live performance seems just as much as a live performance itself. I also never thought of films as pieces of audiovisual work, which they definitely are.

And mostly I feel like this reading was about tapping into something, and a brief insight into how Kurokawa taps in. What he taps into. Want to end on another Rumi quote I found while browsing for the first one: “Dost thou know why the mirror (of thy soul) reflects nothing? Because the rust is not cleared from its face.”

Rumi

What I find most interesting is Kurokawa’s statement, “Nature is disorder. I like to use nature to create order… I like to denature.” I have always thought of nature as a form of order — ecosystems functioning in balance, patterns repeating, and life sustaining itself without human interference. In contrast, I tend to see human beings as the source of disruption and chaos. That is why his perspective feels so unexpected to me. By describing nature as disorder, he shifts the responsibility of structure and organization onto the artist. It suggests that order does not simply exist waiting to be admired; it can be constructed through interpretation and design

I was fascinated by his focus on synesthesia and the deconstruction of nature. He takes the natural randomness of our environment, such as the chaotic motion of microscopic particles, and translates it into highly controlled, digital audiovisual experiences. By acting as a “time designer,” Kurokawa ensures his pieces never just dissolve into a mess of noise. Instead, he carefully layers real-world field recordings with computer-generated graphics so that what you hear and what you see feels like a single, connected unit. This approach shows how we can use digital tools to completely rebuild our perception of the natural world.

Kurokawa’s style offers a great lesson on the importance of flow and artistic intention. When coding generative art, it is very easy for an algorithmic composition to lose its structure and overwhelm the audience. However, Kurokawa proves that by carefully guiding the transitions between order and disorder, an artist can successfully harness that chaos. His work is a powerful reminder that mastering the audio-visual flow is what transforms raw data and abstract code into a truly engaging and meaningful performance.

Reading about Ryoichi Kurokawa made me think differently about how scale and control work in audiovisual art. What stood out to me most was his idea of “de-naturing” nature, to uncover structures that are usually invisible. He breaks natural phenomena down into data, sound and image to create works that feel both precise and unstable at the same time, which makes the experience feel alive rather than fixed.

I was also drawn to how Kurokawa thinks about time. He sees his work as “time design” and he justify by constantly adjusting and reshaping it across performances and installations. His slow and evolving approach contrasts how quickly technology usually moves – he doesn’t seem interested in novelty for its own sake, but in letting ideas develop gradually, the way nature does.

Another aspect I found compelling is that Kurokawa doesn’t confine himself to a single platform or format. He moves fluidly between concerts, installations, sculptures and data-driven visuals, choosing the medium based on what the idea requires rather than forcing the work into one system. This flexibility reinforces his larger interest in scale and transformation, and it made me reflect on how artistic practice doesn’t have to be tied to one tool or discipline to remain coherent.

Background: What is Pure Data?

Pure Data (Pd) is an open-source visual programming environment primarily used for real-time audio synthesis, signal processing, and interactive media. Programs in Pd are built by connecting graphical objects (known as patches) that pass messages and audio signals between one another. Unlike text-based programming languages, Pd emphasizes signal flow and real-time interaction, allowing users to modify systems while they are running.

Pd belongs to the family of visual patching languages derived from Max, originally developed by Miller Puckette at IRCAM. While Max/MSP later became a commercial platform, Pure Data remained open source and community-driven. This has led to its widespread use in experimental music, academic research, DIY electronics, and new musical interface (NIME) projects.

One of Pd’s major strengths is its portability. It can run not only on personal computers, but also on embedded systems such as Raspberry Pi, and even on mobile devices through frameworks like libpd. This makes Pd especially attractive for artists and researchers interested in standalone instruments, installations and hardware-based performances.

Personal Reflection

I find Pure Data to be a really engaging platform. It feels similar to Max/MSP, which I have worked with before, but with a simpler, more playful interface. The ability to freely arrange objects and even draw directly on the canvas makes the patch feel less rigid and more sketch-like, almost like thinking through sound visually.

Another aspect I really appreciate is Pd’s compatibility with microcontrollers and embedded systems. Since it can be deployed on devices like Raspberry Pi (haven’t tried it out though), it allows sound systems to exist independently from a laptop. This makes Pd especially suitable for experimental instruments and NIME-style projects.

Demo Overview: What This Patch Does

For my demo, I built a generative audio system that combines rhythmic sequencing, pitch selection, envelope shaping, and filtering. The patch produces evolving tones that are structured but not entirely predictable, demonstrating how Pd supports algorithmic and real-time sound design.

1. Timing and Control Logic

The backbone of the patch is the metro object, which acts as a clock. I use tempo $1 permin to define the speed in beats per minute, allowing the patch to behave musically rather than in raw milliseconds.

Each metro tick increments a counter using a combination of f and + 1. The counter is wrapped using the % 4 object, creating a repeating four-step cycle. This cycle is then routed through select 0 1 2 3, which triggers different events depending on the current step.

This structure functions like a step sequencer, where each step can activate different pitches or behaviors. It demonstrates how Pd handles discrete musical logic using message-rate objects rather than traditional code.

2. Pitch Selection and Control

For pitch generation, I use MIDI note numbers that are converted into frequencies using mtof. Each step in the sequence corresponds to a different MIDI value, allowing the patch to cycle through a small pitch set.

By separating pitch logic from synthesis, the patch becomes modular: changing the melodic structure only requires adjusting the number boxes feeding into mtof, without touching the rest of the system. This reflects Pd’s strength in modular thinking, where musical structure emerges from the routing of simple components.

3. Sound Synthesis and Shaping

The core sound source is osc~, which generates a sine wave based on the frequency received from mtof. To avoid abrupt changes and clicks, pitch transitions are smoothed using line~, which interpolates values over time.

I further shape the sound using:

  • expr~ $v1 * -1 and cos~ to transform the waveform
  • lop~ 500 as a low-pass filter to soften high frequencies
  • vcf~ for resonant filtering driven by slowly changing control values

Amplitude is controlled using *~, allowing the signal to be shaped before being sent to dac~. This ensures the sound remains controlled and listenable, even as parameters change dynamically.

Randomness and Variation

To prevent the output from becoming too repetitive, I introduced controlled randomness using random. The random values are offset and scaled before being sent to the filter and envelope controls, creating subtle variations in timbre and movement over time.

This balance between structure (metro, counters, select) and unpredictability (random modulation) is central to generative music, and Pd makes this relationship very explicit through visual connections.

Conclusion

Overall, Pure Data feels less like a traditional programming environment and more like a living instrument, where composition, performance and system design happen simultaneously. This makes it especially relevant for experimental music, live performance and research-based creative practice.

(Somehow I can’t do recording with internal device audio… I’ll try recording it using my phone sometime)