I have two vocal mics coming into VSTL which I created stacks for. I have a Waves Vocal Rider, SSL Auto EQ and SSL Auto Dynamics for inserts. Everything works great.
Now I want to use (1) instance of Waves CLA Epic as my effects on the vocals. I can use the mixer as a traditional FX send to EPIC, however I can’t see anyway to select different presets for different songs as the plugin remains on whatever was selected last when you change songs. The VSTL window that Epic opens in lets me create Presets that I can use a pull down menu to access, I can’t figure out how to tie that into making changes for different songs.
I did some searching on past topics and it appears that automating parameters is what a lot of you are doing. Doing that in Epic would not be very fun for each song.
The only solution I can currently see is putting EPIC directly in the FX send of each stack, but that seems like a waste of resources.
Any ideas would be greatly appreciated.
Kevin
it is of course. You can combine STACK container slots, Mixer inserts/sends via MixGroupChannels, also mind the SongGroupChannel (that will be just active for the complete song)… and finally did you find the way to create global STACK? Dropdown menu: “PART > Create Global Part”. After clicking the new green “global part”, add the STACK there to make it global (however that wasn’t your question for now).
So again:
“simple” STACK will be PART based within the song
SongGroup mixer channel will be SONG based
Global STACKS and MixGroupChannels will remain
For FX preset change you can send MIDI messages right into the FX (CC, PGM,…) to modify it’s settings… (mind the QC in the FX upright corner)
I am afraid that’s not possible as that would require your FX plugin to accept program changes (or other MIDI CCs to switch presets). A brief research indicates that Waves plugins - as most plugins - don’t offer that option. So as this can’t be automated there’s nothing VST Live can do to circumvent this restriction.
Via QC’s maybe the parameters?
Or the multiple ways I explained above to use different instances of EPIC?
The Epic is quite complex - that’s why KdogginAK was hoping to find a way around extensive programming and using multiple instances. 
@KdogginAK , I were looking for some more options… found this and makes sense in terms of ProgramChange compared to param changes:
“Since CLA Epic is heavily delay/reverb based, abrupt snapshot changes may chop existing tails.”
@musicullum Discussed the fact a few times in the recent years that sharedLAYERs can only be used if terms of “the VSTi they include” (as shared VSTi).
My theoretical question, maybe this question will make sense to other users too:
do LAYERS has design-limitation that can’t allow using “empty” sharedLAYERs to handle/fire param-changes with their pre-defined knobs (the 8 param knobs, lower zone), maybe a decision to serve other more important aspects? Thank you for your short explanation in advance 
The SongGroupChannel is my solution. I’m using a Soundcraft UI24R as my audio device so I send all my backing tracks to separate channels on the Soundcraft. Nothing was being routed to the Song Group Channel so I put EPIC on it as an insert and used channel sends in the VSTL mixer on my vocal channels. Every song now stores the correct Preset in EPIC within the Song Group Channel. Thank-you fkalmus!
Have lovely gigs with VSTLive 
Yes they have. Just copy/paste, and if you always use it, “Layer/Save Default Layer” and if you use it in every Part, “Part/Save Default Part” and if you use such Part in every Song, “Song/Save Default Song”.
@musicullum thank you. however my question was rather theoretical. The approach as “Shared Layers” are clean, simple and flexible.
With the workarounds above won’t fully do the job. If touching a knob parameter, they won’t be replicated across involved songs/parts in case of any kind preset load… etc.
I strictly mean the low-zone, the 8pcs freely adjustable knobs to send “out” CC’s:
yes I know but that isn’t available, but you can use the other ones.
oh… have an idea… sitting down right now to write a VSTi (using JUCE libs) that will do this to me (the same as the 8pcs free-knobs) and can be used as a SharedLayer… cross your fingers to me
ps.: ehhhh, JUCE libs can query the host’s internal virtual MIDI ports… with the others it’s working already.
@KdogginAK I’m almost done with the VSTi (named it “MIDI Courier”), that contains 4 /or 8 free fuction buttons (1 unit / 2 unit high plugin GUI) . With that VSTi “MIDI Courier” it’s possible use in SharedLayers in any PARTS or MIDItracks
to send out MIDI#CC’s to change any parameters or an another fuction/device/plugin that can modify it’s settings via incoming MIDI#CC.
Example:
SharedLayerChorus: is sending CC values to change settings in EPIC
SharedLayerVerse: sending out differenc CC values to change settings in EPIC
There are two main limitations for now:
(0. I’m still working on the parameter list on mouse click, but will done it soon)
- I’m currently on mac, so have no idea how to test for Windows (also not jet made build for WIN in my life)
- Due to JUCE’s limitations - despite of asking the host for available MIDI O ports, I can only “ask” for ports visible by OS, but can’t list VSTLive built-in vMIDI cables) That one needs more time, not impossible, just needs time to write extra code for.
(3. as I’m not a vendor, - at least on mac - you need to run a single line command in Terminal to make an ad-hoc sign avoid mac gatekeeper to move plugin into trash 
)
Are you interested as soon as I finish it?
[FYI: @musicullum that was my goal originally with LAYER container’s bottom row custom knobs if they were able to be “shared” ]
I’m always willing to try something new, so yes, I’m interested. I’m using Windows so I can test it for you.
This forum focuses on VST Live - its features, faults and future.
It’s, however, not meant to discuss third party add-ons, however well-intentioned that may be.
So, with all due respect, please stay focused and help us to keep this place as tidy as it can be with all us musicians around. 
