I’m new to TouchDesigner and I’m using TDAbleton + Ableton Live 12. I have a Looper device on a track and I want to control its buttons (Record, Overdub) from TouchDesigner using a 0/1 trigger I have already set up in TD.
In TD, I have set up the trigger: MediaPipe → Face Detector → Math + Logic, which outputs 1 when a human face is detected (camera sees face = 1, camera sees no face = 0).
I already have TouchDesigner connected to Ableton via TDAbleton, with the TDA Master in Ableton Live working. I’m using TDAbleton Package + Ableton Parameter CHOP to target: Track → Device → Parameter (Track1, Looper, State). However, although I see the ‘State’ parameter in TDAbleton, I cannot get the Looper buttons (Record / Overdub) to fire when the trigger goes to 1.
My goal: send a pulse from TouchDesigner to the Looper device buttons so that a trigger=1 correctly fires Record or Overdub, and a trigger=0 fires Clear
Any tips, examples, or simple Max for Live patches to achieve this would be greatly appreciated.
The trigger is sending a pulse, not a sustained value (0 → 1 → 0). I’m using a Trigger CHOP configured with Attack 0.05, Sustain 0, Release 0.05.
I’ve tested this trigger by launching clips in Ableton Live using a dedicated Max for Live device specifically designed for clip triggering, and that works as expected. However, in this case I’m trying to control other buttons on a return track, specifically the Looper device controls (Record, Overdub, Clear, and Play).
So I believe the pulse itself is working correctly - the clip triggering works as intended - but my goal is not to launch clips. I need to use this same pulse to directly trigger the Looper device buttons (Record, Overdub, Clear, Play), and I’m not sure what the correct approach is for controlling those device parameters from TouchDesigner.
In Ableton, I can MIDI-map those buttons and trigger them from a hardware controller, but I need them to respond to TouchDesigner, which is driving the interaction via face detection as part of an interactive project.
I would really appreciate any help or suggestions.
From your description it sounds like you need a small network that converts your pulse to a toggle that controls the abletonParameter values. There are multiple ways to do this but here’s a basic example…
thank you so much for sharing the example, I really appreciate it.
Your explanation makes a lot of sense - converting the pulse into a toggle seems like exactly what I was missing.
I’ll test the pulse_to_toggle.tox network in my setup and report back once I’ve tried it.