Genuary - Day 11 & 12
Quine ร Boxes only
Prompt by
@mlarino &
@stranger_in_the_q
This project combines both prompts into a single system.
At its core, this is a quine: a program that outputs its own source code.
The code youโre seeing on screen is not a copy or a recording it is the program continuously printing, executing, and referencing itself in real time.
The quine is built as a self-contained execution loop that:
Tracks which functions are running
Logs its own behavior
Outputs its own source code line by line
Resets and reorganizes itself over time
Each frame, the program updates an internal state that represents its โidentityโ, execution history, coherence, and runtime events. These values are not just visual they are exported as live data and used to drive the 3D scene.
For Day 12 (Boxes only), the visual world is built entirely from instanced boxes using the POPX system by
@_mini_uv .
There are no custom meshes everything you see is boxes reacting to data coming directly from the quine.
The quine exports CHOP channels such as:
Current function being executed
Number of function calls
Execution cycles
Coherence level
Glitch triggers
Runtime uptime
These values control:
Camera position and movement
Lighting intensity and direction
Box scale, spacing, and instance behavior
Scene resets and transitions
The system is audio-reactive:
The music by
@pauk2001 drives the timing, resets, and intensity of the quine. When the music peaks, the quine destabilizes, glitches, and eventually resets itself, starting the self-writing process again from zero.
What I like about this piece is that nothing is decorative.
The text is the program.
The glitches are execution errors.
The boxes are driven by real runtime data.
The reset is an actual reset.
Itโs a system watching itself run, exposing its internal logic, and using that logic to shape the visual output.
Music:
@pauk2001 (็้ ญ็ - Kata zutsuฬ)
POPX:
@_mini_uv
GodRays:
@sarv.vj
Motionblur:
@matterform.xyz
Fully crafted in
@touchdesigner
#genuary #genuary11 #genuary12
