Seems like most sequencers are working now in experimental. Please report any sequencer plugins that do not step forward correctly.
1 Like
Tested this last night and Reaktor and Maschine seem to be working well, Ill be testing more in the next few days/weeks
1 Like
I’m trying to use surge xt as a reference for audioreactive in touchdesigner and I’m not succeeding, could you help me?
working on windows smoothly
however, mac version for intel quite glitchy and drops the FPS a lot on an empty image movie file scene. the window of the plugin gets scaled down and to fix it you need to change back and forth color profiles of the system settings → displays
(my mac specs are 16 GB 2.9 GHz Quad-Core Intel Core i7 MacBook Pro (15-inch, 2017) ) running latest touchdesigner builds.
Thanks for this thread and wish you all lovely armageddon 
Hi,
I’m trying to get sound out of my VST collection, with no success. HyPolyFree (in the vstHost container from the Palette) is working fine. The Audiovst CHOP outputs no sound at all. It’s not a setup misunderstanding, I know how to play audio and MIDI under TD. I’m running Sonoma on a Mac Silicon.
Thx for your help 
When you press a keyboard key in the HyPolyFree do you see an audio wave generated in the visual graph of the vstCHOP? If you see the visual graph of the VstCHOP generating audio - you will still need to append an AudioDeviceOut CHOP to hear anything.
Everything is working fine within the vstHost container. Now if I change the plugin, let say to load Arturia’s Analog Lab, there’s no sound at all. If I build a small network like this : midiin > audiovst > audiodevout, I can load any VST3 I want, display its GUI, but can’t output any sound. I’m probably missing something.
Can you post an example file with HY or Arturia and I will have a look?
Well, that’s very strange because the VST CHOP suddenly works fine. I haven’t touched nothing at all, neither OS or TD. It may be a mistake on my side, but I don’t know where. Anyway, I can now play my synths inside TD ! Thanks for your help.
I have been using Arturia Pigments in TD, and getting very bad performance.
Even one instance seems to drop the frame rate to 14fps, even on a high-spec Win 11 PC.
On the same machine I can run 5 instances of Pigments in Ableton and use only 14% of CPU.
What’s causing the difference? Any way to optimise?
Arturia Pigments has a lot of exposed parameters, so make sure you don’t have them all loaded, that will slow things down a lot. That means disabling the “Regular Parameters” toggle.
Thanks for this!
Ok, switched everything so regular parameters are off.
‘Clear learned parameters’ helped.
Got it back up to 60 fps with one pigments and 2 juno 6’s.
But srtill having issues. I added another pigments and it drops to 50fps.
Any other optimising thoughts?
It feels like it’s a gui issue.
Also, was trying to use different pigments presets, but looks like the easiest route is to have multiple instances of the vat chop with diff states, and then bypass the ones I’m not using.
Is there a better way? Capture all the parameter data, save and then bind to parameters somehow?
Done some more testing. Thought I would share what worked.
Best way I found to use Pigments (and possibly other parameter-heavy VST synths) is to use the bypass flags.
It does seem to be the huge amount of parameters that causes the performance issue.
Here’s what I did.
In VST tab:
Load Plugin State on Start: ON
Learn Parameters: ON
Regular Parameters: OFF
Read Only Parameters: OFF
Opened the synth GUI and loaded a preset. Got it how I wanted it.
Hit ‘Clear Learned Parameters’
At this point, you have the synth state saved, but no GUI pars when you go Plugin Tab.
If you want some pars to play with, go back into the plugin GUI and change just the pars you want to expose.
The main issue is that if you change a synth preset from a library, you’ll expose every preset in the synth, and the chop becomes really expensive.
To save multiple synth presets, I made an Audio VST chop for each state and then used this bypass handler to turn them on and off.
Edit: The issue is 100% not hitting ‘Clear Learned Parameters’ after you’ve loaded a preset from the library. When you load a preset, it exposes every parameter in the synth and TD hates it.