Media Creation Curriculum in the AI Era #5 — Implementing Physical-Space Staging with TouchDesigner — Using the TMU Production Studio as a Case Study
Updated: 2026-05*
1. Introduction
This essay is a Q&A between the author and Claude AI about a redesign of the author’s media production course. As the fifth installment in the “Media Creation Curriculum in the AI Era” series, it works through the implementation decisions involved in staging TouchDesigner (henceforth TD) work in physical space.
Installment #4 surveyed what is possible with media programming in TD across both expression and method. This essay is the implementation guide that follows. That is, it goes one step beyond work that lives inside the screen and takes up the procedures — and the judgments behind them — required to stand the work up as “physical-space staging” that integrates multiple projectors, physical objects, DMX-controlled LED lighting, and sound.
The intended reader is a maker who has reached the stage of handling individual modes of TD expression and now wants their final presentation to take place in a studio environment. As a concrete reference, this essay uses the production studio at Tokyo Metropolitan University. Studios of comparable scale will support the same judgments once you swap in the corresponding equipment and dimensions.
This essay is at most a sketch of the implementation, not a handbook covering every detail. On site, individual equipment quirks, cable-routing decisions, and choices specific to the piece are constant. What this essay offers is the starting point for those judgments: where the options sit and how they relate.
1.1 Reference sites
References
- Media Creation Curriculum in the AI Era #4
- TouchDesigner (Derivative)
- Derivative official documentation
- Projection Mapping (Derivative)
- Palette:kantanMapper (Derivative)
- DMX Out CHOP (Derivative)
- DMX (Derivative)
- TouchDesigner foundations (lecture.nakayasu.com)
- MadMapper materials (lecture.nakayasu.com)
- Suno (official)
- ENTTEC (DMX interfaces)
- DMXKing (DMX interfaces)
- Media Creation Curriculum in the AI Era series: #1, #2, #3, #4
1.2 What this essay covers
- Components of the staging space (wall and floor projectors, DMX-controlled LED lighting, sound, solid primitives)
- Multi-projector coordinate integration
- Projection mapping onto solid primitives (KantanMapper, CamSchnappr, photograph-first calibration)
- DMX lighting control (Art-Net / sACN protocols, DMX Out CHOP)
- Synchronization with AI music (Suno-style tracks and TD’s audio analysis)
- Integrated system design and operational considerations for the actual show
2. The staging space we assume
This essay uses the Tokyo Metropolitan University production studio as a concrete example. Other educational institutions have comparable studio environments, so the descriptions here transfer to those by reading the dimensions and equipment off correspondingly.
2.1 Overview of the staging space
The staging space we assume has the following configuration:
- Wall projector: a projector with resolution and brightness capable of projecting an image roughly 8 m × 4 m
- Floor projector: a projector with resolution and brightness capable of projecting an image roughly 5 m × 2.5 m
- DMX-controlled full-color LED lighting: multiple bar-type LED fixtures can be stood up and arranged
- Sound: PA speakers, subwoofer, and monitors for performers
- White solid primitives that can be placed in the staging space: 30 cm cube, 30 cm sphere, triangular pyramid
These are not independent systems treated piecewise. We assume they are controlled in an integrated way from a single TD project. The goal is a state where image, lighting, and sound are synchronized in time and read as a single experience from the audience’s perspective.
2.2 Wall projector
Wall projection is the primary visual element of the staging. Eight by four meters is large enough to give the audience a sense of being immersed in the space.
- Aspect ratio: 2:1 (8 m × 4 m). Close to common Cinemascope-family ratios
- Required resolution: when the audience views the wall up close, 4K (3840×2160) is desirable. Depending on projection distance and viewer distance, Full HD (1920×1080) can also be practical
- Brightness: in a production studio where ambient light is controllable, roughly 6,000–10,000 lm is practical. Projection in bright spaces requires 20,000 lm or more
- Example models: professional short-throw and ultra-short-throw projectors (Panasonic’s professional PT-RZ series, Epson’s professional EB-PU series, etc.)
Professional projectors allow lens swaps, so you can choose an appropriate lens for the projection distance and projection-surface angle. Short-throw lenses are useful in tight spaces where projection distance cannot be secured, but distortion at the edges of the image is greater.
2.3 Floor projector
Floor projection is a visual element on par with the wall projection. Audience members walking across the floor, or performers interacting with imagery on the floor, create a spatial experience that flat imagery cannot.
- Aspect ratio: 2:1 (5 m × 2.5 m). Matching the wall’s ratio makes it easy to reuse the same image material
- Installation: both the wall projector and the floor projector are ceiling-mounted, with two units running simultaneously
- A note on brightness: the floor may have lower reflectance than the wall, so reaching equivalent brightness requires some headroom in projector output
A ceiling-mounted projector has the problem that audience and performer shadows fall onto the image. There are cases where shadow is used as part of the staging, but if you want to avoid it, design the throw to come down from a steep angle using a short-throw lens.
In some studios the throw direction of ceiling-mounted projectors is movable, in which case extending the wall projector’s coverage down to the floor lets you create continuous imagery that bridges wall and floor. The same design judgments covered in §3.3 “Continuity between wall and floor” then apply directly.
2.4 DMX-controlled LED lighting
DMX lighting installed in a production studio is a strong element you can leverage directly in staging.
- Bar-type LED fixtures: vertical, stick-shaped lights. Standing several of them creates lines of light through the space. Professional gear like Astera Titan Tube and Quasar Science Rainbow 2 is typical
- Flood lights (panel type): uniformly illuminate a wide area
- Moving heads: staging lights whose direction can be changed via pan and tilt
Controlling these via DMX lets color (RGB / RGBW), intensity, strobe, and — for moving heads — pan and tilt synchronize with the imagery. Details are in Chapter 5.
2.5 Sound
Use the studio’s installed PA system.
- Main: stereo L/R, or 4-channel surround
- Subwoofer: emphasizing the low end. In Audio Visual work, the felt low end is strongly bound up with the visual expression
- Monitor: a return feed for performers when present
When sending sound from TD, the internal Audio CHOPs go through Audio Device Out to an audio I/F and then to the PA. Once image and sound live in the same project, latency management becomes important.
2.6 Solid primitives
The solid primitives placed in the staging space become the targets for projection mapping.
- A white 30 cm cube
- A white 30 cm sphere
- A white triangular pyramid (about 30 cm base)
They are white so that projected colors are reproduced without distortion. They are primitive shapes — as opposed to complex sculptures — because their 3D models are easy to create and their mapping design is simplified. Combining several of them as a spatial composition produces visual effects that arise from the assembly.
The basic placement is within the floor projector’s coverage, but designs that combine them with the wall projector, or that use a dedicated small projector for the primitives, are also possible.
3. Multi-projector coordinate integration
When controlling multiple projectors from a single TD project, the most fundamental concern is the design of output destinations.
3.1 Output routing with Window COMP
TD consolidates output to multiple displays and projectors through Window COMPs.
- Use one Window COMP per projector
- Each Window COMP takes its target monitor number, resolution, and window position
- In the OS display settings, have each projector recognized as an “extended monitor,” and reference that number from the Window COMP
When using a wall projector and a floor projector, place at least two Window COMPs in the TD project. Even if you stream the same material, assign each output to its own Window COMP.
3.2 Choosing output resolution
Match each projector’s output resolution to its physical resolution.
- If the wall projector is 3840×2160 (4K), set the Window COMP to 3840×2160 as well
- For a Full HD (1920×1080) projector, use 1920×1080
- Set the floor projector the same way, matching its physical resolution
What to watch out for here is the TouchDesigner Non-Commercial 1280×1280 resolution limit. If a student is using Non-Commercial, then even when the projector’s physical resolution is 4K, TD’s maximum output is capped at 1280×1280. In that case, choose one of:
- Output at 1280×1280 and let the projector scale up (resolution clarity is lost)
- Move to the Commercial, Educational, or Pro version (no resolution limit)
- Obtain an Educational license (a paid non-profit-only license for students and schools)
For presentations as part of an accredited course at a school, adopting an Educational license is a realistic option.
3.3 Continuity between wall and floor
You can also produce wall and floor imagery as separate material, but if you want the spatial experience to read as unified, you design the two as “a continuous field of view of the same world.”
Design options break down as follows:
- Fully independent: different material on wall and floor. Each functions as a separate layer
- Visual continuity: the imagery folds naturally at the wall/floor boundary. For example, design it so that the same pattern continues across the bottom edge of the wall and the wall-side edge of the floor
- Physical continuity: extend the wall projector’s throw down to the floor and have it meet the floor projector at the boundary, so that from the audience the wall-to-floor reads as “a single continuous image.” This works when the wall projector’s throw range is movable in a two-projector ceiling-mounted setup
- Projection from a virtual 3D scene: build a virtual 3D scene in TD and render from virtual camera viewpoints that correspond to the audience’s view of “wall” and “floor.” This requires assuming a single audience viewpoint (the Sweet Spot technique)
Fully independent is the easiest to implement but thinnest in spatial experience. Physical continuity is strong for imagery that flows from wall to floor and is one of the most immersive configurations. Projection from a virtual 3D scene is constrained to a fixed audience viewpoint, but it is strong for spatial expression that includes solid objects. Visual continuity is the middle option.
3.4 Split projection across multiple projectors and edge blending
When a single projector cannot cover a wide surface like 8 m × 4 m with sufficient brightness and resolution, you may use two projectors side by side.
- Edge blending: in the region where the two projectors’ projections overlap, fade their brightness complementarily so the seam is not noticed by the audience
- TD’s bundled projectorBlend component: an N×M projector-blending tool found in the Palette’s Mapping category
- External solutions: dedicated systems like Vioso (auto-calibration) or Scalable Displays are also used
It is rare for student work to need edge blending, but knowing the option exists widens the field of choices.
4. Projection mapping onto solid primitives
Place a cube, sphere, and triangular pyramid within the floor projector’s coverage and map imagery onto each surface. This chapter first organizes the bundled TD tools, then takes up the “photograph-first” approach for simplifying on-site calibration.
4.1 Bundled projection-mapping tools in TD
TouchDesigner comes with several projection-mapping tools under Palette → Mapping.
- KantanMapper: a masking/warping tool that divides the projection surface into 2D polygons and Bézier outlines and assigns a TOP to each shape. The lowest barrier to entry
- Kantan UV Helper: uses the UV Map output by KantanMapper to take Kantan itself out of the render pipeline, reducing load
- CamSchnappr: when a virtual 3D model corresponds to the physical 3D structure being projected onto, six guide points are used to align the two and the projection transform is computed automatically
- projectorBlend: N×M projector blending
- Stoner: in addition to interactive four-corner pinning, a mesh warp lets you fit imagery to a physical surface by hand
- Cornerpin SOP: brute-force four-corner pinning via SOP
- Vioso / Scalable Display TOP: integration with external calibration software
Of these, the protagonists of this essay are KantanMapper and CamSchnappr.
4.2 KantanMapper
KantanMapper is designed, as its name suggests, to be “simple” — TD’s projection-mapping tool whose name comes from the Japanese word kantan (“easy”).
- Launching: drag kantanMapper from the Palette’s Mapping category into the network
- Defining the projection surface: in the KantanMapper window, draw 2D polygons (quad) or Bézier outlines (freeform)
- Mapping interaction: as you move the mouse across the surface the projector is illuminating, the cursor’s crosshair tracks the projected surface, so you can trace the outline of physical objects directly
- Assigning imagery: drag-and-drop a TOP onto each shape
- Output destination: configure the Window COMP from Window Options
The basic flow for mapping imagery onto a cube, sphere, and triangular pyramid is:
- Have the projector throwing onto the floor where the solid primitives are placed
- In the KantanMapper window, create a shape for each visible surface (three visible faces for the cube, the front-facing circle for the sphere, two visible faces for the pyramid)
- Assign a different TOP to each shape
- Refine: use Bézier outlines to smoothly fit the sphere’s outline, use four-corner pins on each face of the cube, and so on
KantanMapper is essentially a 2D-mask tool that delivers a kind of “pseudo-3D” mapping onto solid objects. When proper 3D alignment is needed, use CamSchnappr.
4.3 3D-aligned mapping with CamSchnappr
CamSchnappr is the proper method, aligning a physical 3D structure with a virtual 3D model.
- Prerequisite: a 3D model of the projection target must be prepared in advance (built in Blender, Cinema 4D, Houdini, etc.)
- How it works: specify six feature points on the virtual 3D model and the corresponding points on the projection surface, and the camera transform that aligns them is computed automatically
- Advantage: because the mapping is defined against the 3D model, the imagery side can be produced and edited in 3D space as well
- Application: for simple 3D models like a cube, sphere, and triangular pyramid, you can build each in Blender easily and load them in
When you place an arrangement of solid primitives in the staging space, build a 3D model for each, position them accurately within the virtual space, and align with the physical space via CamSchnappr — the imagery side is then free to move within 3D space. For example, a line of light can travel continuously from one side of the cube onto the surface of the sphere.
That said, CamSchnappr is more setup work than KantanMapper. Choose between them by use case: KantanMapper for simple mapping, CamSchnappr when 3D alignment is required.
4.4 Photograph-first calibration
To simplify on-site fitting, there is a method of photographing the staging space in advance and using the photograph in the mapping design. It is effective when on-site time on show day is limited.
The procedure is:
- As preparation, take a photograph with the solid primitives actually placed in the staging space. Shoot from roughly the same position and angle as the projector will be at on show day
- Load the photograph into TD via Movie File In TOP
- Launch KantanMapper and, with the photograph displayed as the background, draw shapes corresponding to each face of the primitives
- Assign the production imagery TOPs to each shape
- At this point, “accurate mapping against the photograph” is complete
- On show day, install the projector and begin projecting
- Fine-tune KantanMapper’s shape positions and outlines against the actual physical objects
If the detailed design is done against the photograph in advance, on-site fine-tuning takes minutes to tens of minutes. If you can keep the projector and primitive positions close to what they were at photography time, sometimes it works as-is.
The benefit of this method is that the limited on-site time on show day can be spent on finishing touches. Conversely, if the primitive placement or projector position drifts substantially from when the photograph was taken, the photograph-based design loses its value. Aim for installations that can be reproduced precisely.
4.5 On-site fitting flow
On-site fitting on show day proceeds in roughly this order:
- Place the projector as close to the photograph-time position as possible. Marking the position, angle, and distance ahead of time improves reproducibility
- Place the solid primitives at the same positions as when the photograph was taken. Floor tape markings improve reproducibility
- Launch the TD project and confirm output from each Window COMP
- Fine-tune each KantanMapper shape against the outline of the actual physical object
- Play the imagery and confirm it lands correctly on each face
- Adjust color and brightness balance as needed
Running through this whole sequence as a single rehearsal pass by the day before show day greatly reduces trouble on show day itself.
5. DMX lighting control
Drive the production studio’s installed DMX-controlled LED lighting directly from TD. Bundling image and lighting in the same project lets the visual elements be designed as a single whole.
5.1 DMX basics
DMX is a control protocol widely used in stage and event lighting.
- DMX512: 512 channels per universe. Each channel carries a 0–255 value (8-bit)
- A single fixture occupies multiple channels (e.g., 1 ch for a single-color LED’s brightness, 3 ch for an RGB LED, 4 ch for RGBW, around 20 ch for a moving head covering pan, tilt, color, gobo, shutter, etc.)
- Refresh rate: the DMX512 spec maxes at 44 Hz. TD output should also run at Rate ≤ 44 as a guideline
When many fixtures are placed in parallel, the 512 channels of a single universe can be exhausted. In that case, use multiple universes.
5.2 Art-Net and sACN
Rather than carrying DMX signals over physical DMX cable, sending them over Ethernet has become widespread.
- Art-Net: a widely used protocol that implements DMX512-A over UDP
- sACN (Streaming Architecture for Control Networks, E1.31): the newer standard for DMX over IP. Supports multicast
- KiNET: a protocol specific to Philips Color Kinetics
When connecting to a studio’s lighting console, a common configuration is to send Art-Net or sACN from TD to the console’s Ethernet input. The TD PC and the lighting console are linked on a network via an Ethernet hub or switch.
If you want to skip Ethernet and send over USB directly, go through a USB-DMX interface like the ENTTEC USB Pro.
5.3 DMX output from TD
DMX output from TD goes through the DMX Out CHOP.
- DMX Out CHOP supports DMX, Art-Net, sACN, KiNET, and FTDI
- Select the protocol with the Interface parameter (Art-Net, sACN, etc.)
- Each channel of the input CHOP corresponds to a DMX channel (address)
- Example: feed in a 12-channel CHOP and DMX channels 1–12 are driven
- Use the Universe parameter to set the DMX universe
- Keep the Rate parameter at 44 or below
A concrete patch looks like this:
- Read each channel’s meaning from the DMX fixture’s spec sheet (e.g., 1 ch = Red, 2 ch = Green, 3 ch = Blue, 4 ch = Master Dimmer, etc.)
- In TD, generate a CHOP value for each channel (Constant CHOP, LFO CHOP, output of various analysis CHOPs, etc.)
- Combine them into a single CHOP with a Merge CHOP
- Wire that into the DMX Out CHOP
- Set Interface, Universe, and Network Address, then enable Active
5.4 Basic control of LED fixtures
Bar-type LED fixtures — the centerpiece of the studio’s lighting — typically have a channel layout like:
- RGB (3 ch) or RGBW (4 ch) color control
- Master Dimmer: overall brightness (1 ch)
- Strobe: rapid-flash speed (1 ch)
- Per-pixel mode: a mode that splits the bar into segments whose color is controlled individually (increases channel count)
In a layout with several bars stood side by side, sending different signals to each draws a sequence of light through the space. For instance, four bars driven by four sine waves at different phases produce light propagating as a wave.
When moving heads are available, control the beam direction with pan (horizontal rotation) and tilt (vertical inclination). Coordinating with the imagery lets you synchronize beam position with motion in the image.
5.5 Synchronization with image and sound
How you design DMX lighting to synchronize with image and sound has a large effect on the quality of the staging experience.
- Audio coupling: take the result of audio analysis from an Audio Spectrum CHOP and route it into DMX lighting intensity and hue. Wobble flood intensity off the lows, fire the strobe off the highs, and so on
- Image coupling: switch lighting in response to key elements in the imagery (strong motion, scene changes, the start of a particular part)
- Lighting-leads design: have the lighting change first and the imagery respond afterwards. This can feel more impactful than the opposite order
Using Animation COMPs and Timer CHOPs to manage the staging timeline, with imagery, sound, and lighting laid out on a single timeline, makes integrated control much easier.
5.6 Safety considerations
Programmatic control of DMX lighting requires safety considerations.
- Strobe: rapid flashing carries a risk of triggering photosensitive seizures. Provide advance notice to the audience and avoid excessively long strobe sections
- Strong direct light: design the staging so that strong light is not pointed directly into audience or performer eyes
- Failsafe: confirm with the lighting console how lighting behaves when TD goes down — that it falls back to blackout or to normal lighting. When DMX Out CHOP’s Active is turned Off, TD stops sending packets, but the receiving LED fixtures or nodes typically hold the last value received. Verify both the values at scene end and the receiver’s failsafe configuration (behavior on signal loss)
6. Synchronizing with AI music
Music for the staging can be produced with an AI music-generation service, dramatically reducing the time and labor required. Suno, Udio, and Stable Audio are among the choices.
6.1 Generating tracks with Suno
Suno is a service that generates tracks from text prompts. At the time of writing, it is one of the most widely adopted choices.
- Style direction: combine genre and elements — “ambient, drone, low BPM,” “industrial, noise, piano,” and so on
- Structure direction: specify track length, progression, and dynamics changes
- Stem export: stems for vocal, drums, bass, and accompaniment can be exported separately (availability depends on the plan)
When making a track for staging, the following approach is useful:
- Decide on the overall staging structure and timing first, then direct section lengths in the track to match
- Choose a genre that fits the texture of the imagery (drone/noise lines that hold back musical elements for Audio Visual–leaning work, abstract ambient for generative-graphics-leaning work, etc.)
- Generate several outputs from the same prompt, audition them against the imagery, and pick
Terms of use and copyright handling change often on the service side, so check the latest terms when using output for a presentation. Screenings at educational institutions can sometimes count as commercial use — be careful.
6.2 Bringing it into TD
Bringing a generated track into TD is straightforward.
- Save the track file (mp3, wav, etc.) locally
- Read the file with Audio File In CHOP
- Control playback through the Play, Pause, and Cue parameters
- Output through an Audio Device Out CHOP to the audio I/F
When using stems, load each part with its own Audio File In CHOP and assign each to a different visual element via analysis and control downstream. For example, dramatic visual changes on the bass stem, light flashes on the drum stem, and hue shifts on the melody stem — those kinds of correspondences become possible.
6.3 Audio analysis driving image and lighting
Take the output of the Audio File In CHOP, analyze it, and route it into image and lighting control.
- Use Audio Spectrum CHOP to perform FFT and split into low/mid/high bands
- Use Analyze CHOP to extract amplitude, peak, and average from each band
- Map the extracted values to image parameters (particle density, hue, feedback strength, etc.)
- Simultaneously map them to DMX lighting channel values
What matters here is a design in which sound, image, and lighting all share the same audio-analysis result as the “source.” With this in place, the audience perceives that “image and lighting are moving on the same rhythm.” Once visual-aural synchronization clicks into place, immersion grows significantly.
When using stems, more precise control becomes possible. Route only the vocal stem to text display in the imagery; route the bass stem to low-end light pulses; and so on — the parts take on differentiated roles.
7. Designing the integrated system
The elements taken up chapter by chapter so far (multi-projector, solid-object mapping, DMX lighting, AI music) ultimately get integrated into a single TD project.
7.1 Consolidate into a single TD project
A design that runs the various systems on separate software (e.g., imagery on TD, lighting via the lighting console’s software, music on a DAW) is possible, but this essay recommends consolidating into a single TD setup.
- Advantage: imagery, sound, and lighting run on the same timeline, so synchronization drift cannot occur in principle
- Advantage: cross-referencing parameters is easy (audio-analysis results can drive imagery and lighting simultaneously)
- Advantage: the entire show can be reproduced from a single project file
- Caveat: CPU/GPU load is concentrated in one place, so verify machine performance against the contents of the staging
When students are running TD on laptops (e.g., MacBook Air), the basics — poster work, feedback, audio-reactive, single Full HD output — run without problems. Apple Silicon (M1 and later) MacBook Air integrated-GPU performance has improved and is sufficient for general TD use.
That said, the following content puts strong demands on the GPU, so on-site verification is needed when implementing on a student laptop. Depending on the case, plan to switch to a higher-GPU machine or to lighten the staging.
- Real-time AI generation like StreamDiffusion: NVIDIA GPUs (RTX 3090 / 4090, etc.) are effectively required. On Apple Silicon there are alternative paths (via Core ML, etc.), but the TouchDesigner-component standard is Windows + NVIDIA
- ParticlesGPU with millions of particles: combining particle count with frame rate requires a high-performance GPU
- Multi-projector output at 4K: simultaneous rendering of multiple 4K surfaces puts heavy load on the GPU
- Simultaneous processing of multiple Kinects or high-resolution cameras: sensing-side compute load accumulates
- Configurations running StableDiffusion / ComfyUI on a separate machine outside TD: realistically, a dedicated machine should be provisioned
If the staging does not include any of the above, operation on a MacBook Air–class laptop is workable. If it does, consider preparing a gaming-PC-class Windows machine (Nvidia GeForce RTX 4070 or above, 32 GB RAM or more, Ryzen 7 or Core i7 generation or later) as the show machine.
For the final student presentation, a realistic workflow is to build the work on the personal machine and switch to a high-performance machine in the show space. TD project files are compatible across machines, so separating the development machine from the show machine works fine in practice.
7.2 Standardizing project structure
A TD project that handles multiple elements tends to get complex, so having a standard structure for organizing it stabilizes the work.
- Section off with Container COMPs: divide into units like “Video,” “Audio,” “Lighting,” “Mapping,” and “Output,” with related OPs gathered inside each Container
- Bundle reusable subsystems into Base COMPs: e.g., “Audio Reactive Engine,” “Color Palette Generator”
- Place Null TOPs / Null CHOPs as pass-through points: this surfaces the impact range when you change the patch
- Naming conventions: give clear, function-tagged names like
videoOut_wall,videoOut_floor,dmx_bar1,dmx_bar2
7.3 Timeline-based progression management
A staging has a time axis of minutes to tens of minutes. There are several ways to manage this.
- Use Timer CHOP to measure show elapsed time and route that value into section transitions
- Use Animation COMP to write parameters as keyframes
- Cue system: provide a trigger that an operator can advance to the next scene manually during the show. MIDI footswitch, keyboard shortcuts, a separate remote, etc.
Whether to make the show fully pre-programmed or to leave room for an operator to intervene during the show depends on the character of the work. Loop-like staging fixed to music goes fully automatic; staging that includes audience interaction builds in manual intervention.
7.4 Operational considerations for the show
Finally, common problems and countermeasures in actual show operation.
- Rehearsal: before show day, run a full integrated rehearsal. Not individual elements (image, sound, lighting) — the full integrated state
- Backup: back up the entire project file set onto a USB stick. Consider a backup machine in case the show machine goes down
- Cable management: HDMI, Ethernet, DMX, and audio cables run many. Fix them with tape and separate them from audience pathways
- Crash response: confirm the recovery procedure in case TD crashes. Decide in advance how many minutes a project restart takes and what to do during that window
- Lighting and audio failsafes: as noted, verify how DMX Out CHOP behaves when stopped. Do the same for Audio Device Out
Running through these once in pre-show rehearsal lets you handle trouble on show day with composure.
8. Closing
This essay has laid out an implementation guide for taking work made in TouchDesigner and standing it up as physical-space staging that integrates multiple projectors, DMX lighting, and AI music. Combined with Installment #4’s survey of expression and method, the full sequence — from making work in TD to presenting it in physical space — is now visible.
Physical-space staging gives the audience a qualitatively different experience than work that lives inside the screen. The imagery spreads across the wall, opens up across the floor at the audience’s feet, runs over the surfaces of the solid primitives, while lighting draws lines through the space and music binds it all together. This experience is in territory that neither the export-an-mp4-from-editing-software approach nor work whose interactivity stays inside the screen can reach. As a final presentation for student work, the experience of building this kind of piece contributes substantially to the starting point of a media artist.
The next installment in this series will be an essay on shooting technique. The subject is the territory that neither generative-video AI nor real-time generative systems can replace — the act of turning a camera at the physical world and recording. Specifically, brain-play camerawork (compositional shooting in the manner of futa.729s), specialty shooting (the macro world via microscope lens, automated camera motion via Edelkrone, miniaturization via Tilt-Shift / Small Planet, light-trail work via long exposure), and slow-motion expression (the kind of time manipulation done by aaa_tsushi, plus the latest Premiere / After Effects workflows).
Across the series as a whole, the structure will work through the main lineages of moving-image production in order: AI generation (time-based, Installments #1–#3), media programming and physical-space staging (real-time, Installments #4–#5), and shooting technique (time-based, subsequent installments).