extensive input processing through plugins

[unguitar]

Hello,
moving from old-school rack processors to Audiomulch many years ago. After Audiomulch I tried many other applications to process my input but none has offered me the routing flexibility, deep midi control and stability I could have on that sadly abandoned software.
Since then I jumped through many similar applications with poor success, I like to support small developers but unfortunately I've not been lucky to find the right one so far.
I tested Live many years ago and it seemed that it wasn't able to deliver what I was looking for, I would like to give it another try now so I would like to hear from those who are using Live as a processing and routing environment.
I've installed Live 11 Lite on 13" Macbook Pro.
This is what I want to do:
Signal routing: split a single input signal to three different "racks". Each rack contains a different chain of plugins, each rack's output goes to main output.
Midi control: each rack has a specific midi cc setting its input volume.
Preset/scene management: a single preset should allow me to recall the state of all the plugins contained in the scene, without stopping the audio engine.
Many thanks for your time and help.

_luca formentini_
http://www.unguitar.com/
https://lucaformentini.bandcamp.com/

[Greenapples2019]

Hi, yes I believe all of those are possible using chains and macro variations, the manual and/or YouTube will show how.

[silentio246]

A few things come to my mind:

When using cpu-demanding plugins, you should distribute your plugins across different tracks/channels, in your case: three tracks, each with its rack.

For parallel processing the chain selector of a rack works as a on/off switch for the plugin, except that time based plugins will not stop immediately but fade out (delay,reverb), because the chain selector selects the plugin-input (pre), not the output. This could be useful.

Plugin states can be recalled as a standard vst preset by pgm and bank change within a midiclip on another track, which is routed to the plugin.

Track parameters and macro variations of the rack can be stored in dummy (audio) clips in the plugin tracks.

Track and plugin parameters can be stored in dummy (audio) clips by a Live device script called ClyphX (function is called snap action).

Input volume can be realized with the utility plugin in Live. Gain can be midi mapped.

By recalling a scene (with the containing clips in the tracks) you should be able to change the plugin/track states of each track.

Hope that helps.

[unguitar]

thank you so much @silentio246 this is what I needed to know before getting deeper.
all the best,
Luca