1.4.3
Released 2026-11-17
A small cleanup release. The transport_recording channel is gone from Aether In's Info CHOP.
Why it went
transport_recording was meant to read 1 while your DAW records. In practice it read 0 everywhere
it was tested. Plugin formats let a host report record state to an effect, but hosts are not
obliged to, and Ableton Live does not: it never sends the record flag in arrangement or session
record. A channel that works in some DAWs and silently reads 0 in others is worse than no channel,
so it is removed rather than left in place.
The rest of the transport group is untouched and still carries live values: transport_bpm,
transport_ppq, transport_bar_ppq, transport_playing, transport_looping,
transport_timesig_num and transport_timesig_denom. The Info DAT's transport row now reads
playing or stopped, with +loop when the loop is on.
If you need record state in TouchDesigner, your DAW's own remote control (OSC in Live, for example) can send it.
Upgrading
Replace the plugin and copy the new Aether In CHOP into your TouchDesigner plugin folder, the same as any previous update. Saved projects keep their settings.
Check one thing in your projects: anything that picks transport_recording by name loses it, and
anything that picks Info CHOP channels by position shifts by one from transport_looping onwards.
A transport_* pattern in a Select CHOP keeps working unchanged.
1.4.2
Released 2026-09-28
Mostly a latency release. Auto now reaches its lowest safe cushion within seconds instead of minutes, gives latency back on its own after a dropout, and sits a little lower than before: about 25 ms at 60 fps and 17 ms at 120 fps. Alongside that, a handful of fixes to how streams start, switch and recover.
Auto latency, rebuilt
In 1.4.0 and 1.4.1, Auto came down from its starting cushion slowly: it waited ten seconds, then lowered the cushion one small step every second. After loading a heavy project, when the load had pushed the cushion high, that could take a couple of minutes. And if the stream dropped audio while conditions were bad, Auto kept the raised cushion for the rest of the session, until you pressed the node's Reset.
Auto now follows the average length of TouchDesigner's frames and moves straight to the cushion that average needs. On my test project it reaches its minimum within about ten seconds of opening. After a frame rate change it settles again within seconds. A dropout still makes Auto a little more careful, but that extra cushion now fades back out on its own while the stream runs clean. Reset is no longer needed to get your latency back.
Settled values at 48 kHz with a 256-sample DAW buffer, measured on hardware:
| TD frame rate | 1.4.1 | 1.4.2 |
|---|---|---|
| 120 fps | 20.0 ms | 17.3 ms |
| 60 fps | 28.0 ms | 25.3 ms |
| 24 fps | 53.3 ms | 50.7 ms |
A bigger DAW buffer moves these up by the extra samples.
The trade: Auto now prefers low latency over never making a sound. When TouchDesigner hands back a lot of audio at once, after a project load or a long frame, Auto skips the backlog instead of slowly draining it, which can be heard as a tiny skip. The frame on which TouchDesigner changes its frame rate also stalls for a tenth of a second or more by itself, and a cushion this small cannot cover that, so a frame rate switch can still drop a moment of audio. In steady playback it does not: two hours at 60 fps on the test machine had no dropouts at all.
Smaller fixes
- Changing Stream Name switches straight away. The node used to wait about half a second in silence before trying the new name. It now picks it up on the same frame.
- Another program opening your stream no longer knocks the node off it. A second reader, such as a Python script, could clear the node's hold on the stream, and the plugin then read amber whenever the node paused. The node now takes the stream back within a second and warns you, naming the other program.
- Stream setup moved off your DAW's audio thread. Creating and removing the shared memory now happens outside audio processing, where it cannot hold up the DAW's audio.
- Bouncing or exporting no longer floods TouchDesigner. While the DAW renders offline, the plugin stops writing to the stream.
- A damaged stream list repairs itself. If a crash left the list behind the Stream Name menu broken, it is rebuilt the next time Aether starts, on Windows and macOS.
- macOS: reopening an existing stream name could fail, and only the first Aether instance after a restart might appear in the Stream Name menu. Fixed.
- Sturdier against bad data. The plugin and the node now check everything they read from shared memory against sane limits, so a corrupted or foreign segment can no longer silence a healthy stream.
- Leaner plugin. Aether used to write a second, undocumented copy of the audio in TouchDesigner's own shared memory format on every block. That copy is gone, so the plugin writes about a sixth of the data it did. Aether In reads the same stream as before.
Upgrading
Replace the plugin and copy the new Aether In CHOP into your TouchDesigner plugin folder, the same as any previous update. Saved projects keep their settings. Nodes on Auto settle to the new, lower values by themselves; nodes on Manual keep exactly the Prefill you set.
1.4.1
Released 2026-09-18
A bug fix release. Running more than one Aether under the same stream name could corrupt the audio, and in one case it could stop a stream entirely. Both cases are now caught and explained instead of failing quietly.
Two plugins on one stream name
Every Aether instance starts with the stream name default. If you put Aether on a second track
and left that name alone, both instances wrote into the same shared memory segment. Two writers on
a buffer built for one meant the reader was served a mix of the two, and the CHOP was discarding
and re-syncing roughly nineteen times a second to keep up.
The worse half was what happened next. Removing either instance released the segment for both, so the plugin you kept carried on as if it were streaming while nothing in TouchDesigner could open it. The only way out was reloading the plugin, and nothing on screen said so.
Aether now checks the name before it claims it. A second instance on a name that is already running refuses to start streaming and shows name taken in red where the status word usually sits. Give it its own name and it starts immediately. Remove the instance that holds the name and the one that was waiting picks it up within about a second, on its own.
Two Aether In CHOPs on one stream
The same rule applies on the TouchDesigner side, for the same reason: one stream carries a single read position, so a second node reading it takes audio away from the first rather than copying it. Before, the second node attached silently and both ended up with a fraction of the audio, and the first node lost its cushion at the moment the second one appeared.
A second Aether In on a stream that is already being read now shows a node warning naming the stream, and stays silent instead of interfering. The node that got there first is untouched. If you want one stream in several places, fan the node's output out with Select CHOPs, which is free.
This also covers a reader in another process, including the Python consumer in the repo.
Measuring latency
The plugin's Latency help tab said to compute latency as buffered / sample rate. That is wrong
and it reads high, sometimes several times high. buffered is the instantaneous fill level of the
ring: it moves either side of the cushion constantly by design, and it climbs to the whole ring
whenever the node is not cooking. The tab now points at prefill_target / sample rate, which is
the cushion itself and the number that means latency.
If you measured Aether's latency before and got a figure that looked too high, this is likely why.
Upgrading
Replace the plugin and copy the new Aether In CHOP into your TouchDesigner plugin folder, the same as any previous update. Nothing about latency behaviour changed in this release, so existing projects settle exactly where they did on 1.4.0. If you were already running two instances on one name, expect the second one to come back as name taken: that setup was never working, it just was not saying so.
1.4.0
Released 2026-09-16
Latency is now automatic, and it is lower than the old default on most machines.
Until now the Aether In CHOP held a fixed cushion of 2048 frames, about 43 ms at 48 kHz, and tuning it was your job. That number had to be conservative enough for a slow TouchDesigner frame rate, so everyone paid for the worst case whether they were in it or not.
The CHOP sizes its own cushion
There is a new Latency menu on Aether In, set to Auto by default. Auto measures what your machine actually does, the length of each TouchDesigner timeslice and the block size your DAW is running, and keeps the smallest cushion those two can support. It raises immediately when conditions get worse and gives latency back gradually once they hold. If the stream did drop audio while conditions were bad, Auto keeps the safer cushion for the rest of the session, and the node's Reset button returns it.
At 48 kHz, with a 128 to 256 sample DAW buffer:
| TouchDesigner frame rate | Auto settles at | was |
|---|---|---|
| 120 fps | about 20 ms | 43 ms |
| 60 fps | about 27 to 30 ms | 43 ms |
| 30 fps | about 44 ms | 43 ms |
| 24 fps | about 53 ms | 43 ms, and dropping frames |
Two things worth reading off that table. At 60 fps you get roughly a third of the latency back for doing nothing. At 24 fps Auto goes up, and that is the point: 2048 frames was never enough at 24 fps, and the stream had been quietly dropping audio there. Auto fixes that by spending latency where it is actually needed.
Auto needs Drift Correct on, which it is by default. With drift correction off there is no mechanism to move the buffer level smoothly, so the Latency menu falls back to your Prefill value and the Info DAT says so.
Your existing projects keep their settings
Opening an older .toe does not lower its cushion. Auto starts from whatever Prefill that node
already had and only comes down once it has evidence the machine can carry it. If you had raised
Prefill because your setup needed it, that headroom is where Auto begins, not something it
discards.
Pick Manual in the Latency menu to go back to a fixed Prefill exactly as before.
Prefill is now 512 to 8192
The old range was 256 to 16384, and both ends were fiction. The CHOP has always capped the cushion at half the ring, so everything above the halfway mark was silently ignored, and 256 frames is shorter than a single timeslice at any realistic frame rate, so it could never stream. The new range is what the node can actually deliver.
If you are choosing manually, the useful question is not milliseconds, it is the slowest frame rate a setting survives:
| Prefill | 44.1 kHz | 48 kHz | 96 kHz | holds down to (48 kHz) |
|---|---|---|---|---|
| 1024 | 23.2 ms | 21.3 ms | 10.7 ms | 94 fps |
| 2048 | 46.4 ms | 42.7 ms | 21.3 ms | 31 fps |
| 4096 | 92.9 ms | 85.3 ms | 42.7 ms | 13 fps |
| 8192 | 185.8 ms | 170.7 ms | 85.3 ms | 6 fps |
latency = Prefill / sample rate still holds in Manual mode.
A correction to earlier claims
Previous posts and the latency explainer said Aether could go "down to about 5 ms", and in places 11 ms. That was wrong, and I would rather say so than quietly delete it. Those figures came from reading the bottom of the Prefill table without asking what frame rate they require. Five milliseconds is 240 frames at 48 kHz, and a single timeslice at 60 fps is 800 frames, so that setting could never have streamed. The numbers in this release are measured, and they name the frame rate and buffer size they assume.
96 kHz at low frame rates
The audio ring is now 16384 frames instead of 8192. At 96 kHz one timeslice at 24 fps is 4000 frames, and the cushion is capped at half the ring, so that combination could not stream at any setting. It can now.
Under the hood
The plugin publishes its current block size in the shared memory segment so the CHOP can size the cushion exactly instead of guessing. This is an addition to the ring metadata, and both halves stay compatible: a new CHOP reading an older plugin falls back to a safe assumption, and an older CHOP ignores the field. You can update the plugin and the CHOP in either order, though running both at 1.4.0 is what gets you the exact figure.
Upgrading
Replace the plugin and copy the new Aether In CHOP into your TouchDesigner plugin folder, the same as any previous update. Existing projects keep their Prefill value, and the Latency menu arrives set to Auto.
1.3.2
Released 2026-09-02
Documentation and packaging only. The plugin, the CHOP and the wire format are byte-for-byte what 1.3.1 shipped, so there is no reason to update if you are already running it.
This release exists because the free demo is going out to people who have never seen Aether before, and the demo installer was handing them the paid version's documentation.
The demo now explains itself
The demo installer ships its own quickstart, and on macOS its own install screen. Both state the limit up front, in the same words the plugin's own footer uses:
- 5 minutes of stream time per plugin load
- the clock only runs while TouchDesigner is actually reading the stream, so idling is free
- when it ends the stream stops and your DAW audio keeps playing, untouched
- reload the plugin to reset it. No daily cap, no expiry date
The troubleshooting section answers "the stream stopped after a few minutes" first, because that is the question the demo is going to generate.
The paid installer's quickstart is unchanged.
Licence
Section 1 of the EULA is split into a purchased licence and an evaluation licence. The evaluation paragraph covers the demo: what it grants, the five-minute gate, and that it is not licensed for commercial production, public performance or released work. The purchase and withdrawal section is disapplied for it, since nothing is bought.
The bundled Aether In CHOP is identical in both flavors and is not time-limited.
1.3.0
Released 2026-09-01
Everything since 1.1.7. Version 1.2.0 was tagged but never published, so its changes are folded in here.
Two themes: your DAW's transport now reaches TouchDesigner alongside the audio, and Aether is far more honest about whether the connection is actually alive.
The DAW transport, in TouchDesigner
Aether already knew your host's transport. It now hands it over. Eight channels on the Aether In CHOP's Info CHOP:
transport_bpm, transport_ppq, transport_bar_ppq, transport_playing, transport_recording,
transport_looping, transport_timesig_num, transport_timesig_denom
The shared prefix is deliberate: one transport_* pattern in a Select CHOP grabs the whole group,
instead of naming eight channels by hand. The same facts appear as Info DAT rows.
This is what you build beat-synced work against. Tempo, bar position and play state come from the host itself, so visuals lock to the timeline rather than to an estimate from the audio.
Values are probed live at query time, so they report even when the node is not cooking. A transport block that has never been written reports zeros rather than stale numbers.
Stream Name is a live dropdown
The Stream Name parameter is now a menu built from the discovery registry, filtered by PID liveness, so
a DAW that has quit drops off the list on its own. It is still a string underneath, so typed names and
values restored from a saved .toe keep working exactly as before.
The plugin tells you when nothing is reading
The status readout has three states now instead of two:
| Dot | Label | Meaning |
|---|---|---|
| Green | streaming |
The stream is being written and something is draining it |
| Amber | no reader |
The stream is up, but data is piling up unread |
| Outline | inactive |
No stream at all |
Aether is a producer, and the protocol deliberately gives it no way to enumerate consumers (one reader per stream, by construction). The one signal it does have is whether the read cursor moves, so that is what the readout tracks. It waits about a second of no movement before flipping to amber, which tolerates roughly 30 to 60 missed TD cooks, so a file dialog or a .tox load will not make the word flicker.
This case used to show green, which was misleading: it said the plugin was fine while nothing downstream was listening.
Aether In cooks on demand
The Aether In CHOP now uses cookEveryFrameIfAsked rather than cookEveryFrame, so it cooks off
downstream demand like every built-in CHOP instead of running unconditionally.
Expect this, it is correct behaviour: if your TD timeline is paused, or the node is unwired and
nothing is viewing it, nothing asks it to cook, so nothing drains the stream, and the plugin correctly
reads no reader. That is the readout doing its job, not a bug. Wire the node into something (or open
a viewer on it) and it returns to green.
Resuming after a pause is better too. The buffered count is clamped to the ring capacity before the drop-oldest check, so a resume trims back to your Prefill setting and keeps streaming with a single discontinuity. Previously it drained the ring to empty and forced an underrun plus a prefill of silence.
Live connection health in the CHOP
A demand-driven node goes quiet exactly when you most want to confirm the DAW-to-TD hookup is healthy. So the info surfaces probe health when you query them instead of returning whatever the last cook cached, which means they still report while the node is not cooking.
Middle-click the node for the info popup: stream, attached or ended, producer, host process, PID, liveness, format, and unread against capacity.
Info DAT carries the same facts as rows: stream, attached (yes / no / stale), producer,
host_process, producer_pid, producer_alive, format, and unread/capacity.
Info CHOP gains a producer_alive channel from a live PID check, and buffered is now read live
and clamped to capacity.
The host process is resolved from the producer PID, so it names the executable that actually wrote the ring: "Ableton Live 12 Suite", a Python producer, whatever it happens to be. One caveat worth knowing: Bitwig sandboxes its plugins, so it reports Bitwig's plugin-host process rather than Bitwig Studio.
Also fixed
Shared memory create and destroy are now serialized. VST3 hosts call setProcessing and setActive
off the main thread, so a teardown could unmap the view while the idle timer was still running, and
the active flag could advertise a mapping that no longer existed. Each flag is now lowered before its
unmap, under a mutex that is never taken on the audio thread.
macOS bundles also report their real version now. The plug-in's Info.plist was being written before the build filled in the current version, so the macOS VST3 carried a stale 1.1.4 no matter which version you installed. Nothing about how it ran, but Finder's Get Info and any host that shows a plug-in version were reading the wrong number.
A free demo now exists
There is a separate free build with a 5 minute limit per session, for anyone who wants to confirm the hookup works on their machine before buying. It installs alongside the paid plugin under its own identity, so having both causes no conflict in your DAW, and uninstalling the demo leaves the paid install untouched. The limit applies only while TouchDesigner is actually reading the stream, and reloading the plugin resets it.