4.18.5
- Elements follow a renamed or moved source. Renaming the operator an element is bound to, or a COMP above it such as the project COMP, left every element showing errors until you renamed it back. Elements now follow the rename, the way PresetManager does, including in projects saved with an earlier version.
4.18.3
- MIDI and OSC learn and route on the very first message. A one-shot OSC trigger needed two presses to map, and after reopening a project the first message on a mapped address was dropped.
4.18.2
- Stop freezes a morph where it is. Stopped past the halfway point, a morph snapped to its target, and stopped after a Pause it jumped back to its start. Stop now leaves every value where it was.
- A track set to
looporpingpongkeeps looping when another track finishes in the same frame. With equal durations the whole morph used to end. Behaviour change. - Manual Blend moves Int, Toggle and Menu values too: preset A's below a factor of 0.5, preset B's from 0.5 up. They never moved before. Behaviour change.
- A track stored on its own curve keeps that curve's shape instead of taking the global curve's.
- Renaming ParameterMorpher no longer breaks a container. Export presets, Reset parameters, Clear parameters and the element API failed after the tool was renamed. String elements also lost the Look's label width after a rename.
- An imported container's preset buttons respond. After an import they could stay dead.
- An import takes the file's container name only when no other container uses it, so two containers no longer share a name. Behaviour change.
4.18.1
- The Preset Animator ships with no animation. It carried the channels and keys of an old demo animation, with cooking left on. Create Animation builds it on first use, as before.
- The element templates and the Preset Animator no longer carry values from a development session, and the embedded morph engine ships with no state from its last run. Nothing changes in use.
- Unused internal templates and leftover expression text are gone. Nothing changes in use.
4.18.0
The release audit. Items marked Behaviour change alter what an existing setup does, not only what a broken one does. Several come from the embedded PresetManager engine (4.4.0, see the changelog).
Moving, saving and wiring:
- Renaming, moving or copying the tool or a container no longer breaks it. Every Store, Randomize and Morph stopped behind a "nodes have moved" message, and a copy drove the original's parameters. A container now keeps its data on its own elements, straight after a rename or copy and when the project opens. Containers from earlier versions heal on the next open.
- Container callbacks fire again. Since 4.14.0,
onMorphingStart,onMorphingEndandonPresetCallnever ran. Containers saved that way are repaired when the project opens. The first argument is now the ElementsContainer itself, and a blank callbacks parameter is ignored. - The Transport input works. Beat, Bar and Sixteenths sync, per-element Quantize and the header's BPM display were all dead. Sync factors above 1 now step evenly.
Presets and morphing:
- An element's own Lock decides a preset morph when you recall it. The lock stored in the preset is kept for display only.
- An element's End Mode applies on preset recall. Behaviour change: with Multitrack on, an
element set to
looporpingpongwhen the preset was stored keeps looping after recall. - Deleting an element removes its values from every preset, and the confirm says how many. Each later Set or Morph of such a preset used to stop on a modal. Behaviour change: there is no keep option.
- Pause holds a running morph, and Stop fires
onMorphingEndwith the type that ended. Behaviour change: a container'sonMorphingEndnow also fires on Stop. - A morph with nothing to interpolate ends, and Set and Set Random during a morph stick.
- A deleted target is skipped and reported instead of opening a blocking dialog, and a hand-deleted target no longer stops every per-element auto cadence.
- A Filter that matches nothing skips only its own path, a copied tracked node no longer steals its tracking, and a path moved onto an invalid or already tracked node is refused.
- Random values reach the whole menu. A random StrMenu element gets one of its items instead of a number, and a Menu element reaches its whole list.
- An element's Distribution no longer changes the container's.
- A MIDI/OSC-mapped preset morphs on the timing you chose right after switching Global timing.
- Ctrl+click leaves locked elements alone, as a plain click does.
- An element's curve always morphs with its own shape, also when a script sets the curve and
stores or morphs in the same frame. New:
ClaimElementShape(settings, curve). - Changing the number of preset slots keeps an Alt+drag swap. Behaviour change.
- Rename presets in order keeps the lit preset and Blend A/B on the same presets, and a preset button's hover text describes the preset it triggers after an Alt+drag swap.
- The container's own Clear presets and Delete pulses work, asking first like the panel buttons. Behaviour change.
Elements:
- Reset puts a slider's range back everywhere: on the element, the slider you drag and the signal settings. Reset on a Menu or StrMenu element keeps one slot per item, so Randomize after Reset all reaches every item again.
- A value set right after creating an element sticks for sliders and toggles. A menu element still re-applies its original value, so wait 15 frames before setting a new menu element from a script. Behaviour change for scripts that relied on the revert.
- A node dropped on an element row adds elements, as a drop on the empty area does. Dragging one element onto another still reorders them. Behaviour change.
- Header > Channels labels every channel: one channel per element, named after it.
- Set random per element no longer raises after an element is deleted by hand.
- Element API fixes.
GetPresetsManager()returns the container's PresetManager on both element kinds, andEditCustomName(name)works. The non-interpolating element'sDistributionandSnapare removed. Behaviour change for scripts only. - Scripted preset slots must be whole numbers from 1 (
2.0still means slot 2). Behaviour change for scripts only: other values give a warning. ExportPresetManager()is removed. It raised every time. Behaviour change for scripts only: use the standalone PresetManager.HardSyncLFOs()works.- Importing a container file or dropping a node is faster with many elements.
Signals and patterns:
- Pattern signals step only when they should. Editing any signal setting no longer steps every pattern, expanding an editor no longer restarts them, and Manual Trigger steps a pattern once.
- Signals cost less per frame. Settings are parsed once when a signal changes; output is identical.
- A Timeline-synced Once holds its end value.
SetPwrand(sequence)without weights gives every value equal odds, and a mismatched count is refused with a message giving both counts.SetPwhite(0, 1)draws between the bounds instead of picking only 0 or 1.- Pattern sequences accept commas, semicolons or brackets, and a value that is not a number is refused with a message. Opening a pattern editor no longer pops a message for stored values it cannot play.
- The PresetAnimator keeps every key on one timeline, skips an unknown name in the presets sequence, accepts hyphens in names and skips a target deleted after the animation was made.
Files:
- Container import and export use UTF-8.
- A container file from before 4.0 imports and plays.
- The engine's Import JSON and Export JSON go through the container, so they no longer orphan every element.
- Importing a PresetSnap export is refused instead of wiping the embedded PresetManager, and a PresetManager or SceneLauncher file says why it cannot be imported.
- Preset files from before 3.2 morph and set after import, and overwriting a preset value reaches the morph.
- In the embedded ControlMapper, a
pickupmapping on a parameter outside its range engages at the end of the control's travel instead of never.
4.17.6
- Maintenance re-export. No change to how the component behaves.
4.17.5
- A menu parameter keeps its expression too. In 4.17.4 the menu element was the one style that still replaced an expression with a plain value, so the fix below did not actually reach it.
- Deleting an element leaves a driven parameter driven. Removing an element used to reset the parameter to a plain value, which threw away the expression or export that 4.17.4 had preserved. A parameter that really was a plain value still goes back to the value it had before the element.
4.17.4
- An element on a parameter that is already driven keeps it driven. Creating an element on a parameter carrying an expression or an export replaced it with a plain value, so whatever was driving that parameter stopped reaching it. The element now leaves the expression or the export in place. Driving the element still takes the parameter, which is what it is for. Mappings must be re-learned after updating.
4.17.3
- A reopened project keeps its morph targets. After saving a project and opening it again, a container had lost the list of parameters it morphs, although every element was still on the panel. Randomize did nothing, storing a preset reported that there were no associated parameters to make presets from, and adding one element after the reopen made the next Store capture that element alone. Containers now keep the list across a save and reopen, and a project already saved with the fault repairs itself the first time you open it in this version.
4.17.2
- An import no longer empties a container it cannot rebuild. Importing a container file whose source nodes have since been deleted destroyed the elements and left the container empty. The import now resolves every parameter the file refers to before it touches anything, and refuses the file naming what is missing. Nothing is destroyed.
- A file imported into a second container lands on that container. Element order and stored preset states were keyed to the container that exported them, so importing elsewhere drove the original's elements instead. Both now follow the elements just rebuilt, and an element outside the importing container is never written.
4.17.1
- MIDI and OSC reach your parameters from the sliders again. Mapping a knob or fader to a Float, Int or XYZ element moved the slider in the panel but never the parameter it controls, and learning it again did not help. The mapping now lands on the element itself, the way menus and toggles always did, so the knob, the slider and your parameter move together. The Blending slider had the same fault and is fixed as well.
- A parameter driven by an expression or an export can no longer be mapped. A mapping writes values, which would have replaced the expression for good. Clicking such a control in map mode now tells you which parameter is driven. This comes from the embedded ControlMapper, now 1.0.5.
4.17.0
- Page between Element Containers. Past two containers the stacked layout gets hard to work
in, so the header now carries a pager: a single-container view that shows one container at a
time at full height, stepped with the arrows, picked by name from the menu, or driven from the
Pageparameter. The arrows stop at the first and last container rather than wrapping, and both are mappable, so a MIDI button can flip pages during a show. - Paging only changes what you see. A container you have paged away from keeps morphing, keeps its timers and keeps answering its mapped controls.
Pages modeis off by default, so an existing project opens exactly as before. While it is off the arrows and the menu are greyed out: they are controls of that mode, not a way into it, so the toggle is the one way in.
4.15.2
- The Support link opens Patreon again. Six places in the component still pointed at a support page that no longer exists, including the one behind the component's own About panel.
4.15.1
- Setting a preset outright now records which preset was applied. Setting rather than morphing
never updated that record, so the Current Preset readout and the
onPresetCallcallback both kept naming the last preset you morphed to. Stepping a preset sequence never advanced the morph counter either. Both come from the shared PresetManager engine, so PresetManager 4.2.2 carries the same fix.
4.15.0
- An element carries a colour of its own. Right-click its chip to set one. The colour paints a
2 px stripe down the element and a 5 px chip, both sized from
Lib/Look(Elementstripewidth,Elementchipsize). Randomizing no longer overwrites an element's colour. - The sixteen colours on offer are derived from the current skin's accent, so the palette follows
Lib/Look.Skinand a new element seeds from it. The four neutrals (white, grey, dark, black) stay put, for marking something uncoloured on purpose. Lib/Look.Elementcolouringturns the whole feature off. Off also retires the picker, since the chip is the only way into it. Colours you have already stored survive the switch in either direction.- Three skins.
Lib/Look.Skinpicks between Carbon, Verdigris and Mono; Carbon is the default. The skin drives every widget colour in the panel, and the element colour palette with it. - The morph progress bar is the one under the presets, and only that one. The second bar is gone.
- A colour pick writes the exact palette value. It used to be quantised to 1/255, so a picked colour could land a step off the swatch you clicked.
- Fixed: the Readme button raised an error on every press on TransportMapper, PresetAnimator and PresetGrabber. All three open the repository page now.
- Fixed: the DIST and CURVE readouts mirror an attached PresetManager again.
4.14.2
- The help sheet opens centred on the monitor TouchDesigner is running on. It used to open at the mouse pointer, against a fixed display index, so on a two-monitor desk it landed under the cursor and often on the screen you were not working on. The window now finds TouchDesigner's own display every time it opens, and centres there.
4.14.1
Presets carry their own timing, and the signal row is rebuilt around controls that describe themselves.
- Each preset stores its own morph time, curve and distribution. Alongside the per-element values it already kept, a preset now records the global settings that were live when you stored it. With global timing on, recalling a preset runs on those stored values instead of borrowing the timing of whichever element happened to be first in the preset. Two presets can hold genuinely different global timings, and neither depends on element order. With global timing off, each element still uses its own stored time, exactly as before.
- Ctrl and right-click on a preset morphs on the global morph time instead of a fixed one second. The old gesture also wrote that 1 into your global morph time and left it there. That side effect is gone.
- Existing presets are safe in both directions. A preset stored by an older version keeps behaving exactly as it did, and a preset saved here still loads in an older version.
- A Timeline signal now opens on
Projectrather thanCustom.Durationis whatCustommeans, so it no longer appears until you pickCustom. A source you set toCustomyourself stays there. - Elements got lighter, and the row layout no longer shifts its columns as controls appear and disappear.
Breaking:
- A saved MIDI or OSC mapping on a signal row's source or sync control goes dormant. The source menu became three separate menus, one per source, and the sync controls moved one level down. Re-map the control once and it stays mapped.
Lib/ParametersUIandLib/SignalsUImerged intoLib/ElementUI. Both old names still resolve inCreateFromLibrary(), though neither is a listed item.
4.10.0
A signal can now run on the project timeline instead of on its own clock.
- New
Timelinesignal source. Instead of a wave or a pattern, the element plays an envelope over a length you set in seconds.Timelinemodepicks the shape:Loopramps and restarts,Bouncerises and falls,Onceruns a single pass and holds. - New
Timelinesyncing mode, available to every source. The signal's phase becomes a function of the project timeline position rather than an accumulating clock, so scrubbing the playhead scrubs the signal, and an offline render is frame exact. - A timeline signal chooses between two lengths and nothing else.
Projectspans the whole project range,Customuses the element's ownDurationin seconds. The four step and transport modes never applied to a timeline signal and are no longer offered for one. LFO and Pattern sources keep all six modes. Repetitionssets how many cycles fit across the project range, which is the unit that means something against a fixed length, where a rate in Hz does not.
4.8.1
Three fixes, all found by mapping real hardware to the signal controls.
- Deleting an element now stops its signal. The element went but the signal kept running for the rest of the session, holding the transport clock on. With an LFO source it also logged an error every frame; with a pattern source it was silent, which is why it went unnoticed. Deleting a whole container was already handled in 4.8.0.
- Mapping MIDI or OSC to a menu control now works. Learning a knob onto the signal source, the sync mode, the interpolation curve or the random distribution looked like it worked and then did nothing: the control moved internally while the visible dropdown and the value it feeds stayed put. Sliders were never affected.
- The signal enable checkbox can be mapped. Its mapping marker sat on a part of the control that carries no value, so a mapping to it had nothing to write.
4.8.0
The signal and pattern controls are back inside each element, so several elements can show their signals at once. They are now built when you enable a signal and removed when you disable it, which is what keeps the size saving: an element with no signal costs the same as it did in 4.7.x, and only the controls actually on screen exist.
- Every element with a signal shows its own editor. In expert mode each element carries a
sigcheckbox; ticking it opens that element's signal and pattern rows in place. Comparing two elements no longer means expanding one, reading it, then expanding the other. - Only what is visible is built. The sync-step field follows the syncing mode (free running builds none at all), and the pattern editor is whichever of the two families your pattern type uses. Switching either swaps one control rather than rebuilding the row.
- Disabling a signal frees the controls and keeps every value. Your source, wave, pattern type, rate, range, smoothing and each pattern type's own values live on the element's parameters, not in the controls, so re-enabling restores exactly what you had.
Sizes to plan a rig around. An element without a signal is 218 operators. Enabling one adds 106 on the default free-running sequence pattern and at most 140 in the heaviest combination, so twenty elements with every signal enabled land near 7,900 operators and nothing enabled stays where it is today. Fifty all-enabled would be around 19,000, which is large enough to slow the network editor: enable what you use.
Fixed in the same release: switching an element's signal source between LFO and Pattern reset the saved choice for the source you switched to, so an LFO set to Square came back as Sine. It now keeps both.
Your existing projects carry forward. No parameter or stored data changed.
4.7.1
Five fixes to the shared signals inspector introduced in 4.7.0.
- The inspector cut off its own pattern editor. It ignored the height the container gave it, so its controls rendered about three times too tall and the pattern section sat below the fold with no way to scroll to it. It also stopped short of the right edge instead of filling the width. Both are corrected, so the whole editor is visible.
- Retargeting left the menus reading the previous element. Expanding a second element moved the inspector, but the signal source, LFO and pattern menus still showed the first element's choices. They now follow the element being shown, including on the first retarget in a newly created container.
- Deleting the element the inspector was showing left it pointing at nothing, which raised errors across the panel until another element was expanded.
- The two sequence fields did not commit what you typed. A sequence entered in the inspector was displayed but never reached the element, so playback kept the previous values.
- An element's interpolation curve and random distribution menus did not follow their parameter. Changing either by script, by a MIDI or OSC mapping, or through a preset left the on-screen menu showing the old choice while the element morphed with the new one.
No parameters or stored data changed, so projects saved on 4.7.0 carry forward untouched.
4.7.0
The signal and pattern controls are no longer built into every element. They now live in one inspector docked at the bottom of the container, and an element's expand toggle chooses which element it edits. Every interpolatable element drops from 399 operators to 202, and the component from 4455 to 4270, so a project with twenty elements saves roughly 3,900 operators.
Your existing projects carry forward. The parameters holding your signal and pattern setup have not moved or changed, so nothing needs re-entering. The one difference in use is that two elements' signals can no longer be shown at the same time, since there is a single inspector rather than one per element.
The nine pattern scripting methods (SetPseq through SetPbrown) used to set values by
driving the on-screen widgets. They now write the element's stored pattern data directly, so
they keep working with the controls moved, and each pattern type is given the number of values
it actually takes.
4.6.1
- The pattern editor follows the pattern type again. Changing an element's pattern type stopped switching the editor below it, so picking a type like Pwhite still showed the sequence field belonging to the previous type, and any value edited in that state was saved into the previous type's slot. Playback was never affected: the signal always played the type you selected. Introduced in 4.6.0, where moving the signal engines into one shared service removed the part that told the editor which type was selected.
- If you edited a pattern on 4.6.0, check the values on each type, since an edit made after switching type may have landed on the wrong one.
4.6.0
- Signals now run from one shared service instead of a copy inside every element. A project with twenty elements used to run twenty signal engines; there is now a single service in the component that elements feed. Every element drops from 441 operators to 399, and the component from 4574 to 4455.
- Your existing projects carry forward. The parameters holding your signal setup (source, LFO, pattern, frequency, sync mode, range, smoothing) have not moved or changed, the controls behave exactly as before, and nothing needs re-entering. With no signal running the service clock stays stopped, so idle cost is unchanged.
4.5.2
- Internal quality work only. Nothing in the component behaves differently and your projects are unaffected.
4.5.1
- The header map icon is a crosshairs, replacing the MIDI DIN plug it had inherited. One icon covers both protocols, so a MIDI connector was the wrong picture.
- Fixes MIDI input being ignored. The mapping service had stopped following the
component's
MIDIparameter, so a wired MIDI CHOP never reached it and nothing could be learned or routed. OSC was unaffected.
4.5.0: the MIDI/OSC mapping rebuild (breaking)
Version 4.5.0 replaces the MIDI/OSC mapping subsystem outright. Mappings made in earlier versions are not carried forward, and eight parameters were retired, so any mappings you already have need to be made again.
What changes for you:
- One map mode, not two. The separate MIDI and OSC controls are now a single Map icon in the header, shown whenever either a MIDI or an OSC input is wired on the Inputs page. Click it, click any control, then move a fader, knob or key to bind it. Both protocols share one list.
- One mapping list. The
Mappingspage is now Manage Mappings and Clear Mappings, replacing four pulses split across MIDI and OSC sections plus two location toggles. The editor shows every mapping in one table. - Per-mapping range. Each mapping carries its own Min and Max, editable in the list. Previously all MIDI mappings shared one global input range.
- Soft takeover. Each mapping can be set to
pickup, which waits until the incoming control reaches the parameter's current value before taking over, instead of jumping to wherever the fader happens to sit.jumpis the default and matches the old behaviour. - Dead mappings are visible. If a mapped control is renamed or removed, the row is marked
(missing)in the list rather than silently doing nothing, and can be cleared with Prune Dead Mappings. - Retired parameters:
Managemidimappings,Manageoscmappings,Clearmidimappings,Clearoscmappings,Togglelocationmidi,Togglelocationosc, plus the two per-protocol section headers on the Mappings page.
Anything can now be a mapping target, not just the built-in controls: a mapping stores a control and a parameter name, so any custom parameter can be driven.
The rebuild is also most of why the component dropped from 8853 to 4574 operators. The old system gave every mappable widget its own learn overlay, so an interpolatable element cost 572 operators in overlays alone; it is now one shared service plus a single marker operator per control.