You host your plugin in a mini host. Send it buffer sizes of 8 or 1 to modulate the params. Ignore the host automation because that is 512 to 256 or what ever value. you add your own automation up to audio rate . Idea being modularization of plugins
The overhead of doing this will be huge.
What exactly are you trying to modulate at this rate? Usually you’d have several different “granularity” of modulations.
Are you planning to host 3rd party plugins or your own?
Only supported for my own plugins no third party it will help break down my tasks. I need and instrument rack and drum rack for the time being a effect rack will be a plus. I understand that 8 sample buffers is crazy for some plugins but it will only be supported and tested for my own stuff
Technically it’s possible to break your plugin processing in to 8 sample blocks and then prepare the Engine using a block size of 8 and call it with these chunks. But the. You have the overhead of the entire audio graph to run every 8 samples. Which won’t be insignificant, mainly due to function call.
But you could give it a go.
Personally I’d probably use something like Cmajor for the small blocks and then host that in TE.
Very tempting for cmajor I have to look into it. But my plugins are all mono synth voices. Creating everything I wanted in one app multiple instances on different keys and layering is what I was after and nesting layers would be cool too with midi effects. A variable buffer size of 256-512 for effects maybe because those are always on .
When code gets translated it’s kind of hard to debug . I have tried it with max msp type language to juce I didn’t understand the output code