TouchDesigner 2025.31550 — Mac version

The 2025 release introduced Point Operators—a whole new GPU-driven family for creating and modifying 3D data. That shift tells you where the platform is heading.

Visual logic, UI, and show control in one canvas

• Building both application logic and user interface inside a single visual environment.
• Projection mapping projects that need to talk to lighting desks, audio systems and show-control gear at the same time.
• Real-time 3D rendering and compositing, extended with your own custom operators when a project outgrows the built-in tools.
• Pulling in data from hardware—the Kinect Azure wrapper was bumped to 1.10.3, and the Orbbec SDK sits at 1.10.16 now.

Installs like a developer tool, not a Mac app

• It is a separate visual development platform, not a standard Mac app. The way it installs and launches reflects that.
• Intel Mac only, with macOS 10.14 as the floor. Apple Silicon machines run it through Rosetta or not at all.

Most TOPs now handle 3D textures and 2D arrays natively, so the GPU pipeline is far less fiddly than it used to be. If you are wiring up a live event or an interactive installation, that alone saves hours of patchwork.

M1 Macs run it through Rosetta translation

Does it run on an M1 Mac? Only through Rosetta. The current build is Intel-native, so Apple Silicon machines translate it on the fly. In practice that works fine for most projects, but if you are pushing 4K textures through twenty TOPs at once you will feel the overhead. Test your patch early, not ten minutes before doors.

Is this the same as the free version from the Derivative site? The build you have here is the full commercial release, activated and ready. No resolution cap, no watermark on your output, no restriction on commercial use. If you have only used the non-commercial edition before, the jump means your project files will open without the usual nag screens.

How steep is the learning curve? Coming from a node-based world like Blender's shader editor or Max/MSP helps. Coming from After Effects means unlearning layers and timelines. The first afternoon feels slow—you will spend it finding operators and learning which wire goes where. By day three most people can build a reactive visualiser that responds to audio input. The Discord and derivative.ca forums fill the gaps that the manual leaves.

Will it talk to my DMX rig or MIDI controller? Yes, out of the box. Art-Net, sACN, MIDI, OSC, serial—the CHOP family handles them all. If your lighting desk speaks a protocol, TouchDesigner probably already has an operator for it.

What the 2025 build changes day to day

The headline feature is Point Operators, and they matter even if you never touch POPs directly. Because POPs run on the GPU, 3D data flows stay on the card instead of shuttling back to the CPU. That makes particle systems and point-cloud manipulations snappier, especially when you chain several operations together.

The wider change is that most Texture Operators now support 3D textures and 2D arrays natively. Before 2025, working with volume data or layered textures meant workarounds—often involving multiple TOPs to fake what one operator now handles. If you do projection mapping across irregular surfaces, you can feed a depth map straight into a single TOP chain without the old slice-and-stitch routine.

The Orbbec SDK bump to 1.10.16 matters most if you use depth cameras on Intel Macs—that combination was spotty in earlier releases and is now properly supported. The Kinect Azure wrapper upgrade to 1.10.3 improves tracking reliability under mixed lighting, which anyone using body tracking for live performance will notice within the first hour.

A projection mapper's evening

Imagine a designer mapping three storeys of a Victorian warehouse for an all-night arts event. They arrive mid-afternoon with a MacBook Pro from 2019—Intel i9, plenty of RAM, running this build. The building has uneven brickwork, recessed windows and a last-minute scaffolding tower the organisers forgot to mention.

They pull a reference photo into the camera view, align the virtual projectors, then feed a Kinect Azure depth stream through a Point Operator to build a rough point cloud of the facade. The GPU crunch happens in real time. A CHOP chain listens to the audio engineer's MIDI clock so the projection pulses in time with the sound system. By evening the building breathes with the beat, and the designer spends the night tweaking a noise TOP to soften the edges around the scaffolding. No crash, no dropped frames at 1080p. The machine stays warm but never throttles.

Startup under ten seconds on Intel i7 with SSD

On Intel Macs from 2018 onward, the application feels responsive for most single-display setups. Startup is quick—under ten seconds from cold launch to an empty network editor on an i7 machine with an SSD. Loading complex projects with hundreds of operators takes longer, but once the network is in memory, playback stays smooth provided your GPU has the headroom. Integrated Intel graphics struggle above 1080p; a discrete Radeon or Vega card makes a real difference.

Stability has been solid through the 2025 cycle. Crashes, when they happen, tend to come from third-party hardware drivers rather than the application itself—a dodgy USB-to-DMX interface or a webcam driver that does not like being polled sixty times a second. The TNT activation method does not interfere with project saving, exporting, or network communication. Your files stay clean.

RAM usage is modest for what it does. A blank project sits around 300 MB. A full installation patch with video playback, depth sensing and Art-Net output to eight universes might reach 2 GB. If you are on an older machine with 8 GB of RAM, close your browser and Slack before launching—every megabyte counts when the GPU wants its share.

• Point Operators (POPs) added—GPU-based tools for creating and modifying 3D point data.
• Most TOPs now support 3D textures and 2D arrays natively.
• Orbbec SDK upgraded to version 1.10.16.

• macOS 10.14 or newer
• Intel processor